GNOME Bugzilla – Bug 336555
freeze after drag&drop appointment in day view
Last modified: 2013-09-10 14:04:48 UTC
tried to move a recurring appointment in the day view of one of my local calendars by using drag and drop. when i dropped, suddenly the summary of the appointment was displayed one time division above the appointment itself (now the appointment itself did not have a summary) and evolution was frozen. evo CVS head, compiled about a week ago, though it still states "2.5.92". (gdb) run [...] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1099448800 (LWP 22684)] 0x41d40e5e in e_calendar_view_get_tooltips (data=0x8d561a0) at e-calendar-view.c:1991 1991 clone_comp = icalcomponent_new_clone (pevent->comp_data->icalcomp); (gdb) thread apply all bt
+ Trace 67332
Thread 1 (Thread 1099448800 (LWP 22684))
suse9.3/gnome2.10
seems like drag&drop isn't possible at all here. :-( regression.
the same just happened again to me: in week view, i tried to reproduce a never-disappearing calendar tooltip that i had a few minutes ago (i didn't succeed in that, but instead got this crash here). how to reproduce: hmm, dunno exactly, i had the mouse over an appointment and moved around a bit by using the arrow down / arrow up and page down / page up buttons, and it seems that either my laptop or (more likely) evolution was not fast enough to follow my commands... ;-) evo 2.6+ from cvs head on suse9.3, jhbuilded, checked out from cvs a week ago. cannot reproduce it currently. only attaching the thread where this happened: Backtrace was generated from '/opt/gnome/libexec/evolution-2.6' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1099571680 (LWP 32582)] [New Thread 1108126640 (LWP 32597)] [Thread debugging using libthread_db enabled] [New Thread 1099571680 (LWP 32582)] [New Thread 1108126640 (LWP 32597)] [Thread debugging using libthread_db enabled] [New Thread 1099571680 (LWP 32582)] [New Thread 1108126640 (LWP 32597)] 0xffffe410 in ?? ()
+ Trace 67740
adding srini to cc as this seems to be a e_calendar_view_get_tooltips bug... (just reproduced this again; btw i have no idea why bug-buddy states that it's "/opt/gnome/libexec/evolution-2.6". this file does not exist, as "ps ax" clearly states here)
Nice andre :). Is it all with recurring events? IIRC chen was saying that recurring events have some issues wrt dnd.
no, at least the second freeze happened with a normal and non-recurring event.
Seems interesting. I dont see it at all. Could be pretty random.
i can still reproduce this with evolution 2.7.4 cvs head. 0xffffe410 in __kernel_vsyscall ()
+ Trace 69387
rajeev?
Still happening with GNOME 2.16.0 when modifing an event to the calendar by dnd, mentioned on https://launchpad.net/distros/ubuntu/+source/evolution/+bug/45033 too
Ill fix this for 2.8.1
My backtrace is slightly different: (gdb) run [...] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47296141290368 (LWP 8795)] 0x00002b03ff42b32c in e_calendar_view_get_tooltips (data=0xd34c80) at e-calendar-view.c:2134 2134 e-calendar-view.c: No such file or directory. in e-calendar-view.c (gdb) thread apply all bt
+ Trace 72868
Thread 21 (Thread 1124362576 (LWP 8822))
Thread 20 (Thread 1174718800 (LWP 8821))
Thread 18 (Thread 1183111504 (LWP 8819))
Thread 2 (Thread 1082132816 (LWP 8801))
Thread 1 (Thread 47296141290368 (LWP 8795))
Harish is doing the build in another 4 hours. I dont think I have a fix for it now. May be Ill fix it sometime over the week end/next week. Just commited a similiar fix for month view sterday. Need to ananlyze in the same way for day/work-week view too.
Created attachment 73667 [details] [review] Proposed patch
This patch, is slightly on top of bug 333224 . This disables the tooltip when dragging. So the source of crash is fixed. Because the tooltip comes for an old instance of the dragged event which is destroyed. Now the tip wont even occur.
This patch has also been submitted on bug 333224 and reviewed there. See comment #17 on bug 333224.
Harish Ive commened in bug 333224.
Fixed to stable and head.
closing as per last comment, thanks for the heads up.