Bug 435774 – crash in saving task in calendar

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 435774 - crash in saving task in calendar


Summary:	crash in saving task in calendar


Status:	RESOLVED DUPLICATE of bug 343369

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.6.x (obsolete)
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-04 10:35 UTC by michal
Modified:	2007-05-04 11:18 UTC

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

Description michal 2007-05-04 10:35:52 UTC

Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: major
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Ubuntu
Synopsis: crash in saving task in calendar
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. Create a task in Calendar with attachment and save
2. Open this task again
3. change date time start and end, then Save and ... ooops crash

Expected Results:
Saved task with modificate date time information

How often does this happen?
In every cases

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.6'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231386944 (LWP 25372)]
[New Thread -1438921808 (LWP 25405)]
[New Thread -1405084752 (LWP 25388)]
[New Thread -1364210768 (LWP 25387)]
[New Thread -1339032656 (LWP 25386)]
[New Thread -1355818064 (LWP 25384)]
[New Thread -1347425360 (LWP 25381)]
[New Thread -1296254032 (LWP 25379)]
[New Thread -1287132240 (LWP 25377)]
[New Thread -1278735440 (LWP 25375)]
[New Thread -1270342736 (LWP 25374)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 132306

Thread 1 (Thread -1231386944 (LWP 25372))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 es_menu_hook_get_type
#4 <signal handler called>
#5 g_utf8_validate
from /usr/lib/libglib-2.0.so.0
#6 g_convert_with_fallback
from /usr/lib/libglib-2.0.so.0
#7 g_filename_from_utf8
from /usr/lib/libglib-2.0.so.0
#8 comp_editor_show_page
from /usr/lib/evolution/2.6/components/libevolution-calendar.so
#9 comp_editor_show_page
from /usr/lib/evolution/2.6/components/libevolution-calendar.so
#10 comp_editor_show_page
from /usr/lib/evolution/2.6/components/libevolution-calendar.so
#11 bonobo_socket_add_id
from /usr/lib/libbonoboui-2.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 bonobo_closure_invoke_va_list
from /usr/lib/libbonobo-2.so.0
#14 bonobo_closure_invoke
from /usr/lib/libbonobo-2.so.0
#15 bonobo_ui_component_add_verb_list
from /usr/lib/libbonoboui-2.so.0
#16 _ORBIT_skel_small_Bonobo_UIComponent_execVerb
from /usr/lib/libbonobo-2.so.0
#17 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#18 Bonobo_UIComponent_execVerb
from /usr/lib/libbonobo-2.so.0
#19 bonobo_ui_engine_ui_event
from /usr/lib/libbonoboui-2.so.0
#20 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#21 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 bonobo_ui_engine_emit_verb_on_w
from /usr/lib/libbonoboui-2.so.0
#27 bonobo_ui_sync_status_new
from /usr/lib/libbonoboui-2.so.0
#28 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#33 gtk_tool_button_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#34 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#35 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#39 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#40 _gtk_button_set_depressed
from /usr/lib/libgtk-x11-2.0.so.0
#41 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#42 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#43 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#44 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#45 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#46 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#47 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#48 _gtk_button_paint
from /usr/lib/libgtk-x11-2.0.so.0
#49 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#50 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#51 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#53 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#54 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#55 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#56 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#57 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#58 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#59 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#60 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#61 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#62 bonobo_main
from /usr/lib/libbonobo-2.so.0
#63 main
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2007-05-04 10:35 -------

Comment 1 palfrey 2007-05-04 11:18:35 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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