can't update my Lightening extension because of incompatibility of build type (Linux_x86-gcc3)



12 years ago
12 years ago


(Reporter: dmladek, Unassigned)





12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20061023 SUSE/ Firefox/
Build Identifier: 0.3.1

OS: openSuSe 10.2, kernel-
currently used version of Lightening 0.1
available version of Lightening update: 0.3.1
Thunderbird version (RPM): (20060911)
RPM version: MozillaThunderbird-

In Extension dialog is offered to update my Lightening extension 0.1 to  new version 0.3.1, After clicking Update Now button I'm getting error: "Incompatible Extension:"
Lightening could not be installed because it is not compatible with your Thunderbird build type (Linux_x86-gcc3).

Reproducible: Always

Actual Results:  
Error message

Expected Results:  
Extension should be updated
What is your Thunderbird platform? 
The official Lightning builds might work only in the official Thunderbird builds. If your custom Thunderbird build was compiled on a different platform or compiler environment you probably need a custom Lightning build too.

Have you tried the direct download from []? Maybe is not working correctly after the upgrade.

Comment 2

12 years ago
Well, what do you mean Thunderbird platform?
I'm using openSuSe v10.2 and all SW I've installed via Yast thus it should be official  IMHO.
The source channel I'm using is: "SUSE Linux Online Updates" @
Vendor is SUSE Linux Product... 

Here is package info:
delphym@dhcppc0:~> rpm -qi `rpm -qa|grep -i thunder`
Name        : MozillaThunderbird           Relocations: (not relocatable)
Version     :                          Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Release     : 1.1                           Build Date: Fri 09 Mar 2007 04:45:25 PM CET
Install Date: Sat 17 Mar 2007 01:02:46 AM CET      Build Host:
Group       : Productivity/Networking/Email/Clients   Source RPM: MozillaThunderbird-
Size        : 24324671                         License: GNU General Public License (GPL), GNU Library General Public License v. 2.0 and 2.1 (LGPL)
Signature   : DSA/SHA1, Fri 09 Mar 2007 04:51:52 PM CET, Key ID a84edae89c800aca
Packager    :
URL         :
Summary     : The Stand-Alone Mozilla Mail Component
Description :
Mozilla Thunderbird is a redesign of the Mozilla Mail component. It is
written using the XUL user interface language and designed to be
cross-platform. It is a stand-alone application instead of part of the
Mozilla application suite.

    Mozilla Foundation <>
Distribution: openSUSE 10.2 (i586)

Comment 3

12 years ago
Daniel, what Stefan is telling you is, that the Suse builds are not the "official" Thunderbird builds. Only provides official builds of Thunderbird. 

All other builds are vendor-specific builds and it seems that Suse built its own Thunderbird on a different platform than So there's nothing we can do about this. You will have to contact Suse and ask them to provide Lightning also or remove the Suse Thunderbird and install the Thunderbird instead.
Last Resolved: 12 years ago
Resolution: --- → WONTFIX

Comment 4

12 years ago
It's pitty that this extension is so tight with "official" Thunderbird build:-/
Problem is that they are not provided in RPMs form. But what can I do.

Comment 5

12 years ago
The openSuSe bugreport is available at:

I wander who will take it and possibly correct it:-)

Comment 6

12 years ago
I just observed the same problem. The strange thing about this is, that I have been able to install a nightly version in January (Lightning 0.4a). Stefan, are you sure, that nothing has changed on our side concerning the build config?

Comment 7

12 years ago
Finally I've found the solution how to update my Lightening extension.

I've already reported to the openSuse bug #262313
And conclusion is that it was not possible update this extension directly from version 0.1 to 0.3.1  (maybe too big difference in those 2 version's settings/formats). but uninstalling old one and installing new one it works fine.



12 years ago

Comment 8

12 years ago
sorry, I've ment this bug:
not mozilla bug.
You need to log in before you can comment on or make changes to this bug.