On KDE's start I see a background and a panel after a second or two. Panel appears with cpu/memory monitoring plasmoids and menu button. Then I'm waiting for nothing during 10 seconds (cpu isn't loaded at these period), and then sys tray starts to fill in with it contents, as well as assigned startup script also starts to execute (and all these ops also takes about a couple of seconds).

So, what does the system do during those sh.. seconds??

P.S. Any other tried DE starts without delay.

Unusual. Are you able to monitor what the system is doing from another computer to see if it is waiting on Nepomuk/Akonadi or reading data from disk?

I will have an opportunity to ssh to this computer later. ATM I'm almost sure some KDE part wants NetworkManager, but I haven't it installed at all. The reason of the guess is a systemd journal fragment shown below: there are plenty failed networkmanager activating attempts, but one of the attempts seems to wait for activating during ~10 seconds:

фев 08 15:36:29 jazz dbus[307]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or
фев 08 15:36:29 jazz dbus-daemon[307]: dbus[307]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load
фев 08 15:36:29 jazz dbus-daemon[307]: dbus[307]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
фев 08 15:36:29 jazz dbus-daemon[307]: dbus[307]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load
фев 08 15:36:40 jazz dbus-daemon[307]: dbus[307]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
фев 08 15:36:40 jazz dbus[307]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
фев 08 15:36:40 jazz dbus-daemon[307]: dbus[307]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load

Can it help to detect networkmanager-hungry boy?

D-Bus activation certainly could explain part of the delay. Try disabling the "Network Management" applet if present. It could also be Solid.

bcooksley wrote:D-Bus activation certainly could explain part of the delay. Try disabling the "Network Management" applet if present. It could also be Solid.

I have Nepomuk disabled, but have tried with enabled one with the same effect.
I'm not aware of Solid ans where I can look for information related to solid - will google...

And I haven't found any traces of Network Management applet - have not added it to somewhere.

Solid is the KDE Hardware Information abstraction library - it interfaces with UDev and UDisks among other services to retrieve information on your hardware - and NetworkManager for information about your network. You should ensure that Solid is built with NTrack support if you are not using NetworkManager.

OK, I have disabled dhcpcd@eth0 service, installed networkmanager (connection to router was auto-detected), enabled it in systemd and still have the delay.

BTW, has KDE got an NM front-end (if it uses the service)? - have found kdeplasma-applets-networkmanagement Arch package.

Now systemd journal looks the way shown below: you see new session opend in kdm, delay, and then even a command to see this journal Nothing criminal..

фев 08 23:57:25 jazz kdm[1242]: :0[1242]: pam_unix(kde:session): session opened for user anli by (uid=0)
фев 08 23:57:25 jazz systemd-logind[299]: New session 2 of user anli.
фев 08 23:57:44 jazz systemd-logind[299]: Removed session 1.
фев 08 23:57:44 jazz polkitd[327]: Registered Authentication Agent for unix-session:2 (system bus name :1.47 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/Authenti
фев 08 23:58:15 jazz sudo[1766]: anli : TTY=pts/0 ; PWD=/home/anli ; USER=root ; COMMAND=/usr/bin/journalctl

Okay, that isn't too surprising, as I didn't expect the Network Manager lack of contact to be causing a large slow down. It is unfortunately hard to continue to diagnose this without more concrete data on why it is waiting around.

It seems tomorrow evening I will have an opportunity to ssh into this computer. But have no ideas how to monitor KDE boot remotely. Is there some published tips?

I would suggest using the second computer to monitor the performance, while logging in normally on the first computer which is displaying the problem. Tools such as htop (with I/O columns configured) would probably be quite helpful in determining the application causing the wait.

bcooksley wrote:with I/O columns configured

I don't see any storage activity (as well as CPU one) during this period at all (I mean motherboard HDD led). And I use SSD, so 10 seconds is a period to, say, boot all the Linux starting from power on

This means that some process somewhere in the chain is hung, waiting upon a response from somewhere. Do you have any network enabled applets on your desktop? Are you able to see what process unsticks itself first?

Have tried ssh/htop. Have not noticed anything interesting - kdeinit4 and kwin flashed on the first htop strings, and it is all I have perceived.
The problem takes place in netbook mode also. And it takes place in 4.10.0 also...

Hey,

Have a look here : http://forum.kde.org/viewtopic.php?f=66&t=101038&start=60#p257045