Closed
Bug 251931
Opened 21 years ago
Closed 21 years ago
can't update any extensions or themes.
Categories
(Toolkit :: Add-ons Manager, defect, P1)
Tracking
()
RESOLVED
FIXED
People
(Reporter: stefan.vallaster, Assigned: bugs)
References
Details
(Keywords: fixed-aviary1.0)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040717 Firefox/0.9.1+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040717 Firefox/0.9.1+
can't update any extensions or themes, firefox shows the message: "Firefox was
not able to find any available updates. Firefox encountered problems when tryubg
to find updates for some items."
Reproducible: Always
Steps to Reproduce:
1. click in the toolbar on tools
2. than click on extensions or themes
3. choose one theme or extensions and press the update button
Actual Results:
the same es everytime
Expected Results:
say that their is no update this time, or give me a message that their is an
update to download
Confirming: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040722 Firefox/0.9.1+
I was able to reproduce this on WinXP. I created a new profile and did not see
the problem. I then installed the beta of the ieview extension
(http://ieview.mozdev.org/) and did see the problem.
When I clicked "Details", the list box was empty.
Reporter | ||
Updated•21 years ago
|
Severity: normal → major
Comment 2•21 years ago
|
||
*** Bug 253353 has been marked as a duplicate of this bug. ***
Comment 3•21 years ago
|
||
*** Bug 253075 has been marked as a duplicate of this bug. ***
Comment 4•21 years ago
|
||
Confirming based on dupes, carrying over blocking flags. Not sure if this
should be in EM or Software Update.
Message from bug 253353:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]" nsresult:
"0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
chrome://mozapps/content/update/update.js :: anonymous :: line 423" data: no]
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-aviary1.0PR?
Flags: blocking-aviary1.0?
Comment 5•21 years ago
|
||
I'm having the same problem and seeing the same error in the JS console on WinXP
SP1.
UA: Mozilla/5.0 (Windows; compatible; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040730 Firefox/0.9.1+
Comment 6•21 years ago
|
||
I have the same problem under linux. The update window thinks for quite a while
and then always fails to find updates despite updates being available upon
manual inspection -- but I haven't yet verified whether I'm getting the same JS
error.
OS: Windows 2000 → All
Comment 7•21 years ago
|
||
I still see this on 20040731 with the Js error mentioned above.
A major feature is broken here so I really think this should be blocking+
Moreover, this does not only happen when trying to update themes or extensions.
even clicking on the box on the status bar gives the same error.
Reporter | ||
Updated•21 years ago
|
Severity: major → critical
Comment 8•21 years ago
|
||
+ for PR1... need to figure out what is going on.. asa, can you help investigate?
Flags: blocking-aviary1.0PR? → blocking-aviary1.0PR+
Comment 9•21 years ago
|
||
same problem with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803
Firefox/0.9.3. (and 0.9.2 also)
I have my own extensions, with their own update.rdf on a website. Updates works
rarely. Some times, it works, i don't know why. The most of time, it doesn't work.
Comment 10•21 years ago
|
||
Firefox 0.9.2 and 0.9.3 only contained security updates. I would suggest trying
one of the current aviary1.0 branch builds to see if those work any better.
Comment 11•21 years ago
|
||
This may be another bug (#253220 maybe?), but any attemp to update searches
forever without another message/error when you have proxy enabled (bad for
people with forced proxy)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803
Firefox/0.9.1+ (MOOX-AV)
Comment 12•21 years ago
|
||
*** Bug 247093 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•21 years ago
|
Flags: blocking-aviary1.0? → blocking-aviary1.0+
Priority: -- → P1
Comment 13•21 years ago
|
||
I am using WinXP RC2, and clicked on the update button on the bottom of the tool
bar, and got two updates for installation - one for the Tabbrowser Preferences,
and one for the FF 1.0 preview release. I was able to update the TBP
successfully, but was not able to update FF. Now I have a stop sign in the task
bar telling me I still have one critical update, and when I click on it, it goes
back to old disfuctional behavior as mentioned in the original comment for this
bug. Oh, yeah, I have Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040809 Firefox/0.9.1+.
Comment 14•21 years ago
|
||
(In reply to comment #11)
> ...but any attemp to update searches
> forever without another message/error when you have proxy enabled (bad for
> people with forced proxy)
Works now with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2)
Gecko/20040810 Firefox/0.9.1+ (MOOX M2)
Well I get at least the usual "Firefox was not able to find any available updates."
Comment 15•21 years ago
|
||
Sorry for spamming, but it does not work anymore (searches forever again), don't
remember having changed anything at all. Also the "not able to find any
available updates" was not correct since I got that with Extensions who had
newer Versions listed on the official Update-Site.
Assignee | ||
Comment 16•21 years ago
|
||
almost everything here that's needed is in place, just need another round of
testing/verification.
Assignee | ||
Comment 17•21 years ago
|
||
This should work now.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Keywords: fixed-aviary1.0
Comment 18•21 years ago
|
||
Trying to update my extensions.
When checking, display of names of checked extensions/themes would have been
more convincing then just a throbber.
After checking my extensions (Bookmark Backup 3.0, Adblock v.5 * nightly 39,
Favicon picker 0.1, SpoofStick 1.02), Firefox Updates displays the "Updates
found" panel with no updates (white window), which may be normal.
However, the "Install now" button is live even though no updates were found, and
when clicked, "Installing updates" goes into an endless loop.
This cannot be considered as completely resolved.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040819
Firefox/0.9.1+
Comment 19•21 years ago
|
||
I agree. There are several problems:
* It seems that I can update only one extension at a time. Still Firefox tells
that it is "searching for compatibility updates to your Extensions and Themes"
in plural. It would be nice to be able to update all extensions with one click.
Now it is impossible to select more than one extension. And before it showed a
list of failed updates, and that always contained only one extension. Now it
does not show that list anymore, it does not tell which Extension(s) and
Theme(s) failed to update.
* Checking the extension update takes too long and it still does not work. I get
no updates for Linkification 0.8.5 even though there seems to be version 0.9.4.
Comment 20•21 years ago
|
||
Addition to comment #18
Bookmark Backup contains an inaccessible URL, which may explain the odd
behavior. The URL existed when the extension was installed and disappeared
since, but it looks like the EM fails ungracefully in this case.
Comment 21•21 years ago
|
||
Looking further into this issue, problems arise because the operation of EM
Update is much too obscure:
1. When the Extensions windows comes up no extension should be selected (if the
last selected extension is beyond the display area you cannot see it is
selected). This will allow to diaply "Please select extension to update", and
make it clear that only the selected extension is processed. The name of the
selected extension should be displayed in the "Checking for updates" window.
2. If the selected extension has no path for updates (optional in specs?) then
EM should return immediately stating "Extension does not provide updates" and
not churn away uselessly. This is the case for Favicon Picker.
3. If the website for which there is an update path is not reachable then this
should be stated clearly.
4. "Firefox was not able to find any available updates" is really a defeater: if
it is impossible to reach the website (as for Bookmark Backup), then display
this cause. If, however, there was no update, then display "Extension is up to
date".
Updated•17 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•