mozilla upgrade causes enigmail install to crash preferences window

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
--
minor
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: John Pye, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421

When upgrading enigmail, you are told that if you have updated from an earlier
version of Mozilla, then you need to delete a file 'XUL.mfl' (on windows,
something else in *nix) after updating Enigmail. 

Although that works fine, I wondered why it has to be that way. Couldn't the
Mozilla installer delete that file if it exists. We are already told that we
must reinstall all our extensions/plugins anyway.

Reproducible: Didn't try
Steps to Reproduce:
1. install mozilla 1.4 or something
2. install enigmail 0.7 or something
3. update mozilla to latest 1.7 RC1
4. update enigmail to latest 0.8.3
5. (attempt to use enigmail: the mozilla preferences winow is broken and mozilla
won't shut down, there's a phantom window or something like that)
6. delete the XUL.mfl file
7. reinstall enigmail 0.8.3

Actual Results:  
Everything works fine, but it shouldn't be necessary to delete that file. I
thought maybe it should be deleted during the mozilla upgrade, but I don't know
if that would affect other things...

Expected Results:  
I expected to be able to install Enigmail with the one-click 'install' button
but instead I have to fiddle about finding a back-end file in a hidden folder
(my profile directory).

If you *don't* delete that XUL.mfl file, then it is impossible to change your
mozilla preferences until the above is done. Mozilla also fails to shutdown
correctly, and can't be restarted without first killing a phantom mozilla.exe
process using the task manager.
(Reporter)

Comment 1

14 years ago
Bug over on mozdev too :)

http://bugzilla.mozdev.org/show_bug.cgi?id=6292
The XUL.mfl file is automatically scrapped if we find a problem with it
(checksums, etc), which is why Mozilla installs don't need to manually scrap it.
 What exactly is enigmail doing that's failing?

Comment 3

14 years ago
The Enigmail bug was resolved as invalid: Seems Enigmail installation info 
explicitly requests the chrome folder in users profile directory to be deleted
before an upgrade of Mozilla?

I believe this bug shoule be resolved INVALID as well.
Product: Browser → Seamonkey

Updated

13 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.
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.