GNOME Bugzilla – Bug 508022
crash in Tasks:
Last modified: 2008-01-10 22:38:56 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 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: 114065408 vsize: 114065408 resident: 35127296 share: 26308608 rss: 35127296 rss_rlim: 4294967295 CPU usage: start_time: 1199787792 rtime: 69 utime: 61 stime: 8 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 -1208686880 (LWP 5939)] [New Thread -1240470640 (LWP 5946)] [New Thread -1229980784 (LWP 5945)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184496
Thread 1 (Thread -1208686880 (LWP 5939))
----------- .xsession-errors --------------------- --- Hash table keys for warning below: --> file:///home/commy (nautilus:5855): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/commy (nautilus:5871): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) *** glibc detected *** evolution: free(): invalid pointer: 0x002bb9d0 *** CalDAV Eplugin starting up ... ** (evolution:5939): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:5939): 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 --------------------------------------------------
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 431459 ***