You are not logged in.

#1 2026-01-19 17:02:31

just.john3232
Member
Registered: 2026-01-10
Posts: 2

[SOLVED] System returns to sleep shortly after waking, then is normal

My computer has been acting oddly for a few months. Every time I wake the computer from a suspended state, after a short period of time (usually 5-20 seconds) my computer will automatically return to a suspended state. If I then immediately wake up the computer again it will act normally until the next time I either intentionally suspend the computer, or auto-suspend occurs based on my power settings.

I've seen this exact issue discussed before, but only once, here: https://unix.stackexchange.com/question … rst-resume

Unfortunately the OP of that post didn't t appear to find any resolution, so I'm hoping I'll have better luck here.

I'm unsure what journal filters will be the most helpful, so right after logging in for the first time today I ran

$ journalctl -S "today" -FILTER | curl -F 'file=@-' 0x0.st

with several filters. The files can be found here:

Filter   - File
none   - http://0x0.st/PKyX.txt
-p 4     - http://0x0.st/PKyP.txt
-k        - http://0x0.st/PKyZ.txt
-k -p 4 - http://0x0.st/PKyN.txt

For reference my machine specs are:

OS:        Arch Linux x86_64
Host:      INTEL
Kernel:    Linux 6.18.5-arch1-1
DE:        GNOME 49.2
WM:        Mutter (Wayland)
CPU:       12th Gen Intel(R) Core(TM) i5-12600KF (16) @ 4.90 GHz
GPU:       NVIDIA GeForce GTX 980 Ti [Discrete]
Memory:    7.65 GiB / 62.62 GiB (12%)
Swap:      0 B / 4.00 GiB (0%)

There appear to be several warning about usb devices, so I'll mention I currently only have two usb peripherals plugged in, a keyboard and a mouse:

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 048d:5702 Integrated Technology Express, Inc. RGB LED Controller
Bus 001 Device 006: ID 046d:c53a Logitech, Inc. PowerPlay Wireless Charging System
Bus 001 Device 007: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 001 Device 010: ID 3434:0660 Keychron Keychron Q6 Pro
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Hopefully this is enough info for someone to help me start diagnosing this. Any tips or helpful arch wiki links are welcome.

Thanks

--------------------------
EDIT: Post marked solved. See final messages 3/4 for summary

Last edited by just.john3232 (2026-01-19 22:43:49)

Offline

#2 2026-01-19 19:49:56

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,424

Re: [SOLVED] System returns to sleep shortly after waking, then is normal

Online

#3 2026-01-19 21:20:41

just.john3232
Member
Registered: 2026-01-10
Posts: 2

Re: [SOLVED] System returns to sleep shortly after waking, then is normal

Thanks Seth, that appears to be exactly what I'm dealing with.

I think I took away the important bits, but I'm not well versed in everything I read. Do you agree with this short summary of the end of the post?

  • This is due to a conflict between GNOME and NVIDIA when the system tries to suspend. The problem has been identified, and the fix should come when GNOME 50 is released.

  • A potential 'fix' is to comment out the call to chvt 63 on line 41 of /usr/bin/nvidia-sleep.sh.

  • However, per NVIDIA that line is technically needed, so this would be a do at your own risk 'fix' until it's resolved  in GNOME 50?

If so I'll go ahead and mark this solved and try my luck while waiting for the GNOME 50 release in the Spring.

For anyone else encountering this, see the link Seth posted. I basically summarized posts #36 and #37.

Offline

#4 2026-01-19 22:02:48

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,424

Re: [SOLVED] System returns to sleep shortly after waking, then is normal

That's the gist of it, yes.
You could test whether the workaround works for you (just to see whether this is your problem) and if yes what downsides it introduces.

And then your options are
1. that workaround
2. downgrade systemd
3. wait for gnome 50
(none of those options is really great, downgrading systemd might eventually break the system altogether)

Online

Board footer

Powered by FluxBB