After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 345799 - Crash when trying to open "isolated signature" under some conditions
Crash when trying to open "isolated signature" under some conditions
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 487376 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-06-24 08:43 UTC by Øystein Gisnås
Modified: 2009-10-27 05:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Øystein Gisnås 2006-06-24 08:43:06 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

Thread 1 (Thread -1501694272 (LWP 6961))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 segv_redirect
    at main.c line 424
  • #3 <signal handler called>
  • #4 camel_object_is
    at camel-object.c line 1034
  • #5 camel_object_ref
    at camel-object.c line 875
  • #6 em_popup_target_new_part
    at em-popup.c line 295
  • #7 efhd_attachment_popup
    at em-format-html-display.c line 1291
  • #8 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 IA__g_closure_invoke
    at gclosure.c line 490
  • #10 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #12 IA__g_signal_emit
    at gsignal.c line 2241
  • #13 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #18 g_main_context_iterate
    at gmain.c line 2547
  • #19 IA__g_main_loop_run
    at gmain.c line 2751
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 main
    at main.c line 612
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0


Other information:
This bug was originally reported at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286868, find more details there.
Comment 1 Akhil Laddha 2007-10-18 04:20:28 UTC
Also look at bug 487376 , looks similar 
Comment 2 Srinivasa Ragavan 2008-01-12 14:58:59 UTC
*** Bug 487376 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2009-07-24 17:45:53 UTC
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.

Comment 4 Akhil Laddha 2009-10-27 05:26:46 UTC
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.