Closed Bug 205820 Opened 21 years ago Closed 21 years ago

"Don't ask at startup" fails on multiple profiles

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED
Milestone:
Firebird0.7

People

(Reporter: nparks, Assigned: noririty)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4b) Gecko/20030514 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4b) Gecko/20030514 Mozilla Firebird/0.6

Encountered in Moz FB under Win ME, May 13 and May 14 nightlies.

I have 2 profiles.  When I start FB, the profile mgr always appears, even if I
have previously checked "Don't ask at startup", 



Reproducible: Always

Steps to Reproduce:
1. Create at least 2 profiles.
2. Run Firebird.  Select a profile and check "Don't ask at startup".
3. Either exit the profile mgr or start Firebird and then exit.
4. Run Firebird again.

Actual Results:  
Profile mgr appears.  "Don't ask" is unchecked.



Expected Results:  
Should bypass profile mgr launch browser using the previously selected profile.
OS: other → Windows ME
(correction)

Expected Results:  
Should bypass profile mgr, and launch browser using the previously selected profile.


I've seen this problem ever since the .exe was renamed, but I haven't yet been
able to reproduce the bug in Mozilla SeaMonkey (it just crashes after installing?).

Can anyone else confirm that this is Mozilla Firebird specific?
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows ME → All
No problem with Mozilla App Suite.

In Mozilla Firebird, I see this error in my JavaScript console:
Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://communicator/content/profile/profileSelection.js :: StartUp :: line 97"
 data: no]

Probably related to bug 204908.
Cc'ing Conrad, since it's likely his patch is the reason for this breakage.
i get this problem even when i only have one profile: Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6.  but i also
seem to be having a lot of other problems with profile manager that nobody else
is experiencing, so its might be just my computer.  By the way, i don't
experience this with seamonkey with one or more profiles: Mozilla/5.0 (Windows;
U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030517
The reason that the exception cited in comment 3 happens is that FB is missing
this pref from its all.js (or equivalent thereof):
"pref("profile.manage_only_at_launch", false);" Add that pref and it will work.
I would, but I don't currently pull or build FB.
when i set the pref mentioned in comment #6, the "dont ask at startup" works
fine and the exception does not appear
*** Bug 205305 has been marked as a duplicate of this bug. ***
*** Bug 207236 has been marked as a duplicate of this bug. ***
This is marked as hardware=PC but I'm having the same exact problem on Mac OS X
10.2.6 using today's build. (6/20/2003)

...and just like it is reported here, I did not have the problem until I made a
2nd profile.
=> hardware = "all" per comment #10
See also bug #211860 which sounds like the flip side of this one.


Confirming Linux/CVS HEAD, and setting Hardware -> All for real
Hardware: PC → All
The solution proposed in comment 6 does indeed solve the problem. Reassigning.
Assignee: blakeross → noririty
checked in.
Status: NEW → RESOLVED
Closed: 21 years ago
Depends on: 204908
Resolution: --- → FIXED
verified with 20030721 build on W2K
Status: RESOLVED → VERIFIED
*** Bug 216088 has been marked as a duplicate of this bug. ***
*** Bug 221302 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.