This was reported against 1.3.1, however 1.4.2 is available in oldstable. Can
you confirm if this issue is still present? If so, would you also be able to
also check against the latest git revision (many bug fixes are not released)?

-- 
Michael Lustfield

Reply via email to