December 17, 2017, 01:41:13 PM

News : LinuxSolved.com Linux Help Community Forum..


Author Topic: SLED 10 64 Bit (With XGL Enabled) Problem with KDE 3.5  (Read 2640 times)

Offline mabus

  • New Member
  • Posts: 2
SLED 10 64 Bit (With XGL Enabled) Problem with KDE 3.5
« on: November 02, 2006, 10:54:25 PM »
I'm using SLED 10 64 bit, with XGL enabled on KDE.


the problem here is that , surprisingly, my KDE changed it's look.. It happened after I rebooted. I used to have this KDE desktop setup with my chosen wallpaper, now upon loading, it shows that one.. after a while, the desktop shifts . the wallpaper goes back to the default, the theme for icons changed, and when I do a right click on the desktop, it lost the set of options ( the one that has refersh). Now, when I lick on home (the desktop icon), it'll open using nautilus, not konqueror anymore. and another thing, when I right click, and choose to change wallpaper, the menu is different from the ones in KDE.


so what's wrong here?  I was able to fix this problem by deleting the old config files, and logging back in, thus thesame as creating a new setting. But I'd like to know what seems to be the cause of the problem here so I can prevent it.

Any solutions or comments are more than welcome.

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
SLED 10 64 Bit (With XGL Enabled) Problem with KDE 3.5
« Reply #1 on: November 07, 2006, 01:59:59 PM »
May be an unclean shutdown was the reason for currupted config file thus loading default vaules.

Offline mabus

  • New Member
  • Posts: 2
SLED 10 64 Bit (With XGL Enabled) Problem with KDE 3.5
« Reply #2 on: November 09, 2006, 07:50:42 AM »
well.. that can be one, but I rarely shut my PC down, and it happened while it was still on. and besides, my default was KDE. There's a big chance though that this would have happened on that compiz.conf file that you create inside kde's autostart folder.

I was able to solve this, by simply reverting the configs to the default, simply making it run as  if it was the first run.

However, I still wanna know what caused this problem, so I can prevent it. The funny thing is, it only happens on my shell, the other accounts don't get that problem.hehehe.. weird