Bug 448434 - Black screen after suspend, hibernate, or visiting a system console
Summary: Black screen after suspend, hibernate, or visiting a system console
Status: RESOLVED DUPLICATE of bug 447647
Alias: None
Product: Planet KDE
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Ranveer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-14 02:28 UTC by kdbase-kdebug
Modified: 2022-01-15 02:03 UTC (History)
1 user (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 kdbase-kdebug 2022-01-14 02:28:05 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Log into KDE Plama
2. Leave the session temporarily, either with system suspend or hibernate, or entering, for example, ctrl-alt-f4 to use a system console.
3. Return to the plasma session, either by waking up from suspend or hibernate, or entering alt-f1 to go back from a virtual console.

OBSERVED RESULT
The screen is all black.  I cannot get the session back.  If I open a system console with ctrl-alt-f4, I can kill the processes in the session and try again, although I normally log into a different DE, GNOME in my case.

EXPECTED RESULT
Return to plasma shell, with all state properly restored (if necessary).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.23.90, in Arch Linux
(available in About System)
KDE Plasma Version: 5.23.90
KDE Frameworks Version: ?? I don't know
Qt Version: 5

ADDITIONAL INFORMATION
I have seen this problem referenced elsewhere.  It's been present for a number of months.  I thought it might be fixed in 5.24.  Arch Linux released the beta of 5.24 today, and I checked to see if it was fixed, but the problem is still present.

My processor is from AMD.  The graphics chip is radeon.

The problem is similar to the report for bug 447647, and may well be a duplicate.
Comment 1 Nate Graham 2022-01-14 23:27:18 UTC
Could be, yeah. Are you using the Wayland session, or the X11 session?

If you're using the Wayland session, feel free to mark this as a duplicate of Bug 447647, answer the question there, and set the status to REPORTED.

Thanks!
Comment 2 kdbase-kdebug 2022-01-15 02:00:56 UTC

*** This bug has been marked as a duplicate of bug 447647 ***
Comment 3 kdbase-kdebug 2022-01-15 02:03:35 UTC
The session was indeed Wayland, so, following Nate's instructions, I am marking this as a duplicate.