Comment 273 for bug 204996

This bug was originally reported for hardy.
Indeed it was reported on March 22 when hardy was not even shipped yet. At that time development on intrepid was not even open.

How does it come that it is now tracked as an intrepid bug?
The fact that there is a fix available for intrepid does not mean that there is a fix available for hardy. In fact there is not.

Please, track this bug as an hardy bug and leave it open as it should. Do not treat this as an intrepid bug that appears to be solved: it is a trick to do so and it is just confusing for users looking for fixes.

Please allow everybody to easily see that there is a very critical open bug for hardy for which _no_ fix is available (yet) as fixes will need to be identified and backported from the intrepid kernel (admitting that it is possible and practical to do so).