GNOME Bugzilla – Bug 510462
crash in Sound Juicer CD Extractor: fazendo dowloads de atua...
Last modified: 2008-01-18 19:18:20 UTC
Version: 2.16.4 What were you doing when the application crashed? fazendo dowloads de atualzações Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 87519232 vsize: 87519232 resident: 18997248 share: 13852672 rss: 18997248 rss_rlim: 4294967295 CPU usage: start_time: 1200683202 rtime: 583 utime: 347 stime: 236 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/sound-juicer' (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 -1208214656 (LWP 31841)] (no debugging symbols found) 0x006a7402 in __kernel_vsyscall ()
+ Trace 185866
Thread 1 (Thread -1208214656 (LWP 31841))
----------- .xsession-errors (46855 sec old) --------------------- (gnome-background-properties:2953): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:2953): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:2953): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:2953): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:2953): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:2953): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:2953): ...Too much output, ignoring rest... --------------------------------------------------
*** This bug has been marked as a duplicate of 403870 ***