293067 - Profile Manager is not accessable unable to change profile

Status: VERIFIED INVALID

(Toolkit :: Startup and Profile System, defect)

Description

[James Scanlan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

I have found the profile in the files there are 2  I am unable to find the
Profile manager through either the Command line  firefox.exe -p"name" does not
work or in the tool bar?  

Reproducible: Always

Steps to Reproduce:
1.in the Command Line    firefox.exe -p           enter
2.
3.

Actual Results:  
Firefox loads and works  but there is no way to select another profile.

Expected Results:  
Some way to get to Profile manager so I can switch.

This happened after a successful restart of the system at the start of the day.
  The Profile manager came up and said the default profile was being used and
could not load.   I created a secondary profile.   That one now loads and I
cannot get to the Profile Manager to change.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

Are you sure that all instances of Firefox are shut down before try "firefox.exe
-p"? Did you try after a reboot?

Comment 2

[Roy]

I have the same problem, I cant seem to start Profile manager
I tried using Run > firefoxe.exe -p  and he just starts firefox withot 
etting the profile manager pop up.
I also tried changing shortcut with  -profilemanager command.
That didnt work either.

Comment 3

[Brandi]

I'm having the same error! One day when I opened FIrefox, it forced me set up
another profile. Now I can't get back to my original one, and I had a lot of
important bookmarks, etc there! Please let me know how to recover that profile...

Comment 4

[shannon]

I have the same problem as brandi did...and this has now happened twice to me. 
I don't remember how long ago it happened the first time, but it is VERY
distressing to find out that you have lost all of your saved bookmarks.  A LOT
of wasting surfing time to recover from this problem.  PLEASE address this issue
ASAP.

Comment 5

[John P. Linderman]

I saw something similar.  If firefox was already running (on Linux), neither the
  -profilemanager  nor -p <profile>
options worked... I simply got another window duplicating the prevailing profile.

Adding MOZ_NO_REMOTE=1 to my environment cured everything, but it's witchcraft
to me, so I don't know if it has other undesirable side-effects.  But it got
me up and running with multiple concurrent profiles.  YMMV.  -- jpl

Comment 6

[Harish J P]

I have the similar bug in Firefox 1.5 on FreeBSD. Profile Manager comes up when there are no firefox instances running and lets you choose the profile. Further invocations of the command results in use of the same profile that was selected earlier. I am not able to run multiple Firefox instances with different profile. For now I have switched to different browsers (Firefox, Mozilla, Opera) :(. It was fine on the older version Firefox 1.0.7.

Comment 7

[:Gavin Sharp [email: [e-mail]]]

This bug report isn't does not provide enough information to reproduce the bug, the reporter hasn't responded to the question in comment #1. Most comments in this bug are probably a result of bug 239223 or similar.

Comment 8

[Harish J P]

Hi,

It is easily reproducable for me. I am not able to reopen the bug. Sorry for the late response.

The steps to reproduce this:

* Closed every instance of firefox. ps -auxwww does not have firefox* in it.
* Now invoke firefox -ProfileManager. It comes up and shows a dialog allowing you to choose a profile.
* Choose a profile it starts working correctly.
* With this instance running invoke firefox -ProfileManager again. Now the profile manager does not come up at all instead launches another window with the profile chosen in the earlier step.
* Setting MOZ_NO_REMOTE=1 in the env does the trick and firefox comes up with the profile choice dialog.

--Harish.

Comment 9

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #8)
> * With this instance running invoke firefox -ProfileManager again. Now the
> profile manager does not come up at all instead launches another window with
> the profile chosen in the earlier step.
> * Setting MOZ_NO_REMOTE=1 in the env does the trick and firefox comes up with
> the profile choice dialog.

This is intended behavior. You must use MOZ_NO_REMOTE if you want multiple instances of Firefox running (i.e. to use multiple profiles).