Bug 1220941 - "Tap to click" option broken
Summary: "Tap to click" option broken
Keywords:
Status: CLOSED DUPLICATE of bug 1202773
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-12 21:35 UTC by Andreas Gruenbacher
Modified: 2015-05-13 11:34 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-13 11:34:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Andreas Gruenbacher 2015-05-12 21:35:35 UTC
Description of problem:
The "Tap to click" option in "gnome-control-center mouse" doesn't work; tapp-to-click stays off even when the option is enabled.

Version-Release number of selected component (if applicable):
control-center-3.16.1-1.fc22.x86_64

Hardware: 
$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ bcm5974                                 	id=13	[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)]
    ↳ Yubico Yubikey NEO OTP+U2F              	id=10	[slave  keyboard (3)]
    ↳ FaceTime HD Camera (Built-in)           	id=11	[slave  keyboard (3)]
    ↳ Apple Inc. Apple Internal Keyboard / Trackpad	id=12	[slave  keyboard (3)]
$ xinput list-props 13
Device 'bcm5974':
	Device Enabled (136):	1
	Coordinate Transformation Matrix (138):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Tapping Enabled (272):	0
	libinput Tapping Enabled Default (273):	0
	libinput Accel Speed (274):	0.000000
	libinput Accel Speed Default (275):	0.000000
	libinput Natural Scrolling Enabled (276):	0
	libinput Natural Scrolling Enabled Default (277):	0
	libinput Send Events Modes Available (257):	1, 1
	libinput Send Events Mode Enabled (258):	0, 0
	libinput Send Events Mode Enabled Default (259):	0, 0
	libinput Left Handed Enabled (278):	0
	libinput Left Handed Enabled Default (279):	0
	libinput Scroll Methods Available (280):	1, 0, 0
	libinput Scroll Method Enabled (281):	1, 0, 0
	libinput Scroll Method Enabled Default (282):	1, 0, 0
	libinput Click Methods Available (283):	1, 1
	libinput Click Method Enabled (284):	0, 1
	libinput Click Method Enabled Default (285):	0, 1
	Device Node (260):	"/dev/input/event9"
	Device Product ID (261):	1452, 602

Additional info:
Tap-to-click can be enabled manually on the command line with:
$ xinput set-prop bcm5974 "libinput Tapping Enabled" 1

Comment 1 Ondrej Holy 2015-05-13 08:31:12 UTC
Thanks for your bug report.

Please check that tap-to-click gsettings value corresponds with the state of check button in mouse panel e.g. using the following command (or d-conf editor):

gsettings get org.gnome.desktop.peripherals.touchpad tap-to-click

Comment 2 Andreas Gruenbacher 2015-05-13 10:45:32 UTC
The gsettings value and the GUI are always in sync, no matter if I change the checkbox or use "gsettings set" on the command line. This has no effect on the xinput value, though.

Comment 3 Ondrej Holy 2015-05-13 11:34:40 UTC
This is probably bug in mutter, which is responsible for setting libinput properties from gsettings, but I don't have an idea what's wrong, because it works for me correctly. 

There is already bug for mutter, so marking as duplicate.

*** This bug has been marked as a duplicate of bug 1202773 ***


Note You need to log in before you can comment on or make changes to this bug.