microsoft nano transceiver v2 0 model 1447

Start Microsoft Mouse and Keyboard Center, and select Wheel. To do this and to follow the additional troubleshooting steps listed below, first visit the Microsoft Mouse and Keyboard Center, select the download version you want to use, and follow the instructions to install it.

You can also disable the wheel button, if you prefer to use the wheel only for scrolling.

To resolve the problem, avoid pressing down on the wheel while scrolling. If you want to return to the previous window, press the wheel until that window appears again, or use the Windows taskbar to switch to the window that you want. That's why the active window seems to disappear, but it's actually still open on your desktop. Sometimes while scrolling, you might accidentally press the wheel and unintentionally switch to another open program. Pressing the wheel switches to other open programs on your desktop. You can use the mouse wheel to scroll, and you can also use it as a button. Libinput Send Events Mode Enabled Default (263): 0, 0 Libinput Send Events Mode Enabled (262): 0, 0 Libinput Send Events Modes Available (261): 1, 0 Libinput Left Handed Enabled Default (291): 0 Libinput Accel Profile Enabled Default (289): 1, 0 Libinput Accel Profile Enabled (288): 1, 0 Libinput Accel Profiles Available (287): 1, 1 Libinput Accel Speed Default (286): 0.000000 Libinput Middle Emulation Enabled Default (284): 0 Libinput Middle Emulation Enabled (283): 0 Libinput Button Scrolling Button Default (282): 2 Libinput Button Scrolling Button (281): 2 Libinput Scroll Method Enabled Default (280): 0, 0, 0 Libinput Scroll Method Enabled (279): 0, 0, 0 Libinput Scroll Methods Available (278): 0, 0, 1 Libinput Natural Scrolling Enabled Default (277): 0 Libinput Natural Scrolling Enabled (276): 1 ↳ Microsoft Microsoft® Nano Transceiver v2.0 id=13 ↳ Microsoft Microsoft® Nano Transceiver v2.0 id=9 ⎜ ↳ Microsoft Microsoft® Nano Transceiver v2.0 id=11 ⎜ ↳ Microsoft Microsoft® Nano Transceiver v2.0 id=10

(Not sure why it presents itself as doubled up devices.) Is there any hope of a software fix for this? How does libinput learn what properties should be available for any given touchpad? As of Ubuntu 18.04, the Microsoft All-in-one keyboard's touchpad gives the following properties, which don't include any 'tapping' properties.

Microsoft nano transceiver v2 0 model 1447