One of my systems has suddenly started displaying a lot of error
messages any time any package is emerged:
>>> Emerging (1 of 1) x11-terms/rxvt-unicode-9.18
* rxvt-unicode-9.18.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...
[ ok ]
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded:
ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded:
ignored.
>>> Unpacking source...
>>> Unpacking rxvt-unicode-9.18.tar.bz2 to
>>> /home/portage/tmp/portage/x11-terms/rxvt-unicode-9.18/work
>>> Source unpacked in
>>> /home/portage/tmp/portage/x11-terms/rxvt-unicode-9.18/work
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded:
ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded:
ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded:
ignored.
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded:
ignored.
[...]
Googling that error yeielded one suggestion that the sandbox package
was broken and needed to be re-emerged. I did that, but it didn't help.
I also tried a revdep-rebuild, and it didn't find anything that needed
rebuilding.
According to
http://wiki.gentoo.org/wiki/Knowledge_Base:Object_libsandbox.so_from_LD_PRELOAD_cannot_be_preloaded
that message should never occur except right after a particular
message about SELinux security labels.
Any ideas why this would suddenly start happening?
--
Grant Edwards grant.b.edwards Yow! I just remembered
at something about a TOAD!
gmail.com
