On Thu, Sep 10, 2020 at 12:58 PM Neal Becker <ndbecker2@xxxxxxxxx> wrote: > Might be interesting to try logging in as a new user to see if some older kde settings are messing things up. That's definitely possible... However this is a single-user machine and I don't really feel like creating a new user :) If I find some time I'll try it on my other laptop and/or dig deeper... > > On Thu, Sep 10, 2020 at 6:24 AM Ondrej Mosnacek <omosnace@xxxxxxxxxx> wrote: >> >> On Tue, Sep 8, 2020 at 5:30 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote: >> > https://fedoraproject.org/wiki/Changes/WaylandByDefaultForPlasma >> > >> > == Summary == >> > Change the default session selection in SDDM to prefer the >> > Wayland-based KDE Plasma Desktop session over the X11-based one. >> > >> > == Owner == >> > * Name: [[User:Ngompa|Neal Gompa]], [[User:Rdieter|Rex Dieter]], >> > [[User:Jgrulich|Jan Grulich]] >> > * Email: ngompa13@xxxxxxxxx, rdieter@xxxxxxxxx, jgrulich@xxxxxxxxxx >> > * Product: KDE Spin >> > * Responsible WG: KDE SIG >> > >> > >> > == Detailed Description == >> > >> > With KDE Plasma 5.20, the KDE Plasma desktop environment has reached a >> > point where nearly all commonly used features in the desktop and all >> > major applications function in the Plasma Wayland environment on all >> > major GPUs (including NVIDIA with the proprietary driver). Starting >> > with Plasma 5.20 in Fedora 34, we will change the default >> > configuration for Wayland and X11 Plasma sessions so that Wayland is >> > preferred and used by default, while permitting the X11 session to be >> > selected as the alternative desktop environment option. >> > >> > == Feedback == >> > >> > ==== Is Wayland ready? ==== >> > Wayland has been used by default for Fedora Workstation (which uses >> > GNOME) since Fedora 25. And while it was somewhat immature initially, >> > today it is a very rock-solid experience on virtually everything >> > Fedora Workstation runs on. The change in Fedora 25 kickstarted the >> > drive to get everything working on Wayland, and the Workstation team >> > succeeded beyond their wildest dreams. Firefox has been Wayland-native >> > by default since Fedora 31 as well. >> > >> > On the KDE side, serious work into supporting Wayland started shortly >> > after GNOME switched to Wayland by default. Unlike GNOME, KDE has a >> > much broader stack in its toolkit, and it has taken longer to get to a >> > usable state. With the Plasma 5.20 release, the Wayland protocol for >> > screencasting as well as middle-click paste finally are supported, >> > completing the required feature set for switching to Wayland by >> > default. >> >> So yesterday I tried to log in to the KDE Plasma + Wayland session on >> my laptop (F32) and the experience was unfortunately quite horrible... >> >> 1. When I logged out of the X session, switched to Wayland on the >> login screen, and logged in, I only got a black screen. After I >> rebooted, I managed to login to the Wayland session (I have automatic >> login after boot enabled), but... >> 2. The desktop was all squeezed into a small 1024x786 rectangle in the >> upper left corner of the screen (my screen is 1920x1080). So I opened >> system settings to change the resolution, but... >> 3. The screen settings were showing "manufacturer_TODO" and >> "model_TODO" as the name of the screen and the only resolution offered >> was 1024x786. >> 4. The window layout of my KDE session was not preserved (I think even >> the distribution of windows to activities was lost). But I probably >> shouldn't expect this to work... >> 5. Logging out of the Wayland session gave me just a black screen with >> blinking cursor, no login screen. >> >> Reading the other posts in this thread it seems I'm the only one >> experiencing such serious breakage (maybe except 4., which is >> understandable), so I'm wondering if I did something wrong... I simply >> installed plasma-workspace-wayland, logged out, and then logged in >> selecting "Plasma (Wayland) (Wayland)" from the session dropdown. >> >> -- >> Ondrej Mosnacek >> Software Engineer, Platform Security - SELinux kernel >> Red Hat, Inc. >> _______________________________________________ >> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > > > > -- > Those who don't understand recursion are doomed to repeat it > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx -- Ondrej Mosnacek Software Engineer, Platform Security - SELinux kernel Red Hat, Inc. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
