GNOME Bugzilla – Bug 463199
crash in Tasks:
Last modified: 2007-08-10 14:38:44 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 144314368 vsize: 144314368 resident: 53235712 share: 41418752 rss: 53235712 rss_rlim: 4294967295 CPU usage: start_time: 1186113255 rtime: 6340 utime: 5867 stime: 473 cutime:1142 cstime: 112 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 -1208596768 (LWP 11773)] [New Thread -1287148656 (LWP 15427)] [New Thread -1297642608 (LWP 11838)] [New Thread -1237902448 (LWP 11811)] (no debugging symbols found) 0x00c41402 in __kernel_vsyscall ()
+ Trace 152595
Thread 1 (Thread -1208596768 (LWP 11773))
----------- .xsession-errors (5461 sec old) --------------------- (evolution:11773): camel-WARNING **: Search returned an invalid result type (evolution:11773): camel-WARNING **: Search returned an invalid result type (evolution:11773): camel-WARNING **: Search returned an invalid result type (evolution:11773): camel-WARNING **: Search returned an invalid result type (evolution:11773): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed (evolution:11773): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (evolution:11773): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' 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 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 273386 ***