165753 - Profiles are not saved. Browser will only start after creating a profile in profile manager each time.

Status: VERIFIED WORKSFORME

(Core Graveyard :: Profile: BackEnd, defect)

Description

[spliggity]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826

(This problem affected me on 1.0 and 1.1 - Full installs w/ or w/o quicklaunch)
I can run profile manager and create a profile and the "Start Mozilla" button 
will bring up an instance of Mozilla, but as soon as it exits the mozilla.exe 
shows a splash screen and then dies.  One thing to note is that I am using 
folder redirection for my Application Data, etc settings through group 
policies.  Is Mozilla having problems writing its info to a UNC profile path?  
If I bring up Profile Manager again after creating, running moz, and exiting, 
nothing is listed.

Reproducible: Always

Steps to Reproduce:
1. mozilla.exe produces a splash screen and dies.
2. profile manager shows none available, create one and finish and mozilla 
loads.
3. after closing mozilla, quicklaunch dies(if enabled), and re-opening profile 
manager shows no available profiles.

Actual Results:  
Each time I want to run mozilla in any way (I tried making it my default 
browser), I have to create a profile in profile manager and execute mozilla 
through the "Run Mozilla" button in profile manager.

Expected Results:  
It should be saving my profile :D and using it.

I tried running the talkback agent but nothing showed, I would debug this in 
linux but in XP its a bit more difficult.  Again, I'm using Folder 
Redirection, so perhaps there's a problem writing AppData to UNC paths, that's 
all I could come up with.

Comment 1

[Michael Lefevre]

reporter: can you reproduce this bug with a recent build of mozilla (for
example, 1.2beta)? if so, please comment again with details. if not, please
resolve this bug as WORKSFORME. thanks.

Comment 2

[Michael Lefevre]

no response from reporter for >60 days, resolving WORKSFORME.

reporter: if you can reproduce this bug with a recent build of mozilla (for
example, 1.2.1), please reopen this bug and give details. thanks.

Comment 3

[K'Trina Medina]

Verified WFM. Reporter, please reopen if problem still occurs.