On Thu May 1 2008 14:33:47 andy wrote: > Output of ps vax, as suggested: <snip> > 4023 ? Sl 40:36 43190 208 1168611 246932 24.6 > /usr/bin/xfdesktop --sm-client-id 11c0a80128000117172206900000088 <snip> > 4041 ? S 34:10 35998 31 1132264 245552 24.4 > /usr/lib/xfce4/panel-plugins/xfce4-menu-plugin socket_id 23068711
Those two seem to be the source of your VM problem. Maybe an XFCE wizard can tell you why they are using so much VM. I have no idea. > It doesn't seem kosher to have to reboot a GNU/Linux system to recover > full responsivity. That sounds like a MS Windows solution ... or am I > being just too optimistic? > > How do I address problems with a kbuildsycoca and iceape-bin? kbuildsycoca normally only runs for several seconds after changing something in KDE. If it's running non-stop you have a problem. It's probably safe just to kill kbuildsycoca but a reboot would be kinder. As for iceape-bin, it shouldn't be using that much CPU except in very short bursts. Maybe you have a bad plugin, or maybe it's a bad interaction with the multiple windowing systems. You have two gdm's, and xfce desktop, and a lot of KDE running. You have several heavy applications running. That's way more than will fit comfortably in a gig of RAM. If you can't quickly find a solution to those two xfce memory hogs I would suggest dropping xfce and gdm, and using kdm. You're not saving anything with xfce as you're apps are so heavily KDE. --Mike Bird -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
