I can confirm that this bug is still present in 2.6.15-26-386, although the workarounds shown above make it less severe.
I can confirm that this bug is still present in
2.6.15-26-386, although the workarounds shown above make it less severe.