GNOME Bugzilla – Bug 502856
crash in Tasks: starting email
Last modified: 2007-12-10 17:17:28 UTC
Version: 2.10 What were you doing when the application crashed? starting 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.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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 118394880 vsize: 118394880 resident: 39768064 share: 29794304 rss: 39768064 rss_rlim: 4294967295 CPU usage: start_time: 1197297568 rtime: 127 utime: 113 stime: 14 cutime:1 cstime: 2 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 -1209055520 (LWP 25754)] [New Thread -1230406768 (LWP 25776)] [New Thread -1219916912 (LWP 25773)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181443
Thread 1 (Thread -1209055520 (LWP 25754))
----------- .xsession-errors --------------------- --- Hash table keys for warning below: --> file:///home/jim (nautilus:20432): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (evolution:18338): e-data-server-DEBUG: Loading categories from "/home/jim/.evolution/categories.xml" (evolution:18338): e-data-server-DEBUG: Loaded 29 categories inside eab_vcard_control_new inside eab_vcard_control_new inside eab_vcard_control_new inside eab_vcard_control_new inside eab_vcard_control_new in emp_apps_open_in CalDAV Eplugin starting up ... ** (evolution:25754): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:25754): DEBUG: mailto URL program: evolution --------------------------------------------------
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 ***