GNOME Bugzilla – Bug 608637
crash in Evolution: trying to delete an emai...
Last modified: 2010-03-03 06:31:16 UTC
Version: 2.30.x What were you doing when the application crashed? trying to delete an email Distribution: Slackware Slackware 13.0.0.0.0 Gnome Release: 2.28.0 2009-10-30 (GARNOME) BugBuddy Version: 2.28.0 System: Linux 2.6.32.2 #23 SMP PREEMPT Fri Dec 25 10:27:46 EST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10799002 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad Memory status: size: 180969472 vsize: 180969472 resident: 50077696 share: 25542656 rss: 50077696 rss_rlim: 18446744073709551615 CPU usage: start_time: 1264978249 rtime: 3075 utime: 2908 stime: 167 cutime:52 cstime: 30 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/garnome-svn-2.28/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb59cfa10 (LWP 17521)] [New Thread 0xae0ffb90 (LWP 17702)] [New Thread 0xafa4ab90 (LWP 17562)] [New Thread 0xb0a4ab90 (LWP 17542)] [New Thread 0xb126db90 (LWP 17541)] [New Thread 0xb4bffb90 (LWP 17532)] [New Thread 0xb558eb90 (LWP 17531)] 0xb5c989b1 in waitpid () from //lib/libpthread.so.0
+ Trace 220348
Thread 1 (Thread 0xb59cfa10 (LWP 17521))
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, evolution-exchange, gtkhtml2, gtk2 and glib2 (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!