Closed
Bug 19030
Opened 25 years ago
Closed 25 years ago
Exiting without choosing a profile leads to non-start the next time
Categories
(Core Graveyard :: Profile: BackEnd, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M13
People
(Reporter: momoi, Assigned: racham)
Details
** Observed with 11/15/99 Win32 M11 build ** I hope this is a known bug. I don't know if this is true with M12 but it was dicovered while looking M11 candiadte build for Windows. 1. Start with: mozilla -installer 2. When the Profile Manager comes up, don't select any profile but exit. 3. The next time you run Mozilla without the -profile option, Windows version never starts. There is no way to start Mozilla unless the Profile Manager is run and a profile is chosen or created.
Updated•25 years ago
|
Assignee: selmer → racham
Comment 1•25 years ago
|
||
Bhuvan, this looks related to the forget current profile stuff from the code review comments. What happened to the code that's supposed to force them into the profile manager or just use their single profile???
I just checked the behavior on My NT box with today's build. 1. Ran app with -installer flag (mozilla -installler). 2. Had bunch of 4x profiles. Exit profile manager without doing anything. This simply means we have no 5x profiles sofar. 3. Ran the app again (by typing mozilla). As we have no 5x profiles, the createProfile wizard shows up and allows you to create a profile and proceed without any problems. One drawback the way it is that user needs to run mozilla -ProfileManager to see the list of unmigrated profiles. We need to fix that. Marking TFV M13.
Reporter | ||
Comment 3•25 years ago
|
||
My report is more about a case like this: 1. You have **one** existing profile in use. (You also have some un-migrated profiles.) There are no other existing profiles. 2. start: mozilla -installer 3. You see your one exsiting profile along with un-migrated ones. 4. You change your mind about creating or migrating a profile, and exit without selecting any profile. 5. The next time you try "mozilla" without "-profile", it simply will nor start. Double-clicking on "mozilla" leads to the same non-start. If you have more than 1 existing profiles, this problem does not seem to happen. I just checked today's Win32 build and this problem still occurs. Build: 1999111608 Win32.
I could reproduce the behavior you mentioned. The expected behavior is that the app should just proceed with the single 5x profile you have created. I'll look into this. Thanks.
*** Bug 19434 has been marked as a duplicate of this bug. ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
If no current profile is found at the beginning of the app, first of the available profiles is picked. Fix checked in. Marking fixed.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 7•25 years ago
|
||
build 1999121008
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
Updated•8 years ago
|
Product: Core → Core Graveyard
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•