On Tue, Mar 20, 2018 at 6:15 AM, Salvatore Bonaccorso wrote:
> Can you confirm that before we would proceed to mark it as fixed with
> 4.15.11-1?

I have not seen it since updating, so I think it can be considered fixed.

Best wishes,
Mike

Reply via email to