GNOME Bugzilla – Bug 505510
crash in Evolution Mail: start the evolution
Last modified: 2008-01-13 23:52:09 UTC
What were you doing when the application crashed? start the evolution Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 91066368 vsize: 91066368 resident: 19636224 share: 15282176 rss: 19636224 rss_rlim: 4294967295 CPU usage: start_time: 1198553216 rtime: 51 utime: 42 stime: 9 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb67f06b0 (LWP 3693)] [New Thread 0xb40eeb90 (LWP 3715)] [New Thread 0xb388bb90 (LWP 3714)] [New Thread 0xb48efb90 (LWP 3712)] [New Thread 0xb58fab90 (LWP 3710)] [New Thread 0xb60fbb90 (LWP 3709)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 182966
----------- .xsession-errors --------------------- 176: b0 19 92 e9 47 4 c0 ee 184: d1 d2 7 45 f c0 6 d5 192: c5 ec cf e8 f7 1b 7b 64 200: 3a 6 c0 ee b3 c9 d1 fe 208: 23 af 1a 2 8 a1 d3 c1 216: fa c9 f1 a1 ee 25 27 e9 224: e4 6 c0 ee bc d2 b8 d5 232: 18 f7 80 4d 6 d5 c5 d5 240: f1 d6 d2 1d 36 a4 52 4 248: d0 a1 c5 d6 27 30 49 b8 256: 6 cb ef bd a8 f2 d4 27 264: ef a6 a9 6 c0 ee d0 a1 272: c1 fa 2a 9e c2 9 4 d5 280: c5 bb db 2a 2c 46 fd 4 288: ca e7 c5 ae 1a aevolution-shell-Message: Killing old version of evolution-data-server... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the 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 help fixing this by installing some debugging packages [1], start the application as normal, and try to 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] Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces