703897 - Check for Plugin Updates via Add-ons Manager Does not Work

Status: RESOLVED WORKSFORME

(Toolkit :: Add-ons Manager, defect)

Description

[David E. Ross]

Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20110923 SeaMonkey/2.4

Going to [Tools > Add-ons Manager] on the SeaMonkey menu
bar and selecting the Plugins icon in the left margin shows a list of
plugins.  At the top of the list, there seems to be a link "Check to see
if your plugins are up to date".  This is underlined and in the color of
an unvisited link; hovering my cursor over it turns my cursor into a
hand, further indicating a link.  Disabling CSS shows that this is a
button.  In any case, this link is a no-op; hovering my cursor over it
shows no URI in the status bar.  

NOTE:  This bug report does NOT apply when going to <about:plugins>, which has a link "Find updates for installed plugins at mozilla.com/plugincheck."  That link goes to <http://www.mozilla.org/en-US/plugincheck/>.  Of 10 plugins on my
system, however, 6 are indicated as "Unknown plugin".  Those unknowns
include 3 from RealNetworks (e.g., RealPlayer) and 2 from Micro$oft.  This latter deficiency is unrelated to this bug report.  

See also <news://news.mozilla.org:119/[e-mail]> -- the thread in mozilla.support.seamonkey with subject "Add-ons Manager : 'Check to see if your plugins are up to date'" started 18 Nov 2011.

Comment 1

[Hartmut Figge]

The link mentioned in the first paragraph does work on SM 2.81a/Linux x86_64

Comment 2

[Jens Hatlak (:InvisibleSmiley)]

I've checked the newsgroups and found that reportedly nothing appears in the Error Console (ideally this info would have been included in the initial comment!).

The button/link is associated with cmd_pluginCheck, which likely triggers this:
http://mxr.mozilla.org/comm-central/source/mozilla/toolkit/mozapps/extensions/content/extensions.js#746
The matching pref was added for SM long ago:
http://hg.mozilla.org/comm-central/rev/176ec6110ed9

1. Please go to about:config and see which value you have for plugins.update.url. It says "http://www.mozilla.com/%LOCALE%/plugincheck/" here with SM 2.5b4.
2. What is your active locale?
3. Can you reproduce the problem with a fresh profile?
4. Can you reproduce the issue with SM 2.5b4 or later?
5. Can you reproduce the issue with FF 7 or later?

Oh, and please don't file bugs as NEW unless you know for sure it's a bug in the product (e.g. if it's caused by an add-on or manual changes, it's *not* an SM or Toolkit bug). Changing back to UNCO until this has been verified.

Comment 3

[David E. Ross]

Re comment #1:  Version 2.5 has not yet been released, let alone version 2.8.  The latter is still a nightly.  

Re comment #2:
1.  plugins.update.url has the value http://www.mozilla.com/%LOCALE%/plugincheck/.  In about:config, this is NOT bold; thus, this is SeaMonkey's default value.  

2.  If by "active locale" you mean localization, EN-US.  

3.  Given that I have reproduced the problem in Safe Mode, I do not think a new profile would make any difference.  However, I will try that later.  

4.  As a rule, I do not install beta versions of software.  

5.  I do not use Firefox.  

Finally, I left the Status at its default value when I submitted this bug report.  I did not change it; there was no option to change it.  If Bugzilla sets the default Status to New, that is not my fault because I have no way to change it to Unconfirmed.

Comment 4

[David E. Ross]

More re comment #2:

Surprise!  This was not a problem with a new profile.  That profile had 
plugins.update.url with a value http://www.mozilla.com/%LOCALE%/plugincheck/, the same default as I reported in my comment #3.  

However, a subsequent test in Safe Mode still showed the problem.  Thus, the problem is not a consequence of any extension or theme.

Comment 5

[Hartmut Figge]

(In reply to David E. Ross from comment #3)

> Re comment #1:  Version 2.5 has not yet been released, let alone version
> 2.8.  The latter is still a nightly.

It should have been 2.8a1 and not 2.81a. But sure, it is a nightly.

> Finally, I left the Status at its default value when I submitted this bug
> report.  I did not change it; there was no option to change it.  If Bugzilla
> sets the default Status to New, that is not my fault because I have no way
> to change it to Unconfirmed.

It's a long time since i filed my last bug but i seem to recall that i was bitten by this also. I had to reset to 'unconfirmed' later manually.

But my memory may be wrong about that. ;)

Comment 6

[Philip TAYLOR]

Appears fixed in 2.5 under Windows XP PRO;SP3.

However, the page to which one is taken appears
to be under the misapprehension that one is
using Firefox, so it is by no means certain
that the results returned are valid.

Comment 7

[David E. Ross]

Mozilla/5.0 (Windows NT 5.1; rv:8.0.1) Gecko/20111121 SeaMonkey/2.5

I tried this on all four of my profiles, both with a normal launch of SeaMonkey and in Safe Mode.  The problem still existed.  

I then tried creating a new profile in the default profile location.  That worked, both with a normal launch and in Safe Mode.  There the problem did not exist.  Finally, I tried creating a new profile in my usual, non-standard location for profiles, <C:\WINDOWS\Application Data\SeaMonkey>.  There, too the problem did not exist for a normal launch; in that case, I did not try Safe Mode.  

I would hope someone would tell me what to do to diagnose why this does not work -- even in Safe Mode -- for my existing profiles but does work for a new profile.  In the meantime, I assert this is still a problem; and this bug should not be closed.

Comment 8

[Wayne Mery (:wsmwk)]

Do you still see this?
If not, please close as WORKSFORME

Comment 9

[David E. Ross]

Just now tried it for the first time in three years.  It appears that the problem is resolved.