On 23/01/20 20:48:07 CET, Reiner Herrmann wrote:
> On Thu, Jan 23, 2020 at 08:25:10PM +0100, /dev/fra wrote:
> > Just a quick update, upgrading to firejail-profiles 0.9.62-3 does not fix
> > the issue while downgrading to version 0.9.60-2 does it. So it seems that
> > this issue is definitely caused by a change introduced after 0.9.60-2.
> [...]
> The changes between these two version were not so big.
> In firefox.profile these two lines are new:
> 
> whitelist /usr/share/mozilla
> include whitelist-usr-share-common.inc

This is it, commenting out the lines above prevents the issue to happen.

For sake of completeness, the lines added in firefox.profile between 0.9.60-2 
and 0.9.62-3 are these:

    whitelist /usr/share/mozilla
    whitelist /usr/share/webext
    include whitelist-usr-share-common.inc

However by commenting them out we get the issue reported in #948558, and maybe 
something more. I noted in fact that also something else gets out of place 
(with this version of firejail), but I couldn't test it further.

Now, the two whitelist entries are clear, I have also quickly skimmed 
whitelist-usr-share-common.inc but I really couldn't say what is causing this 
odd behaviour. I am starting to wonder if the problem might lie in firefox 
itself, because it is like part of the user preferences are set to certain 
defaults should some conditions change.

For example, try this other test:

1. Create a new firefox test profile, change these preferences
    a. General, Always check if Firefox is your default browser --> Unset
    b. Home, Homepage and new windows --> debian.org
    c. Privacy & Security, Content Blocking --> Strict
    d. Privacy & Security, Allow Firefox to send technical... --> Unset
  and quit firefox.
2. Run such profile with firejail (firejail firefox -P test), note that
    - firefox asks to be set as default browser;
    - indeed preferences a. and d. have been enabled;
3. While running the test profile with firejail, change preferences a. and d. so
  that they are unset, quit firefox;
4. Run again the test profile with firejail, preferences set in step 3 have been
  retained, quit firefox;
5. Run the test profile this time without firejail, note that preferences set in
  step 1 (and 3) remained unchanged, quit firefox;
6. Run one more time the test profile with firejail, and note that preferences
  a. and d. have been enabled once again (like in step 2).

So, most of the user preferences are retained but some are altered when firefox 
is ran with firejail. But I do not understand how and why this happens, given 
that user preferences should be just saved in ~/.mozilla/firefox/<profile>/, a 
path that does should be accessible by firefox without so much restriction from 
firejail.

Cheers

Reply via email to