The reason evdev is confused is that, apparently, ioctl(fd, EVIOCGBIT, EV_KEY, ...) is returning capabilities that don't match the actual device in question. (Come to think of it, EV_ABS coming back with something for a mouse is odd, too.)
I'm not sure if the right solution is to add something to the quirks list in the kernel usbhid stuff, and/or if a workaround in evdev would be useful. Would something like the attached help? (Still trying to figure out how to build it myself so I can test...) ** Attachment added: "Possible workaround for evdev 2.1.1 - untested!" http://launchpadlibrarian.net/22056076/evdev.patch -- kensington pocket mouse model #72237 USB 0d62:1000 not working under 8.10 https://bugs.launchpad.net/bugs/325581 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
