On Wed, Aug 05, 2015 at 01:41:22PM +0530, Ritesh Raj Sarraf wrote: > Today, I noticed (when running chromium from the shell) that eatmydata > was not into aciton.. :-( > > I can go and create the symlink manually, but shouldn't the package take > care of it ? > > rrs@learner:~$ chromium --touch-devices=2 > [7722:7722:0805/133119:ERROR:nss_util.cc(856)] After loading Root Certs, > loaded==false: NSS error code: -8018 > ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored. > ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored. > ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored. > ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored. > ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored. > ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored. > ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored. > ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded > (cannot open shared object file): ignored. > > > rrs@learner:/usr/share/doc/eatmydata$ which chromium > /home/rrs/bin/chromium > 2015-08-05 / 13:39:36 ♒♒♒ ☺ > > rrs@learner:/usr/share/doc/eatmydata$ file /home/rrs/bin/chromium > /home/rrs/bin/chromium: symbolic link to /usr/bin/eatmydata > 2015-08-05 / 13:39:42 ♒♒♒ ☺
I forgot to follow up here, but I investigated with rrs on IRC, and
concluded this is a chromium issue.
From #debian-devel, 2015-08-05:
[11:09:38] <mapreri> RickXy: you know what? i've never used libeatmydata with
with the symlink mode :) what do you mean by "I can go and create the symlink
manually, but shouldn't the package take care of it ?" eatmydata does have no
symlink to create. i think that's just another bug.
[11:10:43] <RickXy> mapreri: Whatever it is complaining about.
[11:12:03] <RickXy> mapreri: Earlier, when hit in the pbuilder environment, the
workaround was to create a symlink.
[11:12:23] <mapreri> RickXy: is that >= jessie?
[11:12:58] <RickXy> I guess. But I'm not sure.
[11:14:29] <RickXy> mapreri: Should be Jessie. Because the issues is not older
than a year.
[11:20:41] <RickXy> mapreri: Do you have any idea why that error pops ?
[11:21:00] <mapreri> RickXy: the fact that the symlink mode does not work is
another bug. but i just tried and i think that's something chromium specific
[11:21:49] <RickXy> mapreri: Hmmm... Let me verify if it is not reproducible
with other binaries.
[11:22:41] <mapreri> it might very well be that it uses a personal
LD_LIBRARY_PATH
[11:23:47] <RickXy> mapreri: Indeed.
[11:24:05] <RickXy> mapreri: chromium is a shell script, and there, it has its
own LD_LIBRARY_PATH
[11:24:40] * RickXy needs to file a new bug against chromium
[11:25:53] <mapreri> RickXy: if you do you can look at the bottom of
/usr/bin/eatmydata on a nice syntax to not overwrite the veriable content
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: Digital signature
