I'd say it should just work or it's a bug. And I know it's tedious to file bugs and report required information but that's really the only way it's going to get

I'd say it should just work or it's a bug. And I know it's tedious to file bugs and report required information but that's really the only way it's going to get fixed. You could start by asking on the list, just to see if this is a known problem that's already fixed in a later version. https://lists.freedesktop.org/mailman/listinfo/wayland-devel https://lists.freedesktop.org/mailman/listinfo/wayland-devel For testing, you don't have to install if you don't want. I suggest installing the latest Fedora 30 beta test candidate. It's more reliable than Rawhide, and yet has the latest libinput so you won't be asked to build a newer version from git. Download the workstation live file, image to a USB stick, and do the testing from the live environment. Software installation is supported, it uses the RAM overlay. https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.7_Summary?rd=Test_Results:Current_Summary https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1... While it's tedious to have to file such detailed bug reports, they make it pretty straightforward to figure out what is needed and how to get it. The devs have no way of guessing what the problem is. Plus, the fix eventually finds its way to all distributions, so people just get the fix rather than you having to maintain a local hack. https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html https://wayland.freedesktop.org/libinput/doc/latest/reportin... https://gitlab.freedesktop.org/libinput/libinput/issues https://gitlab.freedesktop.org/libinput/libinput/issues