Version: (using KDE 4.4.0) OS: Linux Installed from: Mandriva RPMs When creating a new event with a recurrence, this seems to happen in a manner which is not compatible with Google Calender. I am using two-way synchronizing with GCALDaemon v1.0 beta16. It does not seem to be a general problem, because I can create recurring events nicely with my Palm Pre, synchronize this with Google Calendar, and this again with Kontact/KOrganizer. All recurrence date appear nicely within korganizer, too! Here's the output of two manual syncs. The second one fails because I created a new recurring event (asdf). After such a sync, the recurring event is deleted from Kontact, too! [mader@santenay mader]$ ./bin/GCALDaemon/bin/sync-now.sh INFO | GCALDaemon V1.0 beta 16 starting... INFO | Extended synchronization enabled. INFO | RSS/ATOM feed converter disabled. INFO | Local time zone is Central European Time. INFO | Start listening file /home/mader/.PIMstuff/calendar.ics... INFO | File listener started successfully. INFO | Offline file synchronization enabled. INFO | Synchronization finished. [mader@santenay mader]$ ./bin/GCALDaemon/bin/sync-now.sh INFO | GCALDaemon V1.0 beta 16 starting... INFO | Extended synchronization enabled. INFO | RSS/ATOM feed converter disabled. INFO | Local time zone is Central European Time. INFO | Start listening file /home/mader/.PIMstuff/calendar.ics... INFO | File listener started successfully. INFO | Offline file synchronization enabled. WARN | Unable to insert event (asdf)! Entry can not contain both gd:when and gd:recurrence elements. INFO | Synchronization finished.
Created attachment 42276 [details] screenshot of the creation of a recurring event
Can you post the event source?
The calendar is an ical-file. (I don't know any other source which works with GCALDaemon.)
That's a problem with GCALDaemon. Try using the DAV akonadi resource to connect to google, in kdepim 4.6.