Hi, Am Mittwoch, 31. März 2021, 23:24:59 CEST schrieb Andrés Barrantes Silman:
After testing the lessxwl and differentxwl repos, I think the best approach is lessxwl, especially because Firefox prefers Wayland on that configuration.
That is strange, because the "Full Wayland" session for both is identical (or at least supposed to be). The only difference is that "differentxwl" still offers the "XWayland" session, but by patching Qt (which isn't great).
Both repos were tested for about a week, and I think I'll go back X.Org for now. Telegram (Flatpak) and Firefox crash at least once every two hours,
Do you have a link to the upstream reports or have a backtrace? Do the crashes disappear when you run them with Xwayland? If so, then they are one of the reasons why it's IMO beneficial to have a simple option available which makes those applications use Xwayland. Doing that for the whole session (like it is currently) is indeed not ideal.
and the fact that spanish accent marks are not working on Qt apps (that includes LibreOffice for some reason, probably because the Qt version is the one shipped with Plasma).
Is this using the compose key or just plain dead keys as part of the keyboard layout?
Minecraft worked fine with the Intel GPU, and NVIDIA, of course was NVIDIA, as usual, no need for details. * Minecraft works over XWayland
Either repo was clearly a better alternative than the current implementation.
What made the biggest difference?
Also, the rectangular selection issue with Spectacle has been fixed with the version 20.12.3.
Vivaldi also worked fine on the lessxwl repo, and definitely crashed less than Firefox. (and no, I won't try Edge :p)
The change to either repo was seamless for me; in my opinion we can for the scream test.
Ok, so I propose this: Unless there's an objection in the next few days, we'll send an announcement about this change to the MLs (os-f, os-kde) and ask about any regressions in application behaviour or reliability. When the announcement is out, change the default in qtbase to "wayland;xcb" and drop the "XWayland" session. Based on the (hopefully extensive) feedback on applications, further changes can be discussed, maybe application-specific changes. Cheers, Fabian