GNOME Bugzilla – Bug 508414
crash in Tasks: a storm
Last modified: 2008-02-05 08:38:48 UTC
Version: 2.10 What were you doing when the application crashed? a storm 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 93794304 vsize: 93794304 resident: 33939456 share: 27009024 rss: 33939456 rss_rlim: 4294967295 CPU usage: start_time: 1199915716 rtime: 99 utime: 81 stime: 18 cutime:0 cstime: 1 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 -1208588576 (LWP 2940)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184735
Thread 1 (Thread -1208588576 (LWP 2940))
----------- .xsession-errors (39 sec old) --------------------- localuser:msmith being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2724 CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... ** (evolution:2940): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2940): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files CalDAV Eplugin starting up ... (evolution:2940): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel' (evolution:2940): 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 ***