GNOME Bugzilla – Bug 214067
Calendar Information Lost. Can't open calendar.ics
Last modified: 2013-09-10 14:02:36 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: I just downloaded the latest snapshot (release candiate 1). Steps to reproduce the problem: 1. On opening, the following error shows up twice: 'Could not open /home/alex/evolution/local/Calendar/calendar.ics. No items from the calendar folder will be migrated to the Tasks folder.' My calendar information is all gone. 2. When I try to save a new appointment, I get the following error: 'Could not update object'. How often does this happen? This happens everytime I start Evolution or attempt to create a new appointment.
What version were you updating from, Alex?
I try to grab every snapshot. I know I was up to date this morning. Then I updated again this afternoon. That is when I started to get errors. To answer your question, I don't know exactly what version it was, but I think it must have been the last snapshot before the one that it currently available.
Could you check the permissions of all the directories leading to your calendar file? If this does not lead to some obvious problem, could you please trace through evolution/calendar/pcs/cal-backend-file.c:open_cal() and tell us where it fails?
The path to the calendar.ics file looks fine. The calenar.ics file in length 0. Is there a way to trace this backout without looking at the source code?
Robert Marz <Robert.Marz@oracle.com> also reported this on Evolution. This really needs fixing soon. Any ideas, Federico?
I'll throw in a me-too. The latest snap I downloaded (today's) blew away my calendar - the calendar.ics~ is 464k - calendar.ics is 0 bytes. I coped the calendar.ics~ into calendar.ics and evo nicely blew it away again. I strongly suggest you stop the snapshots from being distributed until you nail this one. It has the potential to piss off a lot of people.
Total showstopper; jpr, please, no new snaps until this is fixed.
I found a nasty buffer overrun which may have caused this. If you can test the next snapshots and let us know if it is fixed that would be greatly appreciated. Sorry if you lost any data.
You might want to turn off redcarpet snaps until it's been confirmed fixed. (Just a thought). If you send me pointers to new snap packages I'll be happy to install and test.
I had this bug on my machine today, and Damon's commit fixed it.
BTW, there is a new snapshot up and it contains the fix. Please check it out.
That seems to have fixed the problem for me.