Wrong error message when firefox update failed

RESOLVED INCOMPLETE

Status

()

--
minor
RESOLVED INCOMPLETE
10 years ago
8 years ago

People

(Reporter: ryanli, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-11-01])

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090508 Minefield/3.6a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090508 Minefield/3.6a1pre

Firefox displays wrong error message when it cannot apply update.

Reproducible: Always

Steps to Reproduce:
1. I have firefox nightly build in my home directory
2. As ubuntu firefox does, I linked the dictionaries directory to /usr/share/myspell/dicts, but forgot to chown
3. Apply Downloaded Update and restart firefox
Actual Results:  
The error message is: "The update could not be installed. Please make sure there are no other copies of Firefox running on your computer, and then restart Firefox to try again."

Expected Results:  
Firefox should tell correct detailed information that which file/directory it cannot write.

It seems that this update(20090506 to 20090508) won't modify the dictionaries directory, is it necessary to perform such a test? Leaving the directory unwriteable may also successfully finish the update.
This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.