GNOME Bugzilla – Bug 449831
crash in Multimedia Systems Selector:
Last modified: 2007-09-09 09:38:36 UTC
Version: 2.18.0 What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.1 2007-06-20 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.20-gentoo-r8 #5 Thu Jun 21 13:47:56 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Alphacube GTK 0.5 Icon Theme: TuxnTosh Memory status: size: 162099200 vsize: 162099200 resident: 17182720 share: 12206080 rss: 17182720 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182447830 rtime: 92 utime: 86 stime: 6 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gstreamer-properties' (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 47686252267904 (LWP 17311)] [New Thread 1098918208 (LWP 17344)] 0x00002b5ed02eeb0f in waitpid () from /lib/libpthread.so.0
+ Trace 142709
Thread 1 (Thread 47686252267904 (LWP 17311))
----------- .xsession-errors (515 sec old) --------------------- (gnome-panel:32022): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `pixbuf != NULL' failed (gnome-panel:32022): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed (gnome-panel:32022): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed (gnome-panel:32022): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `pixbuf != NULL' failed (gnome-panel:32022): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed (gnome-panel:32022): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed (gn ...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 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 413801 ***