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.
I unpushed this because it seems to have a real bug. The openQA test failure is not a blip. Installing add-ons in KDE just doesn't work. I reproduced this manually:
This pops up an "Add UBlock Origin? This extension will have permission to:" popover, and nothing in it works, and you can't dismiss it. It has "Cancel" and "Add" buttons; clicking on either makes it animate, but otherwise nothing happens. Hitting Esc doesn't do anything. All you can do is reload the page and try again, which causes the same result.
F34 KDE upgraded since ~F30, x.Org, Fedora's KDE packages: no issues installing uBlock Origin. I wanted to test it in virt-manager with latest KDE respin, but it was so slow, I gave up.
I don't know what @adamwill is seeing, but installing extensions, including uBlock Origin, on "clean F34 KDE Spin install, updated to updates-testing, plus this firefox update" works without problems, both in Plasma Wayland and Plasma X11 sessions.
I'm seeing exactly what openQA sees. Click on the buttons in the popover, nothing at all happens. I'll take a video in a bit (I need to find a tool to do it in KDE).
One thing to note, openQA tests only the packages from the update, and I did the same (I only updated Firefox). It does not update everything from updates-testing at the same time, as manual testers usually do. I can see if this bug goes away if some other package is installed from u-t. If so, that would mean yet again that two packages which should have been combined into one update were not.
At the very least it works fine here on gnome including ublock addon install using only firefox-90.0-1.fc34.x86_64.rpm. It would definitely have to be kde specific or some very specific configuration.
Yes, it only happens on KDE. I said that in my initial comment. But that's not "very specific". It's one of Fedora's release-blocking desktops.
It's still happening for me every time I try it, even with all current updates-testing packages installed. It only happens in Plasma-on-Wayland, it works fine in Plasma-on-X11.
Huh. Interestingly, after trying on X11 (where it worked), when I go back to Wayland, it works there now too. So this may only happen straight out of the box. @decathorpe , did you actually test on a fresh install?
Not to turn this into a support thread (I won't be replying again) but that's not really what I meant. I know you said that but it does appear to be very specific in that others have it working on kde plasma wayland
Maybe its a vm only thing? I don't think anyone else mentioned being on vm.
I'd rather look into the issue a little more first. If it happens on all fresh KDE deployments it'd still be a problem, as anyone installing F34 KDE fresh from now on may run into it.
I'm not sure if holding back important security updates because of a minor UI glitch on KDE is a good strategy. Is a KDE UI bug really worth more than GNOME users and users of other DEs not getting pwned because there's unfixed vulnerabilities in 89? The unpush makes me feel like I can currently not surf the web on Fedora.
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update has been submitted for testing by stransky.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
Thank you.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
This update has been submitted for stable by bodhi.
Works great
Works with no issues.
works great
This update has been unpushed.
I unpushed this because it seems to have a real bug. The openQA test failure is not a blip. Installing add-ons in KDE just doesn't work. I reproduced this manually:
This pops up an "Add UBlock Origin? This extension will have permission to:" popover, and nothing in it works, and you can't dismiss it. It has "Cancel" and "Add" buttons; clicking on either makes it animate, but otherwise nothing happens. Hitting Esc doesn't do anything. All you can do is reload the page and try again, which causes the same result.
@adamwill I don't have this issue, but I use kde from zawertun/kde copr repo and I use X11.
F34 KDE upgraded since ~F30, x.Org, Fedora's KDE packages: no issues installing uBlock Origin. I wanted to test it in virt-manager with latest KDE respin, but it was so slow, I gave up.
Works fine for me. F34 KDE. Addons from https://addons.mozilla.org installed fine as well.
I don't know what @adamwill is seeing, but installing extensions, including uBlock Origin, on "clean F34 KDE Spin install, updated to updates-testing, plus this firefox update" works without problems, both in Plasma Wayland and Plasma X11 sessions.
I'm seeing exactly what openQA sees. Click on the buttons in the popover, nothing at all happens. I'll take a video in a bit (I need to find a tool to do it in KDE).
One thing to note, openQA tests only the packages from the update, and I did the same (I only updated Firefox). It does not update everything from updates-testing at the same time, as manual testers usually do. I can see if this bug goes away if some other package is installed from u-t. If so, that would mean yet again that two packages which should have been combined into one update were not.
At the very least it works fine here on gnome including ublock addon install using only firefox-90.0-1.fc34.x86_64.rpm. It would definitely have to be kde specific or some very specific configuration.
Yes, it only happens on KDE. I said that in my initial comment. But that's not "very specific". It's one of Fedora's release-blocking desktops.
It's still happening for me every time I try it, even with all current updates-testing packages installed. It only happens in Plasma-on-Wayland, it works fine in Plasma-on-X11.
Huh. Interestingly, after trying on X11 (where it worked), when I go back to Wayland, it works there now too. So this may only happen straight out of the box. @decathorpe , did you actually test on a fresh install?
Not to turn this into a support thread (I won't be replying again) but that's not really what I meant. I know you said that but it does appear to be very specific in that others have it working on kde plasma wayland
Maybe its a vm only thing? I don't think anyone else mentioned being on vm.
I think this update should be re-pushed.
I'd rather look into the issue a little more first. If it happens on all fresh KDE deployments it'd still be a problem, as anyone installing F34 KDE fresh from now on may run into it.
also, pushing it stable would cause the test to fail for every other update from now on, unless I disable it or find a reasonable workaround.
@adamwill mine works on KDE (x11) old installation with all updates installed. JFYI. Didn't tested on wayland.
@adamwill you're hitting https://bugzilla.mozilla.org/show_bug.cgi?id=1714132 We may need to disable Wayland on KDE until it's fixed there.
ah, yep, that does indeed sound like it. why did you resolve that as MOVED, btw? where did it move to?
I'm not sure if holding back important security updates because of a minor UI glitch on KDE is a good strategy. Is a KDE UI bug really worth more than GNOME users and users of other DEs not getting pwned because there's unfixed vulnerabilities in 89? The unpush makes me feel like I can currently not surf the web on Fedora.
New build is on the way: https://koji.fedoraproject.org/koji/buildinfo?buildID=1781065
You can also install the update from testing: https://fedoraproject.org/wiki/How_to_test_updates
For me it works on KDE X11 and on KDE Wayland I haven't any issues with this new update. On GNOME it works as expected without issues.