Comment 5 for bug 1767995

Nevermind -- turns out the workaround utilizing xinput set-prop still works, the device ID had changed. Nevertheless, this is a frustrating issue and seemingly simple request that this should just work as it always did. Where are the unit tests to prevent these constant regressions? I understand and appreciate the nature of open source software but it does seem basic quality control has slipped. Every update it seems I have to run around and fix something new that worked fine before.