Can confirm that this bug still exists in version 3.2.5-1.3+b2

Reply via email to