With the arrival of 2.2.1-3 in testing, can this be considered fixed
or will the issue need to stay open until that reaches the next
'release'?

 - Axel

Reply via email to