[Closed - Fixed in 2.1.0.10] Calendar forgets assigned color for CalDAV-Calendar [released]

4140 ●53 ●78 ●78

updated 2017-03-23 22:09:25 +0200

JSEHV
6694 ●134 ●182 ●161

Hello!

I noticed that sometimes that the assigned color for a remote CalDAV-Calendar gets lost and the default bright blue color is used again. At least since 2.1.0.9 the assigned color becomes repeatedly lost, I guess during sync or after the app is closed and opened again. I suspect sync especially, because I've seen that the app during runtime sometimes doesn't show the calendar in the view of Managed calendars. Maybe the connection between local metadata and the assigned remote calendar becomes resetted?

default color

my selected green color

I'm using mailbox.org and the gals and guys there hopefully use sane settings. They offer also free test accounts and I also can create logfiles or similiar, if you tell me to do so.

Thank you

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by JSEHV
close date 2017-03-23 22:09:39.468213

Comments

I've been seeing this behaviour for quite some time (pre 2.0.4.x), but only with one of the calendars I have. It does not happen with my OwnCloud calendars, but is does happen with my Zimbra calendar. Every now and then the colour switches back to the default. I was not able to determine a pattern yet.

What I do see with the OwnCloud calendars is that they start multiplying. I started off with one per calendar, by I have four versions of each calendar (and still only a single instance on the server). I cannot put my finger on it, but I think the two problems are related, as every newly created duplicate OwnCloud calendar also receives the default colour.

dyraig ( 2017-03-20 14:35:37 +0200 )edit

2

answered 2017-02-27 23:44:20 +0200

4140 ●53 ●78 ●78

updated 2017-02-27 23:45:15 +0200

Looks like right reproducing is simpler than I thought:

Add remote-calendar via Settings
Open calendar-app, change color via Manage Calendars
Color is now changed
Close calendar-app
Open calendar-app
Color is still correct
Some background-sync will happen, after a few seconds, entries from remote-calendar will disappear
Entries will reappear a after a few seconds, calendar color is now wrong

6-8 happen automatically, just wait and watch.

Comments

1

I'm observing exactly the same behavior for the hoster all-inkl.com and their built-in web calendars. After step 8. sync is working stable, but colors are always lost.

rweickelt ( 2017-02-28 07:51:40 +0200 )edit

1

Ditto for Davical v. 1.1.3.1-1 on Debian Jessie.

kid ( 2017-02-28 21:46:59 +0200 )edit

1

I see this too, with FastMail CalDAV.

otsaloma ( 2017-02-28 22:51:38 +0200 )edit

0

answered 2017-02-28 08:34:17 +0200

gnuheidix

611 ●5 ●7 ●13

https://gnuheidix.de/

As far as I know, the color of the calendar has to be set on the server side. Does your caldav server provider offer a way to change the color?

Comments

1

I have set manually a green color on server-side and in Evolution, both keep the color. While suggestion a color through CalDAV is neat idea, I don't see a reason to enforce a color from the server-side (i.e. think of a client which is using already some other calendars from other CalDAV-Servers). It just doesn't make sense to enforce the color from the server on the client ;)
The RFC 4791 mentions the word color only once, for alarms and suggests to use non-standard fields for this.

hoschi ( 2017-02-28 11:01:23 +0200 )edit

My calendar provider, as to my knowledge most, offers a very limited palette of colors chosen suit the light background on their own website. Since SFOS has a dark background, it really needs to be overridable, whether the server defines and communicates the color or not.

otsaloma ( 2017-02-28 22:57:47 +0200 )edit

0

answered 2017-03-17 17:01:09 +0200

4140 ●53 ●78 ●78

Even worse:
Newly created events get also lost. Just create it, wait a minute and it's gone. The calender-app is broken.

0

answered 2017-03-23 18:12:16 +0200

4140 ●53 ●78 ●78

Both issues seems to be fixed with 2.1.0.10 Thanks