Bug 244591 (Mozilla_Hang)

Changed "Local Folders" to F:\Users\bdg\... in Mail/News profile, Mozilla now Hangs when starting Mail.



15 years ago
13 years ago


(Reporter: BDGubser, Unassigned)


Windows 98

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a1) Gecko/20040520
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a1) Gecko/20040520

I copied the folders from the default C:\Windows\App...Data\... to my F:\Users\Bdg
folders using same structure, etc. This had worked before with earlier Mozilla
(1.2?). Now after starting Mozilla in browser mode, Mozilla hangs trying to
start Mail client.

Reproducible: Always
Steps to Reproduce:
1. Start Mozilla in browser.
2. Using Cntl-2 to start Mail.
3. Mail client does NOT start up (no new "Mail" window).

Actual Results:  
Mozilla Hangs....

Expected Results:  
New Mail window should appear.


15 years ago
Alias: Mozilla_Hang

Comment 1

15 years ago
By replacing prefs.js in original default location
(C:\Windows\App...Data\Mozilla\Profiles\....) Mail now works.

Comment 2

15 years ago
Following are lines from prefs.js:

Causes "Hang"
user_pref("mail.server.server1.directory", F:\\Users\\bdg\\Mail\\mail.comcast.net");

Original (working version):
user_pref("mail.server.server1.directory", "C:\\WINDOWS\\Application
user_pref("mail.server.server1.directory-rel", "[ProfD]Mail/mail.attbi.com")

Comment 3

15 years ago
Could it be related to bug 241708 comment 17? So it should now work with a newer
Sounds like Bug 242579 & Bug 242970.

>Bug 242579
> Multiple mail copy/move hangs when drive of mail directry is different from
one for profile directry (bug 242970 also occurs).
> This causes hang of Junk move/Junk purge and multiple mail delete.

>Bug 242970
> Bug 241708 has broken Mail&News when mail directry on different drive from one
for profile directry.
> (Server Settings/Local directory was changed to \\.\D:\pop3.server.name after
2004-04-29 build)

If same problem, try trunk builds after 2004-05-21.
As ostgote says, patch for these bugs(bug 241708 Comment #14) was unfortunately
not landed on 1.8a1 release build(2004-05-20 build).
Product: Browser → Seamonkey


14 years ago
Assignee: sspitzer → mail
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.