1165534 - Add-ons Manager shows incorrect add-on version (global extension update not detected)

Status: RESOLVED INACTIVE

(Toolkit :: Add-ons Manager, defect)

Description

[FredMcD]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150513174244

Steps to reproduce:

I sent this message to the Free Downloads Manager Support;

Mozilla Firefox thinks that I have FDM v1.7.3  Today, I downloaded
v3.9.5, but Firefox still shows 1.7.3  and not compatible.



Actual results:

Firefox is not showing the correct version for this program. And it is now disabled.

Comment 1

[FredMcD]

Forgot to add, I had deleted pluginreg.dat  The problem remains.

Comment 2

[FredMcD]

Attachment: Capture1.JPG;

Comment 3

[FredMcD]

Attachment: Capture2.JPG

Comment 4

[Gingerbread Man]

Free Download Manager 3.9.5 build 1542 comes bundled with Free Download Manager plugin 1.7.3.1, which is an extension. I see it as compatible and enabled. Update your version of Free Download Manager, then restart Firefox.

(In reply to FredMcD from comment #1)
> Forgot to add, I had deleted pluginreg.dat  The problem remains.

That only affects plug-ins (things like Flash Player). To accomplish what you want for extensions, see the following support article. Though there's no point in doing so, unless you're still stuck with version 1.7.3 after updating.
https://support.mozilla.org/en-US/kb/unable-install-add-ons-extensions-or-themes#w_corrupt-extension-files

Comment 5

[FredMcD]

Thank you Gingerbread Man for replying. I checked the article. It said;

4 Delete the following files:

    extensions.sqlite
    extensions.sqlite-journal (if found)
    extensions.ini
    extensions.json 

What I found was I only had the INI and JSON files. But I also had another file: EXTENSIONS.LOG
I looked in the file, and found the same message being repeated over and over starting 2015-05-02.
The line reads; 2015-05-15 22:39:36 ERROR [fireie]: updateInterface() failed: TypeError: tab is undefined at resource://fireie/AppIntegration.jsm:617
----------------------
After deleting all the Extensions.* files, I started Firefox. The INI and JSON were restored. But no
SQLITE file. It now shows Free Download Manager plugin v1.7.3.1 and it is now compatible.

Can not having the SQLITE file be a problem?

Comment 6

[Gingerbread Man]

(In reply to Gingerbread Man from comment #4)
> Update your version of Free Download Manager, then restart Firefox.

You were already using the latest version. Looks like you hit some variation of bug 567080.

(In reply to FredMcD from comment #5)
> After deleting all the Extensions.* files, I started Firefox. The INI and
> JSON were restored. But no SQLITE file. It now shows Free Download Manager
> plugin v1.7.3.1 and it is now compatible.
> 
> Can not having the SQLITE file be a problem?

No, that's normal. Some of the files listed in the support article are no longer in use in the current version of Firefox.

Comment 7

[FredMcD]

Other than not having a SQLITE file, it looks the same. Is there some kind of problem with the Add-ons Manager as to updates? Should the user delete these and other Firefox file? Like once a month?
I am using https://addons.mozilla.org/en-US/firefox/addon/places-maintenance/

Comment 8

[Gingerbread Man]

(In reply to FredMcD from comment #7)
> Is there some kind of problem with the Add-ons Manager as to updates?

That's what bug reports are supposed to determine. Even though you worked around the issue, I figured you'd leave this open so a developer can have a look at it. Like I said, it looks to me like the global extension was updated and Firefox failed to notice. This is a similar situation to bug 567080, where the user modified the extension manually (in both cases, the extension wasn't updated via the Add-ons Manager).

> Should the user delete these and other Firefox file? Like once a month?

I certainly hope not. Firefox is supposed to work without having to ever manually delete files, especially not on a regular basis.

> I am using https://addons.mozilla.org/en-US/firefox/addon/places-maintenance/

That affects places.sqlite, the database that stores history and bookmarks. It doesn't affect the add-ons database.

Comment 9

[FredMcD]

So, how to set this bug so the developers take a good look at the issue?

Comment 10

[Gingerbread Man]

(In reply to FredMcD from comment #9)
> So, how to set this bug so the developers take a good look at the issue?

Leave it open.

Please don't inappropriately set the Importance field (Priority + Severity).
https://bugzilla.mozilla.org/page.cgi?id=fields.html#bug_severity

Comment 12

[Gingerbread Man]

> Bug 567080, comment 6

In that case, the extension files were edited manually. What about global extensions, when the files are updated by an external application? Is this a case worth handling differently?

Comment 13

[Dave Townsend [:mossop]]

As in bug 1167583 it is possible that updating Free Download Manager isn't changing the file modification times of the add-on's files. This would mean Firefox isn't rescanning the install.rdf. Can either of you test that?

Comment 14

[FredMcD]

I can try, but you have to tell me what to do,

Comment 15

[Dave Townsend [:mossop]]

You'll need to install the old FDM and start Firefox. Grab a copy of the pref extensions.xpiState from about:config. Then exit and from a command prompt go to the extension's directory and run "dir /s" and copy the output.

Then install the new FDM, start Firefox and verify that it hasn't updated the add-on version. Get the pref extensions.xpiState again and do the "dir /s" from the command prompt again. Copy all that into this bug report, probably best as a text attachment.

Comment 16

[Gingerbread Man]

Attachment: Output for comment 15.txt

Comment 17

[Dave Townsend [:mossop]]

Can you also zip up the contents of C:\Program Files\Free Download Manager\Firefox\extension at that last point and attach here?

Comment 18

[Gingerbread Man]

Attachment: Archive for comment 17.zip

Comment 19

[BMO Automation]

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.