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.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
