After testing I can confirm the patch I mentioned before has been
applied and the bug fixed in version 2:1.19.5-1
-- 
Eric

Reply via email to