CalDAV on KDE/KOrganizer/Akonadi doesn't sync

Rraven24 · Jul 6, 2022

Hi, I just tried to set up CalDAV on a Linux + KDE + KOrganizer client.
I can see the Calendars fine, but the entries don't sync.
This is the log output that is produced:

06.07.2022 14:20:39 [ 2196] [DEBUG] main ------------------ Start
06.07.2022 14:20:39 [ 2196] [DEBUG] main REPORT /dav/calendars/[user@server]/Kalender/
06.07.2022 14:20:39 [ 2196] [DEBUG] main grommunio-dav version 1.0.7.5ef0bf6
06.07.2022 14:20:39 [ 2196] [DEBUG] main SabreDAV version 4.3.1
06.07.2022 14:20:39 [ 2196] [WARN ] error /usr/share/grommunio-dav/lib/GLogger.php:120 DOMDocument::loadXML(): Char 0x0 out of allowed range in Entity, line: 11 (2)
06.07.2022 14:20:39 [ 2196] [WARN ] error /usr/share/grommunio-dav/lib/GLogger.php:120 DOMDocument::loadXML(): Premature end of data in tag href line 11 in Entity, line: 11 (2)
06.07.2022 14:20:39 [ 2196] [WARN ] error /usr/share/grommunio-dav/lib/GLogger.php:120 DOMDocument::loadXML(): Premature end of data in tag calendar-multiget line 2 in Entity, line: 11 (2)
06.07.2022 14:20:39 [ 2196] [DEBUG] main GLogger->LogIncoming(): INPUT
REPORT /dav/calendars/[user@server]/Kalender/ HTTP/1.0
Content-Type: text/xml; charset=utf-8
Depth: 0
Authorization: Basic REDACTED
Accept-Language: de,en;q=0.9
Accept-Charset: utf-8,*;q=0.5
Accept-Encoding: gzip, deflate, x-gzip, x-deflate
Accept: text/html, text/*;q=0.9, image/jpeg;q=0.9, image/png;q=0.9, image/*;q=0.9, */*;q=0.8
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Mozilla/5.0 (X11; Linux x86_64) KIO/5.95 akonadi_davgroupware_resource_3/5.20.2 (22.04.2)
Content-Length: 5894
Connection: close
X-Forwarded-For: 10.10.10.1
X-Real-Ip: 10.10.10.1
Host: flstd.xyz
X-Forwarded-Proto: https

<?xml version="1.0" encoding="utf-8"?>
<calendar-multiget xmlns="urn:ietf:params:xml:ns:caldav">
  <prop xmlns="DAV:">
    <getetag xmlns="DAV:"/>
    <calendar-data xmlns="urn:ietf:params:xml:ns:caldav"/>
  </prop>
  <href xmlns="DAV:">/dav/calendars/[user@server]/Kalender/02000000a5187b6fbcdcea1ed03c5657000000090001.ics</href>
  <href xmlns="DAV:">/dav/calendars/[user@server]/Kalender/02000000a5187b6fbcdcea1ed03c5657000000090002.ics</href>
  <href xmlns="DAV:">/dav/calendars/[user@server]/Kalender/fd9b347b-27fa-4e55-89b4-f2acaf52d392.ics</href>
  <href xmlns="DAV:">/dav/calendars/[user@server]/Kalender/6fafada3-1f26-4c24-b920-0de1dafe8f7c.ics</href>
  <href xmlns="DAV:">/dav/calendars/[user@server]/Kalender/57941603-1b35-49c6-9801-29bfa77bf5f3</href>
</calendar-multiget>

06.07.2022 14:20:39 [ 2196] [DEBUG]  dav GrommunioDavBackend->Logon(): Auth: OK - user [user@server] - session Resource id #128
06.07.2022 14:20:39 [ 2196] [DEBUG] main GLogger->LogOutgoing(): OUTPUT:
HTTP/1.0 500 Internal Server Error
X-GDAV-Version: 1.0.7.5ef0bf6
X-Sabre-Version: 4.3.1
Content-Type: application/xml; charset=utf-8

<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:sabredav-version>4.3.1</s:sabredav-version>
  <s:exception>Sabre\Xml\LibXMLException</s:exception>
  <s:message>Char 0x0 out of allowed range
 on line 11, column 99</s:message>
</d:error>

06.07.2022 14:20:39 [ 2196] [DEBUG] main httpcode='500' memory='4.07 MiB/2.00 MiB' time='0.03s'
06.07.2022 14:20:39 [ 2196] [DEBUG] main ------------------ End

Looks like the client is possibly sending a null byte somewhere(?).
Same setup with a NextCloud Server (afaik they also use SabreDAV) I don't have any problems, setup and sync of all calendars works without problems.

Edit: package versions

$ rpm -qa | egrep '(gromox|grommunio)'
grommunio-admin-web-2.4.0.3.5277083-lp153.77.1.noarch
grommunio-web-3.0.35.b52c14cf-lp153.104.2.noarch
system-user-grommunio-2-lp153.9.4.noarch
grommunio-error-pages-1.0.6.9c50afb-lp153.7.1.noarch
grommunio-imapsync-2.200-lp153.4.1.noarch
grommunio-common-6.2dbc6d3-lp153.13.1.x86_64
grommunio-setup-1.0.62.d4c0c8b-lp153.40.1.noarch
grommunio-admin-common-6.cb985db-lp153.10.1.noarch
grommunio-admin-api-1.7.47.1e03415-lp153.128.1.noarch
gromox-1.26.62.7ea5eed79-lp153.13.1.x86_64
grommunio-release-2022.05.1-lp153.1.1.x86_64
grommunio-dav-1.0.7.5ef0bf6-lp153.1.1.noarch
grommunio-antispam-2.7-lp153.35.1.x86_64
system-user-gromox-2-lp153.11.1.noarch
grommunio-admin-api-bash-completion-1.7.47.1e03415-lp153.128.1.noarch
grommunio-sync-1.0.20-lp153.130.1.noarch

Mmwilliams · Jul 11, 2022

mhhh... well. I'll have a look at it, however you might rather want to get in contact with KDE instead, since sending a null-byte is not allowed by XML as general standard.

As per https://en.wikipedia.org/wiki/Valid_characters_in_XML#Characters_allowed_but_discouraged :

Note that the code point U+0000, assigned to the null control character, is the only character encoded in Unicode and ISO/IEC 10646 that is **always invalid** in any XML 1.0 and 1.1 document.

Mmwilliams · Jul 11, 2022

yeah, well, erm, no. having null bytes wheras the spec doesn't allow it, that's not how it should be. sorry, I rather ask you to reach out to the KDE community instead. allowing null bytes where the spec does not allow it by any means opens many possibilities to be exploited.