Bug 466228 - Black screen when changing from X11 to Wayland or vice-versa
Summary: Black screen when changing from X11 to Wayland or vice-versa
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (show other bugs)
Version: 5.27.1
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-22 03:39 UTC by Doug
Modified: 2023-02-23 03:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.27.1

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Doug 2023-02-22 03:39:12 UTC 
SUMMARY
***
I tried to change from a Wayland to an X11 session and when logging back into the X11 session, all I got was a black screen.  I was able to drop to TTY, reboot and start in X11.  I logged out of X11 and changed to Wayland.  Got a black screen.  Repeated a couple times, it is consistent.
***


STEPS TO REPRODUCE
1. login to a plasma session, either X11 or Wayland
2. log out
3. change display server from drop down menu
4. log in to the new session

OBSERVED RESULT
black screen

EXPECTED RESULT
plasma desktop starts up

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: AMD Radeon Pro WX 3200 Series
Manufacturer: Dell Inc.
Product Name: Precision 7540

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2023-02-22 21:43:22 UTC 
Can you include output of journalctl --user -b after reproducing this issue
Comment 2 Doug 2023-02-23 03:13:47 UTC 
(In reply to David Edmundson from comment #1)
> Can you include output of journalctl --user -b after reproducing this issue

I can no longer reproduce the issue.  I did get an update today- plasma-desktop 5.27.1-2.  Maybe that fixed it?
Comment 3 Nate Graham 2023-02-23 03:41:38 UTC 
Ok, great news! Let's say it did.

Feel free to re-open this bug report if you see the issue again, though.