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 593583 - Quit (possibly crash) when setting reoccurrence to an already existing record
Quit (possibly crash) when setting reoccurrence to an already existing record
Status: RESOLVED DUPLICATE of bug 579779
Product: evolution
Classification: Applications
Component: Calendar
2.26.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-08-30 20:56 UTC by Wouter Buddingh'
Modified: 2009-10-09 10:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Wouter Buddingh' 2009-08-30 20:56:31 UTC
When i add an appointment and then try to set it to reoccur, Evolution just quits (without any prompt) discarding the changes that are made. When i create a record and set the reoccurences in one action, it does work.

I think this should be fixed.
Comment 1 André Klapper 2009-08-30 21:27:13 UTC
Thanks for taking the time to report this bug.
In order to solve the problem a stacktrace is required.

Could you please help fixing this by installing some debugging packages [1],
start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] Please install debug packages for evolution, evolution-data-server,
gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those
packages are provided by your distribution).

More details can be found here: http://live.gnome.org/GettingTraces

If bug-buddy does not popup, please see how to use gdb here:
http://live.gnome.org/GettingTraces/Details
Comment 2 Wouter Buddingh' 2009-08-31 17:37:57 UTC


Thread 29 (Thread 0x7fd8919a3950 (LWP 18913))

  • #0 __lll_unlock_wake
    from /lib/libpthread.so.0
  • #1 _L_unlock_56
    from /lib/libpthread.so.0
  • #2 __pthread_mutex_unlock_usercnt
    from /lib/libpthread.so.0
  • #3 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c line 767
  • #4 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3247
  • #5 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 2980
  • #6 IA__g_signal_emit
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3037
  • #7 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #8 ??
    from /usr/lib/libORBit-2.so.0
  • #9 ??
    from /usr/lib/libORBit-2.so.0
  • #10 giop_thread_queue_process
  • #11 ??
    from /usr/lib/libORBit-2.so.0
  • #12 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.20.1/glib/gthreadpool.c line 265
  • #13 g_thread_create_proxy
    at /build/buildd/glib2.0-2.20.1/glib/gthread.c line 635
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6
  • #16 ??

Thread 1 (Thread 0x7fd8b60a87f0 (LWP 18861))

  • #0 comp_util_sanitize_recurrence_master
    at comp-util.c line 823
  • #1 save_comp
    at comp-editor.c line 804
  • #2 save_comp_with_send
    at comp-editor.c line 913
  • #3 action_save_cb
    at comp-editor.c line 1186
  • #4 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c line 767
  • #5 signal_emit_unlocked_R
  • #6 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 2980
  • #7 IA__g_signal_emit
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3037
  • #8 _gtk_action_emit_activate
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtkaction.c line 727
  • #9 button_clicked
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtktoolbutton.c line 705
  • #10 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c line 767
  • #11 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3247
  • #12 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 2980
  • #13 IA__g_signal_emit
  • #14 gtk_real_button_released
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtkbutton.c line 1702
  • #15 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c line 767
  • #16 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3177
  • #17 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 2980
  • #18 IA__g_signal_emit
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3037
  • #19 gtk_button_button_release
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtkbutton.c line 1594
  • #20 _gtk_marshal_BOOLEAN__BOXED
  • #21 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c line 767
  • #22 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3285
  • #23 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 2990
  • #24 IA__g_signal_emit
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3037
  • #25 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtkwidget.c line 4761
  • #26 IA__gtk_propagate_event
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtkmain.c line 2396
  • #27 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtkmain.c line 1601
  • #28 gdk_event_dispatch
  • #29 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 1814
  • #30 g_main_context_iterate
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 2448
  • #31 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 2656
  • #32 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #33 main
    at main.c line 704

I hope that this is sufficient. I'd imagine that it's much easyier to fix this bug by fixing the use case than by looking at these stack traces.

Good luck!
Comment 3 Akhil Laddha 2009-10-09 10:34:37 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 bug 579779 ***