38095 - Profile manager breaks if home dir doesn't exist

Status: VERIFIED WORKSFORME

(Core Graveyard :: Profile: BackEnd, defect, P3)

Description

[John G. Myers]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; OSF1 V5.0 alpha; en-US; m16) Gecko/20000502
BuildID:    2000042708

Set the HOME environment variable to a directory that doesn't exist.
Start Mozilla.
Notice that there are no profiles listed, yet the "Start mozilla" button has an
enabled appearance.  The button should have a disabled appearance.

Create a profile, in that directory the user cannot create.  Profile manager
allows the profile to be created.  When you then click on "Start mozilla", it
dumps core.



Reproducible: Always

Comment 1

[Ben Goodger (use ben at mozilla dot org for email)]

selmer. 

Comment 2

[selmer (gone)]

A new corner case to guard against...

Comment 3

[racham]

Doing a mass reassign to Conrad Carlen.

Conrad is going address all current and upcoming profile manager issues. Please
do not hesitate to involve me in any of the issues.

Comment 4

[Conrad Carlen (not reading bugmail)]

Is this still happening with current builds?

Comment 5

[Grace Bush]

changing $HOME to a directory that does not exist-and removing all previous 
profile information:
running mozilla - creates the non-existent directory then creates profile called 
default in that directory. 
note does not look for 4.x profile to migrate since $HOME/.netscape not 
available

build 20010305

Comment 6

[Conrad Carlen (not reading bugmail)]

Grace, From your last comment, I'd say that says WFM.

Comment 7

[Grace Bush]

verify