[Profile per channel] I'm still using my existing 'default' profile, but links clicked from other programs are opening the profile manager instead of just opening in the open instance.
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
People
(Reporter: KWierso, Unassigned)
References
Details
Attachments
(1 file)
|
765 bytes,
text/plain
|
Details |
I have several profiles (and Firefox builds) set up on my desktop running Windows 10. I have shortcuts pinned to the taskbar for a few of these.
My setup:
Pinned shortcut for Release Firefox, with the target "C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -P default
Pinned shortcut for Nightly, with the target "C:\Program Files\Nightly\firefox.exe" -P nightly --no-remote
Pinned shortcut for Beta, with the target "C:\Program Files\Mozilla Firefox\firefox.exe" -P beta --no-remote
Most of the time, I'm only using the release build with the default profile. Note that it doesn't use --no-remote, so links clicked from other programs should open into this instance as new tabs. That's how it worked up until I updated to Firefox 67, which IIRC sets its own separate profile by default (but not for existing installations, I think?).
|
Reporter | |
Comment 2•6 years ago
|
||
|
||
Comment 3•6 years ago
|
||
Well, not sure how it got into that state, but that profiles.ini is telling Firefox to always open the profile manager on startup.
Previously if there was any open Firefox then opening it again would cause it to be reopened in one of them. Now we always target the profile you're trying to open. If you select "default" and check the box to use that profile on startup then you should be back in the state you were before.
|
|
Reporter | |
Comment 4•6 years ago
|
||
That seems to work. Want to close this out, or is it worth digging into how we got to this point?
|
||
Comment 5•6 years ago
|
||
I confirm hitting the same bug. If I have my second profile open (not Default User) and I click a link, instead of opening in my currently open, second profile, I get the profile manager dialog box. This is new since Firefox 67.
|
|
||
Comment 6•6 years ago
|
||
(In reply to Daniel Descheneaux from comment #5)
I confirm hitting the same bug. If I have my second profile open (not Default User) and I click a link, instead of opening in my currently open, second profile, I get the profile manager dialog box. This is new since Firefox 67.
Does your profiles.ini show the same value for StartWithLastProfile?
|
|
||
Comment 7•6 years ago
|
||
(In reply to Wes Kocher (:KWierso) from comment #4)
That seems to work. Want to close this out, or is it worth digging into how we got to this point?
The code that controls that setting is pretty straightforward, aside from bug 1542221 (which only made it impossible to change the setting) I've not heard of any issues with it. It's also entirely likely that your system has been in this state for some time, 67 just changed the behaviour in that case.
So I don't really know where to start to try to reproduce this, if you don't either then there might not be much we can do here.
|
|
||
Comment 8•6 years ago
|
||
If it says 0, I get the profile manager, if it says 1 I get my default profile - which is not the behavior I want if I have my second profile active. I'm reasonably sure Wes and I are just the first to report that bug, not the only two affected. It should be dead easy to replicate. Second profile open, click a link, opens in default profile.
|
|
||
Comment 9•6 years ago
|
||
(In reply to Daniel Descheneaux from comment #8)
If it says 0, I get the profile manager, if it says 1 I get my default profile - which is not the behavior I want if I have my second profile active. I'm reasonably sure Wes and I are just the first to report that bug, not the only two affected. It should be dead easy to replicate. Second profile open, click a link, opens in default profile.
This is the expected behaviour. When opening Firefox by default it uses the default profile.
|
|
||
Comment 10•6 years ago
|
||
It sure wasn't in Firefox 66 and prior. Anyway, bug reported. I am done.
|
|
||
Comment 11•6 years ago
|
||
(In reply to Daniel Descheneaux from comment #10)
It sure wasn't in Firefox 66 and prior. Anyway, bug reported. I am done.
Yes, this was implemented in 67.
Description
•