Plasma 5.23 Picking Up Latest Breeze Evolution Style, SDDM Lands Native Wayland Support

[kiffmet]

I'm sorry to hear that your experiences are that negative Deleting stuff in the .config folder is not as much work as it sounds like. Simply omit all the stuff you absolutely have to keep (i.e the autostart and systemd folder) and delete everything else. You'd have to reconfigure your desktop once more (which I understand is the most annoying when you have a lot of customization going on), but I think the chances are good that it "just works" after that.
If you backup the whole folder to another location before doing that, there is also zero risk of loosing important stuff. You can always selectively restore individual configs or the whole folder from the backup, in case things still don't work properly. Deleting ~/.cache when a new plasma release comes out can aid things to run smoothly aswell.

[bug77]

bug77 Have a look at what kscreen-doctor can do, as it seems like it can load and apply kscreen config files. Maybe you can utilize this in a little bash script that gets loaded at autostart as a workaround.

I wish that would solve my issues. But I have others, real deal breakers

Also, there is no proper per-screen DPI in multi-monitor setups yet, only per screen scaling, which behaves differently.

I guess these two were the same in my mind, but I see your point now.

That bug with the desktop background is weird and it didn't happen to me, despite I also switched from xorg to wayland.

This doesn't relate to switching from X to Wayland, it happens when I simply stick to X. It's been doing it for quite a few releases already. I can set the wallpaper again, it's just getting tiresome. For added bonus, now it decided to also remove some widgets I spent a lot of time to configure (because several releases ago someone decided to make them nearly unusable by default). And yes, I thought about cleaning up the configuration a little, but good luck doing that with config files all over .config folder.

[pereiraalex]

About DPI, KDE doesn't even pick that up correctly. I have one monitor set at 100%, the other at 125%. Lo and behold, they both use 100% at startup. Only if I go to the display panel to change DPI by hand does it pick up the correct ratio. Still a looong way to go

Strange, it works nicelly for me: 2 2560x1440 monitors + 1 1920x1080, which i put at 75% ( making 3 monitors at 2560x1440 ) and it always reminds it and configures it correctly at every boot or logout/login.

[kiffmet]

bug77 Have a look at what kscreen-doctor can do, as it seems like it can load and apply kscreen config files. Maybe you can utilize this in a little bash script that gets loaded at autostart as a workaround. Also, there is no proper per-screen DPI in multi-monitor setups yet, only per screen scaling, which behaves differently.

That bug with the desktop background is weird and it didn't happen to me, despite I also switched from xorg to wayland. Should this bug stick, then you could try deleting some files in your ~/.config folder - this is usually a remedy for issues introduced by different config file revisions… I encountered some bugs aswell:

I.e the mouse cursor became invisible in title bars and when it should show the icon for resizing windows. In the end, I figured out that custom cursor designs are broken atm and the only cursor design working is the breeze cursor (deleting some ~/.config files came to the rescue). But as long as it's just theme issues, I can bear with it.

Other than that I noticed that GTK apps don't support the global appmenu plugin on Plasma Wayland because they used to store that information as an Xorg window property and there is no Wayland protocol to replace that (tolerable for me as the only affected application that I use is Firefox).

Latte dock got some issues with the right click context menu and the popup that shows the windows opened by a program disappearing before I can click on anything, which is by far the most annoying bug I've encountered.

Thankfully, some of the bugs are mitigatable by applying some elbow grease, but overall 5.22 is the first version of Plasma on Wayland that's actually usable for me which IMO indicates that we're at least 95% there. I will report any weird behavior I've encountered on the KDE bug tracker and I am in good faith that these will get resolved (some maybe even before Plasma 5.23). Would I have hoped for a cleaner experience? Yes, absolutely but I attribute most of the issues to Wayland requiring devs to work around its restrictive design, either by using hacks or by proposing new protocols (which takes time).

[darkbasic]

I've come to consider Michael's "this new KDE version features vastly improved Wayland support" as sarcasm or twisting the knife in the wound

Me either. This or he never actually tried Plasma on Wayland.

[bug77]

bug77 yeah there is still a lot of room for improvement. I think, everything defaults to 96DPI atm. Being able to manually specify per monitor DPI within the screen settings would make a lot of sense. My main monitor is 2560x1440 24''. I could use a secondary monitor which is 24'' aswell, but only 1920x1080. currently, there is no way to make KDE's screen management understand that both screens have the same physical size

But that's just the problem: I've already told it to use different DPI per screen. It just doesn't do that on startup, it needs me to go in and alter the settings again.
And there are other, more "in your face" bugs too. E.g. on update to Plasma 5.22 it shows me the default wallpaper, even if I can go in the settings files and see my old wallpaper is still listed in there. Switching between X and Wayland also breaks a number of things.

All things considered, I'm happy with KDE on X and I've come to consider Michael's "this new KDE version features vastly improved Wayland support" as sarcasm or twisting the knife in the wound.

[kiffmet]

bug77 yeah there is still a lot of room for improvement. I think, everything defaults to 96DPI atm. Being able to manually specify per monitor DPI within the screen settings would make a lot of sense. My main monitor is 2560x1440 24''. I could use a secondary monitor which is 24'' aswell, but only 1920x1080. currently, there is no way to make KDE's screen management understand that both screens have the same physical size

[bug77]

I'll just leave this here for people who would like a good single-monitor highdpi experience on Plasma w/ Wayland. You'll need two scripts. The first one sets the DPI for Xwayland - replace 123 with your monitor's DPI, make the script executable and add it to your autostart as a program:

#!/bin/bash
[ "$XDG_SESSION_TYPE" == "wayland" ] && echo "Xft.dpi: 123" | xrdb -merge - ;

The second one sets up QT and GTK scaling under Wayland. Save it under ~/.config/plasma-workspace/env/dpi.sh and make it executable. Again, replace 123 with your monitor's DPI. GTK_DPI_SCALE is calculated the following: realDPI/96:

[COLOR=#000000]#!/bin/bash [/COLOR]
[COLOR=#000000][ "$XDG_SESSION_TYPE" == "wayland" ] && export QT_WAYLAND_FORCE_DPI=123 && export GDK_DPI_SCALE=1.28125[/COLOR]

You can omit the last && and move the GDK_DPI_SCALE declaration into a new line if you also want it to get set under Xorg:

[COLOR=#000000]#!/bin/bash [/COLOR]
[COLOR=#000000][ "$XDG_SESSION_TYPE" == "wayland" ] && export QT_WAYLAND_FORCE_DPI=123
export GDK_DPI_SCALE=1.28125[/COLOR]

By setting DPI like this, you also work around all QT bugs related to fractional scaling!

About DPI, KDE doesn't even pick that up correctly. I have one monitor set at 100%, the other at 125%. Lo and behold, they both use 100% at startup. Only if I go to the display panel to change DPI by hand does it pick up the correct ratio. Still a looong way to go

[Awesomeness]

Just like the rootless Xorg support was, another big item crossed off a list. Wayland support has got so much better, I think we can be really confident about its state in the foreseeable future (as long as hopefully no dev jumps off the ship).

Wayland support is in development since 2014. It took almost exactly seven years! https://github.com/sddm/sddm/pull/153

Its maintainers are too lazy to merge done Pull Requests (since since 2019): https://github.com/sddm/sddm/pull/1220

If they don't care for sddm any longer, fine. Onboard some new people and hand them admin status. But with this attitude, there is no way sddm can grow its developer base, let alone transition to new hands.

LightDM is in better shape, despite the CLA thing and Canonical not even using it any longer.

[doomie]

Plasma 5.22.1 with Wayland will now detect additional screens when using a multi-GPU setup.

Yesssss!

hear hear!
login screen no longer requiring X was inevitable, but still glad that's here too now. :3
now when do i get to set a custom screen res, as in other compositors, without compiling EDID files?
inb4 "nobody uses that feature, ur stupid for wanting it, y not do EDID, gNoMeIsMoRbEtTrReR" but sway bothered with it, so somebody must be using it besides just me.