<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - random 90 sec delay on shutdown/reboot (A stop job is running for User Manager for 0)" href="https://bugs.freedesktop.org/show_bug.cgi?id=70593#c28">Comment # 28</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - random 90 sec delay on shutdown/reboot (A stop job is running for User Manager for 0)" href="https://bugs.freedesktop.org/show_bug.cgi?id=70593">bug 70593</a> from <a class="email" href="mailto:mike.cloaked@gmail.com" title="Mike C <mike.cloaked@gmail.com>"> Mike C</a> <pre>This is happening to me on arch linux with systemd 229-2 (and also 229-3 from the testing repo) If right clicking on the plasma desktop and selecting "Leave" and then shutdown or reboot, the console gives a message "A stop job is running for Session c2 for user...." and counts down the 90 seconds before completing the shutdown. In the journal I see: Feb 18 20:13:24 home1 systemd[1]: Stopped target Network. Feb 18 20:14:53 home1 systemd[589]: dbus.service: State 'stop-final-sigterm' timed out. Killing. Feb 18 20:14:53 home1 systemd[1]: <a href="mailto:user@1000.service">user@1000.service</a>: State 'stop-sigterm' timed out. Killing. Feb 18 20:14:53 home1 systemd[1]: Stopped User Manager for UID 1000. Feb 18 20:14:53 home1 systemd[1]: <a href="mailto:user@1000.service">user@1000.service</a>: Unit entered failed state. Feb 18 20:14:53 home1 systemd[1]: <a href="mailto:user@1000.service">user@1000.service</a>: Failed with result 'timeout'. Feb 18 20:14:53 home1 systemd[1]: Removed slice User Slice of mike. Feb 18 20:14:53 home1 systemd[1]: Stopping Login Service... Feb 18 20:14:53 home1 systemd[1]: Stopping Permit User Sessions... Feb 18 20:14:53 home1 systemd[1]: Stopped Permit User Sessions. Feb 18 20:14:53 home1 systemd[1]: Stopped target Remote File Systems. Feb 18 20:14:53 home1 systemd[1]: Stopped Login Service. Feb 18 20:14:53 home1 systemd[1]: Stopped target Basic System. and again from today: Feb 19 15:45:36 home1 systemd[1]: Stopped Simple Desktop Display Manager. Feb 19 15:47:01 home1 systemd[599]: dbus.service: State 'stop-final-sigterm' timed out. Killing. Feb 19 15:47:01 home1 systemd[1]: <a href="mailto:user@1000.service">user@1000.service</a>: State 'stop-sigterm' timed out. Killing. Feb 19 15:47:01 home1 systemd[1]: Stopped User Manager for UID 1000. Feb 19 15:47:01 home1 systemd[1]: <a href="mailto:user@1000.service">user@1000.service</a>: Unit entered failed state. Feb 19 15:47:01 home1 systemd[1]: <a href="mailto:user@1000.service">user@1000.service</a>: Failed with result 'timeout'. Feb 19 15:47:01 home1 systemd[1]: Removed slice User Slice of mike. Feb 19 15:47:01 home1 systemd[1]: Stopping Login Service... Feb 19 15:47:01 home1 systemd[1]: Stopping Permit User Sessions... Feb 19 15:47:01 home1 systemd[1]: Stopped Permit User Sessions. Once the shutdown stop job delay has ended the shutdown then completes rapidly. which seems to be a dbus related shutdown delay with the 90 seconds wait period seen in the timestamps above. I also installed systemd 229-3 from testing but this does not help the issue. This is likely related: <a href="https://lists.freedesktop.org/archives/systemd-devel/2016-January/035619.html">https://lists.freedesktop.org/archives/systemd-devel/2016-January/035619.html</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>