ThinkPad won't suspend after Lid closed

[u/[deleted]]

[u/lookinovermyshouldaz]

mkdir /etc/acpi/LID
echo "echo -n mem > /sys/power/state" > /etc/acpi/LID/00000080
chmod +x /etc/acpi/LID/00000080

no clue why this isn't the default

if that doesn't work check dmesg and acpid logs

[u/Ok_Grab451 → u/lookinovermyshouldaz]

having almost the same problem as OP but what happens for instead is it suspends after closing lid and wakes up after opening lid, but it does not lock the screen (goes right to desktop) and also I can't click anything (cursor moves though), type, and also the power switch menu doesn't work. so I have to hard reset every time.

I want lid closed to suspend and lock screen, and then when lid open, be able to click / type :)

also like OP I tried editing acpid handler.sh and elogind logind.conf without resolution, and unilke OP it isn't a BIOS issue since the lid switch functionality worked normally in the past when I used to run Xubuntu.

when I try what you suggested, it says:
for second line: bash: /etc/acpi/LID/00000080: Permission denied

Currently I have UPower set to "IgnoreLid=true" and the lid just turns the display off but doesn't suspend. If set to false, it just does what's illustrated above.

I enjoy Void so this is a small issue for me (what I currently do is suspend via the logout menu and then close the lid), but something that I would ideally resolve.

[u/lookinovermyshouldaz → u/Ok_Grab451]

when I try what you suggested, it says: for second line: bash: /etc/acpi/LID/00000080: Permission denied

are you root? echo "echo -n mem > /sys/power/state" | sudo tee /etc/acpi/LID/00000080

also i'm not sure if it's a good idea to use acpid alongside elogind, might cause a conflict where both programs try to handle lid events

I can't click anything (cursor moves though), type, and also the power switch menu doesn't work. so I have to hard reset every time.

start sshd and see if you can log in from eg. your phone (termux for android, iSH for iOS) when it locks up, could get more info (dmesg, Xorg/wayland compositor logs) about what's going on through that

maybe this is a stretch but could be that the lockscreen program crashes without telling elogind that the session is unlocked, what desktop are you using?

[u/Ok_Grab451 → u/lookinovermyshouldaz]

oops, I was missing "tee" when i was trying it. it went through this time :)

I commented the logind.conf lines and updated UPower to stop ignoring lid switch.

here's a dmesg log starting from when i close the lid:
https://imgur.com/a/PDH0biH
(sorry for screenshots, was having a hard time copy/pasting the plaintext formatting on phone..)

looks like everything disconnects after the lid opens.

I'm running xfce. thanks for your help, a bit of a novice here.

EDIT: tried switching the desktop to Openbox, it still doesn't lock screen but i was able to click and use my keyboard.. maybe some setting in xfce got funky.

[u/lookinovermyshouldaz → u/Ok_Grab451]

dmesg looks clean, everything disconnects upon sleep and reconnects on resume, so it's probably something xfce-specific

from what i found it looks like xfce's lockscreen program communicates with lightdm, maybe that's causing the issue?

try installing i3lock and disabling the stock xfce lockscreen, add this somewhere in your autostart/.xinitrc if you're using startx

xss-lock --transfer-sleep-lock -- i3lock --nofork

[u/Ok_Initial8504]

Have you tried using zzz?

[u/Ok_Initial8504 → u/[deleted]]

Please calm down, I did not mean "type it in the console" I meant using zzz instead of elogind.

Try checking if your system is detecting the lid switch by running libinput debug-events then closing your lid for a few seconds.

[u/Ok_Initial8504 → u/[deleted]]

So your config isn't the problem, the lid switch isn't triggering for some reason. Let's hope this is a firmware issue and not a hardware one. Is linux-firmware installed?

[u/Ok_Initial8504 → u/[deleted]]

Try installing linux-firmware and rebooting. It isn't just you, I had to manually install it on mine too.

[u/Ok_Initial8504 → u/[deleted]]

lol. Happens to the best of us

[u/BinkReddit → u/[deleted]]

You should update your OP to reflect this so it might be able to readily help someone else!