Creating a new event in a google calendar is not possible. Creating a new event in a lokal calendar is possible. It was also possible in version 4.9.3 Reproducible: Always Steps to Reproduce: 1. Open KOrganizer 2. Create new event (Ctrl+N) 3. Select calendar Actual Results: I was not able to select a google calendar ressource Expected Results: I should be able to select a google calendar ressource Beta 4.9.90 from kubuntu beta ppa, downgrading to KOrganizer 4.9.3 solves this problem.
I can confirm this bug in Kubuntu 13.04 (KDE 4.9.95). I can't create new event or edit existed one. Looks like calendar in read-only mode
What version of LibKGAPI do you have? Please make sure you have updated to the latest (0.4.4) version.
0.4.2-0ubuntu1. So looks like its kubuntu bug. Thank you!
FYI https://bugs.launchpad.net/ubuntu/+source/libkgapi/+bug/1093371
Works with 0.4.4, ubuntu packaging bug
kdepim-runtime >= 4.9.80 requires LibKGAPI>=0.4.3 at build-time, so if only LibKGAPI 0.4.2 is packaged on Kubuntu, I have no idea how they managed to compile it :). Anyway, please make sure the that kdepim-runtime package in Kubuntu depends on LibKGAPI>=0.4.3. I'll close this bug as resolved now.
Sorry, this is not fixed. I have kdepim-runtime 4.9.97 (4.10 rc2) with libkgapi0 0.4.4 and I cannot add new or edit existing google calendar events.
You can't add a new event, because the calendar is marked as read only (is not listed in the combobox in incidence editor), or that the changes are not visible in Google Calendar? If it's the first, make sure you have restarted Akonadi after the update and in Akonadi Console -> "Browser", right-click one of the Google calendars, open "Folder Properties" and check what's in "ACL" tab. If it's the latter, please open a separate bug report.
Thank you Dan, that was the problem. Perhaps the read only status should be more apparent and should not default to read only. It should also be able to be changed from within Kontact and not need the Akonadi console to change it. Looking back over the comments, I see where Yuriy mentions read only. I missed that before posting.
Users are not supposed to change ACLs of folders, therefore it's not accessible from anywhere else. I suppose there was a problem in migration when updating LibKGAPI and KDE that caused the ACLs not being updated by the Akonadi Resource.
I have the same problem with an eGroupware Server using CalDAV. The solution with ACL in akonadi console works for only some minutes. With groupDAV it works, but I get a lot of errors (Server send wrong data) and mostly the calendar is empty. With KDE 4.9 and the same user on the same server it works without problems. KDE 4.10 with an ownCloud Server works also without problems.
Frank, I suggest opening a new bug specifically for the DAV resource, so that it's maintainer can see it.