This bug is marked as fix-released. But the current 2.6.24-18 kernel does not fix it.
Apparently it is 2.6.25 that fixes the bug (hopefully). So the fix is released only for the still not existing intrepid release.
Please do actually release the fix for hardy users.
This bug is marked as fix-released. But the current 2.6.24-18 kernel does not fix it.
Apparently it is 2.6.25 that fixes the bug (hopefully). So the fix is released only for the still not existing intrepid release.
Please do actually release the fix for hardy users.