GNOME Bugzilla – Bug 471650
crash in Volume Control: I was close Volume Contr...
Last modified: 2007-08-30 16:57:49 UTC
Version: 2.18.0 What were you doing when the application crashed? I was close Volume Control when his crash 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: Bluecurve Icon Theme: Bluecurve Memory status: size: 50335744 vsize: 50335744 resident: 12537856 share: 9437184 rss: 12537856 rss_rlim: 4294967295 CPU usage: start_time: 1188436676 rtime: 130 utime: 117 stime: 13 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (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 -1208649488 (LWP 4699)] (no debugging symbols found) 0x0040b402 in __kernel_vsyscall ()
+ Trace 158925
Thread 1 (Thread -1208649488 (LWP 4699))
----------- .xsession-errors (5383 sec old) --------------------- (gnome-background-properties:3402): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:3402): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:3402): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:3402): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:3402): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:3402): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-bac ...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 471133 ***