Right Alt key
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Just recently I started a switch from the default Mate DE to DWM from suckless.org. Since the Alt key is used a lot, I started using both Alt keys. When I used the right Alt key with any combination, my computer shutdown. I thought this might be an issue with my dwm configuration but I was not able to find the issue. Then I thought about testing in Mate and I was so surprised to find out sometimes right Alt + any other key would bring the shutdown dialog. Do any of you have an idea of what the issue could be?
Thank you for any help in advance.
I tried right Alt + a-z and 0-9, but never triggered shutdown. (deblobbed Debian sid with vanilla MATE)
> When I used the right Alt key with any combination, my computer
> shutdown. I thought this might be an issue with my dwm configuration
> but I was not able to find the issue. Then I thought about testing in
> Mate and I was so surprised to find out sometimes right Alt + any
> other key would bring the shutdown dialog.
Weird. Open up a terminal, run
$ xev
and make sure that the white window that pops up is focused. Any
keyboard events while this window is focused will be printed to the
terminal. You'll notice that each key press or release prints a block of
text, in which you should see "keycode" followed by a number. What
keycode do you get when you press Right Alt?
Here is what I could get:
FocusIn event, serial 40, synthetic NO, window 0x3c00001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyPress event, serial 40, synthetic NO, window 0x3c00001,
root 0xe4, subw 0x0, time 224489, (59,-14), root:(1109,269),
state 0x10, keycode 108 (keysym 0xffea, Alt_R), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
MappingNotify event, serial 40, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
FocusOut event, serial 40, synthetic NO, window 0x3c00001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 40, synthetic NO, window 0x3c00001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys: 91 0 0 0 0 0 0 0 0 0 0 0 0 16 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MappingNotify event, serial 41, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
KeyRelease event, serial 41, synthetic NO, window 0x3c00001,
root 0xe4, subw 0x0, time 225264, (59,-14), root:(1109,269),
state 0x18, keycode 108 (keysym 0xffea, Alt_R), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
FocusOut event, serial 42, synthetic NO, window 0x3c00001,
mode NotifyNormal, detail NotifyNonlinear
FocusIn event, serial 42, synthetic NO, window 0x3c00001,
mode NotifyNormal, detail NotifyNonlinear
> state 0x10, keycode 108 (keysym 0xffea, Alt_R), same_screen YES,
Okay, the operating system really is receiving an "Alt" and not
something weird. Do you have another keyboard, like USB or bluetooth,
that you could connect in order to verify that the problem only happens
with your laptop keyboard? It could be a hardware problem.
Once connected to a USB keyboard, the problem doesn't show up, while with the laptop keyboard, it actually shuts down. I guess I have to check that keyboard.
Thank you for the support cmonk
> Once connected to a USB keyboard, the problem doesn't show up, while
> with the laptop keyboard, it actually shuts down.
Sounds like a hardware problem then. If the laptop is under warranty
then see if the vendor can replace the keyboard. Otherwise, do an
Invidious[1] search for your laptop model and "keyboard replacement" to
get a sense of how hard it would be to replace yourself.
Thank you for your advice, I have a corebooted thinkpad X220 so I can order a keyboard on ebay and replace it.
- Vous devez vous identifier ou créer un compte pour écrire des commentaires