[SOLVED] Lightning users: read before patching Seamonkey, Thunderbird
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Lightning users: read before patching Seamonkey, Thunderbird
If you use the Lightning calendar add-on with Seamonkey or Thunderbird, read this before applying yesterday's Slackware patches to Seamonkey-2.22.1 and/or Thunderbird-24.1.1:
I have not found any released version of Lightning that works with the patch Seamonkey-2.22.1. I tried Lighting-2.7b1, 2.6.2, 2.6.3, and 2.8b1. Except for 2.8b1 (which does not install at all), they all start, but the calendar is empty and non-responsive. I don't know yet if this is Slackware-specific (like this one was) or not.
I don't see any mention of Seamonkey on recent posts on the Lightning blog (all the discussion has been about a surprise Thunderbird incompatibility).
Actually the comments say "I would assume the next Seamonkey Beta build should pick up the fix", not specifically mentioning 2.23 (which would require a new version of Lightning, starting the process over again?) This is not encouraging. Seamonkey-2.22.1 is a security fix, and anyone using Lightning with it has to choose between giving up Lightning until some future release, or keeping an 'insecure' browser.
Seamonkey-2.23 has been released, but no version of Lightning works with it - even though one of the documented fixes is "Fixed incompatibility with binary extensions such as Lighting (bug #915574)".
I tried Seamonkey-2.23 on Slackware 14.1 and Lighting-2.8b1 still does not work.
Mozilla bug #941217 says it won't work until Lightning is rebuilt. Watch for Lighting-2.8b2.
Exactly this sort of bug makes me secretly wish for some Holy Boot Of Wrath to come down from heaven and kick some developers' butts until they get their act together.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,086
Rep:
Quote:
Originally Posted by kikinovak
Exactly this sort of bug makes me secretly wish for some Holy Boot Of Wrath to come down from heaven and kick some developers' butts until they get their act together.
D'accord, mon ami.
Last edited by cwizardone; 12-16-2013 at 10:26 AM.
No, this is wrong. Have you tried it? I did. It doesn't work.
I know what the addons page says - that Lightning-2.6.x are for Seamonkey-2.21.x (note 2.21, not 2.22 as you said), but there is more accurate information here: https://developer.mozilla.org/en-US/...endar_Versions
You will see how messed up this situation is. Lightning-2.6.1, 2.6.2, 2.6.3, and 2.6.4 are not listed as compatible with ANY version of Seamonkey. They were supposed to work with Seamonkey-2.21.x (as per the addons page) but they don't due to a library mismatch. Seamonkey-2.22.x requires Lightning-2.7.x, but the only available one (2.7b1) is not compatible with the seamonkey-2.22.1 (which is the current Slackware patch). Seamonkey-2.23.x requires Lightning-2.8.x but the only available one (2.8b1) is not compatible with the latest release Seamonkey-2.23 (even the page I linked to is wrong on this).
The reason is library versions. Seamonkey-2.22 provides the symbol "xul25.0" in libxul.so, Seamonkey-2.22.1 provides "xul25.0.1", and Seamonkey-2.23 provides "xul26". Lightning-2.7b1 expects to find "xul25.0", and Lightning-2.8b1 expects to find "xul26.0".
all say that it can't work. Seamonkey-2.22 requires at least Lightning-2.7. My experience matches that.
Just to be sure, you can see events on the calendar, and click on calendar days to create or open events? (Because for me, as well as those posting in the bug report above, Lightning loads but the calendar is empty and non-responsive.)
If it does work for you, then I have no idea what is going on.
A Slackware 14.1 patch for seamonkey-2.24 was released today. This version works with Lightning-2.9b1 which is available at lighting extension downloads page. I believe this is the first version of Seamonkey that had a working Lightning add-on available in about 2 months.
A Slackware 14.1 patch for seamonkey-2.24 was released today. This version works with Lightning-2.9b1 which is available at lighting extension downloads page. I believe this is the first version of Seamonkey that had a working Lightning add-on available in about 2 months.
Yep, I can confirm that we have a working calendar for Seamonkey again, finally. 2.9b1 is obviously still Beta, after so many years. I hope, they will reach 3.0 soon and stabilise things. It's just bad practice to break interfaces, every so often. This indicates a fundamental weakness in the plug-in architecture, IMHO.
If this happens again with another version any time soon, I am done with Seamonkey, I am afraid, although in general I like this internet suite a lot, otherwise.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.