In my previous comment, please s/less mouse-like/more mouse-like/ .
I have managed to make the lshal output look convincingly mouse-like by creating a file /etc/hal/fdi/information/00kensington.fdi which removes 'input.keys' and 'button' from the 'info.capabilities' like, thus:
However, evdev still thinks it's a keyboard; the Xorg.0.log output remains as per the original report.
I'm still not able to decide with confidence if this is a problem in HAL, evdev or even the kernel HID driver (from which I assume HAL gets device capability info by way of sysfs). Apologies to the evdev team if I've reported this to the wrong place.
In my previous comment, please s/less mouse-like/more mouse-like/ .
I have managed to make the lshal output look convincingly mouse-like by creating a file /etc/hal/ fdi/information /00kensington. fdi which removes 'input.keys' and 'button' from the 'info.capabilities' like, thus:
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> capabilities" type="strlist" >input. keys</remove> capabilities" type="strlist" >button< /remove>
<deviceinfo version="0.2">
<device>
<match key="info.product" string="HID 0d62:1000">
<remove key="info.
<remove key="info.
</match>
</device>
</deviceinfo>
However, evdev still thinks it's a keyboard; the Xorg.0.log output remains as per the original report.
I'm still not able to decide with confidence if this is a problem in HAL, evdev or even the kernel HID driver (from which I assume HAL gets device capability info by way of sysfs). Apologies to the evdev team if I've reported this to the wrong place.