GNOME Bugzilla – Bug 345799
Crash when trying to open "isolated signature" under some conditions
Last modified: 2009-10-27 05:26:46 UTC
Steps to reproduce: 1. Browse an email with detached signature. The crash happened with http://lists.debian.org/debian-devel-announce/2006/06/msg00008.html read through GMANE using evolution NNTP. 2. Make sure evolution "hangs" with 0% complete "verifying signature" 3. While it still hangs, try to open the attachment menu and experience the crash The bug is rare and quite difficult to reproduce Stack trace: Backtrace was generated from '/usr/bin/evolution-2.6' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1501694272 (LWP 6961)] [New Thread -1569719376 (LWP 7054)] [New Thread -1561330768 (LWP 7052)] [New Thread -1551242320 (LWP 7039)] [New Thread -1542853712 (LWP 6999)] [New Thread -1542591568 (LWP 6994)] [New Thread -1534202960 (LWP 6993)] [New Thread -1525253200 (LWP 6990)] [New Thread -1516827728 (LWP 6988)] [New Thread -1508439120 (LWP 6987)] 0xa76c4221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 69031
Thread 1 (Thread -1501694272 (LWP 6961))
Other information: This bug was originally reported at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286868, find more details there.
Also look at bug 487376 , looks similar
*** Bug 487376 has been marked as a duplicate of this bug. ***
This crash report has been submitted against Evolution version 2.10 (or earlier). This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.26. Can you please check again whether this issue still happens in Evolution 2.24 or 2.26 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.26.3 or 2.28.x or later), please reopen. thanks in advance.