With our current nightly builds, this causes an extra profile directory to be created and used (and probably our bundled browser profile is not be used on Linux and Windows).
We should figure out how to disable this feature or modify it to be compatible with the way we crate and use browser profiles).
Looks like part of the official (but weird) downgrade support:
"Always creates an old-style default profile if one does not exist to allow
previous versions of the application to use a different profile."
It seems the MOZ_LEGACY_PROFILES environment variable can be set to disable this feature. On Linux we could set it in the start script, however I'm not sure we can easily set environment variables on Windows and macOS, so maybe patching to disable it will be needed.
It seems the MOZ_LEGACY_PROFILES environment variable can be set to disable this feature. On Linux we could set it in the start script, however I'm not sure we can easily set environment variables on Windows and macOS, so maybe patching to disable it will be needed.
Thanks. We may also be able to disable this by adding the following to our .mozconfig files (but I have not tried yet):
ac_add_options "MOZ_DEDICATED_PROFILES="
We may also be able to disable this by adding the following to our .mozconfig files (but I have not tried yet):
ac_add_options "MOZ_DEDICATED_PROFILES="
The above does not work. It seems that options that are defined using project_flag cannot be overridden easily... or at least Kathy and I could not figure out how to do so via .mozconfig. Here is a patch that changes the default value:
It's a pity Mozilla does not provide an easier, cross-platform way of disabling this feature. But here we are. The change looks good to me and got cherry-picked onto tor-browser-68.1.0esr-9.0-2 (commit 31d00e2f).
Trac: Resolution: N/Ato fixed Status: needs_review to closed