synaptics and unstable?
Dear Lazyweb, I have just found out that ksynaptics has stopped working against the X in unstable, and that ksynaptics is not even in lenny, let alone in current testing and/or unstable. This currently leaves me with an unconfigured touchpad, which is a major nuisance since I have gotten accustomed to tap-dragging and touchpad border scrolling.
xserver-xorg-input-synaptics' README.Debian dates back to 2004, so I suspect that the information given there in does not any more apply to today's configfile-less X.
So, dear lazyweb, how do I get my touchpad back into the more intelligent mode? Clickable configuration preferred.
Trackbacks
No Trackbacks
Comments
Display comments as Linear | Threaded
Markus Hochholdinger on :
not configfile-less but working: xorg.conf Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "CorePointer" Option "SHMConfig" "on" EndSection
graphical program: gsynaptics
i didn't manage to set the option with /etc/hal/fdi/policy/*.fdi
Maik on :
There is a program called synclient in the xserver-xorg-input-synaptics package. This is mentioned in NEWS.Debian.gz.
Zak on :
http://wiki.debian.org/XStrikeForce/InputHotplugGuide
cp /usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi /etc/hal/fdi/policy/
Marc 'Zugschlus' Haber on :
That was helpful, thanks a lot.
Dietz Proepper on :
gpointing-device-settings might be your friend. You can set up stuff the clicky way, settings are preserved between sessions and it does not need SHMConfig.
You can even configure the clickpoint separately from the synaptics pad. Very, very nice.
(On the back side, I was not able to enable tapping, but given the fact that I don't use it anyway...)
Marc 'Zugschlus' Haber on :
That seems to work fine, but the loss of tapping is a major nuisance for me. At least I seem to have scrolling back.
Marc 'Zugschlus' Haber on :
Solved. #497523 says that it was upstream's infinite wisdom to disable tapping if hardware buttins were detected, and one needs tadaaa an xorg.conf to re-introduce the old behavior.
The HAL way suggested in that bug report didn't work on my box.