GNOME Bugzilla – Bug 504832
crash in Tasks: Cerrando un email.
Last modified: 2008-02-05 08:38:38 UTC
Version: 2.10 What were you doing when the application crashed? Cerrando un email. 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 227852288 vsize: 227852288 resident: 103653376 share: 62701568 rss: 103653376 rss_rlim: 4294967295 CPU usage: start_time: 1198225193 rtime: 3847 utime: 3619 stime: 228 cutime:0 cstime: 0 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 -1208256800 (LWP 29175)] [New Thread -1297716336 (LWP 29326)] [New Thread -1318696048 (LWP 29202)] [New Thread -1287226480 (LWP 29188)] [New Thread -1221547120 (LWP 29187)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182517
Thread 1 (Thread -1208256800 (LWP 29175))
----------- .xsession-errors --------------------- CConnection: Using RFB protocol version 3.8 Fri Dec 21 10:22:22 2007 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 8 (8bpp) colour-map CConn: Using ZRLE encoding Fri Dec 21 10:23:46 2007 main: unable to connect to host: Connection timed out (110) (evolution:29175): libebook-WARNING **: invalid escape, passing it through (evolution:29175): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:29175): 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 ***