Do Seamonkey libraries conflict with Mageia packaged libs?

[rolf]

I've used the Seamonkey suite since 2000, when it was Netscape.

Code: Select all

[rolf@p8z68 ~]$ urpmq seamonkey -y
No package named seamonkey

I've been using the Seamonkey Project 64-bit Contributed build by downloading the tarball, checking the hash, extracting it, and linking the binary to /usr/bin:

Code: Select all

[rolf@p8z68 ~]$ ll `which seamonkey`
lrwxrwxrwx 1 root root 29 03-15-2016 17:14 /usr/bin/seamonkey -> /moz/2.40/seamonkey/seamonkey*

I've just noticed a post at mozillazine forums that mentioned security fixes in some Seamonkey libraries:

Addendum for OpenSUSE users: They have published 2.40 in their distros for quite a while already. Since they ship certain core libraries like NSS and NSPR as separate packages, SeaMonkey benefits from the most recent Firefox update, using NSS 3.21.1 rather than 3.20.1 and NSPR 4.12 rather than 4.10.10; this means that a couple of additional security fixes from those libraries (e.g., MFSA 2015-150, MFSA 2016-07, MFSA 2016-35) should be covered already in SM 2.40 ahead of the 2.42 release.

You can check the current version of those libraries at the bottom of the Help > Troubleshooting page.

and was reminded of some recent updates by luigiwalser to packages named something like nspr and nss:

Code: Select all

[rolf@p8z68 seamonkey]$ rpm -qa --last|grep nss3
lib64nss3-3.23.0-1.mga5.x86_64                Wed 16 Mar 2016 01:07:32 PM PDT

[rolf@p8z68 seamonkey]$ rpm -qa --last|grep nspr
lib64nspr4-4.12-1.mga5.x86_64                 Wed 09 Mar 2016 04:07:47 PM PST

At the top of the extracted seamonkey tarball are a number of libraries most of which are installed on my system via Mageia packages. BTW, I don't run ldconfig on this installation path on partition /moz, just link to the binary, as above.

Code: Select all

[rolf@p8z68 seamonkey]$ ls -r | grep lib
libxul.so*
libssl3.so*
libsoftokn3.so*
libsoftokn3.chk
libsmime3.so*
libprldap60.so*
libplds4.so*
libplc4.so*
libnssutil3.so*
libnssdbm3.so*
libnssdbm3.chk
libnssckbi.so*
libnss3.so*
libnspr4.so*
libmozsqlite3.so*
liblgpllibs.so*
libldif60.so*
libldap60.so*
libfreebl3.so*
libfreebl3.chk
dependentlibs.list

I find most of these in Luigi's two referenced packages:

Code: Select all

[rolf@p8z68 seamonkey]$ rpm -ql lib64nss3-3.23.0-1.mga5.x86_64
/usr/lib64/libfreebl3.chk
/usr/lib64/libfreebl3.so
/usr/lib64/libnss3.so
/usr/lib64/libnssckbi.so
/usr/lib64/libnssdbm3.so
/usr/lib64/libnssutil3.so
/usr/lib64/libsmime3.so
/usr/lib64/libsoftokn3.chk
/usr/lib64/libsoftokn3.so
/usr/lib64/libssl3.so


[rolf@p8z68 seamonkey]$ rpm -ql lib64nspr4-4.12-1.mga5.x86_64
/usr/lib64/libnspr4.so
/usr/lib64/libplc4.so
/usr/lib64/libplds4.so

also,

Code: Select all

[rolf@p8z68 ~]$ rpm -qf /usr/lib64/firefox/libxul.so
firefox-38.7.0-1.mga5

Seamonkey takes a very long time to load the first time after a fresh boot, the binary is on an SSD, separate from the SSD that contains /usr, so I wonder if the load time is related to how I've done this or some confusion about what library to use. Have I done something wrong, here? Is there a better way?

Thanks!

[doktor5000]

Well, you don't actually mention where you extracted seamonkey. Did you really put it in /moz/2.40/seamonkey/ ?
And then it's important how you run it, I assume /moz/2.40/seamonkey/seamonkey is not actually a binary but a script?
Usually that is responsible for setting up LD_LIBRARY_PATH and similar so that the bundled libraries are used before the system ones.

To be sure, you might need to run strace to see what it actually loads, something like this:

Code: Select all

strace -tt -e file /usr/bin/seamonkey

Another question would be why you use the contributed x86_64 build and not the official one, and does that give the same slight slowdown?

[rolf]

Well, you don't actually mention where you extracted seamonkey. Did you really put it in /moz/2.40/seamonkey/ ?

Yes, /moz is a partition on an SSD where I extract the various seamonkey version tarballs under a directory named for the version number. Also, I keep my seamonkey user profile files at /moz/.mozilla.

And then it's important how you run it, I assume /moz/2.40/seamonkey/seamonkey is not actually a binary but a script?
Usually that is responsible for setting up LD_LIBRARY_PATH and similar so that the bundled libraries are used before the system ones.

There are seamonkey and seamonkey-bin at the top of the extracted seamonkey directory, both seem the same, and I always have linked to seamonkey.

Code: Select all

[rolf@p8z68 ~]$ file /moz/2.40/seamonkey/seamonkey*
/moz/2.40/seamonkey/seamonkey:     ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, BuildID[sha1]=e502d757897e7b2b6b947a881fb9024fe8af9f90, stripped
/moz/2.40/seamonkey/seamonkey-bin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, BuildID[sha1]=e502d757897e7b2b6b947a881fb9024fe8af9f90, stripped
[rolf@p8z68 ~]$ ll /moz/2.40/seamonkey/seamonkey*
-rwxr-xr-x 1 rolf rolf 123184 01-18-2016 19:31 /moz/2.40/seamonkey/seamonkey*
-rwxr-xr-x 1 rolf rolf 123184 01-18-2016 19:31 /moz/2.40/seamonkey/seamonkey-bin*

To be sure, you might need to run strace to see what it actually loads, something like this:

Code: Select all

strace -tt -e file /usr/bin/seamonkey

Ok. There must be some way to direct this output to a file? I tried by appending > strace.txt but that didn't work. My scrollback is set to 16300 lines in konsole and that wasn't enough. Anyway, what I did was temporarily set scrollback to unlimited, shut down/powered off the machine, booted, then ran

Code: Select all

strace -tt -e file /usr/bin/seamonkey

I'm attaching a text file of the first 1800 lines of output.

Funny but it seemed seamonkey started fairly quickly when running this command first thing after booting. Typically, seamonkey is the first thing I start when the desktop loads and I've wondered if there are system jobs competing right at the beginning of boot time. To test, I power-cycled again and started seamonkey from a desktop icon, as I normally do, and it took a long time. The icon is something I made in the traditional KDE launcher application editor, then added to the desktop. The 'Command' is /usr/bin/seamonkey.

Another question would be why you use the contributed x86_64 build and not the official one, and does that give the same slight slowdown?

To have 64-bit seamonkey, I must use contributed; official is only 32-bit
Thanks.

[doktor5000]

Ok. There must be some way to direct this output to a file? I tried by appending > strace.txt but that didn't work. My scrollback is set to 16300 lines in konsole and that wasn't enough.

Yes by amending

Code: Select all

-o output.log