1565331 - launching Firefox with -P fails to bring up ProfileManager if an instance is already running

Status: RESOLVED DUPLICATE of bug 1565597

(Toolkit :: Startup and Profile System, defect, P2)

Description

[Michael Froman [:mjf]]

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:68.0) Gecko/20100101 Firefox/68.0

When I launch the first instance of Firefox from the command line with -P, the Profile Manager is shown. If I try to open a second instance from the command line with -P, it opens a new window in the running instance of Firefox instead of bringing up the Profile Manager.

This worked as expected in 67, and no longer works in 68. I used mozregression to narrow the range:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=cbaa9021d82f15188e957ebd3a413dede4908330&tochange=b1374f2163b67338d0d0540b51010899452bde96

Comment 1

[Michael Froman [:mjf]]

I just found Bug 1553767, for which it seems like this new bug may be a duplicate. However, I'd like to suggest that for -P, --no-remote should be assumed since there is little reason to use -P other than to start an new instance.

Comment 2

[Stephen A Pohl [:spohl]]

Yuri, would you like to take a look at this?

Comment 3

[cat]

I'm also experiencing this bug. With 68.0, only one profile can be used; trying to use -P with/out --no-remote/-noremote only results in a new window in the active profile. Downgrading (and working through the annoyance of removing compatibility.ini to be able to use existing profiles), it appears that multiple profiles last worked correctly in 67.0.3.

Comment 4

[Yuri Z.]

Looking into these.
Not clearing the NI to keep track of them.

Comment 5

[Yuri Z.]

Should be handled in https://bugzilla.mozilla.org/show_bug.cgi?id=1565597