GNOME Bugzilla – Bug 443187
crash in Rhythmbox Music Player: I just started it!
Last modified: 2007-06-02 22:29:42 UTC
Version: 0.11.0 What were you doing when the application crashed? I just started it! Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.19.2 2007-05-19 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 75497472 vsize: 75497472 resident: 32641024 share: 22044672 rss: 32641024 rss_rlim: 4294967295 CPU usage: start_time: 1180785240 rtime: 121 utime: 96 stime: 25 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208482080 (LWP 21065)] (no debugging symbols found) 0x0014a402 in __kernel_vsyscall ()
+ Trace 137485
Thread 1 (Thread -1208482080 (LWP 21065))
----------- .xsession-errors (175 sec old) --------------------- (gnome-background-properties:21027): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:21027): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:21027): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:21027): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:21027): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:21027): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-proper ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 442236 ***