1226925 - -CreateProfile command line creates an empty prefs.js file. This differs from CreateProfile GUI result.

Status: RESOLVED WONTFIX

(Toolkit :: Startup and Profile System, defect)

Description

[bugra]

1) Open Profile Manager GUI with '$ firefox -P'
2) Create an new profile
Result => the new Profile folder contains 1 file 'times.json'

1) open command line
2) run following command '$ firefox -no-remote -CreateProfile <NewProfileName>'
Result => the new Profile folder contains 2 files ('times.json' and 'prefs.js') 

The expected result should be consistent number of files created through GUI or command line.

There was a past discussion on the command line option #168433

Comment 1

[:Gijs (he/him)]

The commandline option and the profile manager option do different things, I expect. As noted in bug 168433, the commandline option causes the build to actually run and shut down pretty much immediately - which ends up saving the prefs file without any prefs having been set. The profile manager just creates the profile infrastructure in profiles.ini, maybe the directory, and nothing else.

Does this discrepancy actually cause problems for you? What's the impact here?

Comment 2

[Benjamin Smedberg]

This bug is filed in a bugzilla component related to pre-Firefox code which no longer exists. I believe it is no longer relevant and I am therefore closing it INCOMPLETE.

If you believe that this bug is still valid and needs to be fixed, please reopen it and move it to the Toolkit:Startup and Profile System product/component.

Comment 3

[Benjamin Smedberg]

Meh, I don't care about this. Going to close it WONTFIX.