Bug 612174 – Evolution 2.29.92 crashes in em_format_snoop_type when decrypting message

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 612174 - Evolution 2.29.92 crashes in em_format_snoop_type when decrypting message


Summary:	Evolution 2.29.92 crashes in em_format_snoop_type when decrypting message


Status:	RESOLVED DUPLICATE of bug 612082

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-03-08 11:36 UTC by Andreas Proschofsky
Modified:	2010-04-28 10:27 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Andreas Proschofsky 2010-03-08 11:36:30 UTC

Also happened with 2.29.91, just clicking the message (and allowing it t be decrypted) results in the segfault, see the backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa9bbbb70 (LWP 20387)]
0xb60beffb in em_format_snoop_type (part=0xa83be230) at em-format.c:2021
2021	em-format.c: No such file or directory.
	in em-format.c
(gdb) thread apply all bt


(gdb) thread apply all bt

+ Trace 220864

Thread 1 (Thread 0xb678c720 (LWP 20290))

#0 __pthread_mutex_lock
at pthread_mutex_lock.c line 62
#1 IA__g_static_rw_lock_reader_unlock
at gthread.c line 2353
#2 IA__g_type_from_name
at gtype.c line 3301
#3 match_class
at gtkrc.c line 4711
#4 match_widget_class_recursive
at gtkrc.c line 4813
#5 gtk_rc_styles_match
at gtkrc.c line 1872
#6 IA__gtk_rc_get_style
at gtkrc.c line 1978
#7 get_vertical_spacing
at e-cell-text.c line 709
#8 ect_height
at e-cell-text.c line 1165
#9 e_cell_height
#10 ect_height
at e-cell-tree.c line 433
#11 e_cell_height
at e-cell.c line 322
#12 ecv_draw
at e-cell-vbox.c line 151
#13 e_cell_draw
at e-cell.c line 268
#14 eti_draw
at e-table-item.c line 1958
#15 gnome_canvas_group_draw
at gnome-canvas.c line 1676
#16 gnome_canvas_paint_rect
at gnome-canvas.c line 2996
#17 gnome_canvas_expose
at gnome-canvas.c line 3051
#18 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#19 g_type_class_meta_marshal
at gclosure.c line 878
#20 IA__g_closure_invoke
at gclosure.c line 767
#21 signal_emit_unlocked_R
at gsignal.c line 3281
#22 IA__g_signal_emit_valist
at gsignal.c line 2986
#23 IA__g_signal_emit
at gsignal.c line 3033
#24 gtk_widget_event_internal
at gtkwidget.c line 4941
#25 IA__gtk_main_do_event
at gtkmain.c line 1583
#26 _gdk_window_process_updates_recurse
at gdkwindow.c line 5181
#27 _gdk_window_process_updates_recurse
at gdkwindow.c line 5154
#28 _gdk_window_process_updates_recurse
at gdkwindow.c line 5154
#29 _gdk_windowing_window_process_updates_recurse
at gdkwindow-x11.c line 5566
#30 gdk_window_process_updates_internal
at gdkwindow.c line 5340
#31 IA__gdk_window_process_all_updates
at gdkwindow.c line 5448
#32 gdk_window_update_idle
at gdkwindow.c line 5074
#33 gdk_threads_dispatch
at gdk.c line 512
#34 g_idle_dispatch
at gmain.c line 4065
#35 g_main_dispatch
at gmain.c line 1960
#36 IA__g_main_context_dispatch
at gmain.c line 2513
#37 g_main_context_iterate
at gmain.c line 2591
#38 IA__g_main_loop_run
at gmain.c line 2799
#39 IA__gtk_main
at gtkmain.c line 1219
#40 main
at main.c line 607

Comment 1 Akhil Laddha 2010-03-08 12:04:30 UTC

see bug 612082 also

Comment 2 Sepp O. 2010-04-06 11:56:01 UTC

Same here with 2.30.0.1

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa8d5eb70 (LWP 24145)]
0xb4db194e in em_format_snoop_type () from /usr/lib/evolution/2.30/libemformat.so.0
(gdb)

Comment 3 Andreas Proschofsky 2010-04-26 09:02:09 UTC

This seems to be gone with 2.30.1 for me

Comment 4 Milan Crha 2010-04-28 10:27:14 UTC

I agree with Akhil, I'm marking this as a duplicate.

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