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 308062 - crashes when viewing undecrypted gpg mail
crashes when viewing undecrypted gpg mail
Status: RESOLVED DUPLICATE of bug 273386
Product: evolution
Classification: Applications
Component: Mailer
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 365965 367473 368082 371738 418824 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-06-17 13:33 UTC by Johannes Berg
Modified: 2007-04-16 20:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Johannes Berg 2005-06-17 13:33:15 UTC 
Steps to reproduce:
1. send yourself an encrypted gpg email
2. open it, but refuse to enter the gpg password (hit Cancel)
3. evo displays it as two attachments
4. the second attachment can be opened -- do that, close again, open again
5. opening/closing it 2-3 times in rapid succession crashes evolution


Stack trace:
Program received signal SIGSEGV, Segmentation fault.

+ Trace 61164

Thread 16384 (LWP 11216)

  • #0 em_format_set_inline
    from /usr/lib/evolution/2.2/components/libevolution-mail.so
  • #1 em_format_html_display_popup_menu
    from /usr/lib/evolution/2.2/components/libevolution-mail.so
  • #2 em_format_html_display_popup_menu
    from /usr/lib/evolution/2.2/components/libevolution-mail.so
  • #3 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0 
...


Other information:
Comment 1 C Shilpa 2005-06-21 12:49:17 UTC 
*** Bug 308506 has been marked as a duplicate of this bug. ***
Comment 2 C Shilpa 2005-06-21 12:50:33 UTC 
tried to replicate the bug. When i double-clicked on the second attachment,
evolution crashed after the passphrase prompt came up. Here is the stack trace:

Backtrace was generated from '/opt/gnome/bin/evolution-2.2'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread 1095135904 (LWP 6651)]
[New Thread 1134144432 (LWP 14118)]
[Thread debugging using libthread_db enabled]
[New Thread 1095135904 (LWP 6651)]
[New Thread 1134144432 (LWP 14118)]
[Thread debugging using libthread_db enabled]
[New Thread 1095135904 (LWP 6651)]
[New Thread 1134144432 (LWP 14118)]
[New Thread 1133878192 (LWP 14117)]
[New Thread 1133611952 (LWP 14116)]
[New Thread 1133341616 (LWP 14115)]
[New Thread 1128770480 (LWP 10963)]
[New Thread 1122171824 (LWP 10962)]
[New Thread 1119554480 (LWP 6692)]
[New Thread 1117453232 (LWP 6691)]
[New Thread 1115351984 (LWP 6690)]
[New Thread 1110756272 (LWP 6684)]
[New Thread 1112964016 (LWP 6680)]
[New Thread 1108650928 (LWP 6678)]
[New Thread 1106426800 (LWP 6677)]
[New Thread 1104272304 (LWP 6673)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 61342

Thread 1 (Thread 1095135904 (LWP 6651))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 em_format_set_inline
    at em-format.c line 983
  • #5 efhd_attachment_show
    at em-format-html-display.c line 1084
  • #6 efhd_attachment_button_show
    at em-format-html-display.c line 1090
  • #7 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #9 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #12 gtk_button_clicked
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #13 gtk_real_button_released
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #15 g_type_class_meta_marshal
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #17 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #20 gtk_button_released
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #21 gtk_button_button_release
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #22 _gtk_marshal_BOOLEAN__BOXED
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #23 g_type_class_meta_marshal
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #25 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #28 gtk_widget_event_internal
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #29 gtk_propagate_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #30 gtk_main_do_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #31 gdk_event_dispatch
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #32 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #33 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #35 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #36 main
    at main.c line 611
  • #0 __kernel_vsyscall 






Comment 3


Not Zed





          2005-06-24 17:11:13 UTC
        



wow, finally, a real bug to fix.







Comment 4


Not Zed





          2005-08-03 08:56:41 UTC
        



pity i dont have a clue on it anymore :-/  it's some sort of race going on.

lowering pri since this is something you wouldn't normally do.







Comment 5


André Klapper





          2005-11-25 00:11:24 UTC
        



reassigning stuff that has been assigned to notzed. goodbye, dude. :-/






Comment 6


Christian Kirbach





          2006-10-21 10:51:19 UTC
        



the two traces differ already in frame 2 ...  considering the description given to reproduce, they look like different problems to me.






Comment 7


André Klapper





          2006-10-27 21:59:54 UTC
        



still in 2.8, up-to-date stacktrace at bug 365965






Comment 8


André Klapper





          2006-10-27 22:00:05 UTC
        



*** Bug 365965 has been marked as a duplicate of this bug. ***






Comment 9


Karsten Bräckelmann





          2006-10-30 10:24:04 UTC
        



*** Bug 367473 has been marked as a duplicate of this bug. ***






Comment 10


Karsten Bräckelmann





          2006-11-06 23:14:58 UTC
        



*** Bug 368082 has been marked as a duplicate of this bug. ***






Comment 11


Karsten Bräckelmann





          2006-11-06 23:15:12 UTC
        



*** Bug 371738 has been marked as a duplicate of this bug. ***






Comment 12


Akhil Laddha





          2007-03-16 06:20:42 UTC
        



*** Bug 418824 has been marked as a duplicate of this bug. ***






Comment 13


palfrey





          2007-04-16 20:19:30 UTC
        



Thanks for the bug report. 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 273386 ***