Bug 997853 - new calendar on ownCloud not picked up in Evolution
new calendar on ownCloud not picked up in Evolution
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: evolution-data-server (Show other bugs)
19
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-16 05:54 EDT by Patrick C. F. Ernzer
Modified: 2013-08-19 02:11 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-08-19 02:11:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Patrick C. F. Ernzer 2013-08-16 05:54:03 EDT
Description of problem:
after creating a new calendar in ownCloud 

Version-Release number of selected component (if applicable):
owncloud-5.0.10-9.1.noarch (en RHEL6 from EPEL)
gnome-online-accounts-3.8.2-1.fc19.x86_64
evolution-3.8.4-2.fc19.x86_64

How reproducible:
did not try

Steps to Reproduce:
1. have a working ownCloud instance with 2 calendars already defined
2. Install F19 and set up ownCloud in gnome-online-accounts
3. be happy that both calendars are picked up for evolution and gnome-shell (when clicking the clock)
4. define an additional calendar in ownCloud

Actual results:
the additional calendar does not show up in Evolution

Expected results:
any new calendar set up in ownCloud (be it via it's web UI or via any client software on any connected device) shows up in Evolution

Additional info:
- The settings dialog gnome-online-accounts is a bit sparse, maybe it would be nice it it actually showed a list of calendars offered for the entered login credentials.
- FWIW, the new calendar does show up just fine on both my Android device (via CalDAV-Sync beta by Marten Gajda) and my Nokia N9 via built-in capabilities. So it would seem the ownCloud backend is spitting out the additional calendar just fine.
Comment 1 Debarshi Ray 2013-08-16 06:13:00 EDT
gnome-online-accounts doesn't do much apart from verifying your credentials and advertising your account (including a hint as to where the CalDAV endpoint might be) over D-Bus.

It is evolution-data-server that implements the whole CalDAV protocol.

Reassigning to e-d-s for further investigation.
Comment 2 Milan Crha 2013-08-16 11:48:12 EDT
I'd say the new calendar will be recognized only after restart of evolution-source-registry process (simply log out and log in). This process does the discovery part, but it doesn't poll periodically, thus it didn't notice your new calendar (yet). Could you try the log out, log in steps, please?
Comment 3 Patrick C. F. Ernzer 2013-08-16 16:06:39 EDT
fair enough. better than polling I guess. Is there a way to let the user know that logout/login is needed (maybe as a mouseover text when hovering the calendar on/off button?

In any case, you can close this bug. After logging out and back in the new calendar shows up.
Comment 4 Milan Crha 2013-08-19 02:11:39 EDT
(In reply to Patrick C. F. Ernzer from comment #3)
> fair enough. better than polling I guess. Is there a way to let the user
> know that logout/login is needed (maybe as a mouseover text when hovering
> the calendar on/off button?

There is currently no way to do this. Maybe a Refresh on a group would do it, but it should be handled upstream, rather than in Fedora. I do not know Matthew's plans, but it's possible he counts with something like this (current Refresh above calendar only refresh that single calendar, not the whole group - it's done in a different process).

Note You need to log in before you can comment on or make changes to this bug.