[SOLVED] Is there a software to disable the touchpad on the laptop?

[uncleV]

Then try
Configure your Computer( the circle icon down-left)-->Hardware.
?

[Jeremy.Bailey]

Found one that did the trick, touchpadtoggle, installed that and found it in More Applications-->Configurations-->Touchpad toggle.

Thank you very much for your help, uncleV and everyone else.

Now that I got that annoying touchpad disabled, I can sit back, and see how this system looks.
I think it's pretty nice myself, certainly worth checking over and see if I wish to use it more on a daily basis.
Thanks again!

[uncleV]

You're always welcome Jeremy!

I'm almost a noob but here we have some giants and mastodonts.

[Jeremy.Bailey]

thanks. you did a fine job in helping. Some may have been my fault, doing something wrong too. I have used Linux since 2006, and Windows free for a few years, ONLY on Linux, and still some things that should be basic, I can't seem to figure out.

[Jeremy.Bailey]

Edit: Sorry. I ran into other problems, but I just fixed it. I don't know if I told anyone, but I did install this distro, and soon found out that rebooting caused the touchpad to keep turning on again.
Synaptiks is working just fine, even after reboots.

Thanks again!

[parnote]

Touchpad Toggle has to be re-ran at every boot ... which is why I created it to run in a "silent" mode, with the command line switch --no-gui. Simply specify it with the --no-gui option in your autostart settings/folder, and Touchpad Toggle will start silently in the background whenever you reboot or log out and back in.

Hope this helps! I created Touchpad Toggle as a much smaller solution to the touchpad problem I was having (not too dissimilar to yours). As such, Touchpad Toggle is very, very small and does not stay loaded on your system once you run it.

I hope this helps!

parnote

[gobbledigook]

hi there!

having just purchased a wireless mouse i have found this thread very helpful

however... using touchpadtogggle just turns off my nice new mouse not my touchpad! when i run it from the cli i get a pop-up dialogue saying that my touchpad has been turned on, when in fact the mouse has been disabled, and when i run it again it states the same... yet enables the mouse whilst this in itself is not an issue, i intent on running it at start with the --no-gui option, how to i get it to distinguish between my touchpad and my mouse?

Code: [Select]

[dan@localhost ~]$ sudo touchpad_toggle.sh
Couldn't find synaptics properties. No synaptics driver loaded?
Couldn't find synaptics properties. No synaptics driver loaded?
EXIT="OK"


[parnote]

hi there!

having just purchased a wireless mouse i have found this thread very helpful

however... using touchpadtogggle just turns off my nice new mouse not my touchpad! when i run it from the cli i get a pop-up dialogue saying that my touchpad has been turned on, when in fact the mouse has been disabled, and when i run it again it states the same... yet enables the mouse whilst this in itself is not an issue, i intent on running it at start with the --no-gui option, how to i get it to distinguish between my touchpad and my mouse?

Code: [Select]

[dan@localhost ~]$ sudo touchpad_toggle.sh
Couldn't find synaptics properties. No synaptics driver loaded?
Couldn't find synaptics properties. No synaptics driver loaded?
EXIT="OK"


First of all, why are you using "sudo" in your command? Sudo is NOT used with PCLinuxOS.

Secondly, your USB connected mouse should be unaffected. TouchpadToggle only affects the current state of the touchpad, and looks to see if a USB mouse is connected. I've tested it here with 4 different USB mouse combinations (what I have available), both wireless and wired. Other members of the community have also tested with yet other USB mice, and there have been no reported problems.

It was also written to be used and accessible with ordinary user privileges. There is no need to be the root user to utilize it.

I'm suspecting that the use of "sudo" is somehow altering the behavior of TouchpadToggle.

Try again, but this time without the use of "sudo" in your command line. Let me know how that works out.

parnote

[Jeremy.Bailey]

thanks for the info

[gobbledigook]

apologies for not replying sooner... it was a long w/e!

i initially tried it without sudo and it has the same result, i am not saying your script is bad, it is more likely my anchient laptop!
But the issue is as described, with or without sudo... i was more wondering if anythig glaringly obvious came to mind.
i'll look at your script when i am home later to see if i can figure out whats going on