Enable Wayland backend on Plasma/KDE by default (#1922608)
Logout Required
After installing this update it is required that you logout of
your current user session and log back in to ensure the changes
supplied by this update are applied properly.
This update has been submitted for testing by stransky.
The openQA KDE browser test fails quite frequently with this update installed. If I restart it enough times it eventually gets through, but it fails a lot. It's failed at different points, though frequently it fails on the download icon not changing after it downloads a file (it expects a little bar to fill up, indicating the download completed).
In general, the bug here says the Wayland backend should be default "on Fedora 34", but I cannot see a difference between the specs for F34/F33/F32, and I cannot see a relevant version conditional in the spec. Did this enable the Wayland backend by default on F33 and F32? If so, that seems wrong.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
I would rather @stransky looked at my comment first. If this goes stable and causes KDE update tests to fail intermittently on future updates it will be a big problem because we are going to start gating updates on tests soon.
Adam, the wayland backend is enabled only when Wayland session is active. KDE does not use Wayland session on Fedora 32/33 so X11 under KDE may be used here. I suspect you see WebRender bugs as WebRender is enabled by default on KDE too. You can set gfx.webrender.force-disabled to false at about:config to force disable WebRender.
Can you please file a bug at bugzilla about the failures and attach a screenshots there?
Thanks.
is there a generic way to set about:config things in e.g. a policies files? it is not at all easy to teach openQA to set something in about:config, it is far easier if I can just write a configuration file. thanks.
This update has been submitted for testing by stransky.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted firefox-88.0-7.fc33, and has inherited its bugs and notes.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
The openQA KDE browser test fails quite frequently with this update installed. If I restart it enough times it eventually gets through, but it fails a lot. It's failed at different points, though frequently it fails on the download icon not changing after it downloads a file (it expects a little bar to fill up, indicating the download completed).
In general, the bug here says the Wayland backend should be default "on Fedora 34", but I cannot see a difference between the specs for F34/F33/F32, and I cannot see a relevant version conditional in the spec. Did this enable the Wayland backend by default on F33 and F32? If so, that seems wrong.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
works well for me
works well for me
no issues
Could we please push this one as f34 is already stable?
I would rather @stransky looked at my comment first. If this goes stable and causes KDE update tests to fail intermittently on future updates it will be a big problem because we are going to start gating updates on tests soon.
Adam, the wayland backend is enabled only when Wayland session is active. KDE does not use Wayland session on Fedora 32/33 so X11 under KDE may be used here. I suspect you see WebRender bugs as WebRender is enabled by default on KDE too. You can set gfx.webrender.force-disabled to false at about:config to force disable WebRender.
Can you please file a bug at bugzilla about the failures and attach a screenshots there? Thanks.
is there a generic way to set
about:configthings in e.g. a policies files? it is not at all easy to teach openQA to set something in about:config, it is far easier if I can just write a configuration file. thanks.This update has been obsoleted by firefox-88.0.1-1.fc33.