On Fri, 2009-09-18 at 15:11 +1000, Rodd Clarkson wrote: > On Wed, 2009-09-16 at 21:15 +1000, Rodd Clarkson wrote: > > 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. > > 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? Yeah. Likely a kernel bug. Try running something like evtest on the pointer device after resume and see if you get events at all: http://people.freedesktop.org/~ajax/evtest.c If you get events that way, then X is confused; if you don't, then the kernel driver is confused. - ajax
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
