Thanks, I will thoroughly test if that helps.
Does anyone know it this issue has been addressed in Linux kernel 6.12? I am currently running Linux kernel 6.12.6 on a Fedora 41, KDE Plasma 5.2.4 laptop, and I still have this issue. Now to add a little context: I will start my machine at the start of the day, and be able to sleep/wake up many times with no problems only to have the issue appear later on. Thanks of any information and I hope this helps some.
/Mike
I discovered I can consistently get the screen to power on, in relation to my issue which I think is related to this one: Critical behaviour after suspension - #3 by Samuele
When the screen becomes totally black, I can lock the Plasma with a keyboard shortcut, then I can hit “Esc”: the screen flashes on, I can hit “Esc” again and it turns on. Clicking “Esc” again turns it off and so on. But this does not solve my problem: the screen shortly starts again to raise the brightness to the maximum and loop back to the minimum faster and faster until it becomes totally black.
The shortcuts for TTY for me do not work.
Running ArchLinux, the problem has been fixed in Kernel 6.12.8. So in case your issue is the same, it should have been fixed.
In the Arch forum, someone has narrowed down the issue to the mt7921e chip (mine is mt7921k) in combination with certain Linux versions, I guess. So either using an older Kernel (or lts in case of Arch) or disabling Bluetooth could be a workaround.
Anyway, as I said, Linux 6.12.8 has finally fixed the issue in my case.
1 Like
Just my 2 cents. Maybe not immediately relevant in this case, but it is one of the causes for BSOD / weird behaviour after wakeup:
I would check the size of the swap partition / file. If you plan to use hibernate, the size should be the same as the RAM. Thus, if you have 16 GB, you need to ensure that your swap is at least this big.
The reason for that is obvious, as what you do when putting your laptop to “sleep” is also called “suspend to RAM” and it basically just copies all what’s in your RAM to the swap partition or file.
I saw my problem appear again when disconnecting the laptop from the charger, so it seems to be a power management issue.
Arch Linux
Still seeing this after updating to 6.12.8. :\
My machine has WiFi, but it’s never been used as I only use Ethernet. Not exactly sure of my chipset, but lspci reports
Network controller: Intel Corporation Cannon Lake PCH CNVi WiFi (rev 10)
For months now I’ve been using a certain sequence I’ve learned through trial and error to regain control of my desktop session.
When I wake my machine up, I’ll blindly enter my password and hit enter. I can now see my mouse cursor over top a black screen. Then I login to a different TTY and issue
DISPLAY=:0 kwin_x11 --replace
Then go back and I can watch my desktop sesssion slowly recover itself. Every now and then it doesn’t completely recover and I’ll issue
systemctl restart --user plasma-plasmashell.service
After that, I’m back in business, but it’s getting very old.
Guess I’ll try some of the suggestions here to see if anything else works. Really had my fingers crossed that this last update would have fixed it…
You seem to be facing a similar issue caused by something else. Based on your lspci output, it’s a different chipset.
Looking through this thread, it seems that people are facing similar issues with different causes. My computer was completely unresponsive after Wake from Sleep (not being able to switch to any other TTS etc) between Linux Kernel versions 6.11.x and 6.12.7. With 6.12.8, everything went back to normal.
1 Like
I have not observed the problem since then, however I do observe some graphical glitches since then.
It may be worth giving the work around script found Here a try.
Ultra annoying bug that has made me switch to gnome. It’s been there for so long.
I remember it started somewhere after march last year, a couple of months before KDE6.
1 Like
@gibru
Yeah, it seems like a lot of similar problems, but not exactly. I don’t see my specific issue either from what I’ve read, but I’m going to try @jayguerette’s suggestion just to see.
@tcope2112
That looked promising, but powering down my monitor and back on works just fine. I’ll have another look if my first workaround doesn’t workaround.
@kdog1
I feel ya. I come from over a decade of xfce myself and thought I’d give kde a try for some of it’s advanced features. There’s certainly a lot to like, but the more features there are, the more it can go bad. 
Just for reference:
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
The new 570 nvidia driver had this in the notes:
- Disabled a power saving feature on Ada and above generation GPUs
for surfaces allocated with the DRM Dumb-Buffers API, for example,
when using a DRM fbdev. The power saving feature could cause black
screens for DRM Dumb-Buffers which use front buffer rendering instead
of KMS flips.
Does this maybe fix it?
Not sure when I can try it, but the latest on Arch is 565.77-12.
Will report back if something changes.
I just want to add to the context. I have the same problem on Arch Linux. I have all the newest versions including the 570 drivers, Linux 6.13.2 and Plasma 6.2.5. My system had a full system update less than a week ago. This issue seems to come up whenever I suspend/sleep my PC. However, my Hyprland (Wayland) doesn’t have the issue. I am currently on plasmax11 and will test with plasma Wayland.
So it seems like this issue is exclusive to plasmax11 for me, and Wakeup doesn’t produce this problem on Wayland. (I tried only once)
This got me into a frozen desktop. With systemctl restart display-manager it works but there are graphical glitches like the desktop wallpaper is not applied correctly, likely due to resolution changes at one point.
Spoke too soon, it didn’t help. I’ve had this issue in slightly different variations for 5 years now. And outside of using Nvidia on all, on three very different machines (laptop/desktop, intel/amd etc.), so I doubt it’s a hardware issue.