#XINPUT TEST MOUSE DRIVER#

Thank you for reporting this issue and we are sorry that we were notĪble to fix it before Fedora 26 is end of life. Plan to fix it in a currently maintained version, simply change the 'version'

Package Maintainer: If you wish for this bug to remain open because you This bug will be closed as EOL if it remains open with a Fedora 'version' It is Fedora's policy to close allīug reports from releases that are no longer maintained. This message is a reminder that Fedora 26 is nearing its end of life.Īpproximately 4 (four) weeks from now Fedora will stop maintainingĪnd issuing updates for Fedora 26. In this case, how is the mouse connected to your computer? Is it listed in the outputs of `lspci`, `lsusb`, `hciconfig` or `lshw`? If yes, please post the output.

#XINPUT TEST MOUSE DRIVER#

If that does not work, the Kernel might not be able to detect the device correctly or might not provide a driver for it. Maybe that sheds some light on your device, maybe it does not work any more (as a comment on the first answer suggests). gnome-control-center, and assign the button to a keyboard shortcut. You might want to try the trick from : Open some tool, e.g. If that does not work, what do you get when running `scankey -s` from a tty followed by repeatedly pressing the Windows button? (You might need to run it as root)? Since your mouse has a non-standard key, it might also identify itself as keyboard to your computer. I should have mentioned that.Ĭan you try disconnecting the mouse (only the mouse) and get another `xinput list` output? Then compare both and find all IDs provided by your mouse. Yes, xinput is expected to work better on Xorg compared to Wayland.

Xinput test mouse