Bug 274782

Summary:	Akonadi gcal and googledata resource error after resume from suspend to RAM
Product:	[Frameworks and Libraries] Akonadi	Reporter:	lnxusr
Component:	GoogleData Resource	Assignee:	Adenilson Cavalcanti <savagobr>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	ctibor.brancik, kdepim-bugs, linux, lnxusr, vkrause
Priority:	NOR
Version:	1.5.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description lnxusr 2011-06-02 21:24:07 UTC

Version:           1.5.2 (using KDE 4.6.2) 
OS:                Linux

When I resume from suspend to RAM on my laptop, I immediately get two 'Invalid password or network proxy.' error dialogs, one for akonadi_gcal_resource, and one for akonadi_googledata_resource.  To get them working again (a 'Ready' indicator in the Akonadi Configuration Panel), I have to restart Akonadi.  Uppon restarting Akonadi, I immediately get a 'Mail Dispatcher Agent Akonadi Tray' error box complaining that it 'Could not access the outbox folder (Unknown error. (Failed to fetch the resource collection.)).'  Other than two blue checks next to 'MySQL server custom configuration' and ' Protocol version check not posible', there are no problems indicated in my Akonadi logs.

Reproducible: Always

Steps to Reproduce:
Resume from suspend to RAM

Actual Results:  
Error boxes popup at times specified above. akonadi_gcal_resource, and akonadi_googledata_resource are disabled.

Expected Results:  
No errors, akonadi_gcal_resource and akonadi_googledata_resource are not disabled and work as they should.

OS: Linux (i686) release 2.6.38-8-generic-pae
Compiler: cc

Comment 1 lnxusr 2011-08-01 18:42:39 UTC

Your fix for this is to stop displaying the error messages?  What a crock, akonadi_gcal_resource and akonadi_googledata_resource are still disabled when I resume from suspend, and I must still restart Akonadi server to get them working again.  Just because the error boxes don't pop up, doesn't mean the problem is fixed.

If you're going to implement a temp fix, at least do it right.  Have the two services check the state of the network connection.  If it's connected, then connect to google, if not then try again in a couple of seconds.  Repeat until connected. If network connection is established and they can't connect to google, then error out.

That actually sounds like a permanent way to fix it.

Comment 2 Ctibor Brančík 2011-09-05 06:15:57 UTC

I can confirm this problem with akonadi 1.6.0 on gentoo too.

Comment 3 Christophe Marin 2011-09-05 08:11:49 UTC

For all your akonadi-googledata bugs, please give a try to the new resource developed by Dan Vratil. (https://projects.kde.org/projects/playground/pim/akonadi-google)

Comment 4 Michael Holtermann 2011-12-30 10:04:18 UTC

This error still exists in Akonadi 1.6.2 (from Ubuntu 11.10).

Shouldn't this issue become fixed in Akonadi itself? I guess the server is responsible for starting the synchronization processes. If so, it must check network connectivity before starting the sync.

Comment 5 Denis Kurz 2016-09-24 20:43:06 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 6 Denis Kurz 2017-01-07 21:48:46 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.