[solved] incomplete kde startup

Xylankant · 2012-09-05 07:48:42

Hello there,

I am not really sure if this problem is caused by systemd or KDE, but it only showed up now, after starting to use systemd:

I recently switched to systemd and had (actually, have) no problems, the migration worked fine as described in the wiki.
However, ever since the switch to systemd, KDE will only fully go through with its startup after every second boot of my laptop...

every other boot everything looks normal, kdm shows up, I can log into KDE, but for some reason, it seems to be an incomplete start of KDE, e.g., some (most?) system parts just won't load:

these programs don't show up in the "tray":
- kmix doesn't load
- klipper doesn't load
- nm-applet doesn't load (only the applet, NetworkManager is actually working)

Also, scripts/programs from my autostart configuration won't load, for example yakuake doesn't get started.
Furthermore, I can not log out, shutdown, reboot etc. from the KDE menu, but have to start a terminal, e.g. Konsole and do that kind of things.
When I reboot and log in to KDE again, everything is fine. This is reproducable at every second boot.

Has anyone out there experienced similar issues (maybe without systemd? it might be some KDE-only issue...)?

Last edited by Xylankant (2012-09-06 22:21:03)

hadrons123 · 2012-09-05 12:19:02

Strange!
Did you install systemd like this?

pacman -S systemd systemd-sysvcompat systemd-arch-units

ANOKNUSA · 2012-09-05 14:03:49

What parts of the desktop aren't being loaded?
What daemons do they depend on?
Is systemd starting those daemons/services (or, more accurately, did you configure systemd to start those daemons/services)?

Xylankant · 2012-09-05 15:29:57

hadrons123 wrote:

Strange!
Did you install systemd like this?
pacman -S systemd systemd-sysvcompat systemd-arch-units

mhhh, as described in "Installation / A pure systemd installation" in this wiki article, and also installed the systemd-arch-units package.

ANOKNUSA wrote:

What parts of the desktop aren't being loaded?
What daemons do they depend on?
Is systemd starting those daemons/services (or, more accurately, did you configure systemd to start those daemons/services)?

As stated in my original post, the parts that aren't loading are

Xylankant wrote:

these programs don't show up in the "tray":
- kmix doesn't load
- klipper doesn't load
- nm-applet doesn't load (only the applet, NetworkManager is actually working)
Also, scripts/programs from my autostart configuration won't load, for example yakuake doesn't get started.

As far as I can see, the only service those depend on is kdm.service, which gets loaded. Also, using

#> systemctl > services_working

(when everything loads fine) and

#> systemctl > services_notWorking

(when everything does not load fine), I checked if there's a difference in loaded services, but there isn't:

#> diff services_working services_notWorking
#>

It's all very strange...

Xylankant · 2012-09-05 15:43:34

...even stranger.

It seems to be working now, after dealing with a, seemingly unrelated, issue with pulseaudio (audio playback would show an annoying delay)...
after changing a line in /etc/pulse/default.pa to

.ifexists module-udev-detect.so
load-module module-udev-detect tsched=0
.else

and copying pulseaudio.desktop from /etc/xdg/autostart/ to my home folder, everything seems to work now.

The pulseaudio issue was also present before switching to systemd, so that's even stranger, but for now it seems to be fine...I'll try to confirm that over the next couple of boots...

Xylankant · 2012-09-05 22:55:53

ok, that wasn't it. however, it seems to be more related to kde/kdm than to systemd actually:

when those parts, as described, won't start up, I do *not* actually have to reboot apparently. instead, using a terminal issuing

kdmctl suicide

(thus, restarting my xServer and kdm) and re-logging into KDE does the trick and everything loads up fine.

So, the question now is: what causes KDE not to load everything when started up every other boot/login?

cfr · 2012-09-05 23:53:48

When you normally reboot/shutdown, do you do so using kde's graphical dialog?

If you use kdm, have you edited the reboot and shutdown commands in kdmrc?

Xylankant · 2012-09-06 00:17:10

cfr wrote:

When you normally reboot/shutdown, do you do so using kde's graphical dialog?
If you use kdm, have you edited the reboot and shutdown commands in kdmrc?

I tried both using KDE's graphical dialog and a terminal. on the terminal, I tried both

sudo shutdown -h now

and

systemctl poweroff

, all with the same result.
In kdmrc, I changed the commands to use systemctl, but that didn't help either.

Just now, a *massive* update for KDE came in via pacman (>500mB), maybe there is some fix in that, I'll keep this thread updated with the outcome...

Thank you very much for helping

Xylankant · 2012-09-06 06:41:50

it seems like the KDE update did indeed fix it, booted 5 times in a row now without any problems.
I mark this thread as solved.

ANOKNUSA · 2012-09-06 20:35:09

Do you think you could maybe change the title of this thread as well, seeing as how systemd had nothing to do with it? That will avoid future confusion.

Xylankant · 2012-09-06 22:21:29

oh yes, good remark, I renamed it

Arch Linux

#1 2012-09-05 07:48:42

[solved] incomplete kde startup

#2 2012-09-05 12:19:02

Re: [solved] incomplete kde startup

#3 2012-09-05 14:03:49

Re: [solved] incomplete kde startup

#4 2012-09-05 15:29:57

Re: [solved] incomplete kde startup

#5 2012-09-05 15:43:34

Re: [solved] incomplete kde startup

#6 2012-09-05 22:55:53

Re: [solved] incomplete kde startup

#7 2012-09-05 23:53:48

Re: [solved] incomplete kde startup

#8 2012-09-06 00:17:10

Re: [solved] incomplete kde startup

#9 2012-09-06 06:41:50

Re: [solved] incomplete kde startup

#10 2012-09-06 20:35:09

Re: [solved] incomplete kde startup

#11 2012-09-06 22:21:29

Re: [solved] incomplete kde startup

Board footer