GNOME Bugzilla – Bug 503370
crash in Tasks:
Last modified: 2007-12-13 14:24:13 UTC
Version: 2.10 What were you doing when the application crashed? 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: Fedora Memory status: size: 120291328 vsize: 120291328 resident: 40321024 share: 30253056 rss: 40321024 rss_rlim: 4294967295 CPU usage: start_time: 1197529368 rtime: 176 utime: 153 stime: 23 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 -1209145632 (LWP 3231)] [New Thread -1275073648 (LWP 3244)] [New Thread -1264583792 (LWP 3243)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181734
Thread 1 (Thread -1209145632 (LWP 3231))
----------- .xsession-errors (6 sec old) --------------------- ** ERROR **: file object.c: line 3613 (mono_ldstr_metdata_sig): assertion failed: (ret == 0) aborting... CalDAV Eplugin starting up ... ** (evolution:3231): DEBUG: mailto URL command: evolution %s ** (evolution:3231): 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 (evolution:3231): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3231): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3231): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3231): camel-WARNING **: camel_exception_get_id called with NULL parameter. --------------------------------------------------
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 364700 ***