Hi, On a fresh install of Fedora 22 (and updates), I just hit the same bug as https://bugzilla.redhat.com/show_bug.cgi?id=1181565#c7 As I did not find a bug report for this specific issue, I write it here. xorg-x11-drv-libinput is version 0.9.0 revision 1.fc22. On the default session (Gnome on X), none of the touchpad settings in gnome-control-center can be set: you can move the speed cursors, tick the boxes, but it does not change the touchpad behavior. However, this works using the Wayland session (which is for now not a good solution because then I can't copy and paste between applications). As asked Hans de Goede in https://bugzilla.redhat.com/show_bug.cgi?id=1181565#c8, here are some information gathered with xinput : $ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ bcm5974 id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ Apple Computer, Inc. IR Receiver id=9 [slave keyboard (3)] ↳ Apple Inc. Apple Internal Keyboard / Trackpad id=10 [slave keyboard (3)] ↳ Built-in iSight id=12 [slave keyboard (3)] $ xinput list-props 11 Device 'bcm5974': Device Enabled (139): 1 Coordinate Transformation Matrix (141): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 libinput Tapping Enabled (275): 0 libinput Tapping Enabled Default (276): 0 libinput Accel Speed (277): 0.000000 libinput Accel Speed Default (278): 0.000000 libinput Natural Scrolling Enabled (279): 0 libinput Natural Scrolling Enabled Default (280): 0 libinput Send Events Modes Available (260): 1, 1 libinput Send Events Mode Enabled (261): 0, 0 libinput Send Events Mode Enabled Default (262): 0, 0 libinput Left Handed Enabled (281): 0 libinput Left Handed Enabled Default (282): 0 libinput Scroll Methods Available (283): 1, 0, 0 libinput Scroll Method Enabled (284): 1, 0, 0 libinput Scroll Method Enabled Default (285): 1, 0, 0 libinput Click Methods Available (286): 1, 1 libinput Click Method Enabled (287): 0, 1 libinput Click Method Enabled Default (288): 0, 1 Device Node (263): "/dev/input/event10" Device Product ID (264): 1452, 567 If now I tick the "enable tap to click" box in Gnome control center : $ xinput list-props 11 Device 'bcm5974': Device Enabled (139): 1 Coordinate Transformation Matrix (141): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 libinput Tapping Enabled (275): 0 libinput Tapping Enabled Default (276): 0 libinput Accel Speed (277): 0.000000 libinput Accel Speed Default (278): 0.000000 libinput Natural Scrolling Enabled (279): 0 libinput Natural Scrolling Enabled Default (280): 0 libinput Send Events Modes Available (260): 1, 1 libinput Send Events Mode Enabled (261): 0, 0 libinput Send Events Mode Enabled Default (262): 0, 0 libinput Left Handed Enabled (281): 0 libinput Left Handed Enabled Default (282): 0 libinput Scroll Methods Available (283): 1, 0, 0 libinput Scroll Method Enabled (284): 1, 0, 0 libinput Scroll Method Enabled Default (285): 1, 0, 0 libinput Click Methods Available (286): 1, 1 libinput Click Method Enabled (287): 0, 1 libinput Click Method Enabled Default (288): 0, 1 Device Node (263): "/dev/input/event10" Device Product ID (264): 1452, 567 I did not try the suggested fix which is to remove xorg-x11-drv-libinput. Do not hesitate to ask for for more information. Regards, Yvan
This seems to be a bug in mutter, probably a dup of 1214477.
If you change the options in the UI while running xinput watch-props 11 on a terminal, are the value changes reflected on the terminal? Also, if you you try to enable tapping via xinput set-prop 11 'libinput Tapping Enabled' 1 on a terminal, does it work then?
(In reply to Rui Matos from comment #2) > If you change the options in the UI while running > > xinput watch-props 11 > > on a terminal, are the value changes reflected on the terminal? > > Also, if you you try to enable tapping via > > xinput set-prop 11 'libinput Tapping Enabled' 1 > > on a terminal, does it work then? For some other reasons the person who owns the computer had to wipe the disk: I won't be able to provide these informations. I let you close this bug properly. Sorry for the noise, Yvan
Finally I could try on another MacBook Pro, which has the same touchpad (bcm5974). The only difference from above is that I'm using a live USB. If I change the setting while running "xinput watch-props 11", nothing happens. If I use "xinput set-prop 11 'libinput Tapping Enabled' 1", it does enable the "tap to click" (and the right click with two fingers). Regards, Yvan
Hi, (In reply to yvan.masson from comment #4) > Finally I could try on another MacBook Pro, which has the same touchpad > (bcm5974). The only difference from above is that I'm using a live USB. > > If I change the setting while running "xinput watch-props 11", nothing > happens. > > If I use "xinput set-prop 11 'libinput Tapping Enabled' 1", it does enable > the "tap to click" (and the right click with two fingers). Please do "xinput list" and make sure that 11 is the correct id. e.g. if the output of xinput list is like this: xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ bcm5974 id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ Built-in iSight id=10 [slave keyboard (3)] ↳ Apple Inc. Apple Internal Keyboard / Trackpad id=11 [slave keyboard (3)] ↳ Apple Computer, Inc. IR Receiver id=13 [slave keyboard (3)] Then the touchpad is id 12, The touchpad is always under the "Virtual core pointer" parent of the tree. Regards, Hans
Hi, So in the mean time we've gotten confirmation from other users on this, and this is being tracked in another bug so I'm marking this one as a duplicate. Regards, Hans *** This bug has been marked as a duplicate of bug 1206961 ***