GNOME Bugzilla – Bug 489824
crash in Tasks: tried to access a messag...
Last modified: 2007-10-28 14:08:04 UTC
Version: 2.10 What were you doing when the application crashed? tried to access a 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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 683470848 vsize: 683470848 resident: 120000512 share: 35545088 rss: 120000512 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193236537 rtime: 2563 utime: 2509 stime: 54 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496451728 (LWP 1995)] [New Thread 1084229968 (LWP 2594)] [New Thread 1094719824 (LWP 2589)] [New Thread 1126455632 (LWP 2178)] [New Thread 1105209680 (LWP 2109)] (no debugging symbols found) 0x00000035eee0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 172547
Thread 1 (Thread 46912496451728 (LWP 1995))
----------- .xsession-errors (7 sec old) --------------------- ** Message: <info> You are now connected to the wired network. ** Message: <info> You are now connected to the wireless network 'sdtest'. ** Message: <info> Forcing device '/org/freedesktop/NetworkManager/Devices/eth0' ** Message: <info> You are now connected to the wired network. (evolution:1995): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:1995): 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 ***