I confirm that this issue has been fixed (along with bug 1062932).  It
should be marked as done.

Reply via email to