key is repeated, but keyboard does not send scancodessssssss

[Weinga-Unity]

I have found the repeat-key and stuck-key issue in different bug-reports but no working solution.
My problem is, that sometimes a key is stuck within software and the character is printed in the rate configuredddddddd for the keyboard.

catch of KeyPress event, KeyRelease event sequence with "l" with xev, "f" is pressed to stop sequence:
ccccccccc
KeyPress event, serial 37, synthetic NO, window 0x2e00001,
    root 0x7e, subw 0x0, time 632900, (38,-8), root:(632,311),
    state 0x100, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XmbLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2e00001,
    root 0x7e, subw 0x0, time 633234, (38,-8), root:(632,311),
    state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x2e00001,
    root 0x7e, subw 0x0, time 633234, (38,-8), root:(632,311),
    state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XmbLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2e00001,
    root 0x7e, subw 0x0, time 633481, (38,-8), root:(632,311),
    state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES,
    XLookupString gives 1 bytes: (6c) "l"
    XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x2e00001,
    root 0x7e, subw 0x0, time 633500, (38,-8), root:(632,311),
    state 0x0, keycode 41 (keysym 0x66, f), same_screen YES,
    XLookupString gives 1 bytes: (66) "f"
    XmbLookupString gives 1 bytes: (66) "f"
    XFilterEvent returns: False
================================================================

showkey does not print anyyyyy scancodes:
============================================
~$ sudo showkey -s
KB-Modus war ?UNBEKANNT?
[ Wenn Sie das unter X probieren, muss es nicht funktionieren,
  da der X Server ebenfalls von /dev/console liest. ]

Drücken Sie eine Taste (Programmende 10 s nach dem letzten Tastendruck)...
0x9c
0x20
0xa0
......
0x20 0x21 0xa0 0x21 0xa1
0x31
0xb1
0x2d 0x2f 0xad 0xaf
0x24 0x26 0xa4 0x26 << "0x26"=<l> pressed, "0xa6"=<l> released
0xa6 0x21 0xa1 << "0x21"=<f> pressed, "0xa1"=<f> released
==========================================

===========
uname -or
3.16.0-30-generic GNU/Linux

Description: Ubuntu 14.04.2 LTS
Release: 14.04

============

Netbook Gigabyte T1005 CPU Intel Atom N570
---
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: trusty
DistroRelease: Ubuntu 14.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:b100]
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:b100]
InstallationDate: Installed on 2015-05-01 (36 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:1249): WARNING **: Failed to load user image: Datei »/home/klaus/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
 init: indicator-power-main-Prozess (1392) wurde von TERM-Signal beendet
 init: indicator-application-main-Prozess (1398) wurde mit dem Status 1 beendet
MachineType: GIGABYTE T1005M/P
Package: xorg 1:7.7+1ubuntu8.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic root=/dev/mapper/xubuntu--vg-root ro clocksource=acpi_pm quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Tags: trusty ubuntu
Uname: Linux 3.16.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/30/2010
dmi.bios.vendor: GIGABYTE
dmi.bios.version: F09
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: T1005M/P
dmi.board.vendor: GIGABYTE
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnGIGABYTE:bvrF09:bd08/30/2010:svnGIGABYTE:pnT1005M/P:pvrF09:rvnGIGABYTE:rnT1005M/P:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: T1005M/P
dmi.product.version: F09
dmi.sys.vendor: GIGABYTE
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Jun 7 20:42:49 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 7301
 vendor CPT
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

[Weinga-Unity (snaky-1)]

Additional Information:

I have tested a Fedora distribution too. Same Problem.

With Windows XP it works perfect.

[Weinga-Unity (snaky-1)]

Shall i execute after an occurance of a stuck key or just after booting?

[Weinga-Unity (snaky-1)]

I meen execute the apport-collect command.

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

i did apport information a 2nd one because if had the feeling that the first run was not working correct. But at the end the same postings.

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

apport information

[Weinga-Unity (snaky-1)]

I hope this are the correct debugging informations.
For your information: some minutes before the debug dump the key up (or down, i'm not shure any more) stucked again.

[Weinga-Unity (snaky-1)]

Within the BIOS Main Menu following informations are visible:

Product Name: T1005M/P
BIOS Version: F09
BIOS Date: 06/15/2011
EC Version: F14

[penalvch (penalvch)]

Weinga-Unity, to see if this is already fixed in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Weinga-Unity (snaky-1)]

Same Problem with "wily" version.
See Screenshot.

[Weinga-Unity (snaky-1)]

Hallo Christopher,
do you have some news or ideas here or why this issue is caused?

[penalvch (penalvch)]

Weinga-Unity, the last time I had a similar (not the same) problem, I updated my BIOS which fixed it.

Despite this, as this is marked Triaged, it is ready for a developer to review and fix as applicable.

While waiting, it wouldn't hurt to test the latest mainline kernel as outlined in https://wiki.ubuntu.com/Kernel/MainlineBuilds .

[Weinga-Unity (snaky-1)]

I did additional testing with unmodified kernel. Mainline kernel test will be done in the next days.

Within a real termianl Ctrl+Alt+F2 i was not able to reproduce the failure. I used internal keyboard of my Gigabyte T1005 and an external USB-Keyboard. I recognized different delay and repeat-key behaviour of USB- and internal keyboard.

Within a "gui"-terminal of xfce i reproduced the failure with the internal keyboard multiple times. With the external USB keyboard i was not able to reproduce it (but no proof that it will not happen).

Maybe this information will help.

[Weinga-Unity (snaky-1)]

So, i got 3.14.4-031404-generic GNU/Linux installed.
The same issue.

[Weinga-Unity (snaky-1)]

As discribed in my first post xev reports repeat key, showkey nothing is repeated.
So which source files of xservers are involved and use the same functions of showkey and will create the xevents?

Im interessted in reviewing the code and (if possible) to add debug informations.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.