Bug#426286: marked as done (Erratic Caps lock and Ctrl key behavior)
Your message dated Wed, 08 Aug 2007 22:00:47 +0200
with message-id <46BA20EF.6030807@ens-lyon.org>
and subject line Bug#426286: Erratic Caps lock and Ctrl key behavior
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: xserver-xorg-input-kbd
Version: 1:1.1.0-4
On a Thinkpad X40 keyboard - tried with both a standard american English
keyboard and german Deutsch one - there is something extremely bizarre
going on that seem to involve Caps Lock and Ctrl keys. Intermittently
the Caps lock seems to get activated even though the Caps Lock LCD
indicator light is off. Normally to fix it, shift + a character must be
pressed, after which releasing the Shift key will return keys to
lowercase.
More troubling is that from time to time somehow the Ctrl key seems to
get stuck on. This can be extremely dangerous as subsequent keypresses
are now Ctrl-key combinations and have the potential to kill processes,
shut down terminals, etc. I still do not know how Ctrl key gets
untoggled in this state, but it is not by pressing the Ctrl key.
When this problem initially occurred I thought perhaps there was some
severe problem with the keyboard. But changing the keyboard made no
difference. I also completely re-installed Debian but the problem
persisted. The problem does not, however, occur under non-Debian.
--- End Message ---
--- Begin Message ---
Version: 1:1.2.0-1+1.2.1
Daniel O'Neill wrote:
> So wrote Brice Goglin on Wednesday, 8 August 2007:
>
>> Hi,
>>
>> Does this bug still happen with latest xserver-xorg-input-kbd (1.2.0 in
>> testing) and xserver-xorg-core (2:1.3.0.0.dfsg-11) ?
>>
>> Brice
>>
>
>
> I have not noticed the problem in a while. I guess this can be closed.
> Thank you for following-up!
>
And thanks for replying quickly!
Marking as fixed in xserver-xorg-input-kbd since it is likely the one
fixing this issue.
Brice
--- End Message ---
Reply to: