Hello everybody,

I have a really strange problem with my keyboard which I've been dealing with for a few weeks. I've searched the web and I haven't found anything about it.

Undermost circumstances, my keyboards behaves normally. The problem comes when I run certain commandline applications, such as "irb" (ruby interpreter), or "dbtool". When running these console applications, the letter "e" won't register.

This doesn't occur for all console apps. VIM works fine.

Also, "E" seems to work, but "e" does not.

When I cut and paste strings that contain "e", the "e"s are stripped out. For instance. If I cut and paste "Hello world", I get back "Hllo world".

I've even tried importing someone else's keymap from another computer with the same setup, but that didn't seem to help.

I'm running RHEL3 on an Optiplex 740 with and AMD 64 Processor. 'uname -r' returns "2.4.21-50a1smp". Please help!!!

Dave

what is your current keyboard?
PS/2 or USB, part of a KVM?
compressed like on a laptop or the standard type?
what happens if you put a 2nd keyboard on the system?

The Keyboard is called "Microsoft Natural Keyboard Elite". It's USB, but I'm using a PS/2 adapter to connect to a Linksys KVM. Here's a link to the KVM:
http://www.linksys.com/servlet/Satel...VisitorWrapper

Correction. My mouse is using USB to PS/2 adapter to connect to the KVM. The keyboard is using PS/2 to connect to the KVM.

I tried connecting a standard Dell keyboard to the KVM instead, and that didn't seem to work either.

Problem solved. After troubling shooting the hardware, We noticed that when we changed from z-shell to bash, the letter 'e' didn't work either. However, it was outputting to the display just fine. So, we thought that it had something to do with the input buffer, and not the output buffer.

Next, I had a friend login to the computer to attempt to replicate the problem. He wasn't able to do this, and we concluded that it had something to do with my personal configuration settings.

So, after moving all the config files out of the startup directory, I was finally able to recover the missing 'e' key. I then proceeded to incrementally add each config file back, one by one, and I finally found the guilty culprit. It was a file called '.inputrc'. I'm not sure what that file did, but I deleted it, and now everything is working.

Thanks for helping.

Dave

I would check the security of my system if I were you. This is just the type of PITA signature a hacker would leave behind(yes there are ones that are relatively friendly).