GNOME Bugzilla – Bug 636908
crash in Rhythmbox: cristiana
Last modified: 2010-12-10 02:11:58 UTC
Version: 0.13.1 What were you doing when the application crashed? cristiana Distribution: openSUSE 11.3 (i586) Gnome Release: 2.30.0 (null) (SUSE) BugBuddy Version: 2.30.0 System: Linux 2.6.34.7-0.5-default #1 SMP 2010-10-25 08:40:12 +0200 i686 X Vendor: The X.Org Foundation X Vendor Release: 10800000 Selinux: No Accessibility: Disabled GTK+ Theme: Win7.Basic.02 Icon Theme: Win.7.basic.icon.theme.trial.02 GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 363495424 vsize: 363495424 resident: 64131072 share: 26947584 rss: 64131072 rss_rlim: 18446744073709551615 CPU usage: start_time: 1291925886 rtime: 597 utime: 528 stime: 69 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 0xa452cb70 (LWP 12065)] [New Thread 0xae8d1b70 (LWP 12064)] [New Thread 0xa5cffb70 (LWP 12063)] [New Thread 0xa689bb70 (LWP 12027)] [New Thread 0xa75ffb70 (LWP 12026)] [New Thread 0xa7f73b70 (LWP 12025)] [New Thread 0xac7a6b70 (LWP 12024)] [New Thread 0xafd03b70 (LWP 12023)] [New Thread 0xacb9eb70 (LWP 11966)] [New Thread 0xadba0b70 (LWP 11960)] 0xffffe430 in __kernel_vsyscall ()
+ Trace 225060
Thread 3 (Thread 0xae8d1b70 (LWP 12064))
A debugging session is active. Inferior 1 [process 11949] 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 ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ----------- .xsession-errors (9 sec old) --------------------- OK OK OK OK OK OK OK OK OK OK OK OK (nautilus:2450): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed OK --------------------------------------------------
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 624598 ***