Bug 316404 – evolution crash when choosing "until" in recurrence

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 316404 - evolution crash when choosing "until" in recurrence


Summary:	evolution crash when choosing "until" in recurrence


Status:	RESOLVED FIXED

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-09-15 15:42 UTC by oll
Modified:	2005-09-30 12:00 UTC

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

Description oll 2005-09-15 15:42:24 UTC

Steps to reproduce:
1. Create an appointment and choose recurrence
2. Click on Recurrence 
3. Tick "This appointment recurs"
It sometimes crash there but most often (at least once) but what is sure is that
it always crash when with step 4
4. choose "every 1 day until"
5. Choose date : it crashs (I even don't what must appears next since I always
have the bug)


Stack trace:
BACKTRACE : 

Using host libthread_db library "/lib/tls/libthread_db.so.1".
Core was generated by `/opt/STools/gnome-2.10/bin/evolution-2.2'.

+ Trace 63032

Thread 3 (process 23581)

#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2
#1 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#2 libgnomeui_segv_handle
from /opt/STools/gnome-2.10/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 e_date_edit_show_date_popup
at e-dateedit.c line 1198
#5 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#6 IA__g_closure_invoke
at gclosure.c line 437
#7 signal_emit_unlocked_R
at gsignal.c line 2488
#8 IA__g_signal_emit_valist
at gsignal.c line 2247
#9 IA__g_signal_emit
at gsignal.c line 2291
#10 IA__gtk_button_clicked
at gtkbutton.c line 786
#11 gtk_real_button_released
at gtkbutton.c line 1298
#12 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#13 g_type_class_meta_marshal
at gclosure.c line 514
#14 IA__g_closure_invoke
at gclosure.c line 437
#15 signal_emit_unlocked_R
at gsignal.c line 2418
#16 IA__g_signal_emit_valist
at gsignal.c line 2247
#17 IA__g_signal_emit
at gsignal.c line 2291
#18 IA__gtk_button_released
at gtkbutton.c line 778
#19 gtk_button_button_release
at gtkbutton.c line 1214
#20 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#21 g_type_class_meta_marshal
at gclosure.c line 514
#22 IA__g_closure_invoke
at gclosure.c line 437
#23 signal_emit_unlocked_R
at gsignal.c line 2526
#24 IA__g_signal_emit_valist
at gsignal.c line 2257
#25 IA__g_signal_emit
at gsignal.c line 2291
#26 gtk_widget_event_internal
at gtkwidget.c line 3631
#27 IA__gtk_propagate_event
at gtkmain.c line 2191
#28 IA__gtk_main_do_event
at gtkmain.c line 1429
#29 gdk_event_dispatch
at gdkevents-x11.c line 2259
#30 IA__g_main_context_dispatch
at gmain.c line 1934
#31 g_main_context_iterate
at gmain.c line 2565
#32 IA__g_main_loop_run
at gmain.c line 2769
#33 bonobo_main
from /opt/STools/gnome-2.10/lib/libbonobo-2.so.0
#34 main
at main.c line 611



Other information:

Comment 1 oll 2005-09-15 17:53:44 UTC

It's the same with a freshly installed FC4 :

+ Trace 63034

Thread 1 (Thread -1209039168 (LWP 5378))

#0 ??
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 es_menu_hook_get_type
#4 <signal handler called>
#5 e_date_edit_get_time
from /usr/lib/evolution/2.2/libemiscwidgets.so.0
#6 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_button_get_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#14 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_button_set_relief
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_marshal_VOID__UINT_STRING
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 gdk_screen_get_setting
from /usr/lib/libgdk-x11-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 bonobo_main
from /usr/lib/libbonobo-2.so.0
#35 main

Comment 2 oll 2005-09-15 18:14:09 UTC

I tried with a FC4(new account created) : the same.
Seems related to :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=164458

Comment 3 Chenthill P 2005-09-26 07:19:41 UTC

This is an issue with gtk+. Please upgrade the gtk+ (gtk2) to >= 2.8.3 and this
would be solved.

Comment 4 oll 2005-09-26 07:25:04 UTC

...and migrating from gtk 2.6.10 to 2.8.3 will bring a lot of other problems.
No , gnome is definitively not appropriate for a corporate environment.