Closed Bug 193768 Opened 22 years ago Closed 19 years ago

Crashes on load when APPDATA set to a network share

Categories

(Core Graveyard :: Profile: BackEnd, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mozillabugs, Assigned: ccarlen)

References

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030211 Phoenix/0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030211 Phoenix/0.5 After install, mozilla crashes on load when APPDATA is set to a network share. It never gets past the splash screen. Example of APPDATA: APPDATA=\\fin321\ProfilesG-L\graessle\Application Data After changing all instances of APPDATA in registry, Mozilla loaded with no isses. Reproducible: Always Steps to Reproduce: 1. Install on a computer with APPDATA set to a network share 2. Launch 3. Watch splash screen come and go Actual Results: Nothing. After splash screen disappears, you are back to step 2. Expected Results: It should have launched a window that allows browsing, checking of mail, etc. This is Win32 only and there is a work arround. Work arround sucks as it requires regedit. This bug is making it hard to get co-workers to test webcontent in mozilla/netscape. Also of note is that once you get Mozilla working, it doesn't seem to crash even with APPDATA set to a network share. Our admins reset my registiry changes after it was working and it didn't stop working. Maybe this isn't APPDATA but some other aspect of having a roaming profile.
Blocks: 101953
Reporter, do you have a Talkback ID?
Keywords: crash
No Talkback ID is created. ( I'm not sure if talkback was installed. ) But, I did find a workaround. The problem seems to be with the profile manager, not mozilla. It seem that the profile manager can't create a profile on a MS network path. Works fine if network path is mapped to a local drive letter. Copying the mozilla profile directory from a working install fixed the issue. Example of workaround: Copy directory c:\Documents and Settings\graessle\Application Data\Mozilla to \\fin321\ProfilesG-L\graessle\Application Data\Mozilla If the directory \\fin321\ProfilesG-L\graessle\Application Data\Mozilla is renamed or deleted Mozilla once again quits on start.
This bug seems to be related to bug 162025 - duplicate ?
Michael, are you still seeing this with 1.7 beta or newer?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.