I am running opensuse 12.3 and the touchpad is no longer working. It works at start up until the tools icon appears. I believe it is problem between the synaptics driver and evdev. If I look in / Ivar/log/Xorg.0.log I see the touchpad detected for a 2’nd time.
69.936] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event0)
69.941] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
69.941] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
69.941] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
69.941] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/event7)
I also noticed that if I run startx as root The to uchpad works fine.
I am using KDE, and the touchpad stops working shortly after the desktop comes up. But that’s because I am running “synaptiks” and have set it to disable the touchpad if it finds another mouse.
It is a while since I last tried Gnome with a touchpad, though it was Gnome 3 (or 3.2).
My best recollection, is that if I use the function key combo to disable the touchpad, it stops working. If I logout, it starts working again. If I login to Gnome, it stops working again. Or, in other words, something in Gnome is remembering the last state of the function key touchpad control.
I’m not sure whether either of the above (KDE or Gnome) applies to you. If not, report your desktop and maybe someone will know what to do.
I had a similar problem. The touchpad stopped working after I used the hardware switch to enable/disable the touchpad. The KDE notifications went into infinite spiral crashing my session.
As a result the touchpad was non-functional despite trying:
Also the touchpad was enabled during login but disabled after login.
My solution was to rebuild synaptics package. I guess this refreshed some of the settings. Immediately after yast finished reinstalling the package the touchpad was enabled and working.
Try the following:
[li]Start Yast Install/Remove Software tool. [/li][li]Type synaptics and the search result should show:[/li][LIST=1]
[li]Click with the right button on the selected package. Select the fourth option from the drop-down menu. Apply. [/li][li]Wait for it to remove and install again the x86 synaptics. [/li][li]After Yast has disappeared, the touchpad should work. [/li][/LIST]
I have tested this on Compaq CQ61. I hope this solution will help you.
That will indeed fix it. I stumbled into the cause of the problem in another discussion thread. The HP EliteBook’s (mine is a 2540p) allows the touchpad to be disabled by typing Fn f12. It sets touchpadEnabled=false . The ksynaptics gui does not turn it back on. You have to edit ~/.kde4/share/config/ktouchpadenablerrc . Thanks for the comment.
I installed to a Toshiba c650 with a synaptics touchpad. Every now and again, I’d “accidentally” go off and click away from where I was typing, it was pretty frustrating. I thought maybe I was dragging my palm across the touchpad so I started looking at ways to prevent this behavior, which led me to this article.
The gnome touchpad application does not save ~all~ options or even present you with the ability to change some if you’re using a synaptics touchpad. I have found that I can fix a few by editing the xorg configuration option file, other options don’t appear to be sticky and must be set manually using synclient. Tip: execute synclient with no options to list available parameters.
I found these options to be useful in preventing the inadvertent mouse clicks on my synaptics touchpad, I placed them in the configuration file /etc/X11/xorg.conf/70-synaptics.conf:
What I found is that MaxTapTime does not appear to be “sticky” and must be set using the synclient command, so I created a small script file to set it on restart of my machine. I used alacart to create an application pointing to my script file, and tweaktool to launch it on start:
#Script to set trackpad to not do single-click #uncomment the next line to debug
I’m sure this information may be useful to others, but you’ve responded to an old thread and things have changed. In general if you have some contemporary information you’d like to share (as opposed to seeking support), consider posting to our ‘Unreviewed How To and FAQ’ forum instead.