Closed Bug 110453 Opened 23 years ago Closed 23 years ago

-selectprofile hangs loading the default profile

Categories

(Core Graveyard :: Profile: BackEnd, defect)

DEC
OpenVMS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: colin, Assigned: ccarlen)

Details

I am seeing something that might be related to bug #104281.
I have just one profile, named "default". If I start up Mozilla with
no args everything is fine:

$ @mozilla
Starting mozilla-bin...

[mozilla comes up with default profile]

If I start up using -p everything is fine:

$ @mozilla -p default
Starting mozilla-bin...
ProfileName : default

[mozilla comes up with default profile]

But if I start up using -selectprofile, and then select "default" from
the profile selection list (the only profile), it hangs:

$ @mozilla -selectprofile
Starting mozilla-bin...
ProfileManager : StartApprunner
profileName passed in: default

[mozilla hangs - no I/O - no CPU]

This is on OpenVMS (built like Linux), on an almost 0.9.6 build. But I
see identical behaviour on my 0.9.5 build.
More info. If I create another profile then I can start mozilla with the new
profile using -selectprofile, but I still can't get mozilla to start with the
default profile.
Unfortunately I can't reproduce this one my Linux system running 0.9.5. Sigh...
Can you repro it with the lastest nightly?
I don't have any trunk builds at the moment, only 0.9.6 branch builds.

Why do you ask, has something changed on the trunk in the last few days which 
might have fixed this?
Blocks: 110874
No longer blocks: 110874
I can no longer reproduce this problem, either in the released 0.9.6 or the 
released 0.9.7 versions. Marking WORKSFORME.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Verified WFM. Per reporter, problem no longer exists on current builds.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.