On Thursday 13 March 2003 05:43 am, Graham Smith wrote:
On Thu, 13 Mar 2003 19:51, Konstantinos Georgokitsos wrote:
I think the main culprit is Konqueror. Opening an instance can leave up to 4 kdeinit processes behind. As I was also running KNewsTicker, I assume it uses some part of the Konqueror to fetch the news feeds regularly, so that might leave a lot of processes running... I now removed it.
I deleted the contents of temp, but didn't see any change in behaviour.
I renamed .kde and of course session restore is much faster now. I see that I had a lot of things customized. I now customized only the basic font so I can see Greek, and put a nice Wallpaper. Much more trimmed down. Maybe better this way. However the behaviour of Konqueror has not changed. It still leaves running processes behind after closing. A bug?
Kostas
I hate to do the "me too" thing, but I'm having the same problem with kdeinit and it is definately associated with Konqueror. So you are not alone.
First off - noticed the mention of kNewsticker, I had some wierd behaviours that I found were associated w/ this program. (I can't remember just what they were but I'd suggest trying to do without it for awhile and see if that helps. Second - I leave a few web sites open in konq all the time, a couple of them use the nsplugin viewer and in at least one of them the viewer will use 20 to 30% of my cpu time (for no reason, I don't even have the window open). Every time I log back in I wait a couple of minutes for things to settle down, then, I run kdeSystemGuard, click on user % acouple of times to find out what is using cpu time on my freshly logged in machine, and usually end up killing 1 instance of nspluginviewer which is wasting cpu cycles. third - occasionally I've tried to start an instance of konq (or another prog) but no window opens, If you don't kill these somehow then they re-start when you log back in. You could try closing all of your active applets and programs (if they ask if you want to start them the next time you log in choose yes if thats what you want. Then run kdeSystemGuard and kill all remaining insytances of konqueror and nspluginviewer. There are alot of other things you can kill as well but Its better to work through things slowly. Log out (choose save settings if available, my setup saves settings every time I log out), then log back in and use top or kdeSystemGuard to see whats going on. Hope that helps -- dh Don't shop at GoogleGear.com!