GNOME Bugzilla – Bug 497786
crash in Tasks: Sending an email in Evol...
Last modified: 2007-11-18 13:24:33 UTC
Version: 2.10 What were you doing when the application crashed? Sending an email in Evolution by doing a "Reply All" from an old email in the Sent folder 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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 218677248 vsize: 218677248 resident: 79446016 share: 25313280 rss: 79446016 rss_rlim: 4294967295 CPU usage: start_time: 1195322518 rtime: 6448 utime: 4034 stime: 2414 cutime:44 cstime: 12 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 -1208214800 (LWP 3273)] [New Thread -1285989488 (LWP 24788)] [New Thread -1253856368 (LWP 3420)] [New Thread -1285723248 (LWP 3419)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178434
Thread 1 (Thread -1208214800 (LWP 3273))
----------- .xsession-errors (6 sec old) --------------------- Minor opcode: 6 Resource id: 0x65 QClipboard::setData: Cannot set X11 selection owner for PRIMARY X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003465 (evolution:3273): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:3273): e-table-CRITICAL **: e_table_model_pre_change: assertion `E_IS_TABLE_MODEL (e_table_model)' failed X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x65 --------------------------------------------------
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 ***