GNOME Bugzilla – Bug 360533
Evolution crashes when deleting or disabling imap account
Last modified: 2007-06-21 16:44:22 UTC
Distribution: Debian testing/unstable Package: Evolution Severity: Normal Version: GNOME2.14.3 (null) Gnome-Distributor: Debian Synopsis: Evolution crashes when deleting or disabling imap account Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: (null) BugBuddy-GnomeVersion: 2.0 (2.16.0) Description: Steps to reproduce the crash: 1. delete an imap account How often does this happen? every time Debugging Information: 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 -1233307040 (LWP 4302)] [New Thread -1329280080 (LWP 4394)] [New Thread -1320891472 (LWP 4393)] [New Thread -1312502864 (LWP 4346)] [New Thread -1278944336 (LWP 4337)] [New Thread -1261773904 (LWP 4333)] [New Thread -1270555728 (LWP 4332)] [New Thread -1253254224 (LWP 4330)] 0xb7719c21 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 75162
Thread 8 (Thread -1253254224 (LWP 4330))
Thread 6 (Thread -1261773904 (LWP 4333))
Thread 5 (Thread -1278944336 (LWP 4337))
Thread 4 (Thread -1312502864 (LWP 4346))
Thread 3 (Thread -1320891472 (LWP 4393))
Thread 2 (Thread -1329280080 (LWP 4394))
------- Bug created by bug-buddy at 2006-10-08 00:54 ------- Unknown version (null) in product Evolution. Setting version to "unspecified".
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Created attachment 74259 [details] better trace sorry, just realized that myself. attached a better trace.
Created attachment 74271 [details] backtrace, reproduced with current cvs HEAD just tested current cvs HEAD. it's the same problem. trace attached
Thanks for following up! It looks like a unique stack trace according to the simple-dup-finder. I'll paste part of the stack trace here so that the simple-dup-finder can catch if anyone else files a duplicate report for us.
+ Trace 75355
same issue as bug 324168 *** This bug has been marked as a duplicate of 324168 ***