A great idea that I found at the Linux Mint forum.
Original post here!
I've been looking for a solution for this off and on for a long time - and now I found it
There's a handy little CLI tool called syndaemon that does this for you
Shuts off the touchpad when you type and enables it two seconds after the last keystroke
If you add -t you only disable tapping and scrolling, not mouse movement (Just for your info - mostly it's the movement you want to disable)
If you add -i 1 it's enabled after one second
To make syndaemon start automatically add the command to the "Startup Applications" (for Gnome)
Open the menu and type star and you see it
Click the add button and enter syndaemon -d and give it a name (Notouch perhaps?)
In KDE 4 (Gloria) it is Applications > System > System settings > the Advanced tab > Autostart
Click Add program and enter syndaemon -d
To make sure that it works you should enable SHMConfig
In all editions except main and KDE you have to install SHMConfig
gksudo gedit /etc/hal/fdi/policy/shmconfig.fdi
kdesudo kate /etc/hal/fdi/policy/shmconfig.fdi
This brings up an empty file
Add the following to that file
<?xml version="1.0" encoding="UTF-8"?> <deviceinfo version="0.2"> <device> <match key="input.x11_driver" string="synaptics"> <merge key="input.x11_options.SHMConfig" type="string">True</merge> </match> </device> </deviceinfo>
Save, close the file and reboot and you should be done
Note - for versions earlier than Felicia (Mint 6) this is added to xorg.conf
Option "SHMConfig" "true"
First of all, after writing my reply, I have to say thanks for giving us the information. The following may sound harsh, but I can assure you that I appreciate your work
So why do we use a policy just to end up starting up a daemon and editing the xorg.conf. hal policies are all about not having to edit the xorg.conf... In pre-hal ages, we simply added some options to xorg.conf and enjoyed ourselves. I know, it's for old versions, but what's wrong with Option "PalmDetect" in your xorg.conf?
I see the benefits of hal, but why should we do everything the hal way, especially when it's more complicated than the classic way?
If you insist on hal, you might want to try
<merge key="input.x11_options.PalmDetect" type="string">1</merge>
in a policy file.
Whatever you want to do with synaptics and an fdi policy, make sure to consult man synsptics.
Now you might say: "I can kill the daemon whenever I want."
How about sudo /etc/init.d/hal restart?
EDIT: Ok the benefit of the daemon is obvious: It's running userspace and you don't need to be root to change it. In addition, I'm not sure wether there are per user hal policies or not. But on the other hand, we can enable SHMConfig to let the user decide, no matter what the policy says, don't we?
Last edited by Awebb (2009-08-24 22:38:21)
I'm so meta, even this acronym
I merely added
syndaemon -d &
to autostart.sh and it works fine...
I'm just glad I found it...
Last edited by Zwopper (2009-08-24 22:50:46)
I believe in the newer releases of ubuntu those xorg settings are ignored and you have to set it with hal. I usually go the syndeamon route as well, just haven't set it up again yet. Thanks for the reminder Zwopper
I say never be complete, I say stop being perfect, I say lets evolve, let the chips fall where they may.
I'm not having any luck with this. syndaemon generates the following errors. Time to check out some of the launchpad bugs in relation to this.
X Error of failed request: BadDevice, invalid or uninitialized input device Major opcode of failed request: 141 (XInputExtension) Minor opcode of failed request: 3 (X_OpenDevice) Serial number of failed request: 12 Current serial number in output stream: 12
I need to use something like
syndaemon -i 0.5 -S -d
to get things working.
Appears to be ok at this stage but will keep investigating.
i tried your method in addition to every possible way google search threw at me (enabling it through xorg, the new jaunty way through the hsl/policy/fdi way etc..) but nothing works.
I keep getting the following error:
"Cant access shared memory area. SHMConfig disabled?"
Even though i did do the hal xml thing
btw runing it on msi wind u-100 and crunch bang 9.04
thx in advance
syndaemon -d &
And il see if it suits me or if it needs any more tuning of the syndaemon.
Very very very neat - I was getting so anoyed about my touchpad!
Another problem bites the dust! *He he he*
Thx - I love you.
With love and gratitude -
No-Thing But Divine
Last edited by No-Thing (2012-09-14 00:54:48)
With love and gratitude - No-Thing But Divine
I am an orphan, alone; nevertheless I am found everywhere. I am one, but opposed to myself. I am youth and an old man at one and the same time. In woods and mountains I roam, but I am hidden in the innermost soul of man. I am mortal for everyone, yet I am not touched by the cycle of the aeons.
So yes, this is a pretty old thread, but the touchpad on my Lenovo S10-3 was driving me completely insane, and this solution solved it quite simply. I did not need to use the XML and the
syndaemon -d &
and the addition of the shmconfig.fdi file was all it took to start working. Awesome!
I post this because the instructions suggest that there is already an /etc/hal tree. On my Waldorf/Sid build there was no such directory. This makes me wonder if hal has been replaced with something else we should be using for this kind of thing?
Last edited by marmotBreath (2014-03-06 00:30:57)