GNOME Bugzilla – Bug 503282
crash in Tasks:
Last modified: 2007-12-13 12:33:39 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: OSX Memory status: size: 161669120 vsize: 161669120 resident: 78274560 share: 38850560 rss: 78274560 rss_rlim: 4294967295 CPU usage: start_time: 1197471379 rtime: 1572 utime: 1460 stime: 112 cutime:0 cstime: 1 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 -1208191264 (LWP 3564)] [New Thread -1290658928 (LWP 3590)] [New Thread -1223324784 (LWP 3581)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181676
Thread 1 (Thread -1208191264 (LWP 3564))
----------- .xsession-errors --------------------- (evolution:3564): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3564): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3564): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `buf != NULL' failed (evolution:3564): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error (evolution:3564): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3564): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3564): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:3564): e-table-CRITICAL **: e_table_model_pre_change: assertion `E_IS_TABLE_MODEL (e_table_model)' failed --------------------------------------------------
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 239441 ***