Ok, not every single document. Just every single document you find doing a google search. I guess google search doesn’t look in private mailing lists. Who knew?
Anyway, thanks for letting me know it’s still available. Just not thru SDDM, where the only two options are Wayland and IceDM.
Guess finding out how to get SDDM to show an option for X11 is left as an exercise for the reader.
Congratulations.
I don’t.
After the upgrade, I have Wayland and IceDM, and the X11 option is gone. Still, I guess my system is outright lying, and the X11 option is still there, just cropped from the screen, hidden, and inaccessable. Because it’s nonsense to believe my own eyes.
Try:
zypper in plasma6-session-11
erlangen:~ # zypper in plasma6-session-x11
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
kwin6-x11 plasma6-session-x11
2 new packages to install.
Overall download size: 576.6 KiB. Already cached: 0 B. After the operation, additional 1.8 MiB will be used.
Continue? [y/n/v/...? shows all options] (y):
Retrieving: kwin6-x11-6.0.2-1.1.x86_64 (Haupt-Repository (OSS)) (1/2), 495.1 KiB
Retrieving: kwin6-x11-6.0.2-1.1.x86_64.rpm .............................................................................................................................................................................[done (495.1 KiB/s)]
Retrieving: plasma6-session-x11-6.0.2-1.1.x86_64 (Haupt-Repository (OSS)) (2/2), 81.5 KiB
Retrieving: plasma6-session-x11-6.0.2-1.1.x86_64.rpm ....................................................................................................................................................................[done (81.5 KiB/s)]
Checking for file conflicts: .........................................................................................................................................................................................................[done]
(1/2) Installing: kwin6-x11-6.0.2-1.1.x86_64 .........................................................................................................................................................................................[done]
update-alternatives: using /usr/share/xsessions/plasma6.desktop to provide /usr/share/xsessions/default.desktop (default-xsession.desktop) in auto mode
(2/2) Installing: plasma6-session-x11-6.0.2-1.1.x86_64 ...............................................................................................................................................................................[done]
Running post-transaction scripts .....................................................................................................................................................................................................[done]
erlangen:~ #
This is common wisdom among seasoned Tumbleweed users, but maybe the following sentence from
https://en.opensuse.org/Portal:Tumbleweed
Rolling release means no updates, only urgent patches and upgrades
When updating Tumbleweed, you can use YaST or the system update applet just as on Leap.
is not (always) correct.
I was countering your nonsense statement…
Prove it. Every single document says Plasma 6 will NOT support X11…
I think you now realize that your environment is not complete. Refer to nrickert’s subsequent advice.
JFYI: 1221405 – plasma5-workspace -> plasma6-workspace upgrade kills running session, which hopefully will be fixed soon: Request 1158726: Submit libplasma6 - openSUSE Build Service
See, all of you blaming Plasma6, there are people at work on Sunday afternoon to solve ya problems 
I had the same problem. System got message up and broke while in the middle of the update. It failed and then performed a reboot. I got some error I was not able to login, because some file was missing. I noticed from the login screen I could pick Waylan. This is how I was able to login, my screen was black but luckly I could use my hotkey to open the terminal and browser.
I found out zypper had been deleted (2nd time buring updates). So I installed it using a RPM from the terminal and then I performed ‘zypper dup’ multiple times rebooting in between to complete the update.
Finally from the login screen, I was able to switch back to X and everything was working fine for me. Wayland is no were closed to ready for use.
Here are my posts asking for help that might help others:
My main problem has been:
You can block updates of certain applications using the “lock package” function - applying “al” to a package prevents changes to that package.
Good luck with locking all involved Plasma 5 packages…
This is true! 
Done it with all akonadi and Plymouth packages…
If you block anything marked Plasma5, then all packages where it needs to be upgraded to validate their upgrade, methinks you’re not far from success
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.