https://bugs.kde.org/show_bug.cgi?id=463025
--- Comment #8 from TraceyC <kdeb...@tlcnet.info> --- 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 ''' -- You are receiving this mail because: You are watching all bug changes.
