GNOME Bugzilla – Bug 495823
crash in Tasks: Klick Today (Evolution)
Last modified: 2008-03-20 13:35:51 UTC
Version: 2.10 What were you doing when the application crashed? Klick Today (Evolution) Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 733138944 vsize: 733138944 resident: 84881408 share: 60596224 rss: 84881408 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194775769 rtime: 922 utime: 834 stime: 88 cutime:0 cstime: 1 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 46912647313040 (LWP 4025)] [New Thread 1126189392 (LWP 4117)] [New Thread 1178904912 (LWP 4055)] [New Thread 1147169104 (LWP 4049)] (no debugging symbols found) 0x00002aaaacdc297f in waitpid () from /lib64/libpthread.so.0
+ Trace 176967
Thread 1 (Thread 46912647313040 (LWP 4025))
----------- .xsession-errors --------------------- (evolution:4025): e-dateedit.c-WARNING **: time_text:07:30 (evolution:4025): e-dateedit.c-WARNING **: time_text:07:30 (evolution:4025): e-dateedit.c-WARNING **: time_text:07:00 (evolution:4025): e-dateedit.c-WARNING **: time_text:07:00 (evolution:4025): e-dateedit.c-WARNING **: time_text:19:30 (evolution:4025): e-dateedit.c-WARNING **: time_text:07:00 (evolution:4025): e-dateedit.c-WARNING **: time_text:07:00 warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffcbdfd000 --------------------------------------------------
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 426807 ***