>George Kiagiadaki wrote:
> 2009/8/22 Vincent Frison <[email protected]>:
>> Hi all,
>>
>> My laptop touchpad works pretty well on my KDE except for the tap clicking.
>>
>> I tried different solutions but none of them has worked:
>>
>> 1) Enabling tap clicking on gsynaptics
>>
>> 2) Adding an explicit conf in xorg.conf:
>> Section "InputDevice"
>>    Identifier "Touchpad0"
>>    Driver "synaptics"
>>    Option "Device" "/dev/psaux"
>>    Option "Protocol" "auto-dev"
>>    Option "SendCoreEvents" "true"
>>    Option "MaxTapTime" "180"
>>    Option "MaxTapMove" "220"
>> [..]
>> EndSection
>>
>> 3) Adding lines in /etc/hal/fdi/policy/11-x11-synaptics.fdi such as
>> <merge key="input.x11_options.TapButton1" type="string">1</merge>
>>
>> Apparently there's no GUI for touchpad in KDE settings unlike GNOME :(
>>
>> And the weird thing is that it works perfectly when I boot on a Kubuntu 8.10
>> Live CD! In that case there's no special conf relative to touchpad in
>> xorg.conf...
>>
>> I'm under Debian unstable with KDE 4.3.0 and  xserver-xorg-input-synaptics
>> 1.1.2-1 installed.
>>
>> Any help would be appreciated,
> 
> Hi,
> 
> I had the same bug here and I solved it by downgrading
> xserver-xorg-core to version 1.4.2 from testing. It seems like a xorg
> bug to me...
> 
> Regards,
> George
> 
> 

Hi,

it's not a bug, it's a "feature" ;-) . From what I have read (google
"synaptics + hal [+ debian]") it seems that upstream decided that
enabling taping was counter intuitive...

Also Sid xorg should be using hal to control the touchpad, it seems that
nothing under /etc/hal/fdi/policy/ is taken into account, I tried many
different ways to no avail.

What did the trick for me is (from memory, beware):

Section "InputDevice"
        Identifier      "synaptics"
        Driver          "synaptics"
        Option          "TapButton1"    "1"
        Option          "TapButton2"    "2"
EndSection

in /etc/X11/xorg.conf, then reboot (yes, reboot seems needed, I couldn't
do without) .

It might stop working at some point, but then we can expect rules in
/etc/hal/fdi/policy/ to be efficient.

Hope it helps.

Tom


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to