GNOME Bugzilla – Bug 517187
crash in Tasks: Checking the mail
Last modified: 2008-02-18 15:02:55 UTC
What were you doing when the application crashed? Checking the mail Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 115187712 vsize: 115187712 resident: 34988032 share: 21344256 rss: 34988032 rss_rlim: 4294967295 CPU usage: start_time: 1203331521 rtime: 491 utime: 459 stime: 32 cutime:42 cstime: 10 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 -1209026848 (LWP 4260)] [New Thread -1317012592 (LWP 4365)] [New Thread -1327502448 (LWP 4357)] [New Thread -1227273328 (LWP 4328)] [New Thread -1294689392 (LWP 4321)] (no debugging symbols found) 0x005b1402 in __kernel_vsyscall ()
+ Trace 189582
Thread 5 (Thread -1294689392 (LWP 4321))
----------- .xsession-errors (19 sec old) --------------------- (evolution:4260): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' (evolution:4260): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 BBDB spinning up... (evolution:4260): gtkhtml-WARNING **: No such file or directory (evolution:4260): gtkhtml-WARNING **: No such file or directory (evolution:4260): gtkhtml-WARNING **: No such file or directory (evolution:4260): gtkhtml-WARNING **: No such file or directory (evolution:4260): gtkhtml-WARNING **: No such file or directory (evolution:4260): gtkhtml-WARNING **: No such file or directory --------------------------------------------------
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 405646 ***