Bug 501995 - Putting system back to sleep from screen locker after wake from suspend results into a permanent black screen
Summary: Putting system back to sleep from screen locker after wake from suspend resul...
Status: RESOLVED DUPLICATE of bug 500816
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 6.3.3
Platform: Other Linux
: NOR grave
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-25 18:52 UTC by Kalzi
Modified: 2025-04-23 20:34 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kalzi 2025-03-25 18:52:08 UTC
SUMMARY
Put system to sleep/suspend normally from the Application Launcher, wake it up, click on the "suspend" button in sddm then wake it up again to log in, causes a permanent black screen. Not sure if this makes sense, but it happens on every single distro I have ever run, so that tells me it is either a plasma issue or an sddm one. Not sure. At that point, not even tty would should up. Nothing, just permanent black screen. I would then half to force the pc off by holding down the power button. This worries me that I may just corrupt my ssd one day. 

STEPS TO REPRODUCE
1. Put system to sleep/suspend normally from the Application Launcher
2.  wake it up
3.  click on the "suspend" button in sddm
4. wake it up again to log in

OBSERVED RESULT
Permanent black screen

EXPECTED RESULT
To log in normal

SOFTWARE/OS VERSIONS
Operating System: Nobara Linux 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-200.nobara.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: A520I AC
System Version: -CF

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-03-26 15:39:26 UTC
Cannot reproduce on git master.

Do you have multiple monitors? If so, this may be Bug 494262.
Comment 2 Kalzi 2025-03-26 15:44:02 UTC
(In reply to Nate Graham from comment #1)
> Cannot reproduce on git master.
> 
> Do you have multiple monitors? If so, this may be Bug 494262.

Yes, I do have two monitors. The bug you have linked mentions that they lose one monitor and are able to use the second one. I lose both, and I can't even log in anymore. The only way I can get back into my system is by holding down the power button to force it off.
Comment 3 Nate Graham 2025-03-31 18:52:07 UTC
Does the black screen have a cursor you can use?

On the black screen, if you type Alt+Space, does KRunner come up?
Comment 4 Kalzi 2025-03-31 23:56:52 UTC
(In reply to Nate Graham from comment #3)
> Does the black screen have a cursor you can use?
> 
> On the black screen, if you type Alt+Space, does KRunner come up?

No and no. I don't have any cursor or any activity at all. Just plain black screens. I can't even get into a tty. Only solution is holding the power button down to shut it off.
Comment 5 Nate Graham 2025-04-03 19:28:40 UTC
Thanks. That sounds quite bad.
Comment 6 Kalzi 2025-04-03 20:38:30 UTC
(In reply to Nate Graham from comment #5)
> Thanks. That sounds quite bad.

It is bad, if I forget to log in then suspend the system from the desktop instead of SDDM, which I've learned not to forget :)
Comment 7 TraceyC 2025-04-23 20:34:17 UTC
Based on the steps to reproduce and the symptoms, this looks like bug 500816. I'm marking this as a duplicate of that once, since it has developer involvement. Please follow the other report for updates.

*** This bug has been marked as a duplicate of bug 500816 ***