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-2019-c22338aa23Please login to add feedback.
| 0 | 1 | Test Case firefox addons |
| 0 | 3 | Test Case firefox browse |
| 0 | 1 | Test Case firefox media |
| 0 | 0 | Test Case firefox screenshot |
| 0 | 1 | Test Case User:Sr02mu/Draft/firefox bookmark |
This update has been submitted for testing by stransky.
This update test gating status has been changed to 'waiting'.
This update test gating status has been changed to 'ignored'.
works. Thank you
This update has been submitted for stable by bodhi.
I needed this urgently after upgrading system from fc29 to fc30. Works fine. Thank you.
This update has been pushed to stable.
works fine
at least I can use my existing profile now, unfortunately the UI is still degraded, compared to what it used to be!
@hoffmann if FF wanted to create a new profile after upgrade (saying that it was already used by newer version), all you had to do was to modify two time stamps in ~/.mozilla/firefox/profile.name/compatibility.ini. In my case f29 build finished a bit earlier and subtracting two hours sufficed.
Well observed, @ozeszty! Indeed that is the problem I was facing. Thanks for the hint. Obviously it is a trap now, because FF checks profiles against use by future versions, not only with version numbers, but also with build(!) timestamps. This is particularly annoying, as there is no way for most users to get their old profile back until the next upgrade. Not sure, if it is rather a FF bug. But if the packages could be timestamped in the same order as system releases, the problem would be avoided. Anyway, now I have the latest FF on my box and got the opportunity to give some tester feedback, which is not such a bad experience anyway.