Closed Bug 250913 Opened 20 years ago Closed 20 years ago

No Profile Manager with the .ZIP Windows file / installer "Firefox-win32-0.9.2.zip"

Categories

(Toolkit :: Startup and Profile System, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 250680

People

(Reporter: BTJustice, Assigned: benjamin)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2

After extracting the files to "C:\firefox", clicking on START > RUN then typing
in "C:\firefox\firefox.exe" -P no longer brings up the Profile Manager.

----------

I can extract the files in Firefox-win32-0.9.1.zip to C:\firefox then run...

"C:\firefox\firefox.exe" -P

And it brings up the Profile Manager.

----------

I can install FirefoxSetup-0.9.2.exe to C:\Program Files\Mozilla Firefox then run...

"C:\Program Files\Mozilla Firefox\firefox.exe" -P

And it brings up the Profile Manager.

----------

I can extract the files in Firefox-win32-0.9.2.zip to C:\firefox then run...

"C:\firefox\firefox.exe" -P

And it DOES NOT bring up the Profile Manager.

----------

Reproducible: Always
Steps to Reproduce:
1. In Windows, extract the files in "Firefox-win32-0.9.2.zip" to C: which will
create "C:\firefox".
2. Click on START > RUN and type in "C:\firefox\firefox.exe" -P
3. Instead of the Profile Manager appearing, nothing happens.

Actual Results:  
Nothing.  The Profile Manager no longer comes up.  This only happens with
installing the .ZIP.  The Profile Manager appears just fine after installing
with the .EXE version.

Expected Results:  
Open the Profile Manager.
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040707 Firefox/0.9.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040707 Firefox/0.9.2
Ben/mconnor, got a clue what's going on here? This worked in 0.9.1, right?
Flags: blocking-aviary1.0RC1+
Benjamin Smedberg:  Yes it worked fine with "Firefox-win32-0.9.1.zip".
How about the "-ProfileManager" command line argument?
hmm, I haven't tested the zip version, I know the installer version is fine,
which is a huge shock (its always the other way around)
Read another forum thread; ignore comment #4.
(In reply to comment #4)
> How about the "-ProfileManager" command line argument?

That doesn't work either.
I don't know if this is important or not, but, if you guys are testing this on
Windows XP, be sure to go to the Application Data folder for the account /
username you are logged in as and delete the Mozilla & Talkback folders there
(assuming you have things backed up).
I suppose it would be the same in Windows 9x & ME by going to
C:\Windows\Application Data.
Have any of you guys had any luck with this yet?  I appreciate it.
Confirming:
With 0.9.2 zip build, neither -ProfileManager nor -p works.

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040707 Firefox/0.9.2
Status: UNCONFIRMED → NEW
Ever confirmed: true
This bug is a duplicate of bug 250680
I can confirm, that the installer works fine, but the zip file doesn't
(In reply to comment #12)
> This bug is a duplicate of bug 250680
> I can confirm, that the installer works fine, but the zip file doesn't

No... it is similar, but not a duplicate.  And 250680 isn't all that descriptive
either.
How is it not a duplicate? Both bugs describe the same thing: the profile
manager no longer works via the command line in ZIP builds.
(In reply to comment #14)
> How is it not a duplicate? Both bugs describe the same thing: the profile
> manager no longer works via the command line in ZIP builds.

It is just the way it is written.  Upon reading it again, yes it does sound the
same, but most people do not use -profilemanager.  Most simply use -p.
(In reply to comment #15)
> It is just the way it is written.  Upon reading it again, yes it does sound the
> same, but most people do not use -profilemanager.  Most simply use -p.

Also he said he was trying to start Firefox.  I was not.  I was trying to start
the Profile Manager.

Its the same bug, whether he reported it in different words, its the same root
cause/failure case.

*** This bug has been marked as a duplicate of 250680 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Swell... now fix it.
Commment #2 & #5 make me think none of you guys even knew about the other bug.
this isn't a messageboard, or a place for debate or unhelpful comments.  its
quite possible that out of one or two thousand bugs reported, we're not aware of
every single one personally.  Being rude isn't going to get you anywhere.

Also, considering that its quite possible that we'll drop profile manager
entirely, this might be invalid soon.  (Don't bother commenting in this bug
about that, there's a bug on it already, and spamming that bug won't make a
difference either.)
Status: RESOLVED → VERIFIED
I didn't mean it that way.  Here I am reporting a bug, you bug fixers come in
commenting in a way that sounded like no one knew about it, then all the sudden
some dude comes in and says this a repeat so I go and look at his and he states
he was trying to start Firefox whereas I just wanted the Profile Manager.

I know you guys are busy.  On top of that, why not just use -p instead of
-profilemanager?  Simplicity is our friend.

I hope you are not serious about getting rid of the Profile Manager.  A lot of
people make custom versions of Firefox and the key to doing it is making a
profile that will store files & settings in a certain place on any computer it
is installed on.  This is a great benefit to new people who like MSIE.  Believe
it or not, Firefox's default install sucks.  It has next to no features & won;t
even do tabbed browsing right without the proper extensions.
Flags: blocking-aviary1.0PR+
Firefox-win32-0.9.3.zip appears to have a working Profile Manager now.  I
clicked on RUN and used...

"C:\Program Files\Mozilla\firefox\firefox.exe" -P
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.