Bug 266378 - Sogo: "Unable to retrieve items"
Summary: Sogo: "Unable to retrieve items"
Status: CONFIRMED
Alias: None
Product: kresources
Classification: Miscellaneous
Component: groupdav (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-15 14:19 UTC by kaouete
Modified: 2016-01-20 18:30 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 kaouete 2011-02-15 14:19:28 UTC
Version:           unspecified
OS:                Linux

Hi, I set up a groupdav agent for connecting to my SOGo account on the SOGo server at work and at every synchronisation, akonadi tray tells me the following:
ScalableOGo: Unable to retrieve items: The server encountered an error that prevented it from co…

The end is missing, I don't get how to have the end of the message from the kde notifications…

At the same time, the akonadi logs (that I get from starting it from the console) are saying:

akonadi_davgroupware_resource_4(31879): Cannot open  "/inverse.ca/20101018_1/Europe/Paris"
akonadi_davgroupware_resource_4(31879): Cannot open  "/inverse.ca/20101018_1/Europe/Paris"

I don't know what can be the reason of that, there is carddav and caldav spaces with one calendar and several address-books.
Note that one of the address book is backed up by a ldap I think… This address-book does not work from kde, but does from SOGo by the way…

Reproducible: Always
Comment 1 Benjamin 2011-10-24 00:35:18 UTC
the same here, but everything seems to be synced fine
Comment 2 Raimar Sandner 2012-03-31 08:26:27 UTC
I had the same problem using MySQL for SOGo authentication. The problem was caused by the "Shared" addressbook which is composed from the authentication accounts and which is somehow special. It does not display its content but can only be searched, probably this is why akonadi does not play well with it.

As a workaround I disabled this shared addressbook by setting "isAddressBook" to "NO" in the SOGo SQL configuration section. Since that the errors don't appear anymore.

The bug should be fixed by teaching akonadi how to handle this "Shared" addressbook properly, as it is there in many default SOGo installations.
Comment 3 Arthur Schiwon 2012-06-20 11:00:12 UTC
*** This bug has been confirmed by popular vote. ***
Comment 4 Arthur Schiwon 2016-01-20 18:30:20 UTC
I have not seen this for quite a while now.