Hi,

I can confirm that downgrading to evolution 3.36.4-2 and related
packages (from snapshot 20201117T032431Z) avoids the problem and
restores normal/previous behavior.

Reply via email to