AutoConfig in Snap and Flatpak
Categories
(Core :: AutoConfig (Mission Control Desktop), defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox108 | --- | fixed |
People
(Reporter: simmo.saan, Assigned: gerard-majax)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0
Steps to reproduce:
Followed https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig to set up /usr/lib/firefox/firefox.cfg before Ubuntu 22.04 upgrade changed it to the snap version.
Actual results:
Previously set up AutoConfig is ignored.
Expected results:
AutoConfig should also work with the snap version.
According to https://forum.snapcraft.io/t/firefox-snap-no-longer-reads-usr-lib-firefox-for-customization/29713/20 it works for policies. If /usr/lib/firefox is not an acceptable place for such modifications, then some other path should be allowed for AutoConfig in snap.
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:gerard-majax, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
The severity field is not set for this bug.
:gerard-majax, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•2 years ago
|
||
So one thing I always wanted was to set a path for autoconfig and read it from there.
Something like that would fix this (you could just put the file in a place that could be read by the Snap.)
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 5•2 years ago
|
||
So we are going to support reading AutoConfig file from more than NS_GRE_DIR
, i.e., /etc/firefox/
Assignee | ||
Comment 6•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 7•2 years ago
|
||
Mike, do you think we need the same for Flatpak?
Comment 8•2 years ago
|
||
Yes, probably. Should we do it in here or a separate bug?
Ideally we would have a way to check if we are in a package generically.
Assignee | ||
Updated•2 years ago
|
Comment 10•2 years ago
|
||
bugherder |
Comment 11•2 years ago
|
||
Hey guys, isn't this a hack to bypass administrator system policies? Setting MOZ_SYSTEM_DIR
to my own directory ignores the policies in /etc/firefox for example. That's not good I presume.
Comment 12•2 years ago
|
||
Yeah, that policy change didn't need to be in the patch. I'll open a new bug.
Comment 13•2 years ago
|
||
Could you please post link to the new bug?
Comment 14•2 years ago
|
||
Description
•