GNOME Bugzilla – Bug 492647
crash in Tasks: Closing evolution
Last modified: 2007-11-02 20:08:23 UTC
Version: 2.10 What were you doing when the application crashed? Closing 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-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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 751099904 vsize: 751099904 resident: 140218368 share: 46800896 rss: 140218368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193879290 rtime: 9462 utime: 8212 stime: 1250 cutime:1 cstime: 6 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 46912496452976 (LWP 16622)] [New Thread 1115699536 (LWP 26979)] [New Thread 1147169104 (LWP 18573)] [New Thread 1074006352 (LWP 17513)] (no debugging symbols found) 0x00000036ff00d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 174571
Thread 2 (Thread 1115699536 (LWP 26979))
----------- .xsession-errors --------------------- Sample Rate : 44100 Comment : 'transcoded=mp3;166' Time: 00:00.09 [00:00.80] of 00:00.89 ( 10.5%) Output Buffer: 4.42K Time: 00:00.19 [00:00.70] of 00:00.89 ( 20.9%) Output Buffer: 8.88K Time: 00:00.28 [00:00.61] of 00:00.89 ( 31.4%) Output Buffe Done. Increasing itip formatter search count to 1 Increasing itip formatter search count to 2 Decreasing itip formatter search count to 1 Decreasing itip formatter search count to 0 calendar selection changed calendar selection changed calendar selection changed warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffe0bfd000 --------------------------------------------------
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 445309 ***