From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Cc: as-users@afterstep.org, xpert@xfree86.org
Subject: 2.5.x / keyboard goes whacky (linux)
Date: Sat, 30 Nov 2002 14:40:10 +1100 [thread overview]
Message-ID: <20021130034010.GC612@zip.com.au> (raw)
Sometimes when I use the windows key with the arrow keys the keyboard
goes whacky and I can nolonger type anything in. It used to be that I
could switch to console and then back to X would fix it but not this
time. This happens when I'm in X, using afterstep as the windowmanager
where I define the left windows key + arrows as pointer movement.
As far as whackyness goes, the capslock key no longer works and it's as
if every keypress generates 2 bytes (as if the kboard went into
unicode).
I looked in dmesg and there's only 1 line of clue:
atkbd.c: Unknown key (set 2, scancode 0x1d0, on isa0060/serio0) pressed.
X version: 4.1.0 (debian 3.0)
afterstep: stable-cvs20020826
Only recourse I have now is a reboot.
--
All people are equal,
But some are more equal then others.
- George W. Bush Jr, President of the United States
September 21, 2002 (Abridged version of security speech)
reply other threads:[~2002-11-30 3:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021130034010.GC612@zip.com.au \
--to=cat@zip.com.au \
--cc=as-users@afterstep.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xpert@xfree86.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome