LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 08-09-2013, 08:25 PM   #1
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Rep: Reputation: Disabled
Mozilla Lightning fails after Seamonkey update


Does anyone use the Lightning calendar extension with Seamonkey?

After applying the recent Slackware 14 update to seamonkey-2.20, I had to upgrade to the compatible version of lightning-2.5b2 (always have to upgrade lightning after seamonkey, as only specific versions play together). I've done this before without problems, but it won't work at all this time.

Trying to open the Mail/News window in Seamonkey-2.20 with Lightning-2.5b2 crashes out of seamonkey with an error that looks like this:

Code:
seamonkey: relocation error:
.../components/Linux_x86-gcc3/libcalbasecomps.so:
symbol _ZN2js13CheckedUnwrapEP8JSObjectb, version xul23.0 not defined in file libxul.so with link time reference
 
Old 08-10-2013, 10:02 AM   #2
elesmod
Member
 
Registered: Sep 2012
Distribution: Slackware
Posts: 84

Rep: Reputation: Disabled
I've never used Lightning, but I've installed it in my Seamonkey just for you

I can report that I'm encountering the same crash.
 
Old 08-10-2013, 12:31 PM   #3
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Original Poster
Rep: Reputation: Disabled
Thanks! I appreciate the effort.

I'm now pretty sure this is a Slackware problem, not a Mozilla problem. Something seems wrong in the libxul.so shipped with the Slackware 14.0 patch to seamonkey-2.20.

The error message (see above) says it was looking for CheckedUnwrap version xul23.0 in libxul.so and not finding it.

This is from libxul.so in Slackware 14 seamonkey-2.20-i486-1_slack14.0:
Code:
$ objdump --dynamic-syms --demangle libxul.so  | grep CheckedUnwrap
00000000      DF *UND*	00000000  mozjs       js::CheckedUnwrap(JSObject*, bool)
Same command on seamonkey-2.20 as downloaded from www.seamonkey-project.org:
Code:
$ objdump --dynamic-syms --demangle libxul.so  | grep CheckedUnwrap
01863030 g    DF .text	0000003d  xul23.0     js::CheckedUnwrap(JSObject*, bool)
The version is correct (xul23.0) in the one from seamonkey-project, but wrong (mozjs) in the Slackware one. That's as far as I got so far. I haven't tried running the 'official' seamonkey release. I took a quick looks at the seamonkey.SlackBuild script but that didn't help.
 
Old 08-10-2013, 01:26 PM   #4
John VV
Guru
 
Registered: Aug 2005
Posts: 12,107

Rep: Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591
seamonkey-2.20-i486-1_slack14.0 --- i486 version of seamonkey ?
A question ?
are you running a 32 bit OS or a 64 bit OS

i have only seen that error
" not defined in file libxul.so with link time reference"
on multi lib OS's
and normally as a linker error
 
Old 08-10-2013, 02:37 PM   #5
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by John VV View Post
seamonkey-2.20-i486-1_slack14.0 --- i486 version of seamonkey ?
A question ?
are you running a 32 bit OS or a 64 bit OS
Plain 32-bit Slackware 14, not multilib.
 
Old 08-10-2013, 02:45 PM   #6
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.1
Posts: 658

Rep: Reputation: 38
Same here on 64-bits SW-14...
 
Old 08-10-2013, 11:14 PM   #7
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 527
Blog Entries: 3

Rep: Reputation: 126Reputation: 126
Can confirm here on 14.0, 64 bit with multilib. Same crash
 
Old 08-11-2013, 05:20 PM   #8
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Original Poster
Rep: Reputation: Disabled
I confirmed that lightning-2.5b2 extension works with seamonkey-2.20 as downloaded from seamonkey-project.org (the Mozilla binary release).

(And, as an aside, I see that the binary release from seamonkey-project.org does seem to work OK on Slackware 14. Didn't Slackware once ship the Mozilla binaries of this - and firefox - rather than rebuilding from source? I wonder when/why that changed.)

One possibly suspicious difference is that the Slackware seamonkey-2.20 was built with gcc-4.7.1 and the released seamonkey-project Linux binary seamonkey-2.20 was built with gcc-4.5.2.
 
Old 08-11-2013, 05:28 PM   #9
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 836

Rep: Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620
Quote:
Originally Posted by ljb643 View Post
I confirmed that lightning-2.5b2 extension works with seamonkey-2.20 as downloaded from seamonkey-project.org (the Mozilla binary release).

(And, as an aside, I see that the binary release from seamonkey-project.org does seem to work OK on Slackware 14. Didn't Slackware once ship the Mozilla binaries of this - and firefox - rather than rebuilding from source? I wonder when/why that changed.)

One possibly suspicious difference is that the Slackware seamonkey-2.20 was built with gcc-4.7.1 and the released seamonkey-project Linux binary seamonkey-2.20 was built with gcc-4.5.2.
We have never shipped Seamonkey compiled by Mozilla.

Is this extension that's running into problems something that is a binary (I'm assuming that is the case). If so, that's very likely the root of the problem. It's possible that recompiling Seamonkey with the exact configure flags used by Mozilla might clear up the issue, but we've never known what those are for any of the binaries they post.
 
Old 08-11-2013, 06:34 PM   #10
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Original Poster
Rep: Reputation: Disabled
Yes the Lightning extension has a binary component. In fact it is the one named in the error message a the top: libcalbasecomps.so. (I think this explains why it needs to upgraded for each version of the browser.)

I believe using about:buildconfig in Seamonkey gives one the exact configure line that was used, and also the CFLAGS and compiler versions. I considered getting the seamonkey-2.20 source, and building it on Slackware-14 with gcc-4.7.1 using the same configure as they use for their released binaries, as seen by about:buildconfig from their binary release. This should indicate if the problem is the build environment or not. But I balked at the the 83MB source download (or is it 107MB, as on a Slackware mirror?) Maybe I'll go ahead and try it, though.
 
Old 08-11-2013, 06:50 PM   #11
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by volkerdi View Post
We have never shipped Seamonkey compiled by Mozilla.
I stand corrected. It was firefox and thunderbird, but not seamonkey (nor its ancestor, mozilla).
 
Old 08-12-2013, 04:05 PM   #12
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Original Poster
Rep: Reputation: Disabled
I found the cause: the configure option --enable-shared-js

The Slackware build script uses this, and the Mozilla-supplied release does not. When this option is used, Seamonkey gets built with an additional library: libmozjs.so which contains some functions which would otherwise be in libxul.so, I think. This seems to cause the issue with the 'version tag' (not sure if that is the right term) for a function used by the Lightning extension to use 'mozjs' instead of 'xul23.0'.

Using seamonkey.SlackBuild without --enable-shared-js to build seamonkey results in a build that does work with lightning-2.5b2.

It is possible that building Lightning from source on a system that has the Slackware-built seamonkey would work too, but it seems a lot of trouble to get Lightning source so I didn't try that.

I will probably open a mozilla bug report on this option, but I'm not hopeful it would do much good. Perhaps Pat would consider dropping --enable-shared-js for the next seamonkey release, unless there is something out there that relies on it.
 
Old 08-15-2013, 10:40 AM   #13
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,096

Rep: Reputation: 147Reputation: 147
Looks like that has been fixed:

Quote:
Thu Aug 15 03:46:12 UTC 2013

l/seamonkey-solibs-2.20-x86_64-2.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.
Thanks to ljb643.

xap/seamonkey-2.20-x86_64-2.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.
Thanks to ljb643.
 
Old 08-17-2013, 09:56 AM   #14
ljb643
Member
 
Registered: Nov 2003
Posts: 253

Original Poster
Rep: Reputation: Disabled
Great! Tested seamonkey-2.20-2 with lightning-2.5b2 and everything seems to be working. (Not counting the new seamonkey-2.20 crash on my bank's web site, but that seems not to be Slackware specific.)
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Seamonkey and Seamonkey libs update for Slackware 13.1? Lufbery Slackware 7 08-05-2011 03:00 AM
LXer: New release of Mozilla Lightning and SOGo LXer Syndicated Linux News 0 01-25-2010 11:50 PM
LXer: New release of Mozilla Lightning and SOGo LXer Syndicated Linux News 0 08-12-2009 10:41 PM
Mozilla Lightning 0.9 not working hb950322 Slackware 4 07-22-2009 02:05 AM
LXer: Mozilla announces SeaMonkey update LXer Syndicated Linux News 0 11-10-2006 10:54 PM


All times are GMT -5. The time now is 08:53 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration