Hello out there. You are probably my last resort of hope, so this question isn't meant to **** off anyone. But I really have to ask this. Why is the syncing with any Google resource (calendars especially) such a PITA?
In case you don't know, they are developing Android, the market leader in smartphones, so this issue is potentially affecting millions literally.
Please take a look at this bug report, it is plain sad:
http://code.google.com/p/libgcal/issues/detail?id=74
Well, if KDE PIM wants to be taken seriously, this simply *has* to be fixed.
For the DAV option: it never worked for me.
Just let me hear your opinion on this people, devs would be great.

There are currently two resources which are working on getting Google Calendar operable in Akonadi, plus the CalDav method.

operable?

I haven't tested any of those methods but the CalDav method is reported to work quite well, and is the one documented in several blogs posts (which you seemed to have trouble getting to work unfortunately)

Yes, I read about it, doesn't work for me, don't know why. Hence this topic It would be very clever to "sell" this as big feature to make KDE more popular IMHO.

When you try the CalDav method, at which point does it fail?

In the "remote protocol for calendar" window, the "ok" box is always greyed out, no matter what I insert there.

Did you press fetch and select a calendar?

Yap, nothing happens
My address is like:

https://www.google.com/calendar/ical/US ... /basic.ics

Like beforementioned, the "ok" button is greyed out, no data is fetched.

I would recommend ensuring that you have calendars created in your Google account, verify that the url given to you by Google Calendar is correct (recreating it if needed) and ensure that the credentials you are entering are valid (and if you aren't prompted, check in KWallet to see if invalid credentials are in there)

Yes sir, I did all that. Funny thing is... If I save my private ics-link and open that with KOrganizer, it is opened flawlessly Also the address is reachable and all. Well, thanks for your suggestions, but it doesn't work. Still I think, there should be a "official" way to get Google stuff working in KDE-PIM.

Wahhhh. A PM from a member here gave me a hint on how to make it work. The address is supposed to be in this format: https://www.google.com/calendar/dav/use ... om/events/ instead of the direct link to the ics file as before mentioned.
That way it works, I can fetch calendar data, edit it and it works. BUT and that is a big but:
After a reboot, the calendar disappeared out of the calendar list, even if set as default. In the akonadi resource window it is still there and the password field is empty. If I give the password, calendar still does not work and if I reopen the calendar settings EVERYTHING HAS DISAPPEARED! Haha, now I gained exactly nothing, this implementation is as borked for me as the akonadi-googledata one Any help is highly appreciated.
Maybe this log from my akonadiservererror.old is of any use?

Code: Select all

D-Bus session bus is not available!
"[
0: akonadiserver(_Z11akBacktracev+0x39) [0x44e1f9]
1: akonadiserver() [0x44e762]
2: /lib64/libc.so.6() [0x3e6de34160]
3: /lib64/libc.so.6(gsignal+0x35) [0x3e6de340e5]
4: /lib64/libc.so.6(abort+0x186) [0x3e6de35a96]
5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x38bc470864]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xab) [0x4500bb]
7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x38bc4fd9c7]
8: /usr/lib64/qt4/libQtCore.so.4() [0x38bc505d66]
9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x38bc50ec0b]
10: akonadiserver(_ZN13AkApplicationC2ERiPPc+0x145) [0x44b1c5]
11: akonadiserver(main+0x32) [0x449292]
12: /lib64/libc.so.6(__libc_start_main+0xfd) [0x3e6de1eebd]
13: akonadiserver() [0x449169]
]
"


That is simply a backtrace of Akonadi shutting down when you logged out. Have you tried recreating it now that it seems to have broken?

You mean re-entering the account information? Yes, I did that 2 times. It is always the same > after a reboot > all gone.

By recreate I mean deleting the resource then adding it again. If it keeps recurring after an Akonadi restart, it indicates something isn't being saved right. I would suggest verifying permissions under ~/.config/akonadi then filing a bug report.