SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Since yesterday it seems that whenever I press the left-alt key a signal for key-up is also sent. It happens in X but also in the ttyX consoles. I'm very confused by this.
This is the output from xev after pressing and releasing the alt key:
Code:
KeyPress event, serial 37, synthetic NO, window 0x1c00001,
root 0x266, subw 0x0, time 1526064, (169,-14), root:(800,342),
state 0x0, keycode 111 (keysym 0xff52, Up), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 37, synthetic NO, window 0x1c00001,
root 0x266, subw 0x0, time 1526066, (169,-14), root:(800,342),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 37, synthetic NO, window 0x1c00001,
root 0x266, subw 0x0, time 1526180, (169,-14), root:(800,342),
state 0x8, keycode 111 (keysym 0xff52, Up), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 37, synthetic NO, window 0x1c00001,
root 0x266, subw 0x0, time 1526184, (169,-14), root:(800,342),
state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
The keyboard itself is an IBM Model M, connect to ps/2.
That is most likely the culprit. I own the same model. One day I slipped a little bit of a drink into it - it was just a little bit, but the liquid got stuck between the two circuit foils and caused the backspace and the y key to connect to each other.
First, I tried to let it dry out - that did not do the trick.
But the Model M is very robust, so I took it apart, took out the controller board and showered everything else for 5 minutes (yes, in my actual shower - as it was already "broken" I had nothing to lose).
After that, I let it dry in front of a fan for a day - it works better than before.
I did not have the right tools to open the keyboard, but putting some water around the arrow keys and aiming a hairdryer at it did the trick.
Thanks again Schmatzler, I thought this was a software problem which got me baffled.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.