[yjftsjthsd-h]

> The X11 protocol remains fully supported using the XWayland back end.

And they already got rootful xwayland, so if you want to keep using X11 all this means is that you have to replace one X server with another.

[slondr]

Do XWayland programs still scale incorrectly when using dpi scaling in wayland? This thwarted my last serious attempt to switch to sway.

[clhodapp]

If your frustration was that x11 apps are really blurry then: Yes, unless you use kwin as your compositor and tell it to let x11 apps scale themselves.

[slondr]

KDE on Wayland does not even launch when my e-gpu is plugged in, so, with that in mind, I guess I'll be sticking with X11 for the foreseeable future.

[clhodapp]

Ah, I'm not surprised, sadly: KDE has been buggy for me in so many ways ever since they made Plasma...

[akvadrako]

Gnome also supports this; it's how I have it configured.

[Gigachad]

Only if you have two monitors at different DPI scales which is impossible on x11 iirc.

[destructionator]

You can do it with client side scaling in X (which is also the preferred solution on systems like Windows, since an application can scale itself better than a generic compositor anyway).

[slondr]

Hmm, how does that work if you move clients around between displays?

[destructionator]

The client is given an XConfigureEvent when it is moved and can compare it against the monitor's bounding boxes (which it caches in between xrandr change notifications) and rescale itself.

Doesn't work with legacy applications... but neither does Wayland so you aren't really behind.