I just re-tested this machine with the packages from experimental (4.3.0-0pre1v5), and this bug is fixed in that version. Regards, Kevin.