GNOME Bugzilla – Bug 362788
crashes on startup
Last modified: 2007-07-26 21:46:15 UTC
Distribution: Unknown Package: Evolution Severity: blocker Version: GNOME2.12.0 2.4.x Gnome-Distributor: SUSE Synopsis: crashes on startup Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: crashes when trying to execute evolution from drop down gnome menu Steps to reproduce the crash: 1. start evolution 2. 3. Expected Results: How often does this happen? every time. suspect corrupted file when evolution closes Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1097064160 (LWP 13726)] [New Thread 1139911600 (LWP 13733)] [Thread debugging using libthread_db enabled] [New Thread 1097064160 (LWP 13726)] [New Thread 1139911600 (LWP 13733)] [Thread debugging using libthread_db enabled] [New Thread 1097064160 (LWP 13726)] [New Thread 1139911600 (LWP 13733)] [New Thread 1137417136 (LWP 13731)] [New Thread 1135315888 (LWP 13730)] [New Thread 1132465072 (LWP 13729)] [New Thread 1128537008 (LWP 13728)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 76738
Thread 3 (Thread 1137417136 (LWP 13731))
------- Bug created by bug-buddy at 2006-10-17 07:17 -------
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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. For some yet unknown reason, such stacktraces are pretty common currently on certain distros. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue. Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace. Thanks! Closing this bug report as no further information has been provided. Also, please feel free to report any further bugs you find. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
*** This bug has been marked as a duplicate of 339602 ***