You are not logged in.
I've a strange problem which I suspect may have something to do with the recent update of kdebase. After a while logged in, all KDE applications take around five or so minutes to start up. No other programs suffer this problem.
They seem to be blocking. When the window eventually appears it seems to work as normal. I'm not getting any error messages on the console. In fact I'm not getting anything at all - am I correct in saying that the likes of kwrite normally throw lots of messages to stderr?
I've tried a full KDE reinstall and flushing out my .kde directory, but with no luck.
Offline
I have the same problem, since the last kdebase update!
Offline
looks like tpowa is hard at work on it look here http://bbs.archlinux.org/viewtopic.php?t=12947
Offline
Are you running hal && dbus? They should be started in order for KDE to work.
:: / my web presence
Offline
Are you running hal && dbus? They should be started in order for KDE to work.
Yes
Offline
[shaurz@proxima ~]$ hostname
proxima
[shaurz@proxima ~]$ cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
127.0.0.1 proxima proxima
So far the problem hasn't happened again. There's a new build of kdebase so I'll check that out.
Offline
I am having exactly the same problem Starting programs like kwrite takes even tens of minutes or they won't start at all (k3b). This seems to get worse when I keep KDE on overnight or running 24 h a day for a couple of days. When I shutdown KDE and restart it, on startup I instantly get k3b popping up fast.
Offline
The only time I've experienced something like that before was when I tried to follow the kde guide to improve performance and decrease resource usage, I first blamed the fonts (since I just installed some new and just read many fonts would slow down the system, but I started wondering I had more fonts on other distros before with no slowdown) but I later found out it happened only if I had the klipper applet running - if I ran the klipper in system tray instead of the applet, everything worked fine. I have no idea why - I measured it took about 1:30 minutes from the kde splash disappeared until the desktop worked (it just froze).
Offline
I also have clipper running at KDE bar - got to check how things run without it..... About the previous problem: I found out that I have one extra problem as part of it - when programs don't start up and I try to restart KDE, it just stays at the "Initializing system services" - part in splash screen. Then I must kill X using CTRL-ALT and backspace. Then only 'init 1' helps and after that KDE starts up.
Offline
I have tried now for 33 hours to run KDE without Klipper and seems to work nicely. KDE is still repsonsive.
Offline
I have tried now for 33 hours to run KDE without Klipper and seems to work nicely. KDE is still repsonsive.
WOW what a difference, feels like a new machine thanks
Offline
Now I have been using blackbox for a while and kde apps again opened up quite slowly - I have portmap, fam, dbus and hal at rc.conf. I spotted from top command that fam uses 100% of cpu cycles. I shut it down and now all the programs I tried to open started up at once in very fast pace. I also found this: http://linux.derkeiler.com/Mailing-List … /4185.html - Debian users have had the same problem with fam taking all cpu cycles.
Offline