Profile Manager does not appear when trying to create a second profile and turbo is on

VERIFIED FIXED in mozilla1.0.1

Status

Core Graveyard
QuickLaunch (AKA turbo mode)
VERIFIED FIXED
16 years ago
5 years ago

People

(Reporter: Ninoschka Baca, Assigned: Stephen P. Morse)

Tracking

Trunk
mozilla1.0.1
x86
Windows ME
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [adt3 RTM])

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

16 years ago
Branch build 2002-06-03: WinMe
Edited all.js pref and turned the single profile pref to false.

Overview: Profile Manager does not appear when trying to create a second profile

Steps to reproduce:
1. Do a clean install  - emulating first time install on a machine- and have 
multiple 4.x profiles
2. The first launch shows me the ProfileManager with a list of the profiles to 
be migrated.  
3. Choose one and launch etc.  QuickLaunch icon is in the system tray. 
4. Exit
5. Select File|Programs|Netscape|Profile Manager

Actual Results: Profile Manager does not appear. Instead it shows the browser
using the first profile. I also tried using flags such as -installer or
-profilemanager and neither one worked. 

Workaround: I had to turn turbo off, then I could access Profile Manager to
create the second account. 

I logged this as a separate from bug#124255 because the Profile Manager doesn't
appear in any case so long as turbo is on.
(Reporter)

Comment 1

16 years ago
Marking nsbeta1 because if the New Turbo Model is used by default for multiple
accounts then this will make it difficult for the user to discover how to create
the second profile. They have to turn turbo off to see Profile Manger to then
create the second profile.
Keywords: nsbeta1

Comment 2

16 years ago
nsbeta1+/adt3 per nav triage team
Blocks: 108795
Keywords: nsbeta1 → nsbeta1+
Whiteboard: [adt3]
Target Milestone: --- → mozilla1.0.1

Comment 3

16 years ago
->morse
Assignee: law → morse
(Assignee)

Comment 4

16 years ago
Let me paraphrase this bug a bit so as to make it a bit easier to reproduce.

1. Using profile manager normally (w/o turbo), create or delete profiles to that 
you have exactly two of them.

2. Exit profile manager

3. type "mozilla -turbo"

4. type "mozilla -profilemanager".  Profile manager launches as expected

If you do the same steps but with only one profile in step 1, you will not get 
the profile manager in step 4.

So the problem occurs only when you have exactly one profile, turbo is executing 
(i.e., icon on status bar, no windows open), and you try to launch profile 
manager.

Comment 5

16 years ago
If this is not fixed for RTM, the workaround should be mentioned in the release
notes.  Added relnote keyword.
Keywords: relnote
(Assignee)

Comment 6

16 years ago
Another interesting observation.  Everything works fine in this scenario

1. Using profile manager normally (w/o turbo), create or delete profiles to that 
you have exactly one profile.

2. Start browser, go to preferences and set turbo mode on.  Turbo icon appears

3. Exit browser.  Turbo icon remains.

4. type "mozilla -profilemanager".  Profile manager launches as expected
Keywords: relnote
(Assignee)

Comment 7

16 years ago
BTW, this problem has *NOTHING* to do with the new turbo model.  The same 
behavior would have occured in the old model as well.  Removing "New Tubro 
Model:" form summary to reflect that.
Status: NEW → ASSIGNED
Summary: New Turbo Model: Profile Manager does not appear when trying to create a second profile → Profile Manager does not appear when trying to create a second profile and turbo is on
(Assignee)

Comment 8

16 years ago
Problem is occuring on the following line in 
nsNativeAppSupportWin::EnsureProfile

  if (!mForceProfileStartup && NS_SUCCEEDED(rv) && haveProfile)
      return NS_OK;

At this point haveProfile should be false if we were started up with 
-profilemanager.  But instead it is coming up true unless there is more than one 
profile.
(Assignee)

Comment 9

16 years ago
Created attachment 86536 [details] [diff] [review]
set mForceProfileStartup if invoked with -profilemanager
(Assignee)

Comment 10

16 years ago
Created attachment 86558 [details] [diff] [review]
take into account the case that window is open and profilemanager is invoked
(Assignee)

Updated

16 years ago
Attachment #86536 - Attachment is obsolete: true
I can sr if blake or bill will r.

Comment 12

16 years ago
Comment on attachment 86558 [details] [diff] [review]
take into account the case that window is open and profilemanager is invoked

r=law
Attachment #86558 - Flags: review+
Comment on attachment 86558 [details] [diff] [review]
take into account the case that window is open and profilemanager is invoked

sr=ben@netscape.com
Attachment #86558 - Flags: superreview+

Comment 14

16 years ago
adt1.0.1+ (on ADT's behalf) for checkin to the 1.0 branch, pending Driver's
approval. pls check this in asap, then add the keyword "fixed1.0.1".
Blocks: 143047
Keywords: adt1.0.1+, mozilla1.0.1
Whiteboard: [adt3] → [adt3 RTM]

Comment 15

16 years ago
Comment on attachment 86558 [details] [diff] [review]
take into account the case that window is open and profilemanager is invoked

a=asa (on behalf of drivers) for checkin to the 1.1 trunk.
Attachment #86558 - Flags: approval+
(Assignee)

Comment 16

16 years ago
Fixed on trunk.  Pending drivers approval for branch checkin
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 17

16 years ago
marking verified on trunk build 2002060908
profile manager is now accessible using steps outlined in comment 1
 from start menu
 using options -profilemanager and -installer
Status: RESOLVED → VERIFIED

Comment 18

16 years ago
please checkin to the 1.0.1 branch. once there, remove the "mozilla1.0.1+"
keyword and add the "fixed1.0.1" keyword.
Keywords: mozilla1.0.1 → mozilla1.0.1+
(Assignee)

Updated

16 years ago
Keywords: mozilla1.0.1+ → fixed1.0.1

Comment 19

16 years ago
same tests on branch build for 6/11
Keywords: fixed1.0.1 → verified1.0.1
Component: QuickLaunch (AKA turbo mode) → QuickLaunch (AKA turbo mode)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.