seamonkey in ld.so.conf

zerouno · 10-20-2012, 02:43 PM

Why /usr/lib/seamonkey in /etc/ld.so.conf ?
Now libnss3 and other are in mozilla-nss packages, in /usr/lib

If I install some packages as chromium or similar, ldd tell me /urs/lib/seamonkey/libnss3 instead /usr/lib/libnss3

Also, I think that seamonkey-solibs is a no more useful package becouse deprecated from mozilla-nss

ruario · 10-02-2013, 01:49 PM

I have recently wondered this as well? Anyone know why?

volkerdi · 10-02-2013, 02:01 PM

There are several libraries in seamonkey that aren't provided elsewhere in Slackware, and that someone _might_ be using. The problem seems to be that the paths in ld.so.conf are checked before the preconfigured paths. Anyone know of a way to have /lib{,64} and /usr/lib{,64} checked first? I suppose those could also be listed in ld.so.conf first, although that seems a bit hackish.

jtsn · 10-02-2013, 02:16 PM

Quote:

Originally Posted by volkerdi

There are several libraries in seamonkey that aren't provided elsewhere in Slackware, and that someone _might_ be using.

But there is no stable ABI inside Seamonkey, so every security update of this browser could break that stuff.

ruario · 10-02-2013, 02:17 PM

Thanks for the update. As a side note Chrome appears to need the seamonkey-solibs package. I do not know why but if you remove it and only have the libnss libs provided by mozilla-nss it will not start, stating "NSS >= 3.14.3 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer". This is despite the fact that ldd'ing the Chrome binaries with only mozilla-nss installed (and semonkey-solibs removed) does not result in any "not found" lines.

P.S. See also this thread.

jtsn · 10-02-2013, 02:23 PM

Quote:

Originally Posted by ruario

Thanks for the update. As a side note Chrome appears to need the seamonkey-solibs package. I do not know why but if you remove it and only have the libnss libs provided by mozilla-nss it will not start, stating "NSS >= 3.14.3 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer". This is despite the fact that ldd'ing the Chrome binaries with only mozilla-nss installed (and semonkey-solibs removed) does not result in any "not found" lines.

Seamonkey, Firefox and and Thunderbird already have their own copy of libnss and friends, so I think it doesn't harm to provide Chrome with its own copy, too. It could be included into the google-chrome SlackBuild to make it proof for future upgrades of Chrome.

volkerdi · 10-02-2013, 02:46 PM

Quote:

Originally Posted by jtsn

Seamonkey, Firefox and and Thunderbird already have their own copy of libnss and friends, so I think it doesn't harm to provide Chrome with its own copy, too. It could be included into the google-chrome SlackBuild to make it proof for future upgrades of Chrome.

How would this be different than the already provided system mozilla-nss package?

ruario · 10-02-2013, 02:49 PM

Seamonkey, Firefox and and Thunderbird bundle them themselves. Chrome does not. Additionally Chrome updates every six weeks anyway and could potentially have its dependencies change each time (this seems to have happened in the other thread), so I am not sure if that idea actually helps.

volkerdi · 10-02-2013, 02:59 PM

Quote:

Originally Posted by ruario

Thanks for the update. As a side note Chrome appears to need the seamonkey-solibs package. I do not know why but if you remove it and only have the libnss libs provided by mozilla-nss it will not start, stating "NSS >= 3.14.3 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer". This is despite the fact that ldd'ing the Chrome binaries with only mozilla-nss installed (and semonkey-solibs removed) does not result in any "not found" lines.

P.S. See also this thread.

It's working here on x86_64 -current with both seamonkey and seamonkey-solibs removed. Also, adding /lib64 and /usr/lib64 at the top of ld.so.conf makes it properly prefer the mozilla-nss libraries in /usr/lib64. Probably that should be added to ld.so.conf... worst side effect would be that a missing library would be searched for twice by the linker.

ruario · 10-02-2013, 03:21 PM

Oh man, I cannot read! Slackware 14 has mozilla-nss version 3.13.5 but 3.14.3 is needed by Chrome. I do not know how I misread but I thought that the version in Slackware 14 was new enough. Ok, then everything makes perfect sense to me know.

Also, glad to hear that -current works (since it also has 3.14.3 ).

ruario · 10-02-2013, 03:26 PM

Quote:

Originally Posted by volkerdi

adding /lib64 and /usr/lib64 at the top of ld.so.conf makes it properly prefer the mozilla-nss libraries in /usr/lib64. Probably that should be added to ld.so.conf... worst side effect would be that a missing library would be searched for twice by the linker.

Sounds like a plan.

John VV · 10-02-2013, 03:42 PM

Quote:

Anyone know of a way to have /lib{,64} and /usr/lib{,64} checked first?

unsure with slack , but it should be the same .

i export LD_LIBRARY_PATH with the order i need them read in in /etc/profile.local ( RHEL )

Code:

......

LD_LIBRARY_PATH="/usr/lib64;/usr/lib;/DATA/SL6/lib64"

....
export LD_LIBRARY_PATH

garpu · 10-02-2013, 03:43 PM

Quote:

Originally Posted by ruario

Oh man, I cannot read! Slackware 14 has mozilla-nss version 3.13.5 but 3.14.3 is needed by Chrome. I do not know how I misread but I thought that the version in Slackware 14 was new enough. Ok, then everything makes perfect sense to me know.

Also, glad to hear that -current works (since it also has 3.14.3 ).

Heh, I did the same thing yesterday morning. I compiled mozilla-nss from /current, thinking it would need that one.

jtsn · 10-02-2013, 04:33 PM

Quote:

Originally Posted by ruario

Seamonkey, Firefox and and Thunderbird bundle them themselves. Chrome does not. Additionally Chrome updates every six weeks anyway and could potentially have its dependencies change each time (this seems to have happened in the other thread), so I am not sure if that idea actually helps.

Google-chrome-pam-solibs isn't needed anymore, now it would be a google-chrome-mozilla-nss package. Chrome continues to be a moving target, but at least it doesn't depend on a random browser version installed elsewhere in the system anymore...

wildwizard · 10-02-2013, 05:23 PM

Quote:

Originally Posted by volkerdi

It's working here on x86_64 -current with both seamonkey and seamonkey-solibs removed. Also, adding /lib64 and /usr/lib64 at the top of ld.so.conf makes it properly prefer the mozilla-nss libraries in /usr/lib64. Probably that should be added to ld.so.conf... worst side effect would be that a missing library would be searched for twice by the linker.

If you want you can remove the default search path from ld by rebuilding it with "nodefaultlib" then you must ensure that ld.so.conf has /lib /usr/lib else they will not be checked.

As for someone else's suggestion re LD_LIBRARY_PATH this is used at run time only and is ignored for SUID/SGID programs and really should not be set by the distro maintainer.

Good practice has the distro maintainer set /etc/ld.so.conf correctly so that everything runs correctly and users should not have to nor should they change it.