I can confirm this bug, it's still active in 2.12.2-2 from current testing. Bug tracking system claims that this bug will be archived in 2 days - I this shouldn't happen since it's not yet fixed... Regards, Niko