Bug 300712 – Sig 11 after calling camel_mime_part_get_filename() when accepting meeting request

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 300712 - Sig 11 after calling camel_mime_part_get_filename() when accepting meeting request


Summary:	Sig 11 after calling camel_mime_part_get_filename() when accepting meeting r...


Status:	RESOLVED DUPLICATE of bug 272632

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-04-15 08:59 UTC by Mark Ivens
Modified:	2005-04-27 13:45 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Mark Ivens 2005-04-15 08:59:28 UTC

Steps to reproduce:
1. Attempt to accept a meeting request to global calendar (offending email can
be provided on request)


Stack trace:

+ Trace 58211

Thread 2 (Thread 1 (LWP 100268))

#0 camel_mime_part_get_filename
from /usr/X11R6/lib/libcamel-1.2.so.0
#1 em_utils_temp_save_part
at em-utils.c line 1172
#2 update_item
at itip-formatter.c line 744
#3 view_response_cb
at itip-formatter.c line 1159
#4 g_cclosure_marshal_VOID
from /usr/local/lib/libgobject-2.0.so.600
#5 g_closure_invoke
from /usr/local/lib/libgobject-2.0.so.600
#6 g_signal_emit_by_name
from /usr/local/lib/libgobject-2.0.so.600
#7 g_signal_emit_valist
from /usr/local/lib/libgobject-2.0.so.600
#8 g_signal_emit
from /usr/local/lib/libgobject-2.0.so.600
#9 button_clicked_cb
at itip-view.c line 665
#10 g_cclosure_marshal_VOID__VOID
from /usr/local/lib/libgobject-2.0.so.600
#11 g_closure_invoke
from /usr/local/lib/libgobject-2.0.so.600
#12 g_signal_emit_by_name
from /usr/local/lib/libgobject-2.0.so.600
#13 g_signal_emit_valist
from /usr/local/lib/libgobject-2.0.so.600
#14 g_signal_emit
from /usr/local/lib/libgobject-2.0.so.600
#15 gtk_button_clicked
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#16 gtk_button_get_relief
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#17 g_cclosure_marshal_VOID__VOID
from /usr/local/lib/libgobject-2.0.so.600
#18 g_cclosure_new_swap
from /usr/local/lib/libgobject-2.0.so.600
#19 g_closure_invoke
from /usr/local/lib/libgobject-2.0.so.600
#20 g_signal_emit_by_name
from /usr/local/lib/libgobject-2.0.so.600
#21 g_signal_emit_valist
from /usr/local/lib/libgobject-2.0.so.600
#22 g_signal_emit
from /usr/local/lib/libgobject-2.0.so.600
#23 gtk_button_released
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#24 gtk_button_get_relief
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#25 gtk_marshal_VOID__UINT_STRING
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#26 g_cclosure_new_swap
from /usr/local/lib/libgobject-2.0.so.600
#27 g_closure_invoke
from /usr/local/lib/libgobject-2.0.so.600
#28 g_signal_emit_by_name
from /usr/local/lib/libgobject-2.0.so.600
#29 g_signal_emit_valist
from /usr/local/lib/libgobject-2.0.so.600
#30 g_signal_emit
from /usr/local/lib/libgobject-2.0.so.600
#31 gtk_widget_send_expose
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#32 gtk_widget_event
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#33 gtk_propagate_event
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#34 gtk_main_do_event
from /usr/X11R6/lib/libgtk-x11-2.0.so.600
#35 gdk_x11_register_standard_event_type
from /usr/X11R6/lib/libgdk-x11-2.0.so.600
#36 g_main_depth
from /usr/local/lib/libglib-2.0.so.600
#37 g_main_context_dispatch
from /usr/local/lib/libglib-2.0.so.600
#38 g_main_context_dispatch
from /usr/local/lib/libglib-2.0.so.600
#39 g_main_loop_run
from /usr/local/lib/libglib-2.0.so.600
#40 bonobo_main
from /usr/local/lib/libbonobo-2.so.0
#41 main
at main.c line 610



Other information:

Comment 1 Kjartan Maraas 2005-04-27 13:45:50 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 272632 ***