280745 - automatically Downloaded Foxytunes update and Firefox brouser is severely disabled afterwards

Status: RESOLVED EXPIRED

(Toolkit :: Add-ons Manager, defect)

Description

[mark]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217

I downloaded the Foxytunes 1.0 update on Jan 30 after an update window popped
up.  after the software was installed a display window came up with an error
message saying the update was unsucessfull and the brouser was not functional. 
I can't search the web or acess any of the tabs to fix anything like
File...Edit...View.  Several attempts to uninstall and reinstall the brouser and
Foxytunes software have been unsucessful

Reproducible: Always

Comment 1

[Asa Dotzler [:asa]]

Sounds like a bug in the Foxytunes extension. Can you uninstall Foxy tunes by
deleteing it from your profile extension directory or starting in safe mode and
then try to reproduce by installing the old extension and updating it?

Comment 2

[Alex Sirota (iosart)]

(In reply to comment #1)
> Sounds like a bug in the Foxytunes extension. 

Asa, I've seen many similar reports since FF 0.9, but they are not limited to
FoxyTunes - in fact, this seems to happen with many/all extensions. I haven't
been able to reproduce it, but the update/install process somehow leads to
chrome registry/overlay corruption. 

Please let me know if there's something I can do to help reproduce/solve these
problems. 

Comment 3

[Chris Pederick]

I had the same issue reported with an update to my User Agent Switcher
extension. Someone looked into this and tracked it down to a problem with
overlay changes not being correctly updated by the install process. You can read
more about this here:

http://www.chrispederick.com/forums/viewtopic.php?id=589

This is seems like a fairly serious issue and I didn't find a generic version of
the bug so I am adding my report to this bug.

Comment 4

[Nickolay_Ponomarev]

If it is indeed the problem (Alex, could you confirm/deny that you have
renamed/removed any overlay files in that update?), then it is bug 275148,
probably fixed by patch in bug 278534.

Comment 5

[Alex Sirota (iosart)]

(In reply to comment #4)
> If it is indeed the problem (Alex, could you confirm/deny that you have
> renamed/removed any overlay files in that update?), then it is bug 275148,
> probably fixed by patch in bug 278534.

No, I have never changed the FoxyTunes overlay structure. It seems that
something with the chrome registration sometimes goes wrong. It will be
interesting to see if after the bug 278534 patch (new chrome manifests) these
reports disappear.

Comment 6

[Gervase Markham [:gerv]]

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/

Comment 7

[Gervase Markham [:gerv]]

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.