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 638813 - [abrt] (SIGSEGV) day_view_top_item_draw_long_event
[abrt] (SIGSEGV) day_view_top_item_draw_long_event
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 667927 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-01-06 11:10 UTC by Milan Crha
Modified: 2015-03-10 16:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2011-01-06 11:10:42 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=664861

abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: I was ismply attempting to duplicate an All Day event from one day to
another. Not sure if this happens everytime or not as I have not yet attempted
it a second time but these crashes seem to be very frequent. Not sure if it is
a GUI issue or CalDav/WebDav intergration of Evolution.
component: evolution
crash_function: day_view_top_item_draw_long_event
executable: /usr/bin/evolution
kernel: 2.6.35.9-64.fc14.x86_64
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: 1292969777
uid: 500

How to reproduce
-----
1. Right-click on an All Day Event in a CalDav calendar
2. Select "Copy"
3. Select a different day in the same CalDav calendar
4. Right-click in "All Day" event area of Day View
5. Click "Paste"

Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

Thread 1 (Thread 26955)

  • #0 day_view_top_item_draw_long_event
    at e-day-view-top-item.c line 346
  • #1 day_view_top_item_draw
    at e-day-view-top-item.c line 775
  • #2 gnome_canvas_group_draw
    at gnome-canvas.c line 1715
  • #3 gnome_canvas_paint_rect
    at gnome-canvas.c line 3110
  • #4 gnome_canvas_expose
    at gnome-canvas.c line 3170
  • #5 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 86
  • #6 g_closure_invoke
    at gclosure.c line 766
  • #7 signal_emit_unlocked_R
    at gsignal.c line 3290
  • #8 g_signal_emit_valist
    at gsignal.c line 2993
  • #9 g_signal_emit
    at gsignal.c line 3040
  • #10 gtk_widget_event_internal
    at gtkwidget.c line 4992
  • #11 IA__gtk_main_do_event
    at gtkmain.c line 1601
  • #12 _gdk_window_process_updates_recurse
    at gdkwindow.c line 5424
  • #13 _gdk_window_process_updates_recurse
    at gdkwindow.c line 5397
  • #14 _gdk_window_process_updates_recurse
    at gdkwindow.c line 5397
  • #15 gdk_window_process_updates_internal
    at gdkwindow.c line 5583
  • #16 IA__gdk_window_process_updates
    at gdkwindow.c line 5757
  • #17 g_closure_invoke
    at gclosure.c line 766
  • #18 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #19 g_signal_emit_valist
    at gsignal.c line 2983
  • #20 g_signal_emit
    at gsignal.c line 3040
  • #21 IA__gtk_adjustment_value_changed
    at gtkadjustment.c line 668
  • #22 scroll_to
    at gnome-canvas.c line 2486
  • #23 gnome_canvas_set_scroll_region
    at gnome-canvas.c line 3423
  • #24 e_day_view_update_top_scroll
    at e-day-view.c line 1587
  • #25 e_day_view_check_layout
    at e-day-view.c line 4819
  • #26 e_day_view_layout_timeout_cb
    at e-day-view.c line 8497
  • #27 g_timeout_dispatch
    at gmain.c line 3585
  • #28 g_main_dispatch
    at gmain.c line 2149
  • #29 g_main_context_dispatch
    at gmain.c line 2702
  • #30 g_main_context_iterate
    at gmain.c line 2780
  • #31 g_main_loop_run
    at gmain.c line 2988
  • #32 IA__gtk_main
    at gtkmain.c line 1237
  • #33 main
    at main.c line 679

Comment 1 Milan Crha 2011-10-14 08:41:04 UTC
Similar bug report from 3.2.0:
https://bugzilla.redhat.com/show_bug.cgi?id=745741

It crashes in a different function, but with the quite similar circumstances.

Thread 4 (Thread 0x7fda27fff700 (LWP 24192))

  • #0 __internal_statvfs
    at ../sysdeps/unix/sysv/linux/internal_statvfs.c line 242
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 ??
  • #5 g_main_context_poll
    at gmain.c line 3402
  • #6 g_main_context_iterate
    at gmain.c line 3084
  • #7 g_main_loop_run
    at gmain.c line 3297
  • #8 g_dbus_connection_send_message_with_reply_sync
    at gdbusconnection.c line 2024
  • #9 g_dbus_connection_call_sync_internal
    at gdbusconnection.c line 5231
  • #10 g_dbus_proxy_call_sync_internal
    at gdbusproxy.c line 2744
  • #11 g_dbus_proxy_call_sync
    at gdbusproxy.c line 2925
  • #12 proxy_method_call_sync
    at e-gdbus-templates.c line 1925
  • #13 e_gdbus_proxy_method_call_sync_void__void
    at e-gdbus-templates.c line 1934
  • #14 cal_client_view_finalize
    at e-cal-client-view.c line 304
  • #15 g_object_unref
    at gobject.c line 2746
  • #16 update_e_cal_view_for_client
    at e-cal-model.c line 2728
  • #17 redo_queries
    at e-cal-model.c line 3181
  • #18 update_memo_view
    at gnome-cal.c line 1375
  • #19 update_todo_view_async
    at gnome-cal.c line 1283
  • #20 message_proxy
    at gnome-cal.c line 182
  • #21 g_thread_pool_thread_proxy
    at gthreadpool.c line 319
  • #22 g_thread_create_proxy
    at gthread.c line 1962
  • #23 start_thread
    at pthread_create.c line 305
  • #24 splice
    at ../sysdeps/unix/syscall-template.S line 84
  • #25 ??

Thread 1 (Thread 0x7fda5be1c9c0 (LWP 22848))

  • #0 pvl_head
    at pvl.c line 554
  • #1 icalcomponent_get_first_property
    at icalcomponent.c line 504
  • #2 icalcomponent_get_dtstart
    at icalcomponent.c line 1596
  • #3 e_calendar_view_get_icalcomponent_summary
    at e-calendar-view.c line 2114
  • #4 e_day_view_update_long_event_label
    at e-day-view.c line 2194
  • #5 e_day_view_reshape_long_event
    at e-day-view.c line 4799
  • #6 e_day_view_reshape_long_event
    at e-day-view.c line 4698
  • #7 e_day_view_reshape_long_events
    at e-day-view.c line 4692
  • #8 e_day_view_check_layout
    at e-day-view.c line 4658
  • #9 e_day_view_layout_timeout_cb
    at e-day-view.c line 8436
  • #10 g_timeout_dispatch
    at gmain.c line 3907
  • #11 g_main_dispatch
    at gmain.c line 2441
  • #12 g_main_context_dispatch
    at gmain.c line 3011
  • #13 g_main_context_iterate
    at gmain.c line 3089
  • #14 g_main_loop_run
    at gmain.c line 3297
  • #15 gtk_main
    at gtkmain.c line 1362
  • #16 main
    at main.c line 696

Comment 2 Kevin Rauwolf 2011-11-15 07:46:21 UTC
I have gotten a crash in the same function, but my trace looks different.

From gdb:

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe3ea865b in day_view_top_item_draw_long_event (
    height=<optimized out>, width=<optimized out>, y=0, x=0, 
    cr=0x7ffff34a9de0, event_num=3, top_item=0xcdf5d0)
    at e-day-view-top-item.c:300
300		text_x = event->canvas_item->x1;

(gdb) print event->canvas_item
$1 = (GnomeCanvasItem *) 0x0

I can reproduce by switching to Work Week view and clicking the "next" button repeatedly.

Sometimes I get the same trace as this bug report, and sometimes I get the one above.
Comment 3 Akhil Laddha 2012-01-16 04:03:14 UTC
*** Bug 667927 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2015-03-10 16:46:41 UTC
No duplicate for a long time, I'm closing this.