FS#59859 - [systemd] Systemd-logind doesn't react to suspend events
Attached to Project:
Arch Linux
Opened by Anonymous Submitter - Wednesday, 29 August 2018, 10:39 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 07:46 GMT
Opened by Anonymous Submitter - Wednesday, 29 August 2018, 10:39 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 07:46 GMT
|
Details
Description:
Systemd-logind doesn't react to suspend events. It's running. If I restart it with systemctl restart systemd-logind, it starts to working. There is no reason for it as no configuration or anything else changed in between. Log from systemd-logind that doesn't react to suspend key. Aug 29 12:22:37 system systemd-logind[524]: Watching system buttons on /dev/input/event2 (Power Button) Aug 29 12:22:37 system systemd-logind[524]: Watching system buttons on /dev/input/event0 (Lid Switch) Aug 29 12:22:37 system systemd-logind[524]: Watching system buttons on /dev/input/event1 (Sleep Button) Aug 29 12:22:37 system systemd-logind[524]: Watching system buttons on /dev/input/event3 (AT Translated Set 2 keyboard) Aug 29 12:22:37 system systemd-logind[524]: Watching system buttons on /dev/input/event5 (ThinkPad Extra Buttons) Aug 29 12:22:37 system systemd[1]: Started Login Service. Aug 29 12:22:38 system systemd-logind[524]: New session c1 of user lightdm. Aug 29 12:22:47 system systemd-logind[524]: Removed session c1. Aug 29 12:22:47 system systemd-logind[524]: New session 2 of user user. Aug 29 12:29:00 system systemd-logind[524]: Suspend key pressed. Additional info: - ThinkPad X220 - systemd 239.0-2 logind.conf configuration: [Login] HandleSuspendKey=suspend HandleLidSwitch=suspend IdleAction=ignore Steps to reproduce: Press suspend button, see it doesn't do anything. Check systemctl status systemd-logind to see that it is running and nothing happened. |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 25 September 2023, 07:46 GMT
Reason for closing: Fixed
Additional comments about closing: This looks old and stale. Assuming fixed upstream by now. If not, please report upstream.
Monday, 25 September 2023, 07:46 GMT
Reason for closing: Fixed
Additional comments about closing: This looks old and stale. Assuming fixed upstream by now. If not, please report upstream.
After suspending once, systemd doesn't respond to further suspends. Moreover this hangs shutdown by displaying: `A stop job is running for UID 1000 (2 min)`
`journalctl` shows failed system units.