Closed Bug 1554252 Opened 5 years ago Closed 5 years ago

Firefox doesn't start if installs.ini or profiles.ini attribute is set to read-only

Categories

(Toolkit :: Startup and Profile System, defect, P5)

67 Branch
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox-esr60 --- unaffected
firefox67 --- wontfix
firefox68 --- wontfix
firefox69 --- fix-optional
firefox70 --- fix-optional

People

(Reporter: david_chmfr, Unassigned)

References

(Regression)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0

Steps to reproduce:

Set the file profiles.ini or installs.ini to read-only and start Firefox with the profile manager and choose a profile other than the one selected. Firefox display a message box and doesn't start properly.

Actual results:

Unable to start Firefox except if we disable the read only state of the concerned files.
I didn't found another solution to always have the same default profile.

Expected results:

Start Firefox with the default profile; because the profile.ini file is set as read only the default profile never change.
This way worked correctly for several year but this bug has appeared with the version 67.0

Component: Untriaged → Startup and Profile System
Flags: needinfo?(dtownsend)
Product: Firefox → Toolkit
Regressed by: 1474285

What is the use case here?

Flags: needinfo?(dtownsend)

The purpose is to always have the same default profile.
Is the profile.ini file has a read-write access the selected profile is the last used.

Choosing a profile in the profile manager means setting that profile as the new default and so an error is thrown when attempting to save that change to disk. I guess arguably the error in this case is ignorable but in general I dislike the idea of supporting the case of setting important Firefox settings files to be read only. Will think about this a bit more.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P5

This workaround is not perfect and it should be better to have a new option to freeze the default profile.

(In reply to David from comment #4)

This workaround is not perfect and it should be better to have a new option to freeze the default profile.

I don't see that happening. If you wanted to always launch Firefox with a fixed profile then you should use the command line arguments to select it when you run Firefox.

I'm going to say that running Firefox with profiles.ini set as readonly is unsupported.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.