| Summary: | Closing laptop lid does not trigger sleep | ||
|---|---|---|---|
| Product: | [Unmaintained] Powerdevil | Reporter: | TraceyC <kdedev> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | fanzhuyifan, me, natalie_clarius, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
TraceyC
2022-12-14 01:31:44 UTC
For debugging purposes, does it work properly when you disable the "except when external monitor is connected" setting and reboot? Sleep does not get triggered, even when the laptop is unplugged. In that power profile, "except when external monitor is connected" is disabled. Are you wanting me to disable that on the AC power profile as well? Yeah, can you try that too? The option in Energy Saving is actually "Even when an external monitor is connected" I enabled that in the On AC Power tab. The laptop was put to sleep when the lid was closed, as verified by logs for systemd-sleep I disabled that option again and closed the lid again. Sleep was again triggered as expected. I don't know what was different between the times it has not gone to sleep with the lid closed and right now. The problem may be intermittently caused by something else. I haven't changed any other settings. It was definitely not asleep the day I reported the issue. I had closed the laptop and put it in a backpack for a car ride home. When I arrived, the fans were going full tilt and the laptop was hot. The battery had drained significantly. Do you have a different value for that setting on battery vs AC power? In my last test, in my last comment, the settings were the same between AC and battery ( "Even when an external monitor is connected" was enabled in both.) Right now, my settings are the same as in my initial report. Thanks for the info. Can't reproduce, unsure how to proceed. The symptom happened again today, and I have more information from the journalctl logs. It seems the problem may not be related to the lid event. I had tried to put the system to sleep with a keyboard command, and left the house for a few hours. I unplugged the laptop from power. When I returned, the battery was critically low. I saw these entries repeated a few times: ''' Jan 18 19:29:27 tlc-xps17-solus systemd-sleep[84816]: Selected interface 'wlp0s20f3' Jan 18 19:29:27 tlc-xps17-solus systemd-sleep[84816]: 'SUSPEND' command timed out. Jan 18 19:29:27 tlc-xps17-solus systemd-sleep[84811]: Entering sleep state 'suspend'... Jan 18 19:30:09 tlc-xps17-solus systemd-sleep[84811]: Failed to put system to sleep. System resumed again: Device or resource busy Jan 18 19:30:09 tlc-xps17-solus systemd-sleep[84875]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory Jan 18 19:35:21 tlc-xps17-solus systemd-sleep[85123]: Selected interface 'wlp0s20f3' Jan 18 19:35:21 tlc-xps17-solus systemd-sleep[85123]: 'SUSPEND' command timed out. Jan 18 19:35:21 tlc-xps17-solus systemd-sleep[85117]: Entering sleep state 'suspend'... Jan 18 19:36:03 tlc-xps17-solus systemd-sleep[85117]: Failed to put system to sleep. System resumed again: Device or resource busy Jan 18 19:36:03 tlc-xps17-solus systemd-sleep[85178]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory ''' (In reply to TraceyC from comment #8) > The symptom happened again today, and I have more information from the > journalctl logs. It seems the problem may not be related to the lid event. I > had tried to put the system to sleep with a keyboard command, and left the > house for a few hours. I unplugged the laptop from power. When I returned, > the battery was critically low. I saw these entries repeated a few times: > > ''' > Jan 18 19:29:27 tlc-xps17-solus systemd-sleep[84816]: Selected interface > 'wlp0s20f3' > Jan 18 19:29:27 tlc-xps17-solus systemd-sleep[84816]: 'SUSPEND' command > timed out. > Jan 18 19:29:27 tlc-xps17-solus systemd-sleep[84811]: Entering sleep state > 'suspend'... > Jan 18 19:30:09 tlc-xps17-solus systemd-sleep[84811]: Failed to put system > to sleep. System resumed again: Device or resource busy > Jan 18 19:30:09 tlc-xps17-solus systemd-sleep[84875]: Failed to connect to > non-global ctrl_ifname: (nil) error: No such file or directory > Jan 18 19:35:21 tlc-xps17-solus systemd-sleep[85123]: Selected interface > 'wlp0s20f3' > Jan 18 19:35:21 tlc-xps17-solus systemd-sleep[85123]: 'SUSPEND' command > timed out. > Jan 18 19:35:21 tlc-xps17-solus systemd-sleep[85117]: Entering sleep state > 'suspend'... > Jan 18 19:36:03 tlc-xps17-solus systemd-sleep[85117]: Failed to put system > to sleep. System resumed again: Device or resource busy > Jan 18 19:36:03 tlc-xps17-solus systemd-sleep[85178]: Failed to connect to > non-global ctrl_ifname: (nil) error: No such file or directory > ''' Seems the wifi device is preventing sleep. So this is probably not a KDE bug, but a problem with the wifi device configuration or drivers. |