qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1568621] [NEW] input-linux misdetects Logitech keyboar


From: William
Subject: [Qemu-devel] [Bug 1568621] [NEW] input-linux misdetects Logitech keyboard as a mouse
Date: Sun, 10 Apr 2016 22:23:30 -0000

Public bug reported:

The new input-linux.c code misdetects my Logitech K350 keyboard as a
mouse.  The bug is in the input_linux_complete function.  The evdev for
this keyboard returns an "evtmap" with the EV_REL bit set.  Full evtmap
is 0x0012001F.  Using a different keyboard everything works as intended,
so my configuration and setup are correct otherwise.


Suggestion:

I suggest adding an object property called something like "type" where
the user can specify what the device type is manually.  This K350
keyboard shows that "evtmap" cannot be used to reliably detect the
device type.  Since specifying the device type manually is not an undue
burden, perhaps it should be a required option and there should be no
autodetection?


System:

Arch linux, using qemu-git AUR package installed 20160409.


Command line:

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=none /usr/sbin/qemu-system-x86_64 -name win10,debug-
threads=on -S -machine pc-i440fx-2.4,accel=kvm,usb=off,vmport=off -cpu
host,kvm=off -drive file=/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-
efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive
file=/var/lib/libvirt/qemu/nvram/win10_VARS.fd,if=pflash,format=raw,unit=1
-m 8196 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid
58623778-9d9d-4d30-8ec0-b37e12a30fdc -nographic -no-user-config
-nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-17-win10/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard
-no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-
ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-
uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6
-device ich9-usb-
uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9
-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -drive
file=/var/lib/libvirt/images/ISOs/Win10_1511_English_x64.iso,format=raw,if=none,id
=drive-ide0-0-1,readonly=on -device ide-cd,bus=ide.0,unit=1,drive=drive-
ide0-0-1,id=ide0-0-1 -drive file=/var/lib/libvirt/images/ISOs/virtio-
win-0.1.112.iso,format=raw,if=none,id=drive-ide0-1-0,readonly=on -device
ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
file=/dev/sda,format=raw,if=none,id=drive-virtio-disk1 -device virtio-
blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk1,id=virtio-
disk1,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:70:8a:db,bus=pci.0,addr=0x3
-netdev tap,fd=28,id=hostnet1 -device
rtl8139,netdev=hostnet1,id=net1,mac=d4:be:d9:56:2e:35,bus=pci.0,addr=0x9
-device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-
duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device vfio-
pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x2 -device virtio-balloon-
pci,id=balloon0,bus=pci.0,addr=0x7 -object input-
linux,id=kbd1,evdev=/dev/input/event19,grab_all=on -object input-
linux,id=kbb2,evdev=/dev/input/event2 -msg timestamp=on

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1568621

Title:
  input-linux misdetects Logitech keyboard as a mouse

Status in QEMU:
  New

Bug description:
  The new input-linux.c code misdetects my Logitech K350 keyboard as a
  mouse.  The bug is in the input_linux_complete function.  The evdev
  for this keyboard returns an "evtmap" with the EV_REL bit set.  Full
  evtmap is 0x0012001F.  Using a different keyboard everything works as
  intended, so my configuration and setup are correct otherwise.

  
  Suggestion:

  I suggest adding an object property called something like "type" where
  the user can specify what the device type is manually.  This K350
  keyboard shows that "evtmap" cannot be used to reliably detect the
  device type.  Since specifying the device type manually is not an
  undue burden, perhaps it should be a required option and there should
  be no autodetection?

  
  System:

  Arch linux, using qemu-git AUR package installed 20160409.

  
  Command line:

  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
  QEMU_AUDIO_DRV=none /usr/sbin/qemu-system-x86_64 -name win10,debug-
  threads=on -S -machine pc-i440fx-2.4,accel=kvm,usb=off,vmport=off -cpu
  host,kvm=off -drive file=/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-
  efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive
  file=/var/lib/libvirt/qemu/nvram/win10_VARS.fd,if=pflash,format=raw,unit=1
  -m 8196 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid
  58623778-9d9d-4d30-8ec0-b37e12a30fdc -nographic -no-user-config
  -nodefaults -chardev
  
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-17-win10/monitor.sock,server,nowait
  -mon chardev=charmonitor,id=monitor,mode=control -rtc
  base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard
  -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
  PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-
  ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-
  uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6
  -device ich9-usb-
  uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9
  -usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -drive
  
file=/var/lib/libvirt/images/ISOs/Win10_1511_English_x64.iso,format=raw,if=none,id
  =drive-ide0-0-1,readonly=on -device ide-cd,bus=ide.0,unit=1,drive
  =drive-ide0-0-1,id=ide0-0-1 -drive file=/var/lib/libvirt/images/ISOs
  /virtio-win-0.1.112.iso,format=raw,if=none,id=drive-
  ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-
  ide0-1-0,id=ide0-1-0 -drive file=/dev/sda,format=raw,if=none,id=drive-
  virtio-disk1 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive
  =drive-virtio-disk1,id=virtio-disk1,bootindex=1 -netdev
  tap,fd=26,id=hostnet0 -device
  rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:70:8a:db,bus=pci.0,addr=0x3
  -netdev tap,fd=28,id=hostnet1 -device
  rtl8139,netdev=hostnet1,id=net1,mac=d4:be:d9:56:2e:35,bus=pci.0,addr=0x9
  -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-
  duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device vfio-
  pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x2 -device virtio-
  balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -object input-
  linux,id=kbd1,evdev=/dev/input/event19,grab_all=on -object input-
  linux,id=kbb2,evdev=/dev/input/event2 -msg timestamp=on

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1568621/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]