Closed
Bug 253513
Opened 21 years ago
Closed 21 years ago
Firefox does not start if more than one profile is referenced within profiles.ini
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 250680
People
(Reporter: whimboo, Assigned: benjamin)
Details
(Keywords: regression)
Confirmend with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7)
Gecko/20040728 Firefox/0.9.1+
I can see this bug since a couple of days. I didn't have tested all nightly
build but i know that the last one i used is Mozilla/5.0 (Windows; U; Windows NT
5.0; en-US; rv:1.7) Gecko/20040719 Firefox/0.9.1+ and this build is working.
Looking into my profiles.ini shows following entries:
[General]
StartWithLastProfile=0
[Profile0]
Name=Standard
IsRelative=0
Path=X:\Anwendungsdaten\Firefox
[Profile1]
Name=Test
IsRelative=1
Path=Profiles/test
Default=1
When i remove Profile1 manually from this file and start FF again, than it is
working. So i copied the data of profile0 to profile1 to test, if we have a
problem with 'IsRelative=1' but that's not the problem. It seems that we have a
regression here.
Reporter | ||
Updated•21 years ago
|
Flags: blocking-aviary1.0PR?
Summary: Firefox doesn't start when more than one profile is referenced within profiles.ini → Firefox does not start if more than one profile is referenced within profiles.ini
I see it too (in zip builds, installer build seems to work). But I don't think
it is the number of profiles that is the problem here. Firefox starts if I have
StartWithLastProfile=1 in profiles.ini, and I can also start with the -p
"profile" switch. So it looks like a problem with the Profile Manager.
Assignee | ||
Comment 2•21 years ago
|
||
*** This bug has been marked as a duplicate of 250680 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Flags: blocking-aviary1.0PR?
Reporter | ||
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
Updated•17 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•