I've this problem: when I create an event on a google calendar with kontact, sometimes the event is created only locally and not in google calendar. I've tried to investigate with akonadiKonsole and I've find this: when an event isn't syncronized, I don't have a "remoteId" for the event created. (http://wstaw.org/m/2013/12/10/plasma-windowedS24889.png). How I can help for resolve this issue? Reproducible: Sometimes Steps to Reproduce: 1. Insert a event in a google calendar resource 2. 3. Actual Results: sometimes the event isn't present in google calendar Expected Results: event syncronized with google calendar
I've tried to eliminate the google accounts (I have for account linked) an recreate them. Now, If I stop akonadi and restart, I've this error log. http://privatepaste.com/58681fb98d
And this notification message if I try to update calendar with kontact: Google Calendars and Tasks (ezio.vergine@gmail.com): Requested resource does not exist. Google replied 'Not Found'
I've isolated the issue. After resume from sleep, akonadi doesn't sync my calendar correctly. If i stop akonadi then restart, the issue persist. If I go to systemSettings->personal information, selecta a google resource then press the "modify" button, calendar events are syncronized correctly and I can add new one.
Created attachment 86501 [details] workaround script Script to resyncronize google calendar resources
I've also found the script attached with name "workaround script", but it doesn't work, I've to reboot my laptop to have akonadi work.
I have a very similar issue, although I find that my Google calendar resources develop this issue even if the machine has not slept: in particular, I get the same "Requested resource does not exist. Google replied 'Not Found'" error message whenever the resource attempts to refresh the calendar list, which I've set it to do at regular intervals. I've found that the resources behave correctly again if I restart them from the Akonadi console.
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.