Bug 511811 - No display when computer wakes up from sleep
Summary: No display when computer wakes up from sleep
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.5.0
Platform: CachyOS Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-08 08:45 UTC by AFS
Modified: 2025-12-30 08:02 UTC (History)
4 users (show)

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


Attachments
kscreen_doctor (1.71 KB, text/plain)
2025-11-26 18:21 UTC, AFS
Details
drm_info (123.27 KB, text/plain)
2025-11-26 18:21 UTC, AFS
Details
drm_info 2 (215.02 KB, text/plain)
2025-12-21 13:39 UTC, Lorenz Hoffmann
Details
kscreen_doctor 2 (2.91 KB, text/plain)
2025-12-21 13:41 UTC, Lorenz Hoffmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description AFS 2025-11-08 08:45:08 UTC
SUMMARY
When the computer goes to sleep, there is no display after I wake it up.

STEPS TO REPRODUCE
1. Let the computer go to sleep 
2. Move the mouse / press a key to wake it up

OBSERVED RESULT
The monitor remains black. It detects however that "something" happened since the integrated screen saver of the monitor (LG 42" TV) stops, but there is nothing on display.

EXPECTED RESULT
The monitor should display the lock screen.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel version : 6.17.7-3-cachyos

ADDITIONAL INFORMATION
This started to happen after the upgrade to Plasma 6.5.
Comment 1 TraceyC 2025-11-25 22:11:18 UTC
Thanks for the bug report. Can I ask you what graphics card is installed in the system?
If it's NVIDIA, are you using the open or closed source drivers?

Also, can you get the output of this command, when the display is working properly and when the bug happens? Please either paste the two outputs in the report or attach as text files.

kscreen-output -o

Finally, please also attach the output of drm_info as a text file after triggering the issue. Thanks.
Comment 2 AFS 2025-11-25 23:18:18 UTC
(In reply to TraceyC from comment #1)
> Thanks for the bug report. Can I ask you what graphics card is installed in
> the system?
> If it's NVIDIA, are you using the open or closed source drivers?
> 
> Also, can you get the output of this command, when the display is working
> properly and when the bug happens? Please either paste the two outputs in
> the report or attach as text files.
> 
> kscreen-output -o
> 
> Finally, please also attach the output of drm_info as a text file after
> triggering the issue. Thanks.

Hello.

I have an RTX 4090 with the latest Nvidia-open-dkms drivers 580.105.08.

I can't provide any of the outputs you request however : 
- both kscreen-output -o & drm_info are unknown commands
- even if they were recognized, I wouldn't be able to type anything when the bug happens, as there is no display.
Comment 3 TraceyC 2025-11-26 16:58:49 UTC
Sorry for the typo, the first command should be

kscreen-doctor -o

If you can get to a TTY with Ctrl+Alt+F4 you should be able to run that, and pipe it to a file

kscreen-doctor -o > ~/kscreen.txt

On my system, drm_info is here:
/usr/bin/drm_info

You probably just need to install the drm_info package.
Comment 4 AFS 2025-11-26 18:21:26 UTC
Created attachment 187196 [details]
kscreen_doctor
Comment 5 AFS 2025-11-26 18:21:37 UTC
Created attachment 187197 [details]
drm_info
Comment 6 AFS 2025-11-26 18:22:39 UTC
Unfortunately I still can't do anything when I wake the computer from sleep. Even trying to go "blind" by switching TTY and typing the commands you provided, it doesn't output anything. I have a feeling that it's not just a display issue, the PC seems to be completely frozen. I can trigger something vaguely similar by locking my session and trying to switch user : when I type my password on the lock screen, the PC freezes - but I still have a working display.

Anyway, I've attached the kscreen and drm_info logs prior to the crash, I don't know if they will be of any help.
Comment 7 Lorenz Hoffmann 2025-12-21 13:39:15 UTC
I think I'm having the a similar issue, but my setup is a bit different. I have 2 monitors, one connected to a Nvidia RTX 2080 and one to the graphics chip in my AMD CPU. I am using the non-opensource nvidia drivers. After wake-up from sleep, the main monitor connected to the nvidia gpu remains black while the other one works normally. On ctrl+alt+F4, I can see the terminal on the main one. Switching back leaves me with both displays showing the lock screen.

I'll attach the output of the commands here.

System info:

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.17.12-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 2080
Graphics Processor 2: AMD Ryzen 5 7600X 6-Core Processor
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650 EAGLE AX
System Version: -CF
Comment 8 Lorenz Hoffmann 2025-12-21 13:39:50 UTC
Created attachment 187845 [details]
drm_info 2
Comment 9 Lorenz Hoffmann 2025-12-21 13:41:03 UTC
Created attachment 187846 [details]
kscreen_doctor 2

Output from tty showed an error that something with xcb cursor is not installed, so this is the output from a running plasma session.
Comment 10 BOF 2025-12-25 22:15:29 UTC
I'm not sure whether my case is connected to this issue, but it sounds similar to my problem.

After some time of not using my PC it does not respond to user inputs. The screen stays dim, sometimes with a black background (but I think the black background was because of the YouTube video that played, ended and then was just the black screen at the very end of the video).

The system does not respond to any user input. The only thing that works for me is closing the lid of my laptop and opening it again.
I set my system to not do anything when the lid is closed. I also disabled any shotdown or energy saving mode when inactive. The only thing that happens is that the screen is turned off after 30 minutes.

This is behaviour is something very new that seems to have come up with the last update. Since the last update the system also feels noticeable slower and less reactive in multiple apps (webbrowser, libreoffice, etc.).

System Information:
- Operating System: KDE neon User Edition
- KDE Plasma Version: 6.5.4
- KDE Frameworks Version: 6.21.0
- Qt Version: 6.10.1
- Kernel Version: 6.14.0-37-generic (64-bit)
- Graphics Platform: Wayland
- Processors: 12 × AMD Ryzen 5 7530U with Radeon Graphics
- Memory: 32 GiB of RAM (29.2 GiB usable)
- Graphics Processor: AMD Radeon Graphics
- Manufacturer: LENOVO
- Product Name: 21KK
- System Version: ThinkBook 16 G6 ABP
Comment 11 merchamion 2025-12-30 08:01:53 UTC
I think I have a similar issue, after waking up the panel is broken. I still see any open windows. I can get it back after restarting plasmashell from terminal (konsole)

plasmashell --replace
Comment 12 merchamion 2025-12-30 08:02:40 UTC
(In reply to merchamion from comment #11)
> I think I have a similar issue, after waking up the panel is broken. I still
> see any open windows. I can get it back after restarting plasmashell from
> terminal (konsole)
> 
> plasmashell --replace