After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 694343 - "disable touchpad" doesn't completely disable touchpad
"disable touchpad" doesn't completely disable touchpad
Status: RESOLVED OBSOLETE
Product: gnome-settings-daemon
Classification: Core
Component: mouse
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2013-02-21 09:12 UTC by Allison Karlitskaya (desrt)
Modified: 2013-06-13 15:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Allison Karlitskaya (desrt) 2013-02-21 09:12:26 UTC
This is either a shell or g-s-d bug...

I can press Fn+F8 to disable my touchpad.

In that case, the touchpad stops acting as a mouse (can't move, can't tap-to-click, etc).

In the shell overview, however, it seems that tap-to-click on the touchpad will still work to select a window.  It won't work for launching things from the dash or selecting workspaces or open menus or anything else -- just switching to windows.

From that standpoint it could be a shell bug.

On the other hand, if I use xinput to find my device:

desrt@moonpix:~$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                   	id=15	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=13	[slave  pointer  (2)]

and then disable it:
desrt@moonpix:~$ xinput disable 13

then I no longer get tap-to-click working for windows in the overview.

From that standpoint it is probably a g-s-d bug (for not "fully" disabling the device).
Comment 1 Bastien Nocera 2013-02-21 09:16:39 UTC
xinput disable has the same effect as what gnome-settings-daemon does:
       --disable device
               Disable the device. This call is equivalent to xinput --set-prop device "Device Enabled" 0

What's the output of:
xinput list-props 13
before you disable the touchpad?
Comment 2 Bastien Nocera 2013-02-21 09:44:06 UTC
You can also check where the tap-to-click event is coming from with xev (might not be id 13).
Comment 3 Allison Karlitskaya (desrt) 2013-02-21 09:50:21 UTC
I checked xev before -- it shows absolutely nothing in any case (kinda-disabled or fully-disabled).

In the kinda-disabled state (ie: g-s-d disabled, but not "xinput disable"):

desrt@moonpix:~$ xinput list-props 13
Device 'SynPS/2 Synaptics TouchPad':
	Device Enabled (133):	1
	Coordinate Transformation Matrix (135):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	Device Accel Profile (256):	0
	Device Accel Constant Deceleration (257):	1.000000
	Device Accel Adaptive Deceleration (258):	1.000000
	Device Accel Velocity Scaling (259):	10.000000
	Device Product ID (250):	2, 7
	Device Node (251):	"/dev/input/event8"
	Evdev Axis Inversion (260):	0, 0
	Evdev Axis Calibration (261):	<no items>
	Evdev Axes Swap (262):	0
	Axis Labels (263):	"Abs MT Position X" (281), "Abs MT Position Y" (282), "Abs Pressure" (279), "Abs Tool Width" (280), "None" (0), "None" (0)
	Button Labels (264):	"Button Left" (136), "Button Unknown" (253), "Button Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140)
	Evdev Middle Button Emulation (265):	0
	Evdev Middle Button Timeout (266):	50
	Evdev Third Button Emulation (267):	0
	Evdev Third Button Emulation Timeout (268):	1000
	Evdev Third Button Emulation Button (269):	3
	Evdev Third Button Emulation Threshold (270):	20
	Evdev Wheel Emulation (271):	0
	Evdev Wheel Emulation Axes (272):	0, 0, 4, 5
	Evdev Wheel Emulation Inertia (273):	10
	Evdev Wheel Emulation Timeout (274):	200
	Evdev Wheel Emulation Button (275):	4
	Evdev Drag Lock Buttons (276):	0

then:

desrt@moonpix:~$ xinput disable 13
desrt@moonpix:~$ xinput list-props 13
Device 'SynPS/2 Synaptics TouchPad':
	Device Enabled (133):	0
	Coordinate Transformation Matrix (135):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	Device Accel Profile (256):	0
	Device Accel Constant Deceleration (257):	1.000000
	Device Accel Adaptive Deceleration (258):	1.000000
	Device Accel Velocity Scaling (259):	10.000000
	Device Product ID (250):	2, 7
	Device Node (251):	"/dev/input/event8"
	Evdev Axis Inversion (260):	0, 0
	Evdev Axis Calibration (261):	<no items>
	Evdev Axes Swap (262):	0
	Axis Labels (263):	"Abs MT Position X" (281), "Abs MT Position Y" (282), "Abs Pressure" (279), "Abs Tool Width" (280), "None" (0), "None" (0)
	Button Labels (264):	"Button Left" (136), "Button Unknown" (253), "Button Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140)
	Evdev Middle Button Emulation (265):	0
	Evdev Middle Button Timeout (266):	50
	Evdev Third Button Emulation (267):	0
	Evdev Third Button Emulation Timeout (268):	1000
	Evdev Third Button Emulation Button (269):	3
	Evdev Third Button Emulation Threshold (270):	20
	Evdev Wheel Emulation (271):	0
	Evdev Wheel Emulation Axes (272):	0, 0, 4, 5
	Evdev Wheel Emulation Inertia (273):	10
	Evdev Wheel Emulation Timeout (274):	200
	Evdev Wheel Emulation Button (275):	4
	Evdev Drag Lock Buttons (276):	0


The only thing in the diff between those two:
-	Device Enabled (133):	1
+	Device Enabled (133):	0
Comment 4 Christopher Halse Rogers 2013-02-21 10:16:36 UTC
So, synaptics has *two* ways to disable it - there's device-enabled and synaptics-off. These are not the same thing. Are they getting out of sync and producing weirdness?
Comment 5 Bastien Nocera 2013-02-21 10:27:27 UTC
    Device Enabled (133):    1

gnome-settings-daemon isn't disabling the touchpad properly. What's the output of:
gsettings get org.gnome.settings-daemon.plugins.mouse active
gsettings get org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled
Comment 6 Tobias Mueller 2013-06-08 03:45:33 UTC
Ryan, ping.
Comment 7 Allison Karlitskaya (desrt) 2013-06-08 14:03:17 UTC
[desrt@moonpix ~]$ gsettings get org.gnome.settings-daemon.plugins.mouse active
true
[desrt@moonpix ~]$ gsettings get org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled
false


fwiw, this seems to be gone with gnome-shell 3.8.  I'm not sure that means it's fixed -- I think that the shell just changed behaviour.
Comment 8 Bastien Nocera 2013-06-13 15:16:01 UTC
Let's close this then. I suspect touch events getting sent through the wrong device.