Description of problem: After upgrade, extensions are not longer working Tools=> Addons show them all but none of them are working : adblock, brief, https everywhere, gnome-shell extensions, noscript, treestyletab, tabsession manager, etc. I do also have an issue with the language as described in #26934. Mine should also be french. I don't know if it's related to the extensions issu
CC: (none) => boulshet
i created a new profile with another user and installed the same extensions : they did work until i restarted firefox. unfortunately they no longer once restarted
Yep, I can reproduce. I have a couple of extensions with their control icons added to the tab bar and elsewhere, and the icons don't appear when Firefox is first launched. The extensions are not in effect either. However, if I go to the extensions manager, both appear enabled. If I then disable then, and immediately after re-enable them, they work as expected, and their icons appear. This is all lost once Firefox is restarted. As the OP, creating a new, fresh Firefox profile didn't help at all. I don't think this is a Firefox upstream issue, because I checked Firefox 78.0.2 on a Debian Sid machine, and this issue is not present there. I have a secondary issue that also doesn't happen on Debian's Firefox: the "new tab" Firefox Home thingie appears with a white background, ignoring the dark theme that's respected in the rest of Firefox, and which was fine in FF 68.x. And as stated, this is not a problem that happens in Debian's FF. Maybe it's related to the first issue? I've seen Mageia's Firefox builds with plenty of patches, maybe one of them is no longer valid. Thanks for looking into it! =)
CC: (none) => jan-bugs
The manual disable/enable trick dit it for me too and are also lost when restarted thanks
CC: (none) => ouaurelien
CC: (none) => stephane.pontier
I can also confirm this bug. Upon starting/restarting Firefox, all of my extensions are not visible and not functioning, until I disable and then enable them through "about:addons". Furthermore, this issue also affects the theme I've selected in "about:addons" ("Dark") - that is, to get the theme to work, I need to disable it, and then enable it again. As with extensions, this gets lost upon restarting Firefox. (In reply to JanKusanagi from comment #2) > I don't think this is a Firefox upstream issue, because I checked Firefox > 78.0.2 on a Debian Sid machine, and this issue is not present there. I agree. I tested the Flatpak package of Firefox from dl.flathub.org, and this bug did not occur. Though, to be fair, while Flathub's Firefox currently has the same version number as Mageia's Firefox (78.0.2), Mageia's Firefox is an ESR (Extended Support Release) build, while the Flathub Firefox is a regular build. @JanKusanagi Correct me if I'm wrong, but I think Debian Sid also uses a regular build of Firefox, rather than an ESR build. (In reply to JanKusanagi from comment #2) > I have a secondary issue that also doesn't happen on Debian's Firefox: the > "new tab" Firefox Home thingie appears with a white background, ignoring the > dark theme that's respected in the rest of Firefox, and which was fine in FF > 68.x. And as stated, this is not a problem that happens in Debian's FF. Maybe > it's related to the first issue? For me, the "New Tab" page always appears white, even in Mageia 7.1 (which is currently using Firefox 68.10 ESR), unless I've changed Firefox's theme (e.g. to "Dark"). However, because the Firefox theme is currently suffering from the same issue as the extensions, I need to disable and enable the dark theme every time I start Firefox, in order to ensure that the "New Tab" page appears grey. @JanKusanagi Does disabling and enabling the theme fix the issue for you? In summary, there are currently 2 workarounds to this issue: * Disable all extensions/themes, and then enable them, every time you start Firefox * Sideload Firefox from a non-Mageia source, e.g. a Flatpak repository Not that I'm downplaying the seriousness of the issue - the average user probably isn't going to figure out how to work around this bug.
CC: (none) => penguin.sekai+mageiaidentity.writing
(In reply to Andrew Piubellini from comment #4) > @JanKusanagi Does disabling and enabling the theme fix the issue for you? Actually, yes! I didn't realize the Dark theme was not actually getting applied, because about:settings and such, were appearing in dark background as expected =)
CC: (none) => xiche
I'll add, just in case is also related to this sort of brokenness-metabug, that the icons that appear at the bottom of the URLbar (and the separate search bar) when it has focus, next to "This time, search with: [] [] []" are invisible squares, that get highlighted when hovered, but with no icon.
(In reply to JanKusanagi from comment #6) > I'll add, just in case is also related to this sort of brokenness-metabug, > that the icons that appear at the bottom of the URLbar (and the separate > search bar) when it has focus, next to "This time, search with: [] [] []" > are invisible squares, that get highlighted when hovered, but with no icon. I can confirm that this happened to me, too. However, I'm not sure whether it's the same issue, as the extensions/theme being disabled on restart. The reason is that, after the update to Firefox 78 ESR, I added some additional search providers (e.g. Wiktionary, and the Wine AppDB), and these new providers not only showed their icons, but retained the icons on restart (unlike extensions and the theme, which always get disabled on restart).
I can reproduce this bug too with /usr/bin/firefox from the mageia RPMs. It does not happen with /opt/shlomif/firefox/esr/firefox/firefox which I have installed from the mozilla.org binaries nor on my fedora 32 x86-64 installation on a different computer. [I'm also subscribing to this bug.]
CC: (none) => shlomif
Same for me. Disabling/enabling the extensions&themes worked (mentioned already)
Priority: Normal => HighCC: (none) => olav
Sorry to have left this, been elsewhere. The current Firefox does indeed look messy. Assigning to tv who has done recent Firefox updates; please re-assign it (pkg-bugs ?) if you prefer.
Assignee: bugsquad => thierry.vignaud
See also bug 26934 for GUI language issues with this Firefox version.
I can also confirm this bug - but when I manually disable and then re-enable the extensions - they work until firefox is restarted
CC: (none) => rfox
CC: (none) => cooker
Priority: High => release_blocker
I can also confirm that using Firefox-Beta works fine (firefox-beta-79.0-0.b9.mga8) I agree this is a release blocker as well as the NVidia 4.50 build issue Cheers, R.Fox
For the record, Firefox 78.1.0 from today's Cauldron updates doesn't magically fix this :'(
Just updated and can confirm that the problem continues.
CC: (none) => waterbearer54
Hi, There are some differences between firefox-mageia-default-prefs.js from firefox and the one from firefox-beta. When firefox is not running, as root, can you edit /usr/lib64/firefox/browser/defaults/preferences/firefox-mageia-default-prefs.js (or /usr/lib/firefox/browser/defaults/preferences/firefox-mageia-default-prefs.js for 32 bits) to remove the last lines: """ pref("spellchecker.dictionary_path","/usr/share/myspell"); /* disable "Allow firefox to install and run studies" */ pref("app.shield.optoutstudies.enabled", false); /* disable "Allow firefox to make personalized extension recommendations" */ pref("browser.discovery.enabled", false); """ If the problem disappears when firefox is launched, can you add again each line, one by one, when firefox is not running, to try to find the offending one, please? Best regards, Nico.
CC: (none) => nicolas.salguero
Source RPM: firefox-78.0.2-1.mga8.src.rpm => firefox-78.0.2-1.mga8.src.rpm, firefox-78.1.0-1.mga8Summary: Firefox 78.0.2-1 : extensions are no longer working => Firefox 78.*: extensions are no longer working
(In reply to Nicolas Salguero from comment #16) > When firefox is not running, as root, can you edit > /usr/lib64/firefox/browser/defaults/preferences/firefox-mageia-default-prefs. > js (or > /usr/lib/firefox/browser/defaults/preferences/firefox-mageia-default-prefs. > js for 32 bits) to remove the last lines: > """ > pref("spellchecker.dictionary_path","/usr/share/myspell"); > /* disable "Allow firefox to install and run studies" */ > pref("app.shield.optoutstudies.enabled", false); > /* disable "Allow firefox to make personalized extension recommendations" */ > pref("browser.discovery.enabled", false); > """ Tried that, had no effect. New firefox version didn't change anything as well.
(In reply to JanKusanagi from comment #6) > I'll add, just in case is also related to this sort of brokenness-metabug, > that the icons that appear at the bottom of the URLbar (and the separate > search bar) when it has focus, next to "This time, search with: [] [] []" > are invisible squares, that get highlighted when hovered, but with no icon. Hoping not to get this bug report any dirtier, I'll say that this issue I had with the search icons, related or not, is now gone with Firefox 78.1 =)
Blocks: (none) => 26934
Blocks: (none) => 27148
Just reporting that the bug didn't fix itself in version 78.2.0-4
CC: (none) => ita84
I have recibe reports in the spanish blog of a behavior similar to #26934 but for the spanish language
(In reply to katnatek from comment #20) > I have recibe reports in the spanish blog of a behavior similar to #26934 > but for the spanish language Yeah, all translations are affected. By chance?, it default to English. What a nightmare it could have displayed white squares instead of the text... This is release_blocker.
Assignee: thierry.vignaud => pkg-bugsSource RPM: firefox-78.0.2-1.mga8.src.rpm, firefox-78.1.0-1.mga8 => firefox-78.2.0-4.mga8.src.rpmSeverity: major => criticalTarget Milestone: --- => Mageia 8
CC: ouaurelien => (none)
Hi! This bug is still in the latest version of repositories 78.2.0-5 as is bug 26934. Regards!
CC: (none) => joselp
Hi, For me this bug is solved with the last rpm : firefox-78.2.0-6.mga8. So I think you could close this bug. Thank you for your work. Vouf.
CC: (none) => jeanmichel.varvou
Indeed, also fixed for me extensions are working again and the language also closing, txs
Status: NEW => RESOLVEDResolution: (none) => FIXED
Yep, fixed over here! THANKS!!
Seems to be fixed here as well. Thanks!