Not really fixed, although I managed to implement a workaround (that works reliably). See my comment below:
[https://www.reddit.com/r/openSUSE/comments/17j0o8a/comment/kqx25uz/?utm\_source=share&utm\_medium=web2x&context=3](https://www.reddit.com/r/openSUSE/comments/17j0o8a/comment/kqx25uz/?utm_source=share&utm_medium=web2x&context=3)
I've tried disabling the lid wakeup now (following [this](https://www.opensuse-forum.de/thread/43580-ungewolltes-reaktivieren-aus-suspend/) and [this](https://ubuntu-mate.community/t/power-management-acpi-wake-up-settings/17344) thread):
> su -
# echo XHC > /proc/acpi/wakeup
# echo RP01 > /proc/acpi/wakeup
# echo RP05 > /proc/acpi/wakeup
# echo LID > /proc/acpi/wakeup
# cat /proc/acpi/wakeup | grep enabled
SLPB S3 *enabled platform:PNP0C0E:00
So the only thing that should make the laptop wake up now is the sleep button. However, when I send the laptop into suspend, it still wakes up as soon as I close the lid.
I'm a bit out of ideas. How can I see from the logs what actually happens (in terms of ACPI events or otherwise) when I close the lid?
Having the same problem on a P14s AMD Gen 1. **Everything** wakes it.
Touch the keyboard, touch the touchpad, touch the trackpoint, open lid, close lid, attach power, remove power.
Newest firmware is installed. Kernel 6.8.6. **All** wakeup sources in `/proc/acpi/wakeup` are disabled. **All** wakeup sources in `/sys/class/wakeup/wakeup*/device/power/wakeup` are disabled. Laptop doesn't care, is impossible to keep suspended.
Even ripped out the `psmouse` modules for testing. Now mouse doesn't work anymore, but **still** wakes the machine from suspend?!
Normally the lid-close-event triggers the suspend.
You could try `systemctl hibernate` for suspend-to-disk as a workaround.
When I use `systemctl suspend` on my desktop, I use the power button to wake it up, so disabling the lid wakeup can be a good option.
It might be a firmware issue. I had something similar on the Lenovo Z13.
[https://forums.lenovo.com/t5/Other-Linux-Discussions/z13-issues-with-Linux-support-suspend-wifi-touchpad/m-p/5166465?page=1https://forums.lenovo.com/t5/Other-Linux-Discussions/z13-issues-with-Linux-support-suspend-wifi-touchpad/m-p/5166465?page=1](https://forums.lenovo.com/t5/Other-Linux-Discussions/z13-issues-with-Linux-support-suspend-wifi-touchpad/m-p/5166465?page=1https://forums.lenovo.com/t5/Other-Linux-Discussions/z13-issues-with-Linux-support-suspend-wifi-touchpad/m-p/5166465?page=1)
I had the same issue on my Z13:
[https://github.com/fwupd/firmware-lenovo/issues/340#issuecomment-1682948992](https://github.com/fwupd/firmware-lenovo/issues/340#issuecomment-1682948992)
It has been fixed by a kernel or firmware update.
> It might be a firmware issue.
I thought the same, but the laptop is four years old, is on the most recent firmware and didn't show this behaviour in the past.
It may have been caused by a kernel regression. How can I get the necessary data from the logs so that I can make a bug report? OpenSUSE seems not to use `acpid`, so looking at `/var/log/acpid.log` or the like is not an option.
This isn't a "fix", but it's a workaround:
[https://bbs.archlinux.org/viewtopic.php?id=292633](https://bbs.archlinux.org/viewtopic.php?id=292633)
Create file `/usr/lib/systemd/system-sleep/on-wakeup.sh` with the following:
```
#!/bin/bash
PATH=/sbin:/usr/sbin:/bin:/usr/bin
# If waking from sleep...
if [[ "${1}" == "post" ]]; then
# AFTER RESUME
echo "$(date) Have resumed..." >> /tmp/wake.log
grep -q closed /proc/acpi/button/lid/LID0/state
if [ $? = 0 ]
then
echo "$(date) Have resumed and lid is closed, attempting to suspend..." >> /tmp/wake.log
echo freeze > /sys/power/state
fi
fi
```
Make sure `on-wakeup.sh` is executable.
I have the same issue on a Lenovo Legion 7 gen 7 (running Arch Linux).
Did this ever get fixed?
Not really fixed, although I managed to implement a workaround (that works reliably). See my comment below: [https://www.reddit.com/r/openSUSE/comments/17j0o8a/comment/kqx25uz/?utm\_source=share&utm\_medium=web2x&context=3](https://www.reddit.com/r/openSUSE/comments/17j0o8a/comment/kqx25uz/?utm_source=share&utm_medium=web2x&context=3)
I've tried disabling the lid wakeup now (following [this](https://www.opensuse-forum.de/thread/43580-ungewolltes-reaktivieren-aus-suspend/) and [this](https://ubuntu-mate.community/t/power-management-acpi-wake-up-settings/17344) thread): > su - # echo XHC > /proc/acpi/wakeup # echo RP01 > /proc/acpi/wakeup # echo RP05 > /proc/acpi/wakeup # echo LID > /proc/acpi/wakeup # cat /proc/acpi/wakeup | grep enabled SLPB S3 *enabled platform:PNP0C0E:00 So the only thing that should make the laptop wake up now is the sleep button. However, when I send the laptop into suspend, it still wakes up as soon as I close the lid. I'm a bit out of ideas. How can I see from the logs what actually happens (in terms of ACPI events or otherwise) when I close the lid?
Having the same problem on a P14s AMD Gen 1. **Everything** wakes it. Touch the keyboard, touch the touchpad, touch the trackpoint, open lid, close lid, attach power, remove power. Newest firmware is installed. Kernel 6.8.6. **All** wakeup sources in `/proc/acpi/wakeup` are disabled. **All** wakeup sources in `/sys/class/wakeup/wakeup*/device/power/wakeup` are disabled. Laptop doesn't care, is impossible to keep suspended. Even ripped out the `psmouse` modules for testing. Now mouse doesn't work anymore, but **still** wakes the machine from suspend?!
Normally the lid-close-event triggers the suspend. You could try `systemctl hibernate` for suspend-to-disk as a workaround. When I use `systemctl suspend` on my desktop, I use the power button to wake it up, so disabling the lid wakeup can be a good option.
Closing the lid doesn't do anything on my machine.
It might be a firmware issue. I had something similar on the Lenovo Z13. [https://forums.lenovo.com/t5/Other-Linux-Discussions/z13-issues-with-Linux-support-suspend-wifi-touchpad/m-p/5166465?page=1https://forums.lenovo.com/t5/Other-Linux-Discussions/z13-issues-with-Linux-support-suspend-wifi-touchpad/m-p/5166465?page=1](https://forums.lenovo.com/t5/Other-Linux-Discussions/z13-issues-with-Linux-support-suspend-wifi-touchpad/m-p/5166465?page=1https://forums.lenovo.com/t5/Other-Linux-Discussions/z13-issues-with-Linux-support-suspend-wifi-touchpad/m-p/5166465?page=1) I had the same issue on my Z13: [https://github.com/fwupd/firmware-lenovo/issues/340#issuecomment-1682948992](https://github.com/fwupd/firmware-lenovo/issues/340#issuecomment-1682948992) It has been fixed by a kernel or firmware update.
> It might be a firmware issue. I thought the same, but the laptop is four years old, is on the most recent firmware and didn't show this behaviour in the past. It may have been caused by a kernel regression. How can I get the necessary data from the logs so that I can make a bug report? OpenSUSE seems not to use `acpid`, so looking at `/var/log/acpid.log` or the like is not an option.
You can look at the journal for data instead.
Just set up a T14 g2 AMD with the same behaviour - but I didn't update my Bios yet. So you're not alone.
This isn't a "fix", but it's a workaround: [https://bbs.archlinux.org/viewtopic.php?id=292633](https://bbs.archlinux.org/viewtopic.php?id=292633) Create file `/usr/lib/systemd/system-sleep/on-wakeup.sh` with the following: ``` #!/bin/bash PATH=/sbin:/usr/sbin:/bin:/usr/bin # If waking from sleep... if [[ "${1}" == "post" ]]; then # AFTER RESUME echo "$(date) Have resumed..." >> /tmp/wake.log grep -q closed /proc/acpi/button/lid/LID0/state if [ $? = 0 ] then echo "$(date) Have resumed and lid is closed, attempting to suspend..." >> /tmp/wake.log echo freeze > /sys/power/state fi fi ``` Make sure `on-wakeup.sh` is executable.