<div dir="ltr">Sure:<br><br>/dev/input/event1<br> id : 046d:200a, USB, v273<br> phys : "usb-0000:00:14.0-14:2"<br> name : "Logitech K350"<br> : [ 261 codes ]<br> : (null)<br> : (null)<br> : (null)<br> : (null) (null) (null) (null) (null)<br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 11, 2016 at 12:35 AM, Gerd Hoffmann <span dir="ltr"><<a href="mailto:kraxel@redhat.com" target="_blank">kraxel@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On So, 2016-04-10 at 15:10 -0700, William Green wrote:<br>
> Looks like this is a bug with the input-linux. The function<br>
> "input_linux_complete" tries to detect what kind of input device the<br>
> given evdev device is by testing EVIOCGBIT(0, ...). My keyboard (a<br>
> Logitech K350) has the EV_REL bit set, and so input_linux_complete<br>
> sees it as a mouse. That explains my problems.<br>
<br>
</span>Can you mail the output of 'lsinput -vs1' ?<br>
<br>
thanks,<br>
Gerd<br>
<br>
PS: lsinput is here: <a href="https://www.kraxel.org/cgit/input/" rel="noreferrer" target="_blank">https://www.kraxel.org/cgit/input/</a><br>
</blockquote></div><br></div>