I have tried to reproduce this bug using the 2.6.24-19-generic kernel from the Main repo (version 2.6.24-19.36).
I could NOT reproduce the bug. Have I missed a step or a precondition that causes the bug?
If not, do we need more people to confirm this before we can mark the report Fix Released?
I have tried to reproduce this bug using the 2.6.24-19-generic kernel from the Main repo (version 2.6.24-19.36).
I could NOT reproduce the bug. Have I missed a step or a precondition that causes the bug?
If not, do we need more people to confirm this before we can mark the report Fix Released?