Created attachment 317562 [details] [review]
mouse: Remove support for non-libinput mouse configurations

With the configuration for mice and other pointing devices now in mutter
for both Wayland and X11 (with libinput X11 drivers), the mouse plugin
is only ever used to:
- migrate old gnome-settings-daemon mouse settings to
  gsettings-desktop-schemas
- set up a11y features, via mousetweaks and gsd-locate-pointer, which
  weren't ported to mutter/gnome-shell yet
- handle evdev/synaptics pointing devices, usually on non-Linux systems

As we want to move input device handling into the compositor, so there's
only one code path for all their configuration, remove support for
evdev/synaptics settings.

Peter, opinion?

bit early, I reckon. there's still a fair number of people that drop libinput and use synaptics for the touchpad because they claim it has nicer acceleration. I haven't gotten round to figuring out what the accel needs to be to improve.

After some inquiries, it looks like this will have some impact on OpenBSD which does not use libinput yet.

Sounds like duplicate of Bug 747513, doesn't it?

(In reply to Peter Hutterer from comment #3)
> bit early, I reckon. there's still a fair number of people that drop
> libinput and use synaptics for the touchpad because they claim it has nicer
> acceleration. I haven't gotten round to figuring out what the accel needs to
> be to improve.

Though I can empathise with acceleration not behaving exactly the way somebody would want it to, I doubt that this is something that's going to go magically right one day, and pushing everyone off of the olden acceleration. How many people are we talking about?

(In reply to Antoine Jacoutot from comment #4)
> After some inquiries, it looks like this will have some impact on OpenBSD
> which does not use libinput yet.

I know you don't, I was asking about whether reverting that patch for your builds would be good enough for you.

(In reply to Ondrej Holy from comment #5)
> Sounds like duplicate of Bug 747513, doesn't it?

The bug there is about removing the whole of the plugin, this is removing only part of it. Though the first patches were similar...

(In reply to Bastien Nocera from comment #6)
> Though I can empathise with acceleration not behaving exactly the way
> somebody would want it to, I doubt that this is something that's going to go
> magically right one day, and pushing everyone off of the olden acceleration.
> How many people are we talking about?

don't know, but it appears to be a vocal enough set and it seems to be the main reason why people don't use libinput yet.

As *BSDs should be able to revert the patches that remove support for the evdev and synaptics X11 drivers, and that I doubt there will be a day where the most vocal haters of the pointer acceleration in libinput will be happy, I will be committing those patches now for release in GNOME 3.20.

*BSDs will downstream patch gnome-settings-daemon until they have an equivalent to libinput/x11-drv-libinput and people who don't like the libinput acceleration will have to talk to the libinput developers about it.

Attachment 317562 [details] pushed as 66c211f - mouse: Remove support for non-libinput mouse configurations

*** Bug 747513 has been marked as a duplicate of this bug. ***