the libical upgrade on bug #368508 should workaround the bug, could you give it a try and comment on the other bug to say if it makes a difference for your issue?
the libical upgrade on bug #368508 should workaround the bug, could you give it a try and comment on the other bug to say if it makes a difference for your issue?