Description of problem: xmms deqfaults, when i try to open the xosd plugin config dialog Version-Release number of selected component (if applicable): xmms-xosd-2.2.14-10.fc8 xmms-faad2-2.0-21.20050131.lvn8 xmms-crossfade-0.3.12-2 xmms-acme-0.4.3-8 xmms-1.2.10-36.fc7 bluecurve-xmms-skin-1.0.0-1.fc8 xmms-cdread-0.14-12.fc6 xmms-speex-0.9.1-11 xmms-libs-1.2.10-36.fc7 xmms-musepack-1.2-5.fc8 xmms-mp3-1.2.10-5.lvn6 xmms-flac-1.1.4-3.fc8 xmms-modplug-2.05-11.fc8 How reproducible: Always Steps to Reproduce: 1. start xmms 2. go to options/settings/plugins 3. select "On Screen Display 2.2.14" 4. click "configure" Actual results: xmms segfault Expected results: opening configuration dialog for OSD Additional info: Please see attachment
Created attachment 310959 [details] Backtrace of xmms segfaulting
Cannot reproduce. Backtrace is not helpful as it lacks details and points into pulseaudio-libs instead of xmms/xmms-xosd. Please install the missing debuginfo packages. As root run: debuginfo-install pulseaudio-libs xmms-xosd xmms Then capture another backtrace. Find more about that at: http://fedoraproject.org/wiki/StackTraces
ok, i installed the packages and run xmms with gdb. Please see the attached file with the output from gdb. best regards
Created attachment 323851 [details] gdb output running gdb xmms
That's a crash in gtk2 (libgdk_pixbuf-2.0.so.0) whereas xmms and xmms-xosd use gtk+ 1. Please show the output of ldd /usr/lib/xmms/General/libxmms_osd.so|grep pix and ls -la /usr/lib/libgdk_*
Ok, here we go: $ ldd /usr/lib/xmms/General/libxmms_osd.so|grep pix libgdk_pixbuf.so.2 => /usr/lib/libgdk_pixbuf.so.2 (0x00119000) $ ls -la /usr/lib/libgdk_* lrwxrwxrwx 1 root root 29 17. Jun 18:47 /usr/lib/libgdk_pixbuf-2.0.so -> libgdk_pixbuf-2.0.so.0.1200.8 lrwxrwxrwx 1 root root 29 15. Apr 2008 /usr/lib/libgdk_pixbuf-2.0.so.0 -> libgdk_pixbuf-2.0.so.0.1200.8 -rwxr-xr-x 1 root root 117124 7. Apr 2008 /usr/lib/libgdk_pixbuf-2.0.so.0.1200.8 lrwxrwxrwx 1 root root 22 23. Nov 2007 /usr/lib/libgdk_pixbuf.so.2 -> libgdk_pixbuf.so.2.0.0 -rwxr-xr-x 1 root root 90868 22. Aug 2007 /usr/lib/libgdk_pixbuf.so.2.0.0 lrwxrwxrwx 1 root root 34 17. Jun 18:47 /usr/lib/libgdk_pixbuf_xlib-2.0.so -> libgdk_pixbuf_xlib-2.0.so.0.1200.8 lrwxrwxrwx 1 root root 34 15. Apr 2008 /usr/lib/libgdk_pixbuf_xlib-2.0.so.0 -> libgdk_pixbuf_xlib-2.0.so.0.1200.8 -rwxr-xr-x 1 root root 65412 7. Apr 2008 /usr/lib/libgdk_pixbuf_xlib-2.0.so.0.1200.8 lrwxrwxrwx 1 root root 27 23. Nov 2007 /usr/lib/libgdk_pixbuf_xlib.so.2 -> libgdk_pixbuf_xlib.so.2.0.0 -rwxr-xr-x 1 root root 130552 22. Aug 2007 /usr/lib/libgdk_pixbuf_xlib.so.2.0.0
Reassigning to xosd, which is the right component for xmms-xosd. Kevin, seen this before? Quick summary. xmms-xosd backtrace from comment 4 crashes in gtk2's gdk_pixbuf instead of gtk+ 1's gdk-pixbuf lib that was built with. As if it were preloaded. 0x001cdde1 in gdk_pixbuf_new_from_file () from /usr/lib/libgdk_pixbuf-2.0.so.0
Very strange. No, I have not seen this... I don't have a f8 machine handy, but I guess I can install a virtual. Can you duplicate this? or is the reporter the only one seeing it? Stefan: do you have any LD_PRELOAD set? output of 'env | grep -i ld' ? Do you see the same thing if you make a new user and login and use it as that user?
No, can't reproduce it -- only if I preload. ;-) Noticed the following in the attached memory map, though: 0027f000-0028d000 r-xp 00000000 fd:00 7798785 /usr/lib/gtk-2.0/modules/libgnomebreakpad.so [...] 002a2000-002f5000 r-xp 00000000 fd:00 14682600 /usr/lib/bug-buddy/libbreakpad.so.0.0.0 [...] 002f6000-00312000 r-xp 00000000 fd:00 13674951 /usr/lib/libgdk_pixbuf-2.0.so.0.1200.8 bug-buddy! And preloading bug-buddy's libgnomebreakpad is one way to crash xmms-xosd, of course. Just that bug-buddy here is not active and not loaded either when starting xmms: $ echo $GTK_MODULES gnomebreakpad $ xmms Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: No such file or directory Something else may be necessary to preload it.
(In reply to comment #8) > Stefan: do you have any LD_PRELOAD set? output of 'env | grep -i ld' ? No, none LD_PRELOAD Variables set. > Do you see the same thing if you make a new user and login and use it as that > user? Yes. > 0027f000-0028d000 r-xp 00000000 fd:00 7798785 > /usr/lib/gtk-2.0/modules/libgnomebreakpad.so Upps! This reminds me of a little change, that i've done long time ago. I added the following to "gtk-2.0.conf", because of various complains from applications about "libgnomegreakpad.so" not found. $ cat /etc/ld.so.conf.d/gtk-2.0.conf # /usr/lib/gtk-2.0/modules /usr/lib64/gtk-2.0/modules best regards
Well, that's the way you break Gtk+ 1.x in libgdk_pixbuf.so.2
So, if you remove the ld.so.conf.d/gtk-2.0.conf file and restart, does everything work?
Hi,... yes, i removed the lines, run "ldconfig" again and xmms/xosd works ok. But with this, the following error came back: Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: No such file or directory How can i avoid this? greetings
Ignore it, or enhance the /usr/bin/xmms script to unset $GTK_MODULES
I'm going to go ahead and close this now. If you spot anything further, please file a new bug.