Your message dated Mon, 21 May 2012 13:47:31 +0800
with message-id <874nrajdak....@jidanni.org>
and subject line Re: Bug#648797: xinput cannot disable built-in keyboards, only
USB keyboards
has caused the Debian Bug report #648797,
regarding xinput cannot disable built-in keyboards, only USB keyboards
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
648797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xinput
Version: 1.5.3-1
File: /usr/bin/xinput
We find that there is no way to disable the keyboard.
E.g., if one has a defective builtin keyboard that types phantom characters and
wishes to turn it off in lieu of a USB keyboard.
One finds one can enable and disable USB keyboards fine, but not
built-in keyboards!
$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech Trackball id=11 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=13 [slave pointer (2)]
⎜ ↳ Ever Electronics Corp. Usb KeyBoard id=9 [slave pointer
(2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=14 [slave keyboard (3)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
↳ Ever Electronics Corp. Usb KeyBoard id=10 [slave
keyboard (3)]
$ xinput set-prop 10 "Device Enabled" 0 # Works fine, but:
$ xinput set-prop 12 "Device Enabled" 0 # Works but sends infinite RET (0x0D) to
the terminal!
(One also notices that the latter does not leave any trace in Xorg.0.log.
The former causes two entries, as it comes back, but just disabled. And
no entries when reabling with "1".)
Anyway, one ends up using
# cat /usr/share/X11/xorg.conf.d/66-jidanni.conf
Section "InputClass"
Identifier "Bypassed Busted Keyboard"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event0"
Option "Ignore" "on"
EndSection
--- End Message ---
--- Begin Message ---
OK Thanks seems fixed now.
--- End Message ---
