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 331977 - Evolution crashed when entering a recurring appointment
Evolution crashed when entering a recurring appointment
Status: RESOLVED DUPLICATE of bug 311406
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-02-21 04:28 UTC by Vladimir Mencl
Modified: 2006-02-21 04:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Vladimir Mencl 2006-02-21 04:28:48 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: Evolution
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution crashed when entering a recurring appointment
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:

Evolution crashed when entering a recurring appointment for over a month
ahead. I started creating a single-day 2-hour appointment, then selected
"appointment repeats", selected "until", clicked the arrow to select the
date.

First, the calendar appeared with the current day and month selected,
then disappeared. On subsequent click on the arrow, evolution crashed.

Steps to reproduce the crash:
1. Start creating an appointment.
2. Select "appointment repeats", select "until"
3. Try to select the date.

Expected Results:

Calendar appears to select the date.

How often does this happen?

First time.

Additional Information:

Timezone is Asia/Hong_Kong



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208285504 (LWP 13322)]
[New Thread -1211655248 (LWP 13345)]
[New Thread -1210995792 (LWP 13324)]
(no debugging symbols found)
0x00c4a402 in __kernel_vsyscall ()

Thread 1 (Thread -1208285504 (LWP 13322))

  • #0 __kernel_vsyscall
  • #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




------- Bug created by bug-buddy at 2006-02-21 04:28 -------

Comment 1 Vladimir Mencl 2006-02-21 04:37:15 UTC
I have now tried to enter the appointment again, and Evolution crashed again.

It seems that at least on my laptop (Fedora 4, updated as of Feb 15, 2006), this bug is 100% reproducible.

So far, I have found a workaround to enter the date manually and avoid using the drop-down calendar.

Still, while moving around the Recurrence dialog box, Evolution had several times overwritten the date I entered with the current date.  Eventually, I succeeded to enter the appointment as intended this way.

Comment 2 Karsten Bräckelmann 2006-02-21 04:41:43 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.


Same stacktrace as bug 316967, which is a duplicate of bug 311406.

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