Bug 340493 – Critical warning and crash in e-attachment-bar.c

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 340493 - Critical warning and crash in e-attachment-bar.c


Summary:	Critical warning and crash in e-attachment-bar.c


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	Do Not Use
Version:	2.6.x (obsolete)
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	Harish Krishnaswamy
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-05-03 06:31 UTC by Kjartan Maraas
Modified:	2013-09-13 12:25 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Attachments
the message that causes the problem (15.78 KB, text/plain) 2006-05-03 07:35 UTC, Kjartan Maraas	Details

Description Kjartan Maraas 2006-05-03 06:31:27 UTC

Got this when reading linux-kernel mail. Just moved from one message to another using '.'

+ Trace 67995

#0 ??
#1 ??
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 820
#3 <signal handler called>
#4 ??
#5 *__GI_raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
#6 *__GI_abort
at abort.c line 88
#7 IA__g_logv
at gmessages.c line 497
#8 IA__g_log
at gmessages.c line 517
#9 IA__g_return_if_fail_warning
at gmessages.c line 532
#10 IA__gdk_pixbuf_copy_area
at gdk-pixbuf-util.c line 131
#11 update
at e-attachment-bar.c line 386
#12 add_common
at e-attachment-bar.c line 157
#13 efhd_attachment_button
at em-format-html-display.c line 1590
#14 efh_object_requested
at em-format-html.c line 590
#15 html_g_cclosure_marshal_BOOLEAN__OBJECT
at htmlmarshal.c line 83
#16 IA__g_closure_invoke
at gclosure.c line 490
#17 signal_emit_unlocked_R
at gsignal.c line 2438
#18 IA__g_signal_emit_valist
at gsignal.c line 2207
#19 IA__g_signal_emit
at gsignal.c line 2241
#20 html_engine_object_requested_cb
at gtkhtml.c line 521
#21 html_g_cclosure_marshal_BOOLEAN__OBJECT
at htmlmarshal.c line 83
#22 IA__g_closure_invoke
at gclosure.c line 490
#23 signal_emit_unlocked_R
at gsignal.c line 2438
#24 IA__g_signal_emit_valist
at gsignal.c line 2207
#25 IA__g_signal_emit
at gsignal.c line 2241
#26 element_parse_object
at htmlengine.c line 1540
#27 parse_one_token
at htmlengine.c line 3759
#28 html_engine_timer_event
at htmlengine.c line 1356
#29 html_engine_flush
at htmlengine.c line 6495
#30 gtk_html_flush
at gtkhtml.c line 5819
#31 emhs_sync_flush
at em-html-stream.c line 127
#32 emcs_gui_received
at em-sync-stream.c line 161
#33 g_io_unix_dispatch
at giounix.c line 162
#34 IA__g_main_context_dispatch
at gmain.c line 1916
#35 g_main_context_iterate
at gmain.c line 2547
#36 IA__g_main_loop_run
at gmain.c line 2751
#37 bonobo_main
at bonobo-main.c line 311
#38 main
at main.c line 611
#39 __libc_start_main
at libc-start.c line 231
#40 _start

Comment 1 Kjartan Maraas 2006-05-03 07:35:33 UTC

Created attachment 64724 [details]
the message that causes the problem

Comment 2 Teppo Turtiainen 2006-05-07 16:11:26 UTC

According to simple-dup-finder this is a unique stack trace.

Comment 3 Kjartan Maraas 2006-07-01 12:12:52 UTC

This looks like it has been fixed. I can view the message just fine now.