Closed Bug 1273098 Opened 8 years ago Closed 7 years ago

update/install fails w/TB 45.1.0 - restart announced "Lightning incompatible", then Lightning was disabled

Categories

(Calendar :: General, defect)

Lightning 4.7.1
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: tlhackque, Unassigned)

References

Details

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

Steps to reproduce:

Environment: Windows 7 ultimate 64 bit.

Accepted update to TB, going to 45.1.0


Actual results:

TB updated.
Restart announced "Lightning incompatible".
Accepted search for updated version.
Found 4.7 (I think .1, but I'm not sure.  Wish there was a log...)
Accepted update/install.
Said required restart.
Restarted TB.
Lightning incompatible & disabled.

Have tried:
Removing Lightning from add-ons menu, restart, re-install.  Says restart required. Restart, says incompatible.

Removing {e2fda1a4-762b-4020-b5ad-a41df1933103} from profile, reinstall.
Lightning appears in 'staged'.  Restarting TB, {e2fda1a4-762b-4020-b5ad-a41df1933103} reappears in profile momentarily.  Then vanishes.  Add-ons GUI reports (check)Lightning will be installed after you restart TB.  Restart Now.  Restart has same result.

Disabled Calendar tweaks.  Disabled Inverse SOGO connector.  No change.

Tried downloading .xpi from website and installing from file.  No change.

Download is lightning-4.7-sm+tb-windows.xpi

Tried removing staged and rebooting.

Compatibility page on website says 45.1.0 is compatible with 4.7.1 (10-May).  But that doesn't seem to be available for download at https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/.  And "get add-ons" from TB says Lightning 4.7 last update 25-Apr).  So if 4.7.1 is required for TB 45.1.0, it's not available.

If I look inside the 'staged' .json, I see "{"id":"{e2fda1a4-762b-4020-b5ad-a41df1933103}","version":"4.7","
(Note not 4.7.1).  It claims compatibility with 45.*...  This is true whether I use the downloaded .xpi or install from "get-addons".

Bottom line is that no matter how many restarts or where I get the extension, Lightning won't install.

The only good news is that my calendar is on a NAS cloud, so I have (limited) access to it via the cloud's web GUI...


Expected results:

Seamless upgrade :-)
or at least, ability to install.
(In reply to tlhackque from comment #0)

> Removing {e2fda1a4-762b-4020-b5ad-a41df1933103} from profile, reinstall.
> Lightning appears in 'staged'.  Restarting TB,
> {e2fda1a4-762b-4020-b5ad-a41df1933103} reappears in profile momentarily. 
> Then vanishes.  Add-ons GUI reports (check)Lightning will be installed after
> you restart TB.  Restart Now.  Restart has same result.

> The only good news is that my calendar is on a NAS cloud, so I have
> (limited) access to it via the cloud's web GUI...

Are you using a local or roaming Windows profile?

Where is your Thunderbird profile physically stored - local hdd/ssd or a network share, e.g. your NAS? Is it stored at a place within your Windows profile?

Even if your using a local windows profile or your TB profile is not stored within the Winows profile, is the TB profile synced in any way with a remote copy? If so, what sync mechanism do you use?

As you seem to be able to reproduce the issue, can you please enable extensions.logging.enabled in the advanced preferences to debug the installetion/update process? It will be helpful if you attach them to this bug.
Flags: needinfo?(tlhackque)
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Whiteboard: [ipdate version number][4.7.1]
Whiteboard: [ipdate version number][4.7.1]
Version: Lightning 4.7 → Lightning 4.7.1
tlhackque has not replied, so closing.
(but probable duplicate)
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(tlhackque)
Resolution: --- → INCOMPLETE
Summary: update/install fails w/TB 45.1.0 → update/install fails w/TB 45.1.0 - restart announced "Lightning incompatible", then Lightning was disabled
You need to log in before you can comment on or make changes to this bug.