Sleep not working when having (certain?) apps open
Hi all, for a few month now I can only get my computer to sleep (on two different machines) when most apps are closed. If these apps are open (most often Dolphin, Firefox and Thunderbird but it sometimes works with some of them open), the screen just turns black for a few seconds and then turns on again with the lockscreen (I can then unlock, close a few more apps and try again).
What can I try to pinpoint the problem here (which logs to look at and how?)
Some info:
KDE Plasma 6.4.3
Kernel 6.15.6-105.bazzite.fc42.x86_64 (64-bit)
AMD Ryzen 7 7700
NVIDIA GeForce RTX 4070
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
42.20250720 (2025-07-20T07:52:37Z (Oh, I see there is a new version, I'll update and see if this has gone away).
Thanks for all the cool work you do! ^__^
Solution:Jump to solution
Yay, that seems to work! So the systemd-service is now (slightly modified from here):
[Unit] Description=Prevent system from waking immediately after suspend ...
[Unit] Description=Prevent system from waking immediately after suspend ...
19 Replies
Looks like it works now!? I'll see if it contienues to do so but that would be amazing!
No, spoke to soon, problem still persists +___+
I have the same problem even with no applications open. Seems like it sleeps for a second or two then everything lights up again and it wakes up
@ellen_bogen so two questions:
1. What motherboard do you have?
2. Do you by any chance have a logitech wireless mouse or keyboard?
O no, it even not working with no applications open is so much worse! (I have an ancient laptop where sleep doesn't seem to work, no matter the distro). For me it feels like the system tries to go sleep but some process doesn't let it / interrupts it, so monitor turns on again.
1. dmidecode -t 2 says the motherboard is a Gigabyte B650M AORUS ELITE AX and that sounds familiar
2. Using usb mouse and keyboard, only wireless thing (except for wifi) is sometimes a bluetooth speaker (UE Boom).
Can you show me the output of
cat /proc/acpi/wakeup | grep enabled?Looks like you need to append this karg:
acpi_osi="!Windows 2015"Interesting, I'll check that out, thanks!
that outputs:
GPP1 S4 *enabled pci:0000:00:01.2
GPP7 S4 *enabled pci:0000:00:02.1
UP00 S4 *enabled pci:0000:03:00.0
DP00 S4 *enabled pci:0000:04:00.0
DP20 S4 *enabled pci:0000:04:04.0
DP28 S4 *enabled pci:0000:04:05.0
DP30 S4 *enabled pci:0000:04:06.0
DP38 S4 *enabled pci:0000:04:07.0
DP40 S4 *enabled pci:0000:04:08.0
DP48 S4 *enabled pci:0000:04:09.0
DP50 S4 *enabled pci:0000:04:0a.0
DP58 S4 *enabled pci:0000:04:0b.0
DP60 S4 *enabled pci:0000:04:0c.0
XH00 S4 *enabled pci:0000:0e:00.0
DP68 S4 *enabled pci:0000:04:0d.0
GP17 S4 *enabled pci:0000:00:08.1
XHC0 S4 *enabled pci:0000:10:00.3
XHC1 S4 *enabled pci:0000:10:00.4
XHC2 S4 *enabled pci:0000:11:00.0
GPP0 S4 *enabled pci:0000:00:01.1Mmmh, how would I do that? As described here:
https://docs.bazzite.gg/Advanced/dracut-and-initramfs/ ? But how would I handle the quotes?
would
rpm-ostree kargs --append-if-missing="acpi_osi=!Windows 2015"
work?
How to Modify Initramfs and Dracut - Bazzite Documentation
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices.
Just adding the karg like that should do the trick yeah.
If that doesn't work, it may require to disable one or more of those wakeup triggers.
Try what @biebel suggested first with kargs and if that doesn't work try disabling the GPP0 wakeup trigger
mmmh,
rpm-ostree kargs --append-if-missing="acpi_osi=!Windows 2015"
output was:
bash: !Windows: event not found
so tried both
rpm-ostree kargs --append-if-missing="acpi_osi=Windows 2015"
and
rpm-ostree kargs --append-if-missing="acpi_osi=!"
(as per https://askubuntu.com/questions/1455159/acpi-osi-windows-2015-not-working )
do you think that should be the same as !Windows 2015?
rpm-ostree kargs
now outputs (among a lot of other things) both
acpi_osi=Windows 2015
and
acpi_osi=!
(obviously)
(obviously)
Ask Ubuntu
acpi_osi='Windows 2015' not working
I have tried
acpi_osi='Windows 2015' in /etc/default/grub file;
GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi='Windows 2015'"
After update-grub an reboot machine
I ran: sudo dmesg |grep -i add
But...
well, that did not boot. i think it said something about hard-lockup of cpu 1 and 15.
mmmh, could you point me towards how i disable the wakeup triggers permanently?
i tried to make a systemd-service (as described here https://github.com/ublue-os/bazzite/issues/1928#issuecomment-2537412829 and here https://pliszko.com/blog/post/2025-07-31-fixing-instant-wake-from-suspend-on-gigabyte-motherboards-on-arch-linux)
but i'm getting the following error:
systemd[1]: gpp-disable.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
which is fair, these are not in the script.
is there a better way to do this?
GitHub
Desktop goes to sleep but actively wakes up after a few seconds of ...
Describe the bug I can suspend my desktop manually, but if it suspends on its own then it never actually sleeps. It wakes up repeatably and I know by system sounds that KDE Plasma makes when it hap...
huh? can you show what
cat /etc/systemd/system/gpp-disable.service shows? Or what you named the service ?it's only:
[Unit]
Description=Prevent system from waking immediately after suspend
[Service]
ExecStartPre=/bin/sh -c '/bin/echo GPP0 > /proc/acpi/wakeup'
Type=oneshot
[Install]
WantedBy=multi-user.target
( basically copied from here: https://github.com/ublue-os/bazzite/issues/1928#issuecomment-2537412829 )
GitHub
Desktop goes to sleep but actively wakes up after a few seconds of ...
Describe the bug I can suspend my desktop manually, but if it suspends on its own then it never actually sleeps. It wakes up repeatably and I know by system sounds that KDE Plasma makes when it hap...
Oh, now the errormessage makes sense. Change ExexStartPre to ExecStart and it should be fine
Solution
Yay, that seems to work! So the systemd-service is now (slightly modified from here):
[Unit] Description=Prevent system from waking immediately after suspend [Service] ExecStart=/bin/sh -c '/bin/echo GPP0 > /proc/acpi/wakeup' Type=oneshot [Install] WantedBy=multi-user.target cat /proc/acpi/wakeup also shows GPP0 as disabled after a reboot. I'll check if it continues to work but it looked really good yesterday, had no problems with sleep-mode. Thanks so much @biebel and @asheriif ✨
[Unit] Description=Prevent system from waking immediately after suspend [Service] ExecStart=/bin/sh -c '/bin/echo GPP0 > /proc/acpi/wakeup' Type=oneshot [Install] WantedBy=multi-user.target cat /proc/acpi/wakeup also shows GPP0 as disabled after a reboot. I'll check if it continues to work but it looked really good yesterday, had no problems with sleep-mode. Thanks so much @biebel and @asheriif ✨
Unfortunately, after a few days this problem has come up again +___+ Any other ideas? I the other GPP wake timer mentioned inthe Github issue is already disabled for me otherwise I'd try that. Is there a way to mark the „unsolved“ again?
Does disabling more wake triggers help?