GNOME Bugzilla – Bug 477493
crash in Tasks: forwarding unsent messag...
Last modified: 2007-10-12 13:12:47 UTC
Version: 2.10 What were you doing when the application crashed? forwarding unsent message 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 152215552 vsize: 152215552 resident: 69439488 share: 37437440 rss: 69439488 rss_rlim: 4294967295 CPU usage: start_time: 1189953427 rtime: 1453 utime: 1341 stime: 112 cutime:0 cstime: 2 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 -1208947984 (LWP 3182)] [New Thread -1255146608 (LWP 3247)] [New Thread -1282700400 (LWP 3245)] [New Thread -1240822896 (LWP 3205)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163330
Thread 1 (Thread -1208947984 (LWP 3182))
----------- .xsession-errors (6 sec old) --------------------- (evolution:3182): libebook-WARNING **: invalid escape, passing it through (evolution:3182): libebook-WARNING **: invalid escape, passing it through (evolution:3182): libebook-WARNING **: invalid escape, passing it through (evolution:3182): libebook-WARNING **: invalid escape, passing it through (evolution:3182): libebook-WARNING **: invalid escape, passing it through (evolution:3182): libebook-WARNING **: invalid escape, passing it through (evolution:3182): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:3182): 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 ***