Bug 16580 - lightning 3.3 is incompatible with thunderbird 38.1
Summary: lightning 3.3 is incompatible with thunderbird 38.1
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-13 10:03 CEST by José Jorge
Modified: 2015-08-25 23:19 CEST (History)
1 user (show)

See Also:
Source RPM: thunderbird-lightning-3.3-6
CVE:
Status comment:


Attachments

Description José Jorge 2015-08-13 10:03:44 CEST
After the update of the system, the agenda lightning still started, but was not localized.

Extensions manager then indicated that lightning 3.3 is not compatible with thunderbird 38.1.

I worked around the problem removing the rpm thunderbird-lightning-3.3-6.mga5 and adding the extension through extensions manager.

Reproducible: 

Steps to Reproduce:
Comment 1 John L. ten Wolde 2015-08-14 05:14:37 CEST
Hi José.  I think the real bug here is that your existing thunderbird-lightning-3.3-6.mga5 package should have been automatically removed by rpmdrake upon your system update as Lightning is now going to be bundled by default with *all* Thunderbird installations from version 38 onwards.

I'm not a Lightning user.  I've never used it.  So imagine my surprise when after installing the same update, I suddenly had an agenda side panel I'd never seen before.  At the bottom of my screen was a button bar asking to "Disable", "Keep", or get "Learn More" about the extension.  Clicking "Learn More" leads to the following release from Mozilla:

https://support.mozilla.org/en-US/kb/thunderbird-calendar-integration

CC: (none) => johnltw

Comment 2 David Walser 2015-08-25 23:19:05 CEST
Lightning is now a part of Thunderbird,  you just have to enable it.  You shouldn't install any external extension for it anymore.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.