Since upgrade to Fedora 27 my owncloud calendar is broken. In the web interface the calendars never load, I just see an infinite spinner. Upstream bug reports strongly suggest that this is because owncloud needs to use sabre/vobject 4.0.x instead of 3.5.x. Both versions are packaged and installed for F27, but it looks like the incorrect php-sabre-vobject4 is the dependency for owncloud(?). i.e. the suggestion from upstream is that this is a packaging bug: https://github.com/owncloud/calendar/issues/832 Further background: https://github.com/owncloud/core/issues/29663 https://github.com/owncloud/core/issues/27474
owncloud-9.1.5-2.fc27.noarch php-sabre-vobject-3.5.3-6.fc27.noarch owncloud-httpd-9.1.5-2.fc27.noarch php-sabre-vobject4-4.1.3-1.fc27.noarch
On Fedora 27, downgrading php-sabe-dav to php-sabre-dav-3.0.9-4.fc26.noarch temporarily works around this issue. The current F27 version is 3.2.2-2.fc27 I'm not clear if the packaging issue is in owncloud or php-sabre-dav?
If the latter, possibly same root cause as bug #1514823
I've been having this same issue for weeks after upgrading to F27. Thanks for the workaround! (it worked for me as well). I've had to add exclude=php-sabre-dav to /etc/dnf/dnf.cnf -- hopefully the maintainer can get the dependency issue resolved... I'd hate to have to try getting owncloud 10 working as a standalone install on F27 just to work around this.
I too have stumbled across this bug as I just upgraded my server from F26 to F27. I can also confirm that the workaround fixes it, but of course only temporarily. James, what can we do to help get this solved?
See also https://bugzilla.redhat.com/show_bug.cgi?id=1514823
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days