firefox 147.0.1 has been verified on ubuntu not to create the ~/.mozilla/extensions directory if firefox profile is under ~/.config/mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=2001887#c24 I use firefox-147.0.1-2.fc43.x86_64, and it still creates ~/.mozilla/extensions whenever I start it. firefox then works all right based on its profile under ~/.config/mozilla. What am I missing? Reproducible: Always
The same bug happens on my side regardless of whatever it is in a new fedora profile or not. I am using Fedora 43 KDE and native 147.0.1 firefox.
Yes, the file is created by language pack install script at /usr/bin/firefox.
Thanks for the hint. In ubuntu, they probably do it differently. Isn't it possible to improve the /usr/bin/firefox script so that it first tries the XDG directory (which defaults to ~/.config/mozilla) and if not found then falls back to the traditional ~/.mozilla?
Added to firefox-147.0.1-5 package.
Thank you so much. Then I am closing this one.
FEDORA-2026-4d2a7298e1 (firefox-147.0.1-5.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-4d2a7298e1
FEDORA-2026-b870bff523 (firefox-147.0.1-5.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-b870bff523
FEDORA-2026-4d2a7298e1 (firefox-147.0.1-5.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-b870bff523 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-b870bff523` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-b870bff523 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-8283a41c2a (firefox-147.0.1-6.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-8283a41c2a
Confirmation: with firefox-0:147.0.1-5.fc43.x86_64, the extension directory is created as expected, under the ~/.config/mozilla directory if such exists.
FEDORA-2026-8165773b54 (firefox-147.0.2-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-8165773b54
FEDORA-2026-d7d488beb4 (firefox-147.0.2-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-ecf98bfc3e (firefox-147.0.2-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-ecf98bfc3e
FEDORA-2026-ecf98bfc3e (firefox-147.0.2-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
Hi, the firefox launch script hardcodes its config location to ~/.config which does not play well if XDG_CONFIG_HOME is set to a different folder. It would be nice if it read XDG_CONFIG_HOME if set and fallback to ~/.config. A small fix for /usr/bin/firefox (that I unfortunately have been unable to test) if [ -d "$HOME/.mozilla" ]; then MOZ_CONFIG_DIR="$HOME/.mozilla" else MOZ_CONFIG_DIR="${XDG_CONFIG_HOME:-$HOME/.config}/mozilla" fi MOZ_EXTENSIONS_PROFILE_DIR="$MOZ_CONFIG_DIR/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}" # ... (restorecon -vr $MOZ_CONFIG_DIR/firefox/*/gmp-widevinecdm/* &)
Can confirm, this bug is still present. Firefox keeps creating .mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384} folder
(In reply to sajberkod from comment #17) > Can confirm, this bug is still present. Firefox keeps creating > .mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384} folder I moved ~/.mozilla to ~/.config/mozilla (i.e. I haven't ~/.mozilla any longer), and the extensions directory is created under my ~/.config/mozilla, which is I believe the intended behavior. To get rid of that extensions directory, some env variable has to be set to disable something in firefox, I forgot what was that exactly. The original bug was about ~/.mozilla getting recreated, but that has been fixed. I use this: $ rpm -q firefox firefox-148.0-1.fc43.x86_64