GNOME Bugzilla – Bug 354719
crash in Evolution: viewing the calendar
Last modified: 2006-10-04 12:48:39 UTC
What were you doing when the application crashed? viewing the calendar Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 195244032 vsize: 0 resident: 195244032 share: 0 rss: 28082176 rss_rlim: 0 CPU usage: start_time: 1157597270 rtime: 0 utime: 344 stime: 0 cutime:310 cstime: 0 timeout: 34 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232365904 (LWP 6283)] [New Thread -1370035296 (LWP 8375)] [New Thread -1323304032 (LWP 6338)] [New Thread -1275823200 (LWP 6337)] [New Thread -1284252768 (LWP 6296)] [New Thread -1267430496 (LWP 6292)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71772
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I've installed the debug version of these packages. Here's the output I initially get from BugBuddy: Memory status: size: 1703936 vsize: 0 resident: 1703936 share: 0 rss: 487424 rss_rlim: 0 CPU usage: start_time: 1159480539 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-data-server-1.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". 0xffffe410 in __kernel_vsyscall ()
+ Trace 73511
I have tried deleting the calendar directories in ~/.evolution to start over with my calendaring but nothing seems to get rid of them.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Marking as duplicate of a later filed bug, because that one got all debugging symbols. *** This bug has been marked as a duplicate of 359574 ***