The latest package seems to have fixed this bug, or at the very least it's 
fixed on the box that I reported this bug from.

If no one else has seen this bug recently then I'm happy for it to be 
closed.

Thanks for the great work guys.

Grahame

Reply via email to