Closed
Bug 562936
Opened 15 years ago
Closed 15 years ago
Unable to install add-ons: different hashes
Categories
(Toolkit :: Add-ons Manager, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: aryx, Unassigned)
Details
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100430 Minefield/3.7a5pre (.NET CLR 3.5.30729)
Trying to install add-ons in the new add-ons manager from the AMO page results in file hash conflicts like
"The download of https://addons.mozilla.org/en-US/firefox/downloads/latest/722/addon-722-latest.xpi?src=search failed: -2"
Error console (needs maybe extensions.logging.enabled=true):
LOG addons.xpi: Download started for https://addons.mozilla.org/en-US/firefox/downloads/latest/722/addon-722-latest.xpi?src=search to file C:\DOKUME~1\SEBAST~1\LOKALE~1\Temp\tmp-pvy.xpi
LOG addons.xpi: Download of https://addons.mozilla.org/en-US/firefox/downloads/latest/722/addon-722-latest.xpi?src=search completed.
Warning: WARN addons.xpi: Download failed: Downloaded file hash (e5fa0a2d3b7cdb419c224649c45b12cdc313d86d125c470e680a4965ab352af4) did not match provded hash (b64da358f4dc97627abfd910e3466091744f942e9af8d7d779ecac17c753516d)
Tested with Noscript from https://addons.mozilla.org/en-US/firefox/search?q=noscript&cat=all and Adblock Plus 1.2
Comment 1•15 years ago
|
||
It doesn't happen with the old addons manager?
![]() |
Reporter | |
Comment 2•15 years ago
|
||
Works now with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100430 Minefield/3.7a5pre (.NET CLR 3.5.30729)
(I'm sure I got a second nightly update today, size 2.4 MB)
Comment 3•15 years ago
|
||
hmm, so it was an AMO fallout?
![]() |
||
Comment 4•15 years ago
|
||
In the past we've had conditions where one update check will get mixed up with another. This *might* be what is happening here with the rewrite.
Updated•15 years ago
|
Priority: -- → P2
Comment 5•15 years ago
|
||
Sounds like this was AMO's side.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•