mplayer-bin dumps core because libXext.so.6 => /usr/NX/lib/libXext.so.6 and libX11.so.6 => /usr/NX/lib/libX11.so.6, when they should be coming from /emul/linux/x86/usr/lib/. This happens because /etc/env.d/50nxclient gets picked up before /etc/env.d/75emul-linux-x86* by env-update. Easy fix would be to mv /etc/env.d/50nxclient to /etc/env.d/80nxclient. With that nxclient doesn't seem to be affected, but mplayer-bin works flawlessly.
Well, this is not a real fix. Upstream should rename the libs to something not stupid to avoid apparent clash and breakage. Happens all the time, not only w/ mplayer.
nxclient is linked with rpath=/usr/NX/lib, so the fix will work for sure. yes, you are right about it being a temp fix, ideally speaking.
not an mplayer-bin problem, it's all NX's fault :P
I had the problem too with a sancho 32-bit binary (well all 32bit binaries will encounter problems if they load these libs :/ ). I did not find a better solution other than moving env.d file in the 80s range though
refer comment #2 and please implement the env.d fix in the portage. It is safe to do so. I recently hit the crash again and took me a while (about two hours) to debug with strace and gdb, and then I remembered about this bug.
Hi, This should be fixed by the new packages in the NX overlay. I'll add the packages to the Portage tree as soon as possible. Best regards, Stu
