Flatpak Firefox: can't use profile folder from host system
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
People
(Reporter: trialism, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Copied my .mozilla into the ~/.var/app/org.mozilla.firefox folder
Actual results:
Firefox keeps creating new profiles and new "installs"
Expected results:
Firefox should have used my profile.
|
||
Comment 1•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 2•6 years ago
|
||
Can you provide some more information here? I would expect the FlatPak version to be considered a different install to normal Firefox. Does copying the contents of your profile into the profile created for the FlatPak not work?
A flatpak install is still a linux config. What you asked doesn't work and if someone doesn't have a firefox cloud account then it means that the user will need to manually migrate and set everything which is a lot of work.
|
|
||
Comment 4•6 years ago
|
||
Just to be clear what I'm saying:
When you run the flatpak install of Firefox it will create a user profile somewhere, from your report presumably somewhere in ~/.var/app/org.mozilla.firefox. The directory will have a random name like xxxxxxxxx.default-release. Likewise the non-flatpak install will have created a profile, somewhere like ~/.mozilla/firefox/xxxxxxxxx.default-release. If you copy the files from inside the default-release folder for the non-flatpak install into the default-release folder for the flatpak install what happens?
|
||
Comment 5•6 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (non,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
|
|
||
Comment 6•6 years ago
|
||
Closing out, if you are still seeing this issue please reopen the bug and answer the question in comment 4.
Description
•