Am 07.12.2014 um 19:39 schrieb Ralf Jung: > Hi, > >>> This behavior only started recently, about the same time as the upgrade to >>> systemd 215-7. >>> KDE has not seen updates in 2 weeks. That's why I reported this against >>> systemd. >> >> Is this behaviour reproducible after a reboot? > > Indeed it is not, though I was sure I saw this not just after systemd > upgrades... sorry for this. It's probably just another duplicate of > "systemd upgrade restarts something, and some things break until next > reboot".
postinst has:
if [ -n "$2" ]; then
systemctl daemon-reexec || true
systemctl try-restart systemd-logind.service || true
systemctl try-restart systemd-networkd.service || true
systemctl try-restart systemd-resolved.service || true
systemctl try-restart systemd-timesyncd.service || true
fi
Can you run those commands step-by-step and check if a specific restart
is able to trigger the issue?
Might be, that some KDE program doesn't cope with the restart of
systemd-logind and doesn't properly reconnect to the logind D-Bus service.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
