14
how to investigate unexpected power management behavior
(discuss.tchncs.de)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Apr 2025
14 points (93.8% liked)
Linux
53346 readers
626 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
So when lid is closed, OS doesnt suspend or takes long to suspend? The best way is to use journalctl. Close the lid, wait 2 - 5 mins, then open it up and check most recent journalctl messages. Hopefully that gives you some clues.
Now, are you dual booting Windows? Try to check Bios if your laptop has any funny settings for power. On Lenovo, there used to be something like "Power scheme for both Linux and Window" button..
Lastly, xfce4-power-manager app really is just a GUI for your core systemd services. So... as a test, can you not autostart it? Xfce has a setting for that. Or just remove it, you can easily install it back later.
Once youre done, reboot back and check:
Does closing the lid make the laptop to go into suspend mode? If yes, great. Test again to see if behavior is erratic, i.e. sometimes it takes 5 sec to suspend, sometimes it does not suspend at all..etc.
If above fail, try to run "systemctl suspend" to check if suspend really works on your system.
if 1) and 2) fail, you can play around with /etc/systemd/sleep.conf script. Maybe uncomment "AllowSuspend" or something similar....