I find it easier to write a script to execute something, then manually put a symbolic link to it in the autostart directory (which might well be in ~/.kde4/Autostart but I don’t really remember and I’m on the wrong OS right now to check…)
But it might well be in configure desktop / advanced.
Not difficult (well… not a script like this anyway. :))
Make a file in a text editor (not a word processor, because it’ll fill it with invisible characters. Use nano, vim, kwrite, gedit, mousepad, something like that) with #!/bin/sh as the first line, then what you want executed.
syndaemon -t -d
Something like that. Save it as, say, ~/scripts/touchpad.sh
I dont know if the code is effective, so removed the code.
See the problem is still there as I find typing very difficult. Sometimes it moves to some other line and starts typing or highlighting.
When I type ‘syndaemon -t -d’ the cursor becomes a ‘I’ shape and stays in one place. So I try it in a Word document but I have to type slow.
The touchpad does not freeze, the cursor is a lit well-behaved and so it lets me type. Or else, it jumps , highlights and even deletes sentences.
It is the cursor that gives me grief.
When running syndaemon , the cursor does not jump about.
But the reason to cursor is jumping is almost certainly because you have ‘tap to click’ enabled on your touchpad, and it’s interpreting you brushing against it as a click. Similarly, the reason it ‘autofills’ with text is because it thinks you’re tapping (probably with two fingers) and it’s interpreting that as a middle click, which in Linux means ‘paste whatever is selected’.
So what I’m asking you to do is to run a terminal, then put that code in, then minimize the terminal. Then open a word processor, or firefox, or whatever it is you’re having problems in, and see if the problems are still there - and if they aren’t, we can work on making it all happen automatically.
Ah - I think you edited your post (or I misread it… :))
So the syndaemon thing does work? Then you can try the instructions I put before so it runs it as a script. (note that you’ll have to make the scripts directory first, if you choose to put it in there - you would use ‘mkdir ~/scripts’)