At some point my Windows (Super) key stopped working.
Trying the following doesn't produce any output when the super key is pressed:
$ xinput list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ xwayland-pointer:18 id=6 [slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:18 id=7 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ xwayland-keyboard:18 id=8 [slave keyboard (3)] $ xinput test 8
But pluggin my keyboard into my work laptop running windows it works fine.
Thanks, Richard
On Wed, 2021-09-01 at 10:40 -0500, Richard Shaw wrote:
At some point my Windows (Super) key stopped working.
Trying the following doesn't produce any output when the super key is pressed:
$ xinput list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ xwayland-pointer:18 id=6 [slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:18 id=7 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ xwayland-keyboard:18 id=8 [slave keyboard (3)] $ xinput test 8
But pluggin my keyboard into my work laptop running windows it works fine.
How about Xorg?
poc
On Wed, Sep 1, 2021 at 4:15 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Wed, 2021-09-01 at 10:40 -0500, Richard Shaw wrote:
At some point my Windows (Super) key stopped working.
Trying the following doesn't produce any output when the super key is pressed:
$ xinput list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ xwayland-pointer:18 id=6 [slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:18 id=7 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ xwayland-keyboard:18 id=8 [slave keyboard (3)] $ xinput test 8
But pluggin my keyboard into my work laptop running windows it works fine.
How about Xorg?
Nope, same result as wayland, nada.
Thanks, RIchard
On 9/1/21 8:40 AM, Richard Shaw wrote:
At some point my Windows (Super) key stopped working.
Trying the following doesn't produce any output when the super key is pressed:
$ xinput list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ xwayland-pointer:18 id=6 [slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:18 id=7 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ xwayland-keyboard:18 id=8 [slave keyboard (3)] $ xinput test 8
I don't see what you're trying to test here. That keyboard is going to be filtered. I actually can't get any output from that test when I try it, regardless of what keys. If you want to see if the keyboard is actually producing codes, then you need to use "evtest" instead. That gets you events at the kernel level.
On Wed, Sep 1, 2021 at 10:25 PM Samuel Sieb samuel@sieb.net wrote:
On 9/1/21 8:40 AM, Richard Shaw wrote:
At some point my Windows (Super) key stopped working.
Trying the following doesn't produce any output when the super key is pressed:
$ xinput list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ xwayland-pointer:18 id=6 [slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:18 id=7 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ xwayland-keyboard:18 id=8 [slave keyboard
(3)]
$ xinput test 8
I don't see what you're trying to test here. That keyboard is going to be filtered. I actually can't get any output from that test when I try it, regardless of what keys. If you want to see if the keyboard is actually producing codes, then you need to use "evtest" instead. gets you events at the kernel level.
Thanks, I was just trying whatever I found googling the problem. I did get output from every other key I tried other than Super.
Just tried evtest and all the keys I tried worked except for Super.
Thanks, Richard
On Thu, 2 Sep 2021 07:09:36 -0500 Richard Shaw hobbes1069@gmail.com wrote:
On Wed, Sep 1, 2021 at 10:25 PM Samuel Sieb samuel@sieb.net wrote:
On 9/1/21 8:40 AM, Richard Shaw wrote:
At some point my Windows (Super) key stopped working.
Trying the following doesn't produce any output when the super key is pressed:
I don't see what you're trying to test here. That keyboard is going to be filtered. I actually can't get any output from that test when I try it, regardless of what keys. If you want to see if the keyboard is actually producing codes, then you need to use "evtest" instead. gets you events at the kernel level.
Thanks, I was just trying whatever I found googling the problem. I did get output from every other key I tried other than Super.
Just tried evtest and all the keys I tried worked except for Super.
So the symptoms are:
Only the Super key doesn't work on your system, even at the kernel level.
The Super key works on windows.
I would conclude it is not the keyboard, but that you have something set that is capturing that key in linux. Do you perhaps have it set as a dead key in your keyboard mapping? That is, you press that key and then press two other keys to get a special character. For instance, on my system pressing my dead key, the windows menu key, and then t and m gives the ™ symbol.
On 9/2/21 5:09 AM, Richard Shaw wrote:
Just tried evtest and all the keys I tried worked except for Super.
That is very strange. Nothing should be able to capture keys before you read it there. If you run "evtest" with no parameters, it will give you a list of devices.
What is your keyboard? What name does it have in the list? Are there any other keyboards in the list? When you select the keyboard, there is a list of events. Do you see LEFTMETA in that list? Does the keyboard have two logo keys? If so, does the right one work? Do you have another keyboard to try?
On Thu, Sep 2, 2021 at 1:20 PM Samuel Sieb samuel@sieb.net wrote:
On 9/2/21 5:09 AM, Richard Shaw wrote:
Just tried evtest and all the keys I tried worked except for Super.
That is very strange. Nothing should be able to capture keys before you read it there. If you run "evtest" with no parameters, it will give you a list of devices.
What is your keyboard? What name does it have in the list? Are there any other keyboards in the list? When you select the keyboard, there is a list of events. Do you see LEFTMETA in that list? Does the keyboard have two logo keys? If so, does the right one work? Do you have another keyboard to try?
HAH! It's a Corsair K55 RGB keyboard. I did try a second keyboard (cheap USB Acer I had laying around) and it worked!
So that caused me to look up the manual. There's a "Lock" button at the top which apparently specifically disables the Super key! Who would have thought?!?
Apparently it's system dependent though as the key did work when plugged into another computer.
Thanks, Richard
On Thu, 2021-09-02 at 14:03 -0500, Richard Shaw wrote:
So that caused me to look up the manual. There's a "Lock" button at the top which apparently specifically disables the Super key! Who would have thought?!?
To make gamers happier, who find accidentally hitting that key interrupts their game.
Apparently it's system dependent though as the key did work when plugged into another computer.
Interesting, first I've heard of a keyboard detecting what OS it's being used by. Not sure how that could be done.
If you're using Windows, and installed a driver for the keyboard, I could understand detection working in the other direction. The OS polling the keyboard, and then using software to manage whether to ignore certain keys.
-
Patrick O'Callaghan -
Richard Shaw -
Samuel Sieb -
stan -
Tim