GNOME Bugzilla – Bug 581688
Editing a previously created recurring appointment freezes evolution and corrupts the calendar.
Last modified: 2010-12-21 10:48:38 UTC
Please describe the problem: When one edits a recurring event and saves the changes made to it, Evolution greys out and must be force quit. Thereafter, any attempts to access the Evolution Calendar causes Evolution to grey out (lock up). All other aspects of Evolution (email, address book, tasks) still work, only when accessing Calendar does the program lock up. Steps to reproduce: This is one way to reproduce the event: -create a calendar event that recurs weekly. Evolution defaults to 1 occurrence, which is a separate issue that I feel should be addressed (the point of a "recurring event" is that it happens more than once). -save event. See that it's not recurring on the calendar. -open event, click "Recurrence" and change "for 1 occurrence" to "forever". -Close, Save. -a window pops up asking "You are modifying a recurring event. What would you like to modify?" Select "All Instances" and "OK". Evolution immediately greys out and must be force quit. Actual results: Evolution program turns grey and locks up, forcing a force quit. Expected results: The calendar event is modified properly. Does this happen every time? Yes. Other information: See other user reports and commentary at Launchpad, where I was instructed to report here: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/362318
could be bug 580724 Thanks for taking the time to report this bug. Without a stack trace from the hang it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! If you can reproduce it while running Evolution under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this), that might help getting a better trace if you've already got debug packages installed.
See comments from taiebot65 in the report I posted at Launchpad: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/362318 He/she posts that "there is no log error in evolution" and also reports "OK it seems that evolution is creating two events at a time and making it totally unusable. I have attached an ics calendar with an events which was moved and the bug occured." Also, Dan McArdle on the Launchpad bug page reports: "Rather than trashing your calendar after you run into this bug, edit ~/.evolution/calendar/blahblahblah/calendar.ics I searched for the name of my repeating event and came up with two items. For both of them I deleted everything from the "BEGIN" line to the "END" line (including those lines). Then I restarted evolution and it worked as if I never created that event in the first place." Hopefully this helps? Let me know if you still need to get a stack trace and I will attempt to do so.
Created attachment 134520 [details] Editing the recurrence of calendar entry locks up evolution
Created attachment 134521 [details] Open evolution with the calendar componenet active, crashes evolution
Steps: Open evolution switch to calendar Create new event make it recurrent (1 time) save make it recurrent (2 times) save select all instances lock up The second attachment is the trace (at least I hope so, as I've never made one) when opening evolution after the lock up with the calendar component active. (evolution -c calendar). Florian
This bug has been fixed in Ubuntu. Has the fix been applied upstream yet? See: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/362318
Could you please confirm if this bug is still happening at your end ? Please try in 2.30.3 or 2.32.1 and report back, thanks.
(In reply to comment #7) > Could you please confirm if this bug is still happening at your end ? Please > try in 2.30.3 or 2.32.1 and report back, thanks. Version 2.32.1 The lockup is no more reproducible at my end. Florian
Thanks.