GNOME Bugzilla – Bug 101858
performance problem when using home dir as desktop
Last modified: 2004-12-22 21:47:04 UTC
I have found this bug both in the version shipped with RH8 and the 2.1.3. If I set nautilus to use my home dir as the desktop I can't drag the windows smoothly anymore. Setting nautils back to the standard desktop doesn't fix the problem: I must logout, remove the gconf directories under my home and start gnome again.
Possible dupe of bug 105105. Do you have much data in your home dir that might be slowing down?
Yes, probably the bug is the same: it doesn't appear if I keep less items on the desktop.
*** This bug has been marked as a duplicate of 105105 ***
I discovered that my problem isn't really related the to the number of items on the desktop, but on the background settings. If I choose a solid color, there is no performance issue at all, even with lots of folders. If I choose an image or even only a gradient everythings slows down. Even 2.2 has the same problem.
So are you saying that using $HOME had nothing to do with it? If not, and setting $HOME as desktop has a compound effect on using a big background that might still be a bug.
I'm saying that either if I set home as desktop or not, and I have a wallpaper or a gradient background, the things slow down. With 2.0.x (RedHat 8) having less items on the desktop fixed the thing, but with the 2.2 version (Garnome) this doesn't work anymore, so I suppose it's background's fault. Infact the problem does not occur with a solid color background. By the way, I have 12 folders and 5 launchers on the desktop, 13000 items and 5 Gb in the home dir. I also found that removing the gconf directories is a too drastic solution: setting nautilus not to draw the desktop and then settig it back to default is sufficent on 2.0; on 2.2 I only need to switch the background to a flat color.
ah, Ok. Well I'll leave it resloved unless you want to re-open. I'm not sure if it a bug. Any chance you are using the latest NVIDIA drivers?
I am using them. I guess it's NVIDIA's fault then ...
NVIDIA drivers fault confirmed: switching back to version 3123 fix everything