422213 - failure in chrome registration if multiple extensions are being updated

Status: VERIFIED INVALID

(Toolkit :: Add-ons Manager, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9b5pre) Gecko/2008031109 Minefield/3.0b5pre - Build ID: 2008031109

During the last weeks, I have seen the following problem multiple times:
0. Minefield update: Clicked restart now.
1. Got the "New Add-on updates available" pop-up.
2. Downloaded the updates.
3. Got the following error message: Minefield could not install this item because of a failure in Chrome Registration. Please contact the author about this problem.
( http://mxr.mozilla.org/firefox/source/toolkit/locales/en-US/chrome/mozapps/extensions/extensions.properties#75 )
All add-on updates installed fine, but the compatibility updates for extensions got lost (which bump the maxVersion).

The last time this happened was after upgrading from yesterday's today's nightly and upgrading IE Tab, View Dependencies, MR Tech Toolkit 6.0a22 to 6.0a23 and Searchbar Autosizer.

Comment 1

[Dave Townsend [:mossop]]

Anything in extensions.log?

Comment 2

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

2008-03-11 19:37:17 - upgradeExtensionChrome: failed for extension [e-mail] - why not convert to the new chrome.manifest format while you're at it? Failure exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.create]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///F:/Software/Browser/Firefox%20Trunk/components/nsExtensionManager.js :: anonymous :: line 1782"  data: no]

This is the Microsummary Generator Builder extension, but it isn't compatible with the trunk at all.

Comment 3

[Dave Townsend [:mossop]]

That's not one of the extensions that got updated right?

Comment 4

[Dave Townsend [:mossop]]

Also is the extension working ok at the moment and do you see a chrome.manifest file in it's directory in <profile>/extensions/[e-mail] ?

Comment 5

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Yes, this didn't get updated. It is in active because it is incompatible.

The problem is: The file manager shows the chrome.manifest with 212 bytes, but if I open it in the editor, it tells me that the file doesn't exist.

Comment 6

[Dave Townsend [:mossop]]

(In reply to comment #5)
> Yes, this didn't get updated. It is in active because it is incompatible.
> 
> The problem is: The file manager shows the chrome.manifest with 212 bytes, but
> if I open it in the editor, it tells me that the file doesn't exist.

Ok that makes some sense. From the EM's point of view it believes the file doesn't exist and then fails when it tries to create it. I suggest you should run a disk check, I suspect that file is just corrupt.

The reason this extension is even getting touched by the upgrade is a side effect of bug 415175

Comment 7

[Dave Townsend [:mossop]]

Did anything come of the disk check?

Comment 8

[Dave Townsend [:mossop]]

I'm fairly confident that the real problem here was a disk error and in that case there isn't a lot we can do to make everything work correctly. If this isn't the case then please reopen.