Bug resolved when upgrading evolution to 3.26.3-1 and/or evolution-data-server to 3.26.3-4 when they entered testing.

So problem resolved.

/Martin

Reply via email to