For list of changes see: https://www.mozilla.org/en-US/firefox/40.0/releasenotes/
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2015-13397Please login to add feedback.
| 0 | 0 | Test Case firefox addons |
| 0 | 0 | Test Case firefox browse |
| 0 | 0 | Test Case firefox media |
| 0 | 0 | Test Case firefox screenshot |
| 0 | 0 | Test Case User:Sr02mu/Draft/firefox bookmark |
This update has been submitted for testing by xhorak. This critical path update has not yet been approved for pushing to the stable repository. It must first reach a karma of 2, consisting of 0 positive karma from proventesters, along with 2 additional karma from the community. Or, it must spend 14 days in testing without any negative feedback
Taskotron: depcheck test PASSED on i386. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/115874/steps/runtask/logs/stdio (results are informative only)
Taskotron: depcheck test PASSED on x86_64. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/115874/steps/runtask/logs/stdio (results are informative only)
works for me
This update is currently being pushed to the Fedora 21 testing updates repository.
This update has been pushed to testing
Critical path update approved
Didn't notice anything bad, now I've updated to firefox-40.0-4.fc21 due to the OMTC issue
This update has reached the stable karma threshold and will be pushed to the stable updates repository
Taskotron: upgradepath test FAILED on noarch. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/116497/steps/runtask/logs/stdio (results are informative only)
Automatic push to stable based on karma has been disabled for this update due to failure of an AutoQA test. Update submitter, please check the AutoQA test result and see if there is a valid problem to be fixed here, and fix it if so. If the failure is a mistake on AutoQA's part, you can re-enable the automatic push feature for this update if you like, or push it stable manually once it reaches the requirements under the Updates Policy.
This update is currently being pushed to the Fedora 21 stable updates repository.
First of all, I understand that firefox-40.0-3.fc21 is already obsoleted by firefox-40.0-4.fc21, which sets "layers.offmainthreadcomposition.enabled" to "false" by default. This is a good thing: I experienced not just crashes but also severe problems with screen refresh during scrolling, with lines of text on web pages like https://bugzilla.redhat.com/show_bug.cgi?id=1253086 temporarily disappearing or with the scrolling on https://admin.fedoraproject.org/updates/ getting "stuck" when trying to scroll back to the top, unless the mouse pointer hovered over the tab bar forcing repaint. Disabling OMTC works around this very annoying issue as well.
isv: so you experience same stuff that people with gtk3 build (f22)? Are you fine with firefox-40.0-4.fc21 now?
This update has been pushed to stable
xhorak wrote: > so you experience same stuff that people with gtk3 build (f22)? I haven't seen a comment mentioning this new "wavy" scrolling for the firefox build with OMTC enabled on f22. If people complained about "stuck" scrolling before, this might have been due to various effects of https://devtalk.nvidia.com/default/topic/729908/linux/-gt-334-21-redrawing-problems-in-gnome-3-10-3-12-gtx-580/ and https://bugzilla.gnome.org/show_bug.cgi?id=728464. Will test on f22 later. The new thing about it was that the latter issue appeared in firefox on previously immune NVIDIA driver 331.113 starting with firefox-40.0-3.fc21 with OMTC enabled. Regarding crashes: yes, the same stuff. > Are you fine with firefox-40.0-4.fc21 now? Yes. No crashes so far and the scrolling works as it should.
xhorak: I'm sorry for the unreadable mess above â I didn't expect this website eating double line breaks.
xhorak: couldn't make firefox-40.0-4.fc22 crash on f22 (possibly didn't try hard enough), especially no scrolling issues with the cairo-gtk3 build at all â even with "layers.offmainthreadcomposition.enabled" set to "true" and firefox restarted. Meanwhile on f21, the stock cairo-gtk2 build gets literally unusable with OMTC deliberately enabled due to the broken scrolling / repaint issues.
For now (2015-08-21 19:59 UTC), the new bodhi lists me as submitter of this package. This is utter nonsense and the most embarrassing bug I ever experienced. I wonder, how many more commenters are affected by https://github.com/fedora-infra/bodhi/issues/241 ?