Bug 229073 - Does not sync when no events in google callendar
Summary: Does not sync when no events in google callendar
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: GoogleData Resource (show other bugs)
Version: 4.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Adenilson Cavalcanti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-01 22:36 UTC by Petr Kolesnikov
Modified: 2017-01-07 21:40 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Kolesnikov 2010-03-01 22:36:48 UTC
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    Ubuntu Packages

I found interesting think about akonadi's googledata module. When the google calendar does not contain any event, syncing fails. There was used assumption there has to be at least one event.

It starts working after I had added one event.

Problematic code part:
          /* GCalendar returns last updated entry as first element */
          event = gcal_event_element(&all_events, 0);
          if (!event) {
                kError() << "Failed to retrieve last updated event.";
                const QString message = i18nc("@info:status",
                                        "Failed getting last updated"
                                        " event.");
                emit error(message);
                emit status(Broken, message);
                return;

          }
Comment 1 Petr Kolesnikov 2010-03-01 22:38:18 UTC
It is located in:

akonadi-googledata-1.0.1/calendar/gcalresource.cpp:

void GCalResource::retrieveItems( const Akonadi::Collection &collection )
Comment 2 Stephan Wienczny 2010-08-09 02:43:13 UTC
I can confirm this bug. My googlecalendar was empty and I tried to sync my lokal events to googlecalendar but nothing happens. Then I added a test event to googlecalendar and the synchronization started working.
Comment 3 Denis Kurz 2016-09-24 20:36:42 UTC
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.
Comment 4 Denis Kurz 2017-01-07 21:40:45 UTC
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.