running Nexcloud 10 for a long time. Upgraded my fedora version from fc26 to fc27 and after fixing some selinux, httpd and firewall, mariadb issues all of nextcloud components work except calendar. I've enabled debug in NC but no useful info. I can't sync from clients and when accessing via a browswer it spins when trying to retrieve the calendar name. no useful info in the logs. I'm suspecting a php version issue but not sure. After all the work i've down i'm not wanting to downgrade but will if i can resolve soon. i'm opening a new bug as this is with fc27 and an upgrade, not a new install. the calendar app version is 1.5.3 the latest from nc apps store for this version of NC
I'm experiencing this also. I upgraded from 26 to 27 and caldav and the Calendar app stopped working. I think this be related to Bug 1514823 - owncloud needs some patches for sabre dav 3.2 <https://bugzilla.redhat.com/show_bug.cgi?id=1514823> since php-sabre-dav was updated from 3.0.9-4.fc26 to 3.2.2-2.fc27
I just downgraded to php-sabre-dav-3.0.9-4.fc26.noarch and left everything else at Fedora 27 with all updates and calendars work again.
It is also related to bug 1525208. Also contact synchronization is affected. I confirm php-sabre-dav downgrade fixes all the problems. It looks like php-sabre-dav-3.0.9-4.fc26 uses sabre-vobject 3.5 but php-sabre-dav-3.2.2-2.fc27 uses sabre-vobject4. I think the best solution would be to upgrade nextcloud to version 12, which looks to be designed to use sabre-vobject4.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.