GNOME Bugzilla – Bug 762691
CalDAV calendars saved with wrong security information
Last modified: 2017-11-24 21:41:21 UTC
1. Calendar Settings: Add: From Web 2. Paste in a https URL to any CalDAV server 3. Provide username and password when prompted 4. Select your calendars from the list 5. Save Actual: In the process of saving the new calendars as Evolution sources, the Authentication:Port is set to 0 instead of 443 and Security:Method is set to none rather than tls. The calendar is completely invisible to Calendar but does appear in Evolution as broken/inaccessible. Expected: The newly added calendars to appear in Calendar. Secondary expectation: Calendar should provide feedback about broken data sources instead of just hiding them out of sight. Work-around: Edit the Evolution source files and correct the [Security]\nMethod and [Authentication]\nPort entries in the files manually. Or edit the calendar sources from inside Evolution.
I can reproduce this bug with gnome-calendar 2.20.1 from current Debian testing. Indeed, after adding a CalDav calendar in gnome-calendar, the process seems successful but nothing appears. Then, in Evolution, the calendars appear to be of type "on the web" (back translating from French) instead of "caldav". I had to remove it and re-add it from scratch in Evolution. Now it appears fine in gnome-calendar (and looks much better than in Evolution...).
Any progress on this? GNOME Calendar is enough for my purposes since I use vdirsyncer/khal to sync my calendars with the Android phone via Baikal server, so I don't have need for the whole Evolution suite, so it would be nice that Calendar by itself can define required calendars *without* creating them within Evolution...
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/40.