GNOME Bugzilla – Bug 324612
Can't disable trackpad/touchpad tap-to-click
Last modified: 2007-05-05 12:38:57 UTC
The mouse control panel has no checkbox to enable/disable tap-to-click on trackpads, though I think this is possible with the X configuration file. It seems worthy of an option, because some people can use it but it annoys the hell out of other people. I often tap-click by accident while typing, so the text gets redirected to different widgets.)
The capplet only does dynamic changes, it doesn't edit the xorg.conf. Is there a way to change that setting without changing the xorg configuration?
> Is there a way to change that setting without changing the xorg configuration? I have no idea.
This blog entry seems to give some hints: http://ubuntu.wordpress.com/2006/09/20/disable-touchpad-temporarily-when-typing/ " First, I edited the /etc/X11/xorg.conf file and added the Option “SHMConfig” “on” line to the section called “Input Device” for the Synaptic Touchpad input device. Then I restarted X (by using the ctrl+alt+backspace key combination). Once I was logged in, I used syndaemon as $syndaemon -t -d The -t option specifies that only the tapping and scrolling actions are to be disabled, "
Once Option "SHMConfig" "on" is set in xorg.conf, you can do pretty much anything you want to the synaptic driver settings. If this is to be added to the mouse control panel, I suggest it is grayed out when you can't switch it from user space because the user didn't set is xorg.conf right and add a link to the documentation about what to do to activate this box.
I guess this bug can be marked as duplicate of 154029. As said on previous comment, it's enough to have Option "SHMConfig" "on" in xorg.conf gsynaptics (http://gsynaptics.sourceforge.jp) shows us what can be done.
> I guess this bug can be marked as duplicate of 154029. I don't think so. That's about adding a confirmation dialog when changing touchpad settings. That won't help if there is no way to change this setting.
Sorry, I must have typed in the wrong bug number. Yes, let's make this a duplicate. *** This bug has been marked as a duplicate of 154029 ***