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.
Can't get Lightning to work after upgrading to Seamonkey-2.49.5, and I can't find any information on a newer version of Lightning that is for this Seamonkey, so I reverted to 2.49.4. What happens is that the Mail/News window expands way out horizontally, no calendar is displayed, and the UI elements are disabled (grayed out).
These are the message seen if Seamonkey is started from a terminal:
Quote:
[calBackendLoader] Using Thunderbird's builtin libical backend
... addons.manager WARN Exception calling callback: ReferenceError: openAddonsMgr is not defined (chrome://...)
(Note: This first line about Thunderbird is normal - Lightning always does this, even though it is in Seamonkey.)
The release notes you linked to says Seamonkey includes the Lightning extension. It doesn't in the Slackware release. I might download the official release and try it just to see if it does actually include a working Lightning - or if that was just a typo in the release notes.
I found that the official builds from seamonkey-project.org do in fact include Lightning. They build with --enable-calendar and Slackware does not. And Lightning does work in the official Seamonkey build. The bundled Lightning (which works) reports it is version 5.4, same as the one you can download from the Thunderbird extensions site (which does not work), but it has a much more recent build date, so maybe it is one of the newer unreleased versions. I'll try some of them and see.
To review:
1. Slackware Seamonkey-2.49.5 does not include the Lightning extension. You can add the extension, downloaded from Thunderbird Add-ons site, but it does not work. It did work with 2.49.4.
2. The official Seamonkey build from seamonkey-project.org includes the Lightning extension, and it does work.
Now it gets weird.
The Lightning extension bundled in the official Seamonkey build DOES NOT work with Slackware Seamonkey-2.49.5.
The Lightning 4.5 extension downloaded from Thunderbird Add-ons site DOES work with the official Seamonkey build from seamonkey-project.org. (Used Add-ons and removed the bundled one, then installed from file).
I tried comparing the bundled Lightning extension with the downloadable Lightning extension, and the bundled one seems to have a bunch of specific bug fixes, but nothing related to the startup failure. ("Boo" to the developers for fixing bugs and leaving the version number unchanged.)
Theory: The problem is with Seamonkey, not Lightning. It looks to me like starting with 2.49.5, if Seamonkey is built without Lightning (no --enable-calendar), it won't accept Lightning as an add-on.
Last edited by ljb643; 09-07-2019 at 07:16 PM.
Reason: --with-calendar should be --enable-calendar
I don't know. I wouldn't think the problem was due to a change in the Slackware build. More likely something changed in Seamonkey, between 2.49.4 and 2.49.5, that omits some code Lightning needs if --enable-calendar is omitted. But I'm just guessing.
I can confirm that the Lightning calendar doesn't work using the Slackware 2.49.5 package but it indeed works with the official build from www.seamonkey-project.org. Has anyone tried to rebuild the Slackware package with the calendar configure option enabled?
I can confirm that the Lightning calendar doesn't work using the Slackware 2.49.5 package but it indeed works with the official build from www.seamonkey-project.org. Has anyone tried to rebuild the Slackware package with the calendar configure option enabled?
Thanks for confirming. Always good to know it isn't just my PC.
I don't think I have the bandwidth, tools, etc needed to rebuild from source, unfortunately.
Quote:
Originally Posted by khronosschoty
If you haven't done so yet maybe make a request in the "requests for -current" thread and also add you'd like to see it added in 14.2 as well.
(that is ask to have Seamonkey compiled with the --enable-calendar)
I could be wrong, but wasn't there a specific decision not to include Lightning in Slackware's Seamonkey back when it started getting bundled first with Thunderbird, then with Seamonkey too?
Thanks for confirming. Always good to know it isn't just my PC.
I don't think I have the bandwidth, tools, etc needed to rebuild from source, unfortunately.
I could be wrong, but wasn't there a specific decision not to include Lightning in Slackware's Seamonkey back when it started getting bundled first with Thunderbird, then with Seamonkey too?
Could be; but If so I missed it. I don't see any harm in asking for its return however.
If you haven't done so yet maybe make a request in the "requests for -current" thread and also add you'd like to see it added in 14.2 as well.
(that is ask to have Seamonkey compiled with the --enable-calendar)
I have asked in the request for -current tread if it's possible to recompile SeaMonkey with --enable-calendar. I tried to recompile it myself but I don't have enough disk space to finish the compilation. I will update the request to include 14.2 -stable as well.
I could be wrong, but wasn't there a specific decision not to include Lightning in Slackware's Seamonkey back when it started getting bundled first with Thunderbird, then with Seamonkey too?
I can only find this in the 14.0 ChangeLog, but that's a different issue:
Quote:
Thu Aug 15 03:46:12 UTC 2013
patches/packages/seamonkey-2.20-i486-2_slack14.0.txz: Rebuilt.
Recompiled without the --enable-shared-js option to fix the Mozilla
Lightning plugin. This removes libmozjs.so, but there's a standalone js
package now anyway.
There are no other references to the Lightning plugin in any of the ChangeLog files.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.