Bug 308506 – evolution crashed when trying to view an encrypted message without entering the passphrase

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 308506 - evolution crashed when trying to view an encrypted message without entering the passphrase


Summary:	evolution crashed when trying to view an encrypted message without entering t...


Status:	RESOLVED DUPLICATE of bug 273386

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.2.x (obsolete)
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	411380 (view as bug list)
Depends on:
Blocks:

Reported:	2005-06-21 10:57 UTC by C Shilpa
Modified:	2013-09-10 14:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.5/2.6

Attachments
screenshot showing the message after clicking on cancel when the passphrase prompt came up. (171.03 KB, image/png) 2005-06-21 12:06 UTC, C Shilpa	Details

Description C Shilpa 2005-06-21 10:57:25 UTC

Distribution/Version: NLD

Received an encrypted message.When tried to access the message, a dialog asking
for the passphrase came up. Clicked on cancel. The message showed like the one
in the attachment. Evolution crashed when double-clicked on the second
attachment 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 61338

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


Other information:
This happens everytime. I sent the encrypted mail to myself to test encryption.

Comment 1 C Shilpa 2005-06-21 12:06:39 UTC

Created attachment 48093 [details]
screenshot showing the message after clicking on cancel when the passphrase prompt came up.

double-clicking on the second attachment crashed evolution

Comment 2 C Shilpa 2005-06-21 12:49:12 UTC


*** This bug has been marked as a duplicate of 308062 ***

Comment 3 Christian Kirbach 2006-10-21 10:55:28 UTC

I doubt the duplication marked

Comment 4 Christian Kirbach 2006-10-21 10:55:45 UTC


*** This bug has been marked as a duplicate of 273386 ***

Comment 5 Christian Kirbach 2007-02-23 22:09:14 UTC

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