So, google-talkplugin has been added to the portage tree. And then I tried installing it. And then Chrome stopped working. [ebuild R ] www-plugins/google-talkplugin-1.8.0.0 USE="system-libCg" 0 kB [ebuild R ] www-client/chromium-9.0.597.94 USE="cups -gecko-mediaplayer -gnome -gnome-keyring (-system-v8)" 0 kB I'm trying to start chromium using a new empty user-dir: chromium --user-data-dir=$HOME/tmp At first, it shows the google/yahoo/bing selector. After we select one of them, it crashes with the following message (as well as when we try to launch it again): Inconsistency detected by ld.so: dl-open.c: 582: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed! There are also messages about libffmpegsumo.so, but these are unrelated to this bug. Uninstalling google-talkplugin makes chromium work again. I'd attach a strace log, but chromium doesn't launch when strace is attached. I don't know why.
Created attachment 263587 [details] emerge-info.txt emerge --info
Related forum post: http://forums.gentoo.org/viewtopic-p-6569199.html Related upstream bug: http://code.google.com/p/chromium/issues/detail?id=64761 Running: ldd /opt/google/talkplugin/* Shows: libpng12.so.0 => not found Then, re-emerging media-libs/libpng-1.2.44 fixes this issue, because it installs the missing libpng12.so.0 file. I feel it is weird, because I already had that package installed, even though the file was missing. I have two solutions: either rev-bump libpng 1.2 and 1.4, adding some code to see if the libpng*.so* files are sane; or add such checking to the google-talkplugin.
I can reproduce this by removing libpng12.so.0 on my system. I'm not sure why that file would be missing under normal circumstances, however. Have you identified the exact sequence of events that led to this? I must say that it is a bit strange for Chromium to crash when a plugin fails to load.
(In reply to comment #0) > So, google-talkplugin has been added to the portage tree. And then I tried > installing it. And then Chrome stopped working. That sounds like a problem with the plugin, not the browser (which should handle it fine, but anyway the plugin is broken).
(In reply to comment #2) > Then, re-emerging media-libs/libpng-1.2.44 fixes this issue, because it > installs the missing libpng12.so.0 file. I feel it is weird, because I already > had that package installed, even though the file was missing. I remember having the same problem at a certain point after the update to libpng-1.4, which was due to the pkg_setup of the libpng-1.2. > I have two solutions: either rev-bump libpng 1.2 and 1.4, adding some code to > see if the libpng*.so* files are sane; or add such checking to the > google-talkplugin. I can add a message saying "re-emerge libpng:1.2" in the case that no libpng12.so.0 was found.
Oh, one more thing! revdep-rebuild should have noticed that google-talkplugin was broken, and at least should have warned me.
(In reply to comment #6) > revdep-rebuild should have noticed that google-talkplugin was broken, and at > least should have warned me. That is strange, revdep-rebuild parses the output of ldd and looks for "not found".
(In reply to comment #7) > (In reply to comment #6) > > revdep-rebuild should have noticed that google-talkplugin was broken, and at > > least should have warned me. > That is strange, revdep-rebuild parses the output of ldd and looks for "not > found". > It doesn't search for /opt in purpose (it's for binary-only pkgs).
(In reply to comment #3) > I can reproduce this by removing libpng12.so.0 on my system. I'm not sure why > that file would be missing under normal circumstances, however. > > Have you identified the exact sequence of events that led to this? I don't know what exactly caused this, but gentoo updates over time, somehow, has led to a system with libpng-1.2 installed but libpng12.so.0 missing. MAYBE some ebuild message told me that file was left from previous versions and told me it was safe to delete it. MAYBE it was a conflict. I really don't know. But the fact is that my system was in such state, and (looking at other bug reports and forum posts) it seems other people also have the system in such state (libpng12.so.0 missing, but libpng-1.2 installed).
This is preserve_old_lib (from eutils.eclass) plus SLOT'd library problem where the old library gets owned by the package preserving it. Solved in Portage 2.2 by preserved-libs feature.
*** Bug 370291 has been marked as a duplicate of this bug. ***