On Wed, 2009-09-16 at 21:15 +1000, Rodd Clarkson wrote:
You could verify this with "DISPLAY=:0 xinput list" when the mouse pointer stops. If you don't see the bluetooth mouse in the list, then the kernel is refusing to re-plug it right. If you _do_ see the mouse in the list, then X is confused somewhere.
Does keyboard navigation still work when this happens? Does alt-tab switch windows, etc.
I'll give this a try when I next have a lock-up.
I'm pretty sure that this problem only occurs before I've cycled through a suspend-resume.
I suspect bluetooth issues because the bluetooth icon appears until I do the suspend-resume cycle and then the icon doesn't appear and bluetooth doesn't work (but the mouse does).
Keyboard navigation still works, and I can switch to a VT too.
Ajax
Alright, I've had this happen after a suspend-resume cycle, and it appears that it's not bluetooth related as the output of xinput is the same before as after.
Do you want me to file a bug on this and then work from there?
Rodd