It's not a red herring. Those advanced options still need to be tested and maintained. If no one tests and maintains those options, they will break and users wi

It's not a red herring. Those advanced options still need to be tested and maintained. If no one tests and maintains those options, they will break and users will complain again and you're right back where you started. The idea is that it's better to just remove them instead of creating a false expectation that they're going to work. I personally would agree with that decision, at least in this case anyway. In libinput, people who understand the problem and are willing to work with the developers and contribute upstream can edit the hardware quirks. The maintainer has also blogged about this: https://who-t.blogspot.com/2018/06/libinput-and-its-device-quirks-files.html https://who-t.blogspot.com/2018/06/libinput-and-its-device-q...