Version: (using KDE 4.2.96) OS: Linux Installed from: SuSE RPMs first, i'm not sure, if it is realy a bug of plasma. then i start the pc (and kde) some programms need some minutes to start, for example konqueror (after konqueror has startet it freezes again for some minutes then typing the first letter in the adressbar) and kmail, other programms start normal like konsole and firefox. then killing the x-server after the first start of kde and restart kde the programms start normal (this way is much faster as waiting) i think, the bug is in plasma, because the arrow to expand systemtray comes then konqueror works normal. i use opensuse 11.1 and kde 4.2.96
Created attachment 35513 [details] the sytemtray, before the programms work normal
Created attachment 35514 [details] the sytemtray, then everything is normal
Is Kmail always executed on the start of the session ? Can you disable it just for testing ? Thanks
no, i start it manually
Can you try this: - After Plasma/the KDE session starts, launch Konsole, type "kquitapp plasma-desktop" and press Return. Plasma should close. Now you can try to launch some application and see what happens. Also, - when this problem appeared? - what is the cpu usage during the startup ? (is some application using too much CPU? you can find this using the shell program "top" or just "ksysguard") Thanks
well, this doesn't change anything, the cpu usage is low
- When this behaviour started? Thanks
i'm not sure, i think it started after the update from 4.3beta1 to 4.3beta2
I've the same behaviour since some weeks, maybe more than one month... I've never reported because I can understand some slow behaviour on a "trunk" version :-) kde starts, plasma starts, I launch some apps (with krunner)... the systemtray is empty, konqueror or firefox (started with krunner) needs some time... after a bit the systemtray apps are all visible, and all software starts fine. after the desktop, plasmoids and panel have been started, the system needs from 30 to 60 seconds to be really usable (CPU E8500 with 4Gb of RAM). bye P.s: I start kmail manually too (because it doesn't start automatically :-( ).
Mh.. It also takes me some seconds to get an "usable system", but not that much, even with a less powerful computer (Celeron1.8ghz,1Gbram) Some questions: - Does the KSplash screen takes a lot of time ? (here it takes some time; may be you are not spending that much time on KSplash but in the initialization later ) - Between Plasma starts rendering and the applications you launched start to be responsible, what other symptoms do you have? (you said there was no CPU full usage, but, what about disk activity, some other programs loading in background, maybe Nepumuk/strigi indexing files) ?
i have a pentium m 1,5ghz, 1gb ram - not really fast, but i think that should be enough. it is really slow, in the time to get a usable system, i normaly can start the pc about 3 times. -ksplash needs some time, but not much more than in kde3 -the disk activity is also low, strigi is enabled, but it was the same when disabled.
On my system the kspash needs about 20-30 seconds. I've got no strigi/nepomuk/akonadi enabled and the disk activity seems low.
Any plasmoids that might require internet access? is there a possibility to check with a clean user account ? (creating a new account just for testing)?
i don't think, that one of the plasmoids require internet access. using a clean user account doesn't change anything
Since today kmail has been keep starting on startup yeah... one bug less... anyway, I've just re-tested with a clean user account. the splash screen needs 10 seconds to displays all 5 icons, and other 20 seconds to disappear (30 seconds in total), but after the system is quite reactive. instead, my user account needs some more time to loads all the applications and plasmoids (only one is connected to the network: microblogging). if I logout and re-login with my user account, the splash needs only 10 seconds and all apps starts almost immediatly.
Mh... that happens because all the KDE libs are already cached/loaded in memory I think. so you should test everycase after starting/rebooting the PC.
that's not all, as i write in my first post, it is much faster to get an usable system when i kill the x-server after the first startup of kde (after the reboot) and restart it than waiting.
same with kde 4.2.98
Under kde 4.3.0, i tested some programms (dolphin, kmail, konsole, konqueror) after startup, konqueror is still extreme slow. The other programms do not really start fast, but much faster than konqueror it still needs some minutes.
Do you have the loopback device enabled? ("lo") ? Thanks
Yes, it is enabled
i still have the problem with kde 4.3.1
same problem here. it takes about 1-2 minutes from kdm to a reactive system. disk activity is high, of course, it's loading a lot of libraries. but should/must kde load all/so many libs at startup? archlinux: kde 4.3.1, qt 4.5.2, kernel 2.6.30.5 @all with same problems: please vote!
with kde 4.3.3 it is ok now
@FiNeX: can you confirm this too ? Thanks
KDE 4.3.4 and trunk seems quite better than 4 months ago :-) I think we could consider this bug gone.
Bye bye report...