GNOME Bugzilla – Bug 482270
crash in Volume Control: Increising the volume in...
Last modified: 2007-10-03 09:59:03 UTC
Version: 2.18.0 What were you doing when the application crashed? Increising the volume in XMMS 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: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 44380160 vsize: 44380160 resident: 12910592 share: 9846784 rss: 12910592 rss_rlim: 4294967295 CPU usage: start_time: 1191252567 rtime: 74 utime: 69 stime: 5 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 -1208727312 (LWP 14770)] (no debugging symbols found) 0x008a8402 in __kernel_vsyscall ()
+ Trace 166876
Thread 1 (Thread -1208727312 (LWP 14770))
----------- .xsession-errors (154982 sec old) --------------------- (gnome-background-properties:9242): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:9242): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:9242): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:9242): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:9242): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:9242): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:9242): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 471133 ***