On Thu, Mar 3, 2016 at 5:23 PM, Michael Gratton <m...@vee.net> wrote:
On Thu, Mar 3, 2016 at 4:47 PM, Tim <dark...@fastmail.fm> wrote:
On 03/03/16 15:57, Tim wrote:
On 03/03/16 14:59, Michael Gratton wrote:
On Thu, Mar 3, 2016 at 12:36 PM, Michael Gratton <m...@vee.net>
wrote:
Also, the touchpad settings in gnome-control-centre are being
completely ignored. None of the UI elements relating to the
touchpad seem to
have any effect on my Macbook Pro's built-in touchpad, nor my
external Apple Bluetooth touchpad. Natural scrolling is not
getting enabled
when
it set to On, Tap-to-click is not enabled when set or On, and
disabling the touchpad by setting it to Off does not work
either. I don't know
if this is related to the UI refresh or something else, any
suggestions?
I don't have a macbook, but I will take a quick look at this on
my laptop and see if its the same, when I get a chance.
That would be great, ta!
After a bit of investigation, the problem doesn't occur under X11
when using libinput instead of synaptics/evdev as the input driver
-
removing xserver-xorg-input-synaptics and
xserver-xorg-input-evdev, installing xserver-xorg-input-libinput
and restarting my X session fixes it.
Since using evdev/synaptics worked fine under Wiley with Mutter
3.18, I'm not sure if the problem is with changes to
xorg/evdev/synaptics in
Xenial or a bug in Mutter 3.19.
File a bug against mutter, I think 3.20 will need to be using
libinput on X11 by default.
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=66c211ff24bec6a938d6a6a0dd8730f4689ef383
Bug filed - <https://bugs.launchpad.net/ubuntu-gnome/+bug/1552558>
The commit you reference above suggests that the compositor, i.e.
mutter will need to take care of this in teh future. Also, mutter
does seem to have code to implement this for X11 - it uses X
properties to update the settings, so it should work, provided that
supported by evdev/synaptics, I guess?
Oh, except that Mutter's X11 backend only updates libinput properties
on config changes, not synaptics, and hence you're right - 3.19 does
require using libinput.
Also is installing libinput enough to fix this or does it require
further configuration (i.e without removing evdev/syaptics drivers,
since that
would break other DE's where users have several installed)
Unfortunately not. I already had libinput installed, but after
installing xserver-xorg-input-libinput its config was a lower
priority in xorg.conf.d, so I had to remove
xserver-xorg-input-synaptics and xserver-xorg-input-evdev first to
get it working.
//Mike
--
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>
--
Ubuntu-GNOME mailing list
Ubuntu-GNOME@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-gnome
