Bug 296412 - CalDAV resource fails to read Calender entries, but succeeds to write
Summary: CalDAV resource fails to read Calender entries, but succeeds to write
Status: RESOLVED NOT A BUG
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: 4.8
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-20 08:06 UTC by Henning Schnoor
Modified: 2012-09-19 08:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Debugger output from akonadi console (3.31 KB, text/plain)
2012-09-19 08:34 UTC, Wolfgang Lorenz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Henning Schnoor 2012-03-20 08:06:03 UTC
I added a CalDAV Calender to KOrganizer which already contained some entries. KOrganizer connected to the Calender, but no entries stored on the server are shown. When I add entries in KOrganizer, they are stored into the calender correctly (displayed by Web interface and Lightning), hence writing seems to work. When I delete events on the server that I added with KOrganizer, the events still show up in KOrganizer. 

Manual syncing the calender, restarting Korganizer, even rebooting the system does not help.

On Akonadiconsole, I see that the Akonadi resource only contains the items added in KOrganizer. Modifications of the calender content in Akonadiconsole immediately show up in KOrganizer, hence the problem seems to be with the CalDAV resource and not KOrganizer. When I force a resync of the calender (either in KOrganizer or in Akonade Console), I get the following output in the "Debugger" tab of Akonadi Console:

-----------------------
akonadi_davgroupware_resource_10 (0x82d74e8) 231 LSUB 6 0 (RESOURCE akonadi_davgroupware_resource_10) (ANCESTORS INF) 
akonadi_davgroupware_resource_10 (0x82d74e8) * 6 5 (NAME "calendar" MIMETYPE (application/x-vnd.akonadi.calendar.todo application/x-vnd.akonadi.calendar.event) REMOTEID "https://cal.mail.uni-kiel.de/ucaldav/user/MY-USER-ID/calendar/" REMOTEREVISION "" RESOURCE "akonadi_davgroupware_resource_10" CACHEPOLICY (INHERIT false INTERVAL 5 CACHETIMEOUT -1 SYNCONDEMAND true LOCALPARTS (RFC822)) ANCESTORS ((5 "akonadi_davgroupware_resource_10") (0 "")) AccessRights "a" davprotocol "0") 
akonadi_davgroupware_resource_10 (0x82d74e8) 231 OK List completed 
------------------------

The information view in the Debugger Tab says: "AgentBase(akonadi_davgroupware_resource_10): Unable to retrieve items: There was a problem with the request. Unknown error code 0 Please send a full bug report at http://bugs.kde.org. (400)."

KOrganizer does not show that there is any problem. I'm using KDE 4.8.1 on openSUSE 11.4, x86 architecture. The server is a Bedework calender server.
Comment 1 Grégory Oestreicher 2012-03-20 09:33:00 UTC
Hi Henning,

Apparently Bedework chokes on a request sent by the dav resource (it returns a 400 error). I've never tested this server, so I'll setup a test system to see what the problem is. Can you tell me which Bedework version you are running?

Cheers,
Grégory
Comment 2 Henning Schnoor 2012-03-20 09:43:46 UTC
Hi Grégory,

I can't find the version information on the website (this is a University calender, so I don't have access to the admin interface). The "HOWTO" links on the University page refer to the manual for version 3.6 (but I'm not sure the links would be changed after a possible software update).

Thanks for looking at this!

All the best,
   Henning
Comment 3 Grégory Oestreicher 2012-03-24 10:52:17 UTC
Hi Henning,

I've tested the 3.6 release and I indeed have the same issue. Apparently the bug is in Bedework 3.6 as testing with 3.8 yields normal results (everything works fine).

In this case the only solution is to ask your IT dept to update Bedework as nothing can be done in the resource.

Cheers,
Grégory
Comment 4 Henning Schnoor 2012-03-26 06:42:08 UTC
Hi Grégory,

thanks very much for all the work you put into this, it's really appreciated! Unfortunately, I'll probably be not able to convince the IT department to upgrade, since CalDAV access works well in 3.6 with Lightning, and that seems to be what everybody uses... But I'll try! Maybe I'll find some other argument to convince them that 3.8 is much  better.

So, thanks again for your work!

All the best,
   Henning
Comment 5 Wolfgang Lorenz 2012-09-19 08:34:17 UTC
Created attachment 74022 [details]
Debugger output from akonadi console

Hello,

I'm having the same problem as Henning (reading fails, writing succeeds), but with an Open XChange server and without any error message, other than (from akonadi console):
    AgentBase(akonadi_davgroupware_resource_1): Unable to retrieve items: oxdav.***

I have attached the full debugging log of one "Synchronize All" call. Is there a way to get a more verbose output?

I know, I could use the Akonadi Open-XChange-module, but I think the CalDAV-module is the more elegant solution for me. (Well, would be, if it was working with Open XChange. ;-) )

Version Info:
Server:
* Open XChange 6.20.7
Client:
* OS: Fedora 16
* KDE: 4.8.5