More stuff on the "KDE is slow to start up" front...

I just noticed that the notification system plasmoid is separate from the system tray. On a whim I removed it from my desktop... Now I no longer get pretty Plasma notifications for everything, but KDE's startup time is shorter by about 5 seconds (when already loaded into RAM). Not bad, considering no essential functionality has been lost.

This is with KDE 4.5.5 on SalixOS 13.37 (compatible with Slackware 13.37), 32 bit. Hardware is an EeePC 1005HAB, with a bog standard 160GB SATA HDD and the dreaded Intel 945 shared memory graphics controller.

Can anyone confirm this on a newer version of KDE? How about on other low-spec hardware?

> Can anyone confirm this on a newer version of KDE?
Confirmed. (w.r.t 4.8.2)
Apparently, that was the cause of the few seconds freeze I was experiencing at startup.

This is extremely unusual behaviour.
Are you using any non-standard applets on your desktops? (My guess is that the Notification applet registers a global interface, but as Plasma is being slow the applet is slow at responding, slowing the starting applications down)

No, no non-standard applets whatsoever; everything is as per the defaults.

I do have folder view configuration instead of the default desktops and a script set to run at startup. But they shouldn't interfere with notifications in any way.

One possible reason this happens for me could be because 2 notifications(one showing the starting of yakuake and another for a bug in the audio stack) are shown regularly at start.

Btw, is there a way to defer the launch of the notification system to..say..1 min afterwards ?

The notification system launches as part of Plasma, so it probably cannot be delayed. I would recommend filing a bug at bugs.kde.org, as this sort of slow down in startup should not occur.

... And funnily enough I haven't been able to reproduce this. Some weird quirk of the code, I guess. Or maybe my clock was on the fritze. *sigh* Sorry for the red herring.

Heads up to anyone who reads this thread, my problem was with the network daemon...not really the notification system, as I had assumed on the basis of simple inferences.