![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Clicking on Firefox's shortcut to specific profile when it's already open doesn't work. What am I missing?
Well, that's a hard problem to describe in one sentence.
I'm currently using windows. I have 2 Firefox profiles, and each of them have desktop shortcuts to: "C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -no-remote -P "Developer" "C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -no-remote -P "Lazy"
They work just fine. The thing is: if the profile is already active and I click the shortcut, I get a "Firefox already running but not responding" error (Firefox just fails to open. The current opened window still works). The behavior I want is either maximize/focus the corresponding window, or open a new window with the same profile. Is it possible to achieve this? What am I missing?
I don't know if I'm being clear. In other words: - Desktop shortcut to specific profile works fine - While profile is open, double click the same desktop shortcut - Receive a "Firefox already running" error popup - Press ok, current profile still working but new window is not opened as expected
Vybrané riešenie
You can't open a link if you use the -no-remote command line switch. You will have to start one profile without the -no-remote switch. Then you can open external links in that profile instance (but not in the other).
- http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile
- https://developer.mozilla.org/Mozilla/Multiple_Firefox_Profiles
Všetky odpovede (2)
Vybrané riešenie
You can't open a link if you use the -no-remote command line switch. You will have to start one profile without the -no-remote switch. Then you can open external links in that profile instance (but not in the other).
cor-el said
You can't open a link if you use the -no-remote command line switch. You will have to start one profile without the -no-remote switch. Then you can open external links in that profile instance (but not in the other).
Huh. If I didn't know better I would bet that I had tried this and hadn't worked. Thanks for the answer.