Bug 292257 - Akonadi-google calendar stays in "Retrieving list of events"
Summary: Akonadi-google calendar stays in "Retrieving list of events"
Status: RESOLVED FIXED
Alias: None
Product: libkgapi
Classification: Frameworks and Libraries
Component: General (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-23 09:16 UTC by Frédéric COIFFIER
Modified: 2012-05-21 22:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 0.3
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric COIFFIER 2012-01-23 09:16:13 UTC 
Version:           unspecified (using Devel) 
OS:                Linux

I'm using KDE 4.8rc2 with the latest Git revision of akonadi-google : 

commit be021c6f12e6804976dcac203a1864686a219c26
Author: Dan Vrátil <dan@progdan.cz>
Date:   Sat Jan 21 17:58:11 2012 +0100

    Link libkgoogle against libkio (fixes build on Fedora)


I have several problems :
 * in akonadiconsole, the Google Calendra resource stays in "Retrieving list of events (100%)"
 * a kio_http process consumes 5% of CPU permanently :
kdeinit4: kio_http [kdeinit] https local:/tmp/ksocket-fcoiffie/klauncherZT8324.slave-socket local:/tmp/ksocket-fcoiffie/akonadi_googlecalendar_resource_1V26639.slave-socket
 * (I don't known if it's linked) Google Calendra resource doesn't remember my calendar name : everytime in open the configuration box, the ComboBox is empty and I have to select my calendar each time.

Reproducible: Always

Steps to Reproduce:
Open the akonadiconsole.


Actual Results:  
The resource Google Calendar is always in "Retrieving list of events (100%)".

Expected Results:  
The resource Google Calendar should return in "Ready" state.
Comment 1 Frédéric COIFFIER 2012-01-27 08:51:21 UTC 
It seems to be a regression in the latest Git revisions as on older revision provided by Gentoo (20111130) works fine.
Comment 2 Daniel Vrátil 2012-05-21 22:37:09 UTC 
This issue was fixed in 0.3.1, please reopen if you should run into the problem again with recent version.