Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Cari Bantuan

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Pelajari Lebih Lanjut

Utas ini telah diarsipkan. Silakan membuat pertanyaan baru jika Anda membutuhkan bantuan.

Create DEFAULT firefox profile via command line before the first run

  • 1 balas
  • 1 memiliki masalah ini
  • 30 kunjungan
  • Balasan terakhir oleh cor-el

droidus
droidus
more options

Hi,

I want to setup a number of addons via command line on a completely fresh Firefox ESR installation on Linux (i.e. while Firefox hasn't been opened yet for the first time by the user). To do this, I first need a default profile directory, but the .mozilla folder is missing from the home path when I install Firefox (it is only created when I run the browser for the first time).

So I tried to create a profile immediately after installing FF:

firefox -createprofile default-esr

This creates the .mozilla folder containing a XXXXXXXX.default-esr directory and the profiles.ini file with the following contents:

[Profile0] Name=default-esr IsRelative=1 Path=XXXXXXXX.default-esr

[General] StartWithLastProfile=1 Version=2

However when I run FF for the first time later on, it completely skips this profile and instead generates a new default one, YYYYYYYY.default-esr-1, and profiles.ini is edited with the following contents:

[Profile1] Name=default-esr-1 IsRelative=1 Path=YYYYYYYY.default-esr-1

[Profile0] Name=default-esr IsRelative=1 Path=XXXXXXXX.default-esr Default=1

[General] StartWithLastProfile=1 Version=2

[Install3B6073811A6ABF12] Default=YYYYYYYY.default-esr-1 Locked=1

I can revert to the profile that I explicitly created by going to about:profiles and setting it again as the default, but this defeats the purpose because I want to prepare my profile via the command line without having to open FF to change a setting. Is this possible?

Hi, I want to setup a number of addons via command line on a completely fresh Firefox ESR installation on Linux (i.e. while Firefox hasn't been opened yet for the first time by the user). To do this, I first need a default profile directory, but the .mozilla folder is missing from the home path when I install Firefox (it is only created when I run the browser for the first time). So I tried to create a profile immediately after installing FF: firefox -createprofile default-esr This creates the .mozilla folder containing a XXXXXXXX.default-esr directory and the profiles.ini file with the following contents: [Profile0] Name=default-esr IsRelative=1 Path=XXXXXXXX.default-esr [General] StartWithLastProfile=1 Version=2 However when I run FF for the first time later on, it completely skips this profile and instead generates a new default one, YYYYYYYY.default-esr-1, and profiles.ini is edited with the following contents: [Profile1] Name=default-esr-1 IsRelative=1 Path=YYYYYYYY.default-esr-1 [Profile0] Name=default-esr IsRelative=1 Path=XXXXXXXX.default-esr Default=1 [General] StartWithLastProfile=1 Version=2 [Install3B6073811A6ABF12] Default=YYYYYYYY.default-esr-1 Locked=1 I can revert to the profile that I explicitly created by going to about:profiles and setting it again as the default, but this defeats the purpose because I want to prepare my profile via the command line '''without having to open FF''' to change a setting. Is this possible?

Diperbarui oleh droidus pada

Semua Balasan (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You can possibly install extensions and make other changes to settings via a policies.json or autoconfig file.