Op 09-03-2021 om 21:25 schreef Fabian Vogt:
Hi,
Am Dienstag, 9. März 2021, 16:47:24 CET schrieb Adrien Glauser:
Fabian, your package
Why are you trying to make this a personal issue now?
diverge from the "pure, unpatched, not reconfigured" plasma-workspace produced upstream. *That* upstream package is our test target, to justify the extent to which we need to diverge:
Honestly, the tone of that statement doesn't sit well with me.
- if the upstream package is satisfying to the user, it should be the one shipped to oS distros; and - if it's not, you'll be able to extrapolate from the feedback we'll get you whether GDK_BACKEND & QT_QPA_PLATFORM should be set to some value (as opposed to left alone), and also which specific value to set them to (if at all).
Top priority (at least for me) is user experience. It's what finally counts.
Also Fabian, would be willing to create this package on Factory, while we announce a time window for the community to try it, with guidelines as to how participate to the test?
I already proposed a way how to do the relevant tests easily, without any package changes on the system. So far you dismissed that and also the reasons the split sessions exist in the first place. That way there's no common ground, which is key to a proper discussion.
Here's an untested (!) project with just a single "Plasma (Wayland)" session: https://build.opensuse.org/project/show/home:Vogtinator:lessxwl After adding, install with "zypper dup --from lessxwl --allow-vendor-change". Might need Plasma 5.21.2, which TW so far couldn't pick up. I have to repeat that this is not the method for testing I recommend.
If so, I'd be happy to take care of the announcement post on news-o-o, if you can make the test build. Then I'd send you my text so that you can check it out for bias risks, and after your validation I'd post it to news-o-o.
Does that look like a fair deal for you?
AFAICT, we're on the same side, we just differ in the view on how to approach this. That really has to be cleared up first. Please also look at the side of the discussion which isn't yours.
Cheers, Fabian
If I understand correctly the two options of "Plasma Wayland" and "Plasma Full Wayland" are an all or nothing approach: at login the default is set for all applications. I can see this is good for testing, but in normal use it gives problems. At least, as far as I can see. An application like zotero (for working with bibliographies, www.zotero.org) does not have wayland support. In Full Wayland it does not start. It took me some time to find the workaround, setting GDK_BACKEND=x11 explicitly before executing this app. I did a test and removed GDK_BACKEND=wayland from plasmafullwayland in /usr/share/wayland-sessions. I don't know what this means and what is set for GDK_BACKEND in that case, but I saw that firefox worked better than with the old GDK_BACKEND=wayland setting. Because of bug [1] firefox is unusable in full wayland, but starting the the changed plasmafullwayland the bug is not there. Maybe it is because x11 is used, but looking at /usr/lib64/firefox/firefox.sh it tests for a wayland session. I don't know how useful this observation is, I am far from an expert and find it all a bit confusing, but who knows. :) Regards, Cor [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1660567