GNOME Bugzilla – Bug 421886
crash in Evolution:
Last modified: 2007-04-29 15:31:21 UTC
What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 365871104 vsize: 365871104 resident: 34181120 share: 18644992 rss: 34181120 rss_rlim: -1 CPU usage: start_time: 1174657484 rtime: 231 utime: 210 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.8' (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 47783514856816 (LWP 5242)] [New Thread 1124096336 (LWP 5262)] [New Thread 1098918224 (LWP 5261)] [New Thread 1107310928 (LWP 5260)] [New Thread 1115703632 (LWP 5256)] [New Thread 1090525520 (LWP 5252)] [New Thread 1082132816 (LWP 5251)] 0x00002b757321e5cf in waitpid () from /lib/libc.so.6
+ Trace 121447
Thread 7 (Thread 1082132816 (LWP 5251))
Thread 6 (Thread 1090525520 (LWP 5252))
Thread 5 (Thread 1115703632 (LWP 5256))
Thread 4 (Thread 1107310928 (LWP 5260))
Thread 3 (Thread 1098918224 (LWP 5261))
Thread 2 (Thread 1124096336 (LWP 5262))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!