GNOME Bugzilla – Bug 640382
[abrt] Prevent a crash in e_week_view_on_text_item_event()
Last modified: 2013-10-17 09:24:58 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=672114 abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: /usr/bin/evolution comment: Sometimes (without any particular regularity) evolution crashes whenever a day is clicked on in the calendar viewing mode (this happened here again) component: evolution crash_function: e_week_view_on_text_item_event executable: /usr/bin/evolution kernel: 2.6.35.10-74.fc14.i686 package: evolution-2.32.1-1.fc14 rating: 4 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1295827884 uid: 500 How to reproduce ----- 1. Click on a date entry in the calendar Core was generated by `/usr/bin/evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 225673
Thread 1 (Thread 16233)
*** Bug 655232 has been marked as a duplicate of this bug. ***
Another downstream bug from evolution 3.4.3: https://bugzilla.redhat.com/show_bug.cgi?id=845384 Core was generated by `evolution'. Program terminated with signal 11, Segmentation fault. 0x0000003dbee8d56b in e_week_view_on_text_item_event (item=item@entry=0x333e400 [EText], gdkevent=0x1fdbe40, week_view=0x2eebbf0 [EWeekView]) at e-week-view.c:3678 3678 pevent->x = ((GdkEventMotion *) gdkevent)->x_root;
+ Trace 230621
Thread 1 (Thread 0x7f8fa85cd9c0 (LWP 2590))
Err, I forgot about comment and xsession_errors: Deleting a calendar all day event (A birthday, I had the date wrong but it was in three different calendars). xsession_errors: :(evolution:2590): Gtk-CRITICAL **: gtk_targets_include_uri: assertion `targets != NULL || n_targets == 0' failed :(evolution:2590): Gtk-CRITICAL **: gtk_targets_include_text: assertion `targets != NULL || n_targets == 0' failed :(evolution:2590): Gtk-CRITICAL **: gtk_targets_include_image: assertion `targets != NULL || n_targets == 0' failed :(evolution:2590): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' :(evolution:2590): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed :(evolution:2590): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject' :(evolution:2590): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed :(evolution:2590): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' :(evolution:2590): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed :(evolution:2590): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject' :(evolution:2590): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed :(evolution:2590): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' :(evolution:2590): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed :(evolution:2590): calendar-gui-WARNING **: tooltip_get_view_event: index 2 is out of bounds [0,2) at array 0xd83e60 :(evolution:2590): calendar-gui-WARNING **: tooltip_get_view_event: index 2 is out of bounds [0,2) at array 0xd83e60 :(evolution:2590): calendar-gui-WARNING **: tooltip_get_view_event: index 2 is out of bounds [0,2) at array 0xd83e60
Downstream bug report about the same from 3.8.5: https://bugzilla.redhat.com/show_bug.cgi?id=1018589 Core was generated by `evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 232608
Thread 1 (Thread 0x7f2542574a40 (LWP 2183))
Created attachment 257485 [details] [review] evo patch (workaround) for evolution; I cannot reproduce this on will, but I know it can happen from time to time. Let's use this workaround, which will prevent the crash, until the UI gets its revamp done.
Created commit af81b13 in evo master (3.11.1+) Created commit 12e2745 in evo gnome-3-10 (3.10.2+)