Ok, I understand.
So I guess, we can leave it as-is then. The bug is still present in 4.0.0~beta3, currently shipped in noble, but is fixed by e96fdc0f5b5aea78c7860e37e0ca149e9dac3480 / 1c7127d30d3388119a4f8293ae3ac093016356ea which is included in 4.0.0~beta4+
Ok, I understand.
So I guess, we can leave it as-is then. The bug is still present in 4.0.0~beta3, currently shipped in noble, but is fixed by e96fdc0f5b5aea7 8c7860e37e0ca14 9e9dac3480 / 1c7127d30d33881 19a4f8293ae3ac0 93016356ea which is included in 4.0.0~beta4+