You are not logged in.
After the recent update to systemd 229-2 I have been getting a delay of 90 seconds before the system shuts down or reboots, when selecting those options when right clicking on the plasma desktop and choosing "Leave". The shutdown starts but then gives a countdown timer for "A stop job is running for Session c2 of user....." This shutdown delay does not happen if I logout from the plasma desktop and then click the reboot icon at the top right of the sddm greeter screen.
I have added a comment to an existing arch report at https://bugs.archlinux.org/task/47734
I don't know if this is a problem with systemd, dbus or plasma?
Last edited by mcloaked (2016-02-19 20:52:36)
Mike C
Offline
This is an on going problem. It started for some people last fall. For some reason it doesn't seem to start causing issues for everyone at the same time. My laptop had this problem a release after my desktop.
Offline
Seems there is also an upstream report at https://bugs.freedesktop.org/show_bug.cgi?id=70593
Mike C
Offline
Not a solution, but you can reduce the delay in /etc/systemd/system.conf:
DefaultTimeoutStopSec=30s
Offline
You can also force an immediate shutdown/reboot by pressing <Ctrl>+<Alt>+<Delete> seven times in two seconds.
Last edited by Head_on_a_Stick (2016-02-20 22:35:22)
Freedom for Öcalan!
Offline
Pretty sure this is a KDE issue, the kded module has some open connections, that it can't properly close, there was a hack to make it work again, but this hack was removed in frameworks 19 because qt 5.6 is supposed to have a better suited fix, but we don't have that yet.
Scratch that, checking the respective KDE commit again shows that this was already a QT version check, so the particular commit I had in mind isn't likely to be the culprit
Last edited by V1del (2016-02-21 00:58:03)
Offline
Same problem. Solved by downgrading systemd to 228-4.
Offline
Same problem. Solved by downgrading systemd to 228-4.
Hopefully this is something that is being actively worked on by upstream systemd developers?
Mike C
Offline
My summary (it took me a lot of reboots):
systemd 228-4 - Works fine.
systemd 229-2 - Reboot always worked, combination of logout + shutdown worked, but shutdown directly from KDE desktop delayed with timeout. I tested everything at least twice.
Very strange, I have no idea what's going on. This is on DELL Latitude E5550 (N-5550-N3-PR1) with KDE Plasma.
Last edited by sand6 (2016-02-21 16:06:32)
Offline
My summary (it took me a lot of reboots):
systemd 228-4 - Works fine.
systemd 229-2 - Reboot always worked, combination of logout + shutdown worked, but shutdown directly from KDE desktop delayed with timeout. I tested everything at least twice.Very strange, I have no idea what's going on. This is on DELL Latitude E5550 (N-5550-N3-PR1) with KDE Plasma.
Same behaviour for me - so is it that systemd is buggy or is it that version 229-2 (and 229-3) of systemd has exposed a bug in dbus? I have this behaviour in a Lenovo y510p, and a Lenovo S540, as well as in a home constructed Intel DQ77KB motherboard with an Ivybridge i3 processor. Basically all my arch systems have the same issue! Presume by KDE desktop you meant plasma desktop.
Last edited by mcloaked (2016-02-21 16:22:17)
Mike C
Offline
Same problem. I'm using startx/Fluxbox, and reboot/shutdown by calling systemctl reboot/shutdown entryes added to fluxbox menu.
Solved by downgrading systemd to 228-4.
Also added *systemd* to Pacman's IgnorePkg, for now, because systemd 229-3 is obviously buggy.
Offline