Summary: | Can't see the contents of my Nextcloud calendar | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | David de Cos <david.decos> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | grave | CC: | auxsvr, bovender, buschmann23, david.decos, faure, vkrause |
Priority: | NOR | ||
Version: | 5.12.2 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
David de Cos
2019-10-22 12:29:43 UTC
I have the same issue since upgrading my Nextcloud to version 17. At least I think that started after the upgrade as I only recognized the issue with Kontact/Korganizer today as it is working on my phone as expected. Nextcloud throws an exception about a bad request with the following message: "A calendar-query REPORT on a calendar with a Depth: 0 is undefined. Set Depth to 1" My system: - openSUSE Tumbleweed - Qt 5.13.1 - KDE Frameworks: 5.63.0 - KDE Plasma: 5.17 - KDE Applications: 19.08.2 - Kontact: 5.12.2 I just fixed a regression in kio_http which led to a similar issue for me. https://cgit.kde.org/kio.git/commit/?id=02a8d3deb4f97046da4a0bb79abf9510d2d1c0a2 However that last comment makes me wonder. If Depth:0 came from kio_http and Depth:1 came from kdav, then things might still be wrong, since my patch ignores the kdav-provided depth. Any chance you can try the above kio fix and let us know if it works for you? BTW if you want to downgrade anything, short term, it's kio that you should downgrade (or all of KF5) from 5.63 to 5.62. I can confirm that downgrading to kio 5.62 fixes my problem. Thanks! If you can mail me some instructions on how to apply the kio fix, I'd be willing to try it. It may take me a few days, though, since I don't want to do it on my work computer, so I'll have to install a working system on some other machine. Hey David Faure, your fix works for me. :) With the changes applied, the calendar data is visible and Nextcloud stops throwing the exception about a bad request. *** Bug 413914 has been marked as a duplicate of this bug. *** |