somewhat work-around for logitech keyboard error "unknown e1 escape sequence"
From: DrTebi (drtebi_at_yahoo.com)
Date: 20 Apr 2004 15:44:14 -0700
I have googled quite a bit, and it seems nobody had a solution for the
strange error that some people experience with Logitech keyboards.
Usually this was the problem (as posted by email@example.com):
I recently purchased a Logitech MX Duo wireless keyboard/mouse for use
with my Linux and Windows 2000 systems, through a KVM switch.
Everything was fine at first, then after a couple days, my Linux
began acting funny. Whenever I press the backspace key, about a
later, a 'q' appears on the screen. This happens in all applications
X. When in another virtual console, the 'q' will not print, but the
following message will:
keyboard: unknown e1 escape sequence
keyboard: unrecognized scancode (65) - ignored
I am also using BeOS besides Linux, and had the same problem there.
Believe it or not, this is what I just found out:
When pressing the "F-Lock" key after logging in, _that_ problem
disappears. Well, as I named this post a "somewhat work-around", there
is a downside to this: The F keys won't work anymore.
OK, this may sound like a lame solution, but I am posting this because
I believe it may help lots of people who have gone nuts when writing
email etc., not being able to use the backspace key is quite a pain.
So just hit the F-Lock key, the ghost-writing of logitech's keyboard
will stop, and when you need the F-Keys badly again, hit the F-Lock
Hope this helps some people ;)
qqqqqqq (just kidding)