|Summary:||keyboard randomly puts a ` backtick on the screen.|
|Product:||[Retired] Red Hat Linux||Reporter:||jkoyle|
|Component:||kbd||Assignee:||Jeff Johnson <jbj>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1999-03-30 16:47:36 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description jkoyle 1999-02-12 01:20:03 UTC
keyboard randomly puts a ` backtick on the screen. I've noticed this with Caldera v1.2, v1.3 RedHat v5.2, and SUSE v5.3. This only happens on a DELL computer system, and I've had problems with it on multiple different systems so I'm sure it isn't just one box. I thought you might find it interesting since you just signed DELL on.
Comment 1 ajoas 1999-03-03 22:32:59 UTC
I've experienced the same problem on a DELL OptiPlex GX1 (Dell QuietKey, Model #SK-1000REW) since upgrading from 5.1 to 5.2. Additional symptom is that (far less frequently than the backtick problem), the entire keyboard stops responding. LEDs don't even light up when you hit capslock, numlock, etc. Keyboard starts responding again if you unplug and replug the keyboard cable from the jack (although this kills the repeat rate of the keyboard). Another coworker here has the exact same situation/history/symptoms. ------- Email Received From John Koyle <email@example.com> 03/03/99 17:35 -------
Comment 2 Jeff Johnson 1999-03-30 16:47:59 UTC
This is a hardware problem. Kbd is a software package. The two are only distantly related.
Comment 3 Dax Kelson 2003-06-06 18:23:46 UTC
I'm teaching a Red Hat Linux 9 class in a room full of Dell OptiPlex GX110 computers with the Dell QuietKey keyboard model SK-1000REW and the students have all week been experiencing "attack of the backtics". We tried upgrading the BIOS from A02 to A09 with no effect. A student brought in a USB keyboard, and used it all day with no problems. Maybe this should be filled under "kernel", it doesn't happen in any version of Windows. Thought folks might want to know this bug was still out there. :)