GNOME Bugzilla – Bug 499011
crash in Tasks: downloading mail
Last modified: 2007-11-22 20:01:25 UTC
Version: 2.10 What were you doing when the application crashed? downloading mail 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-10.fc7 #1 SMP Fri Oct 19 14:35:28 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 636882944 vsize: 636882944 resident: 46919680 share: 31084544 rss: 46919680 rss_rlim: 18446744073709551615 CPU usage: start_time: 1195750960 rtime: 365 utime: 316 stime: 49 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912498623968 (LWP 4026)] [New Thread 1094719824 (LWP 4079)] [New Thread 1115699536 (LWP 4052)] (no debugging symbols found) 0x000000362d60d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 179264
Thread 1 (Thread 46912498623968 (LWP 4026))
----------- .xsession-errors --------------------- (evolution:4026): camel-WARNING **: Could not create key entry for word 'daly': Interrupted system call (evolution:4026): camel-WARNING **: Could not create key entry for word 'iafrica': Interrupted system call (evolution:4026): camel-WARNING **: Could not create key entry for word 'banbayrs': Interrupted system call (evolution:4026): camel-local-provider-WARNING **: Didn't get the next message where I expected (12964206) got 13147317 instead (evolution:4026): camel-local-provider-WARNING **: Didn't get the next message where I expected (12964206) got 13147317 instead warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffb59fd000 --------------------------------------------------
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 ***