I confirmed that this bug continues to exist in version 1:10.0p1-5, currently in testing.

--
JP

Reply via email to