GNOME Bugzilla – Bug 638813
[abrt] (SIGSEGV) day_view_top_item_draw_long_event
Last modified: 2015-03-10 16:46:41 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.
+ Trace 225427
Thread 1 (Thread 26955)
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.
+ Trace 228795
Thread 4 (Thread 0x7fda27fff700 (LWP 24192))
Thread 1 (Thread 0x7fda5be1c9c0 (LWP 22848))
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.
*** Bug 667927 has been marked as a duplicate of this bug. ***
No duplicate for a long time, I'm closing this.