Bug 515416 - System is non-responsive / hangs when attempting to return from automatic sleep/suspend
Summary: System is non-responsive / hangs when attempting to return from automatic sle...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.5.5
Platform: openSUSE Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-02 08:30 UTC by kde.sleeve173
Modified: 2026-02-02 09:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde.sleeve173 2026-02-02 08:30:24 UTC
SUMMARY
Trying to wake system from automatic sleep (suspend) following user-determined period of inactivity leads to no response or waking; screen remains black and no keyboard or mouse inputs cause this to change; shutdown button does not shut down system, force shutdown is necessary. This has been happening for a couple months now.

STEPS TO REPRODUCE
1. Allow system to automatically go to sleep (suspend)
2. Wait a moment, then attempt to wake the system through keyboard input
3. Screen remains black, no signs of response or waking from system

OBSERVED RESULT
Non-responsive, black screen, shutdown button does not shut down system, while all hardware is still on and active.

EXPECTED RESULT
Show lock screen.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20260123, kernel 6.18.6-1-default
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Comment 1 kde.sleeve173 2026-02-02 08:32:39 UTC
ADDITIONAL NOTES: Not even hotkeys to change to TTL do anything. No combination of keyboard inputs wake the screen from black.
Comment 2 Akseli Lahtinen 2026-02-02 08:45:56 UTC
I have similar issue but I manage to solve it by unplugging and replugging PC monitor.

Do you use DisplayPort monitor by chance? Or is this with a laptop?

Operating System: KDE Linux 2026-02-01
KDE Plasma Version: 6.6.80
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.18.7-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 6600
Comment 3 kde.sleeve173 2026-02-02 08:58:27 UTC
(In reply to Akseli Lahtinen from comment #2)
> I have similar issue but I manage to solve it by unplugging and replugging
> PC monitor.
> 
> Do you use DisplayPort monitor by chance? Or is this with a laptop?
> 
> Operating System: KDE Linux 2026-02-01
> KDE Plasma Version: 6.6.80
> KDE Frameworks Version: 6.23.0
> Qt Version: 6.10.2
> Kernel Version: 6.18.7-zen1-1-zen (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
> Memory: 16 GiB of RAM (15.5 GiB usable)
> Graphics Processor: AMD Radeon RX 6600

Hi. This is with a laptop, but I have this issue both when using the internal monitor and when connected to an external monitor. I use HDMI 2.0.
I tried unplugging the external monitor the most recent time this happened, as normally this would reenable and switch to the internal monitor, but it does nothing in this case.
I vaguely remember once the lock screen reappearing on the external monitor but not the internal monitor when I had both enabled, strangely enough, but I haven't tried reproducing this.
I also currently have the integrated graphics (Optimus) disabled, but this problem has been happening for a while, with plasmashell/kwin_wayland doing this when I had Optimus enabled as well.
I have not tried seeing if the issue exists on X11.

As a temporary solution I have disabled automatic suspend when plugged in.

Do you have any idea what might be causing the issue on your end? It sounds like this might be a bug we both have. Not sure with what though.

Operating System: openSUSE Tumbleweed 20260131
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 32 × Intel® Core™ i9-14900HX
Memory: 16 GiB of RAM (15.4 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4060 Laptop GPU
Comment 4 Akseli Lahtinen 2026-02-02 09:41:05 UTC
> Do you have any idea what might be causing the issue on your end? It sounds
> like this might be a bug we both have. Not sure with what though.
> 
>

In my case I have desktop PC tower. I have a feeling it might be a driver bug, but I will have to investigate it proper. 
What I have noticed is that powercycling the monitor fixed the issue until PC is rebooted. To me it feels like the driver/something is unable to restore power to the display normally.

I will try to investigate it further. Will set this as confirmed for now.