FireFox snap no longer reads /usr/lib/firefox for customization

Yes.­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­

Doesn’t appear to work

$/etc/firefox$ tree .
.
├── config.js
└── pref
    ├── apturl.js
    └── config-prefs.js

or with …browser/defaults/preferences/config-prefs.js

(apturl.js was already here)

read again above :wink:

Still no joy with things like github[.com]/onemen/TabMixPlus/#installation that use github[.com]/xiaoxiaoflood/firefox-scripts#instructions

# pwd; tree .                                     
/etc/firefox
.
├── policies
│   ├── config.js
│   └── defaults
│       └── pref
└── pref
├── apturl.js
└── config-prefs.js

4 directories, 3 files

As I wrote earlier in this thread:

That said, there may be a way to have firefox read custom scripts in a more snap-friendly place. Would you mind filing a bug to request that feature?

There’s already some input from Mozilla at https://github[.com]/xiaoxiaoflood/firefox-scripts/issues/64 but it’s from the security team rather than Snap/feature development.

2 Likes

Mozilla fixed the issue https://bugzilla.mozilla.org/show_bug.cgi?id=1785278 with Firefox snap for Linux, by adding an new path to add config files. Starting with Firefox 108 (currently fairly far away from release) files in /etc/firefox/config.js and /etc/firefox/defaults/pref/config-prefs.js should work

I can’t update to a nightly, so will have to await the release

1 Like

This seems to work now, with the above paths.

1 Like

Any idea, why /etc/firefox/profiles might not get recognized in some cases?

I’ve got two systems both running Ubuntu 22.04 LTS, both with latest firefox from snap. The identical profiles.ini in /etc/firefox/profiles gets applied on system #1, but not on #2.

Have you compared the file and directory permissions and ownerships too ?