GNOME Bugzilla – Bug 647483
crash in Rhythmbox: Ctrl+Q after disabling a...
Last modified: 2011-04-11 22:07:14 UTC
Version: 0.13.3 What were you doing when the application crashed? Ctrl+Q after disabling all plugins Distribution: openSUSE 11.4 (x86_64) Gnome Release: 2.32.1 (null) (SUSE) BugBuddy Version: 2.32.0 System: Linux 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10903000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Gilouche GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 934817792 vsize: 934817792 resident: 67567616 share: 31854592 rss: 67567616 rss_rlim: 18446744073709551615 CPU usage: start_time: 1302544720 rtime: 196 utime: 169 stime: 27 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0x7f6b5720c700 (LWP 5351)] [New Thread 0x7f6b49771700 (LWP 5347)] [New Thread 0x7f6b49f72700 (LWP 5346)] [New Thread 0x7f6b4a773700 (LWP 5345)] [New Thread 0x7f6b4af74700 (LWP 5344)] [New Thread 0x7f6b4b775700 (LWP 5343)] [New Thread 0x7f6b4bf76700 (LWP 5342)] [New Thread 0x7f6b4c777700 (LWP 5341)] [New Thread 0x7f6b4cf78700 (LWP 5340)] [New Thread 0x7f6b4d779700 (LWP 5339)] [New Thread 0x7f6b4df7a700 (LWP 5338)] [New Thread 0x7f6b618e1700 (LWP 5336)] 0x00007f6b6f8dee6d in __libc_waitpid (pid=<value optimized out>, stat_loc=<value optimized out>, options=<value optimized out>) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 226692
Thread 1 (Thread 0x7f6b71c52800 (LWP 5335))
Inferior 1 [process 5335] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ----------- .xsession-errors (11 sec old) --------------------- ** (gnome-session:3847): DEBUG: GsmXSMPClient: UserID = 'sbrabec' ** (gnome-session:3847): DEBUG: GsmXSMPClient: ProcessID = '5335' ** (gnome-session:3847): DEBUG: GsmXSMPClient: RestartStyleHint = 0 ** (gnome-session:3847): DEBUG: GsmXSMPClient: Set properties from client '0x757830 [rhythmbox 1075efa57d4dc72fd313025447214771300000038470066]' ** (gnome-session:3847): DEBUG: GsmXSMPClient: _GSM_DesktopFile = 'file:///usr/share/applications/rhythmbox.desktop' ** (gnome-session:3847): DEBUG: GsmXSMPClient: Client '0x757830 [rhythmbox 1075efa57d4dc72fd313025447214771300000038470066]' received SaveYourselfDone(success = True) ** (gnome-session:3847): DEBUG: GsmXsmpServer: sms_error_handler (0x74def0, FALSE, 3, 9, 32771, 0) Varování správce oken: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x480003e (Přehráva) Varování správce oken: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (gnome-session:3847): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:3847): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:3847): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:3847): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:3847): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:3847): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 645145 ***