Reporter: if you're looking for a workaround, we've had at least one report that this issue goes away if you use the Mozilla "official" build, available here: https://www.mozilla.org/firefox/new/ (See the "Download options and other languages" link there, if you want a different localization from the default one that's offered to you there.) That version is just a .tar.gz that you can extract into a folder of your choice and run directly (and e.g. drop a symbolic link into some directory that's in your $PATH like maybe $HOME/bin if you want to be able to start Firefox more directly), so it's not quite as integrated into your system as the PPA-provided version is. It does auto-update itself when updates are available, though. If you do happen to try that to get back to a working Firefox setup, it'd be helpful if you could confirm whether it helps or not -- that's useful information for other affected users, and it helps us narrow down what might be going on. Thanks!
Bug 1846399 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Reporter: if you're looking for a workaround, we've had at least one report that this issue goes away if you use the Mozilla "official" build, available here: https://www.mozilla.org/firefox/new/ (See the "Download options and other languages" link there, if you want a different localization from the default one that's offered to you there.) That version is just a `.tar.bz2` that you can extract into a folder of your choice and run directly (and e.g. drop a symbolic link into some directory that's in your $PATH like maybe $HOME/bin if you want to be able to start Firefox more directly), so it's not quite as integrated into your system as the PPA-provided version is. It does auto-update itself when updates are available, though. If you do happen to try that to get back to a working Firefox setup, it'd be helpful if you could confirm whether it helps or not -- that's useful information for other affected users, and it helps us narrow down what might be going on. Thanks!
Reporter: if you're looking for a workaround, we've had at least one report that this issue goes away if you use the Mozilla "official" build, available here: https://www.mozilla.org/firefox/new/ (See the "Download options and other languages" link there, if you want a different localization from the default one that's offered to you there.) That version is just a `.tar.bz2` that you can extract into a folder of your choice and run directly (and e.g. drop a symbolic link into some directory that's in your $PATH like maybe $HOME/bin if you want to be able to start Firefox more directly), so it's not quite as integrated into your system as the PPA-provided version is. It does auto-update itself when updates are available, though (and according to the user from bug 1849022, it's not affected by this issue). If you do happen to try that to get back to a working Firefox setup, it'd be helpful if you could confirm whether it helps or not -- that's useful information for other affected users, and it helps us narrow down what might be going on. Thanks!