GNOME Bugzilla – Bug 475699
crash in Tasks: sending mail.
Last modified: 2007-10-12 13:12:37 UTC
Version: 2.10 What were you doing when the application crashed? sending mail. 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.18-8.1.8.el5xen #1 SMP Tue Jul 10 07:06:45 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 776069120 vsize: 776069120 resident: 157220864 share: 44847104 rss: 157220864 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189472916 rtime: 4524 utime: 3576 stime: 948 cutime:29 cstime: 135 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496390288 (LWP 30832)] [New Thread 1126189392 (LWP 31045)] [New Thread 1126455632 (LWP 30862)] [New Thread 1094719824 (LWP 30858)] (no debugging symbols found) 0x0000003e39a0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 161957
Thread 1 (Thread 46912496390288 (LWP 30832))
----------- .xsession-errors (8 sec old) --------------------- Major opcode: 19 Minor opcode: 0 Resource id: 0x629016 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30105cf X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2a42f47 (evolution:30832): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:30832): 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 ***