← Back to team overview

kernel-packages team mailing list archive

[Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

 

Doug, you added the tag 'kernel-fixed-upstream' but I don't think we
have hard evidence of that at this point.  Was your tagging based only
on Viktor's reports that it hasn't happened (yet) on a 4.6 kernel, or is
there more information elsewhere?

Viktor, your result with 4.6 is promising!  However, since this problem
is known to "come and go" it is also possible that code has just moved
around such that its just not manifesting in your current 4.6 kernel
build you currently (but could reappear in some future build of 4.6).

I do see one potentially interesting fix in 4.6 (50220de HID: core:
prevent out-of-bound reading).  I'm going to produce a test kernel with
just that fix backported on top of Xenial 4.4.0-22.40 (which I've seen
manifest the problem), and will post that here for further testing.

** Changed in: linux (Ubuntu)
     Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu)
   Importance: Medium => High

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
     Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Wily)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1579190

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep pressing key 5.
  It mostly happens when I leave the computer alone for some time, but sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably kernel related."

  Here is where most of the people are complaining:
  https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
  ⎜   ↳ Logitech K520                           	id=10	[slave  pointer  (2)]
  ⎜   ↳ Logitech M310/M310t                     	id=11	[slave  pointer  (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick           	id=15	[slave  pointer  (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPad        	id=14	[slave  pointer  (2)]
  ⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
      ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
      ↳ Integrated_Webcam_HD                    	id=12	[slave  keyboard (3)]
      ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
      ↳ Video Bus                               	id=7	[slave  keyboard (3)]
      ↳ Power Button                            	id=6	[slave  keyboard (3)]
      ↳ AT Translated Set 2 keyboard            	id=13	[slave  keyboard (3)]
      ↳ Power Button                            	id=8	[slave  keyboard (3)]
      ↳ DELL Wireless hotkeys                   	id=16	[slave  keyboard (3)]
      ↳ Dell WMI hotkeys                        	id=17	[slave  keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
      device: 10 (10)
      detail: 14
      flags:
      root: 449.00/427.00
      event: 449.00/427.00
      buttons:
      modifiers: locked 0x10 latched 0 base 0 effective: 0x10
      group: locked 0 latched 0 base 0 effective: 0
      valuators:
      windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
       property: 308 'Synaptics Off'
       changed: modified
  EVENT type 2 (KeyPress)
      device: 10 (10)
      detail: 14
      flags: repeat
      root: 449.00/427.00
      event: 449.00/427.00
      buttons:
      modifiers: locked 0x10 latched 0 base 0 effective: 0x10
      group: locked 0 latched 0 base 0 effective: 0
      valuators:
      windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
      device: 10 (10)
      detail: 14
      flags: repeat
      root: 449.00/427.00
      event: 449.00/427.00
      buttons:
      modifiers: locked 0x10 latched 0 base 0 effective: 0x10
      group: locked 0 latched 0 base 0 effective: 0
      valuators:
      windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
      device: 10 (10)
      detail: 14
      flags: repeat
      root: 449.00/427.00
      event: 449.00/427.00
      buttons:
      modifiers: locked 0x10 latched 0 base 0 effective: 0x10
      group: locked 0 latched 0 base 0 effective: 0
      valuators:
      windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
      device: 10 (10)
      detail: 14
      flags: repeat
      root: 449.00/427.00
      event: 449.00/427.00
      buttons:
      modifiers: locked 0x10 latched 0 base 0 effective: 0x10
      group: locked 0 latched 0 base 0 effective: 0
      valuators:
      windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
      device: 10 (10)
      detail: 14
      flags: repeat
      root: 449.00/427.00
      event: 449.00/427.00
      buttons:
      modifiers: locked 0x10 latched 0 base 0 effective: 0x10
      group: locked 0 latched 0 base 0 effective: 0
      valuators:
      windows: root 0xf6 event 0xf6 child 0x36000f8
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.21.22
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  viktor     2133 F.... pulseaudio
   /dev/snd/controlC0:  viktor     2133 F.... pulseaudio
  CurrentDesktop: GNOME
  Date: Fri May  6 20:45:07 2016
  HibernationDevice: RESUME=UUID=67c8171e-474f-4bdb-a2c8-22aead3fb294
  MachineType: Dell Inc. Latitude E5550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/system_vg-root_lv ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware                            1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0JPRM5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0JPRM5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579190/+subscriptions


References