Please report any other irregularities here.
This is in many ways a Dup of bug 775623 but I am filing this in the context of the 38 Beta. It would appear that in this somewhat edge case of downgrade from Daily the Lightning add-on that is bundled is not installed and in fact Lightning is disabled. This may well be a weakness in the search for updates that only searches for higher version numbers, rather than compatible versions, but I am only guessing.
tracking-thunderbird38: --- → ?
tracking-thunderbird_esr38: --- → ?
I don't think it's specific to bundling though. It's always been the case that if you upgrade an extension that doesn't automagically downgrade in case you want to go back to the older app version. And if it's incompatible, it will disable itself.
I agree, Dup if you want. It is however worth noting as downgrading from the beta to release channel will I assume have the same issues. Perhaps what this bug should be about is not fixing the issue. Bug 775623 is to address that. I think this bug should address informing the user that manual intervention in add-ons, including the bundled calendar, is required. The existing test/update add-on dialog does not make it clear enough that the add-ons will be disabled. My suggestion is, on failure to locate updates to add-ons. We drop the user into the add-on manager where what is disabled and what is not is clearly displayed. It also addresses the issue of discoverability. The user is where they need to be to look at the issue.
tracking-thunderbird38: ? → ---
Summary: installed 38 Beta6 Lightning 4.3a1 installed add-on update disabled lightning. → Provide better feedback to the user when add-ons are disabled on upgrade
You need to log in before you can comment on or make changes to this bug.