Hello,

I can't reproducre this bug with LO 5.4.1-1.

Seems fixed.

Regards,

-- 
Stéphane Aulery

Reply via email to