Linux is cool, I can do a lot of things with it. If i set a config file in Linux, I am damn sure that it is ran every single time. The code does what you tell it to do.
There is 1 thing that always seems to be “black magic”: 1) lid close and suspend 2) lid close and suspend and lock.
If we ignore locking for a moment and focus on suspend. I cant seem to figure out why sometimes lid close would suspend immediately, when other time it takes 5 seconds after lid closes. On some days, lid closes would not even suspend !!
Did anyone manage to get suspend work 100 %? I cant believe we have tons of great linux tools and years into kernel dev, and still suspend is a hit or miss.
Few seem to address the issue here : it does not work 100% of the time for you.
It might work for everybody else but that doesn’t help you much. You have your setup, no theirs.
So… you need to investigate. When it works, great, nothing to learn from. When it fails though… can you find a pattern? Does it always fail after you have use something specific? Check https://lemmy.ml/post/46800646/25494455 which gives examples of potential failure point and
journalctllogs. You can then check what failed and if not you can at least know when then backtrack to others logs, e.g.dmesg.They key take away is that when things do not behave as expected you need to put a detective hat on and you investigate :
- what’s your crime scene? Your laptop and it’s log files
- what’s the crime? It didn’t suspend properly
- where are the traces? In the logs
- where are the logs? Using
journalctlordmesgand typically in/var/log/ - what would a good detective do? Search for specific clues, e.g. places where fingerprints do stick, e.g metal or glass, which here would be error messages. That can be found using
grepand other tools
You also have limited times because the logs will, just like on a real crime scene, get contaminated or rotated or deleted. So… if you do encounter the problem do not rush to the next tasks at hand because you are wasting an opportunity to learn and there is vanishing window.
TL;DR : grep logs
Suspend and hibernate both work 100% of the time for me so far on both of my laptops, and have for as long as i’ve had them.
Thinkpad x270 Fedora (current) KDE spin
Thinkpad x250 Ubuntu 24.04 GNOME
Fully working since 2019 and 2016 respectively. I have not tested opening the lid after just 5 seconds so i can’t say for sure how long it takes.
My previous laptop before these (an x200) would sometimes fail to suspend and get super hot in my bag before running out of battery. I was using Gentoo at the time and i suspect i had something configured incorrectly. It only happened a few times but it was pretty frustrating.
For starters, do you know if your laptop does S3 sleep or S0? I feel like the latter introduces a lot of uncertainty.
Depends a bit on your setup. If you’re using systemd you can use the logind.conf as already mentioned, or if you’re on a non-systemd distro you can use the forked elogind, which works pretty much the same way. For locking your session when suspending, since i use wayland, i use swayidle for that. In its config i just put
before-sleep 'swaylock', which will execute swaylock before the system goes to sleep.Kde on debian here. It just works nowadays
A lot depends on hardware actually, mix of USB Controller, video card, UEFI and etc type of suspeing s3,s0ix so huge fragmentation actually, it so bad that eveb on modern windows it holy crap shit not work because they forced on s2idle. Tell what ur hardware and please share journactl logs of when it fails
I don’t know, I just installed Aurora Linux and everything works by default.
I bet your issue is hardware related, maybe you could change something in the bios to make it work.
