GNOME Bugzilla – Bug 447816
crash in Calendar: e
Last modified: 2007-06-15 15:47:58 UTC
What were you doing when the application crashed? e 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: 157474816 vsize: 157474816 resident: 37437440 share: 23494656 rss: 37437440 rss_rlim: 4294967295 CPU usage: start_time: 1181898698 rtime: 542 utime: 506 stime: 36 cutime:46 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1209063712 (LWP 3513)] [New Thread -1240953968 (LWP 3600)] [New Thread -1230464112 (LWP 3581)] [New Thread -1359078512 (LWP 3578)] (no debugging symbols found) 0x00ebf402 in __kernel_vsyscall ()
+ Trace 141151
Thread 1 (Thread -1209063712 (LWP 3513))
----------- .xsession-errors (300 sec old) --------------------- (gnome-background-properties:3365): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:3365): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:3365): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-properties:3365): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (gnome-background-properties:3365): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (gnome-background-properties:3365): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed (gnome-background-pro ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 447817 has been marked as a duplicate of this bug. ***
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 431342 *** *** This bug has been marked as a duplicate of 431342 ***