User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 ISP (not Modem) broke connection during mail saving process; that resulted in freezing of Mozilla immediately and ! after closing program and even OS and restarting it, whenever a tried to save or send a newly composed message; address book was not accessible either. After unistalling/re-installing 1.2.1. , there was no improvement, i.e. the profile information was corrupt. Only by creating a new profil, mailnews was working as before. Reproducible: Always Steps to Reproduce: 1. open old profil 2. create message 3. save or send it Actual Results: mozilla freezes, only window frame remain visible; other programmes were not affected. Expected Results: ... problem probably was caused by ISP which is in the process to upgrade the system without closing down completely but with frequent shut downs (radically!)
Reporter, please do the following: 1. Close Mozilla. 2. Find your profile, and delete the "xul.mfl" file there. 3. Start Mozilla 4. Try to recreate the problem? Does that solve it?
Summary: so saving/sending possible, programm completely freezes due to corrupt profile data → so saving/sending possible, programme completely freezes due to corrupt profile data
If the above step does not work, then try this: Disable copy to Sent folder. Then try to reproduce this problem. Does the problem still happen?
Reporter, to troubleshoot this problem, please follow these steps. When you reply, make sure to include your operating system version, and the build ID. The build ID is located in the Mozilla title bar. If the problem is sovled, please indicate what step solved it. 1. Make sure that the test machine you're running is in good condition. On Windows 9x, run scandisk. On Windows NT/2000/XP, error-check the drives. On *nix, check for filesystem errors. Furthermore, if you have an antivirus program, make sure the antivirus definitions and program files are up to date. Make sure you have recently scanned the system for viruses, and removed any you find. 2. Download and install the latest trunk nightly build. Running a nightly build has a slight amount of risk involved. Back up your Mozilla data including your bookmarks before proceeding. You can download the latest nightly build from ftp://ftp.mozilla.org/pub/mozilla/nightly/latest . For example, for Windows, download the file mozilla-win32-installer-sea.exe. Uninstall your current Mozilla build. Make sure the new directory where you will install the new build is completely empty, except for any plugins subdirectory. Install the nightly build. Having done that, can you still reproduce the problem? 3. If it still fails, exit Mozilla. Go to your profile directory. Find the file xul.mfl (or xul.mfasl on *nix). Rename it. Restart Mozilla. Does that solve the problem?
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.