Bug 89270 - synclient TouchpadOff has no effect
Summary: synclient TouchpadOff has no effect
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/synaptics (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Peter Hutterer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-21 19:48 UTC by Ramon Wirsch
Modified: 2015-02-23 03:53 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Dmesg output (76.91 KB, text/plain)
2015-02-23 01:33 UTC, Ramon Wirsch
no flags Details

Description Ramon Wirsch 2015-02-21 19:48:51 UTC
The setting TouchpadOff=1 is accepted and reported by synclient but has no effect on Touchpad operation. Probably as a consequence syndaemon has no effect.

Other settings like AccelFactor work like expected.

Setup:
Fedora 21
Kernel 3.18.7
Syaptics Driver version 1.8.1

on Dell XPS 12 9Q33
Comment 1 Peter Hutterer 2015-02-22 23:29:25 UTC
run xinput watch-props "<device name>" then toggle the property. does it change? does it change back immediately? might be something else running that also controls the property.
Comment 2 Ramon Wirsch 2015-02-22 23:43:34 UTC
The property does in fact change. Interference does only seem to come from syndaemon, because mode "2" was toggled each time i hit a keyboard key. After killing syndaemon, the property is set and remains that way until i manually change it.

>> behavior with syndaemon running

Property 'Synaptics Off' changed.
	Synaptics Off (308):	0
Property 'Synaptics Off' changed.
	Synaptics Off (308):	2
Property 'Synaptics Off' changed.
	Synaptics Off (308):	1
Property 'Synaptics Off' changed.
	Synaptics Off (308):	0
Property 'Synaptics Off' changed.
	Synaptics Off (308):	2
Property 'Synaptics Off' changed.
	Synaptics Off (308):	0

>> killed syndamon

Property 'Synaptics Off' changed.
	Synaptics Off (308):	1
Comment 3 Peter Hutterer 2015-02-22 23:54:16 UTC
setting it to 2 means "disable tapping and scrolling only", movement will still work. so it *looks* like it's not working. I suspect that second instance came from gnome-settings-daemon which enables the -t flag.

Closing this as NOTABUG, unless I misread something and it still doesn't disable when the property stays on 1 - pls reopen in that case.
Comment 4 Ramon Wirsch 2015-02-22 23:56:53 UTC
On second look it seems that my touchpad is detected as 2 separate devices:

⎜   ↳ DLL05E3:01 06CB:2734                    	id=11	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=13	[slave  pointer  (2)]

Both have the same synaptics properties. Synclient writes to the second device.
Using xinput set-prop to modifiy the first device actually deactivates the touchpad only, leaving the 'Click' on.
Comment 5 Peter Hutterer 2015-02-23 01:24:48 UTC
weird, what device is this? Can you attach dmesg?
Comment 6 Ramon Wirsch 2015-02-23 01:33:30 UTC
Created attachment 113746 [details]
Dmesg output
Comment 7 Ramon Wirsch 2015-02-23 01:39:35 UTC
Dell XPS 12 (2nd gen). Should be comparable / same hardware on the more common XPS 13 (2nd gen).

Both models had trouble getting both touchpad and touchscreen working under linux, because of some I2C complications. But that has been working for a while and I only recently discovered that deactivating the pad on typing is the default behavior.
Comment 8 Peter Hutterer 2015-02-23 03:53:33 UTC
I'm gonna point you to https://bugzilla.redhat.com/show_bug.cgi?id=1188439 then, it's a kernel issue and likely that the fixes to the bug above will fix yours too.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.