GNOME Bugzilla – Bug 378591
crash in Rhythmbox Music Player: starting rhythmbox
Last modified: 2006-12-07 13:58:21 UTC
What were you doing when the application crashed? starting rhythmbox Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6xen #1 SMP Fri Nov 10 13:56:52 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:8730): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:8730): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:9507): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:9507): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files ** (bug-buddy:9747): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 53596160 vsize: 0 resident: 53596160 share: 0 rss: 11517952 rss_rlim: 0 CPU usage: start_time: 1164309270 rtime: 0 utime: 17 stime: 0 cutime:14 cstime: 0 timeout: 3 it_real_value: 0 frequency: 8 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208600864 (LWP 9744)] (no debugging symbols found) 0x00f75402 in __kernel_vsyscall ()
+ Trace 88857
Thread 1 (Thread -1208600864 (LWP 9744))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 379010 has been marked as a duplicate of this bug. ***
Is this what you need? [~]$ gdb rhythmbox GNU gdb Red Hat Linux (6.5-13.fc6rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (gdb) run Starting program: /usr/bin/rhythmbox (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209002272 (LWP 6537)] (no debugging symbols found) (no debugging symbols found) ..........................SNIP.................................. (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1209002272 (LWP 6537)] 0x08078f5c in rb_shell_player_set_selected_source () (gdb) thread apply all bt
+ Trace 89322
Thread 1 (Thread -1209002272 (LWP 6537))
The program is running. Exit anyway? (y or n) y [~]$
Almost - we need you to install the debug symbols for rhythmbox first. http://live.gnome.org/GettingTraces/DistroSpecificInstructions describes how to do that for fedora core 6.
here is a gdb trace following the instructions - This appeared after a yum update. bash-3.1$ gdb /usr/bin/rhythmbox GNU gdb Red Hat Linux (6.5-13.fc6rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... warning: the debug information found in "/usr/lib/debug//usr/bin/rhythmbox.debug" does not match "/usr/bin/rhythmbox" (CRC mismatch). (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/rhythmbox (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208170784 (LWP 4201)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) warning: the debug information found in "/usr/lib/debug//usr/lib/libgtk-x11-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgtk-x11-2.0.so.0" (CRC mismatch). (no debugging symbols found) warning: the debug information found in "/usr/lib/debug//usr/lib/libgdk-x11-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgdk-x11-2.0.so.0" (CRC mismatch). (no debugging symbols found) (no debugging symbols found) warning: the debug information found in "/usr/lib/debug//usr/lib/libgdk_pixbuf-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgdk_pixbuf-2.0.so.0" (CRC mismatch). (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so" (CRC mismatch). Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208170784 (LWP 4201)] 0x08078f5c in rb_shell_player_set_selected_source () (gdb) (gdb) thread apply all bt
+ Trace 89399
Thread 1 (Thread -1208170784 (LWP 4201))
bash-3.1$ exit Script done, file is 378591-061125-1950
(In reply to comment #5) > warning: the debug information found in > "/usr/lib/debug//usr/bin/rhythmbox.debug" does not match "/usr/bin/rhythmbox" > (CRC mismatch). > > [same for gtk+ libraries] I'm not sure why that's happening, but it means that the stack trace you've given still doesn't include the debug symbols for rhythmbox. Do the packages that provide /usr/bin/rhythmbox and /usr/lib/debug/usr/bin/rhythmbox.debug come from the same package repository, and do they have the same version number?
*** Bug 379463 has been marked as a duplicate of this bug. ***
I finally figured out that I needed to do a "yum --enablerepo core-debuginfo install rhythmbox-debuginfo" to get the right file installed. I get a 'warning: the debug information found in "/usr/lib/debug//usr/bin/rhythmbox.debug" does not match "/usr/bin/rhythmbox" (CRC mismatch).' error. [~]$ rpm -q rhythmbox rhythmbox-debuginfo rhythmbox-0.9.5-7.fc6 rhythmbox-debuginfo-0.9.5-4.fc6 I'm going to file a bug against bugzilla.redhat.com.
heh. rebuilt everything related to rhythmbox, and I mean *everything* to get the matching debuginfo from the src.rpms. Although I see some oddments are still not the correct version of debuginfo to match. But the stack trace looks complete. $ gdb /usr/bin/rhythmbox GNU gdb Red Hat Linux (6.5-13.fc6rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/rhythmbox warning: the debug information found in "/usr/lib/debug//usr/lib/libavahi-glib.so.1.0.0.debug" does not match "/usr/lib/libavahi-glib.so.1" (CRC mismatch). [Thread debugging using libthread_db enabled] [New Thread -1209141536 (LWP 17969)] warning: the debug information found in "/usr/lib/debug//usr/lib/libnautilus-burn.so.4.0.0.debug" does not match "/usr/lib/libnautilus-burn.so.4" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/libgtk-x11-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgtk-x11-2.0.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/libgdk-x11-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgdk-x11-2.0.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/libgdk_pixbuf-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgdk_pixbuf-2.0.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so" (CRC mismatch). Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1209141536 (LWP 17969)] 0x08078f2c in get_key_code_from_keyval (keyval=<value optimized out>, modifiers=GDK_MOD1_MASK, key_code=0xbfe8b500 "?���\b", xmodifiers=0xbfe8b4fc) at rb-shell-player.c:720 720 if (modifier_mapping[j].xmodifier_mask != 0) { (gdb) thread apply all bt
+ Trace 89622
Thread 1 (Thread -1209141536 (LWP 17969))
Thanks, that tells me everything I need to know: This is a bug in a fedora patch, rhythmbox-0.9.5-fix-keybinding.patch In the function modifiers_to_xmodifiers, it uses 'j' before initializing it: new_xmodifiers = 0; for (i = 0; modifier_mapping[i].type != (GdkModifierType) 0; i++) { if (modifiers & modifier_mapping[i].type) { Atom atom; if (modifier_mapping[j].xmodifier_mask != 0) { // <-- here new_xmodifiers |= modifier_mapping[i].xmodifier_mask; continue; } .. continuing code that actually initializes 'j'.. since this problem is introduced by a distributor patch, I'm closing the bug.
Sorry for the confusion guys, that patch was never meant to go into an fc6 update. It was an early attempt to implement what was discussed here: http://bugzilla.gnome.org/show_bug.cgi?id=133815#c38 but it was pretty complicated, so instead of finishing the patch, I decided it would probably be better to come up with a control-center specific solution instead. It ended up getting released accidentally when an update went out to address file monitoring (bug 346759).
*** Bug 380464 has been marked as a duplicate of this bug. ***
*** Bug 380520 has been marked as a duplicate of this bug. ***
*** Bug 380699 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217315 I have resolved this bug on FC6 with "yum --enablerepo=updates-testing -y update rhythmbox" .
*** Bug 381744 has been marked as a duplicate of this bug. ***
*** Bug 383336 has been marked as a duplicate of this bug. ***