Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36708 - Reboot/poweroff takes very long after Systemd 206-2 update
Attached to Project:
Arch Linux
Opened by Hao (qft) - Wednesday, 28 August 2013, 11:23 GMT
Last edited by Dave Reisner (falconindy) - Monday, 02 September 2013, 14:34 GMT
Opened by Hao (qft) - Wednesday, 28 August 2013, 11:23 GMT
Last edited by Dave Reisner (falconindy) - Monday, 02 September 2013, 14:34 GMT
|
DetailsDescription:
After upgrade to systemd 206-2 in testing, reboot or poweroff now takes several minutes to complete. While waiting for poweroff, pressing the SysRQ key combination ALT+PrntScr+E instantly shuts off the computer. Downgrade systemd back to 204-3 solves the problem. Additional info: The same problem happens no matter logging into X (using slim display manger and awesome WM) or logging into console. The following items from system log are relavent to this problem, and both are not present with systemd 204-3: During booting: systemd[335]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory During poweroff: systemd[1]: session-1.scope stopping timed out. Killing. |
This task depends upon
Closed by Dave Reisner (falconindy)
Monday, 02 September 2013, 14:34 GMT
Reason for closing: Upstream
Additional comments about closing: Upstream bug, long since fixed in git, but the patches are non-trivial.
Monday, 02 September 2013, 14:34 GMT
Reason for closing: Upstream
Additional comments about closing: Upstream bug, long since fixed in git, but the patches are non-trivial.