KOrganizer does not seem to "see" most of the events I'm saving in the calendar (from KOrganizer itself). This means they are NOT shown in the summary and the reminders do NOT work. I'm using a calendar synced with Google Calendar, it worked fine up to some days ago I think, now the calendars don't seem to sync anymore. Akonadi Console does not report errors as far as I can tell. All seems OK. PS: this caused me to miss an important event yesterday :( Reproducible: Sometimes Steps to Reproduce: 1. Create a test event 2. Check if the test event is present in the summary 3. Check if the reminder(s) for the events work 4. Check if the events have been synced with Google Calendar Actual Results: Most of my events are not shown in the summary page nor the reminders work. I did some test and only 1 event out of 5 worked. IfI move the event around the calendar, it still works, so it's not date-related. To-dos do not seem to be affected. Here below are 5 screenshot of the problem: TEST SETUP https://copy.com/1d8qvz7Wraf2 SUMMARY PAGE FOR TEST SETUP https://copy.com/fPTu8DtWup1I MODIFIED TEST SETUP https://copy.com/rGN9RV8Y8RSG SUMMARY PAGE FOR MODIFIED TEST SETUP https://copy.com/G1d6PZXohrDe SYNC WITH GCALENDAR DOES NOT SEEM TO WORK https://copy.com/3RNJKcH7BWtn Expected Results: Events should show in the summary page, should trigger reminders and should sync. It seems to happen with other calendars too (not only the one in sync with GCalendar). To-dos are not affected. Event setup (reminders, all-day, block etc.) does not seem to matter. I did not try with a new user. If possible, I will provide any additional info as requested.
Also, when I update to-dos (e.g. with a new priority or new info) they do NOT get synced with gcal and after a while they go back to the previous situation, making them pretty useless.
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.