GNOME Bugzilla – Bug 367176
crash in Evolution: Update from previous ver...
Last modified: 2006-11-08 17:35:21 UTC
What were you doing when the application crashed? Update from previous version of evolution. If the directoty "~/.evolution" is removed/or renamed, evolution will not crash. But how to get my saved mails ? Distribution: openSUSE 10.2 (i586) Beta1 Gnome Release: 2.16.1 2006-10-24 (SUSE) BugBuddy Version: 2.16.0 Memory status: size: 64188416 vsize: 0 resident: 64188416 share: 0 rss: 6991872 rss_rlim: 0 CPU usage: start_time: 1162155534 rtime: 0 utime: 148 stime: 0 cutime:133 cstime: 0 timeout: 15 it_real_value: 0 frequency: 0 Backtrace was generated from '/opt/gnome/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 -1234835776 (LWP 7415)] [New Thread -1258964080 (LWP 7424)] [New Thread -1250575472 (LWP 7423)] [New Thread -1241810032 (LWP 7421)] (no debugging symbols found) 0xb6971b71 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 80028
Thread 4 (Thread -1241810032 (LWP 7421))
Thread 3 (Thread -1250575472 (LWP 7423))
Thread 2 (Thread -1258964080 (LWP 7424))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] 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! [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
$ gdb evolution GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) thread apply all bt (gdb) run Starting program: /opt/gnome/bin/evolution Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread -1234839872 (LWP 4675)] CalDAV Eplugin starting up ... ** (evolution-2.8:4675): DEBUG: mailto URL command: balsa -m "%s" ** (evolution-2.8:4675): DEBUG: mailto URL program: balsa (evolution-2.8:4675): e-utils-WARNING **: No parent set, or default parent available for error dialog [New Thread -1241814128 (LWP 4682)] [Thread -1241814128 (LWP 4682) exited] [New Thread -1241814128 (LWP 4683)] [New Thread -1250579568 (LWP 4685)] [New Thread -1258968176 (LWP 4686)] Program received signal SIGSEGV, Segmentation fault.
+ Trace 80300
Thread NaN (LWP 4675)
*** Bug 367459 has been marked as a duplicate of this bug. ***
The above report is from gdb, this one if produced with bug-buddy. You need more information ? Heiko --- Distribution: openSUSE 10.2 (i586) Beta1 Gnome Release: 2.16.1 2006-10-24 (SUSE) BugBuddy Version: 2.16.0 Memory status: size: 64258048 vsize: 0 resident: 64258048 share: 0 rss: 6991872 rss_rlim: 0 CPU usage: start_time: 1162197846 rtime: 0 utime: 151 stime: 0 cutime:136 cstime: 0 timeout: 15 it_real_value: 0 frequency: 0 Backtrace was generated from '/opt/gnome/bin/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1234360640 (LWP 4723)] [New Thread -1258488944 (LWP 4734)] [New Thread -1250100336 (LWP 4733)] [New Thread -1241334896 (LWP 4731)] 0xb69e5b71 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 80303
Thread 1 (Thread -1234360640 (LWP 4723))
Stacktrace looks very good, thanks. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 359236 ***