This and profiles path/folder is a different issue.
Use firefox profile creator/manager to create the new profile, where you are asked/allowed to specify path for the profile data.
This creates a new entry in profiles.ini, (as already said). I don’t think you can avoid ~/.mozilla, although I haven’t tried (I think… ). I have used a different profile successfully.
Edit: The path (~/.mozilla) is hardoded, but you can use a symlink.
Look that IsRelative=0 means not relative to ~/.mozilla/firefox/ for the Path, being absolute, wherever you like. IsRelative=1 means relative to ~/.mozilla/firefox/ for the Path, inside ~/.mozilla/firefox/ folder.
I don’t find a reason for this not working, unless it is a bug in mozilla code that gets the path, confusing it with the default mozilla path.
If you try again and still fails, maybe post a bug report upstream mozilla.
You can also try changing the IsRelative value in profiles.ini to 0 .
I ran firefox with -P to bring up the profile manager, it didn’t show /.config/mozilla as a location at all.
Also manually putting a profile in there and setting InRelative=0 and specifying the absolute path resulted in profile not being able to load or inaccessible. Odd.
Maybe one more misunderstanding?
There is only one profiles.ini and it’s at $HOME/.mozilla/firefox. Do your changes there.
Or it’s me this time misunderstanding…
Yes. That’s how it should go.
Unless mozilla has this in the Known Issues somewhere, it looks like a bug. this is using the word mozilla as a profile name.
As it’s not such a problem, I guess nobody would care to report or fix it
But, we’ve got it!!