I have upgraded to 2.2.1 and this problem no longer occurs.

Reply via email to