I’m running Tumbleweed on an AMD 7800X3D + 7900XTX.
Plasma + Wayland all updated.
Everything works fine but once the computer enters sleep it won’t wake up anymore. I have to force a shut down and power it up again. Blank screen, bloq mayus won’t work on the keyboard. Just frozen.
It is a completelly new install and all up-to-date. I dont’ know if happened before or after updating it as once downloaded and installed first thing I did was updating it using zypper.
PS: I meant Caps Lock, (bloc mayus is in catalan). My bad.
Very similar config here… I have openSUSE with a Ryzen 7 7700X and AMD Radeon RX 7900XTX, and I’ve had this issue for a little over a month now. I have to turn off the screen instead of sleeping, which isn’t an ideal workaround.
I have tried so many things, to no avail. SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false did help, but it seemed to change the behavior to successfully wake from sleep once, and then freeze on wake if you tried to sleep a second time.
Incredibly, the comment above actually worked. When I disable BT it wakes from sleep every time. When I re-enable BT, it freezes on wake again. Disabling BT is a fine workaround for me since I don’t actually use any BT devices, but it won’t work for people who do. Plus long-term, I would prefer to properly solve the problem. (I may want to use my BT in the future.)
Glad to hear that turning off BT solves the issue for you. Actually, there is a bug report entitled “hard freezes related to btusb device 04ca:3802” at 1231599 – hard freezes related to btusb device 04ca:3802, which should be solved by kernel 6.11.6. Could you please check it? If this version doesn’t work, could you please open a bug report at https://bugzilla.opensuse.org/? Since there have been some btusb patches starting with kernel 6.11.3, which one is the last working one for you? Thank you.
I generally keep my kernel up-to-date, doubly so lately as I’ve been hoping that a fix would just come with some update.
I am on 6.11.6-2-default and I still have the problem. I don’t recall the last version that worked for me, but I can poke around another day (I have a busy day with work so can’t go too deep down rabbit holes).
As I mentioned before I can’t turn off bluetooth as I need it.
But, what about turning off the screen? Could you elaborate please? Do you mean that you actually turn off the screen manually every time you leave the computer?
I can confirm that the bug you mention seems to be exactly my problem, but in kernel 6.1.6-2-default isn’t fixed.
This is my output after lsusb:
Bus 001 Device 002: ID 0b05:1a52 ASUSTek Computer, Inc. USB Audio
Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 0e8d:0608 MediaTek Inc. Wireless_Device
Bus 001 Device 006: ID 1b1c:0c3f Corsair iCUE LINK System Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 005 Device 003: ID 1b1c:1bc5 Corsair CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard
Bus 005 Device 004: ID 046d:c539 Logitech, Inc. Lightspeed Receiver
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
I do have a mediatek wireless device that could be the source of the problem
I set a shortcut key to turn off my screen (CTL + ALT + S was handy) to make it a quick access. It does mean if anything even slightly perturbs your mouse, though, your screen will turn back on. But by-and-large, it’s gotten me through the last couple of months.
Now I will switch to disabling BT. Sorry that it isn’t an acceptable workaround for you.