No touch-and-drag with Synaptics pad

Bug #36958 reported by Irios
6
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Confirmed
Medium
Ubuntu-X

Bug Description

tap-tap-drag functionality has disappeared in my laptop since I updated to dapper. Single taps and double taps work, but dragging the finger before lifting after the second tap does not work like mouse click-and-drag.

Hardware manager tells me it is a "SynPS/2 Synaptics Touchpad"

Revision history for this message
Irios (irios) wrote :

Ho-hum ... I've found the problem, and maybe it is fixed by now.

It is the DETECTION of the Synaptics pad that failed when installing Ubuntu, so the pertinent entry was not present in /etc/X11/xorg.conf. The pad was working through the PS2 driver, which explains the problems.

Copying the Synaptics section from the Breezy partition fixed the issue. Now, I don't know whether it would fail to be detected at installation time as of today.

Revision history for this message
Jerome S. Gotangco (jsgotangco) wrote :

Thank you for your bug report. Please confirm if this still persists on latest Dapper release (Flight 6 and up).

Jerome

Changed in xserver-xorg-input-synaptics:
status: Unconfirmed → Needs Info
Revision history for this message
Tomasz Dominikowski (dominikowski) wrote :

I can fully confirm this report.

Changed in xserver-xorg-input-synaptics:
status: Needs Info → Confirmed
Revision history for this message
Tomasz Dominikowski (dominikowski) wrote :
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

[ 44.844685] Synaptics Touchpad, model: 1, fw: 4.1, id: 0x848a1, caps: 0x0/0x0
[ 44.880795] input: SynPS/2 Synaptics TouchPad as /class/input/input2

Kernel can see this just fine -- so it's whatever writes xorg.conf

Changed in xserver-xorg-input-synaptics:
assignee: nobody → ubuntu-x-swat
Revision history for this message
mihai.ile (mihai.ile) wrote :

i can confirm this bun on my Acer Aspire 1694WLMi, on dapper flght 7 (on breezy touchpad worked great..
so:
mihai007@acer:/proc/bus/input$ cat devices
gives this output about touchpad:

I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/class/input/input4
H: Handlers=mouse1 event3 ts1
B: EV=b
B: KEY=6420 0 7000f 0 0 0 0 0 0 0 0
B: ABS=11000003

Is there a manual fix for this?? i would really appreciate...

Revision history for this message
mihai.ile (mihai.ile) wrote :

i just recieved an email from Nacho de los Rios and thanks to his solution touchpad works great:
edit /etc/X11/xorg.conf
Add this section below the ps2 mouse's
Section "InputDevice"
       Identifier "Synaptics Touchpad"
       Driver "synaptics"
       Option "SendCoreEvents" "true"
       Option "Device" "/dev/psaux"
       Option "Protocol" "auto-dev"
       Option "HorizScrollDelta" "0"
EndSection

then add:
    InputDevice "Synaptics Touchpad"
in the ServerLayout section, for example:
Section "ServerLayout"
       Identifier "Default Layout"
       Screen "Default Screen"
       InputDevice "Generic Keyboard"
       InputDevice "Synaptics Touchpad"
EndSection

restart and it should work at least for acer 1694wlmi laptops.

Revision history for this message
roots (roots) wrote :

doesn't work for me on acer 382tmi, any further suggestions?

Revision history for this message
roots (roots) wrote :

ah, forgot to mention, this is on dapper latest update as of 2006-06-02.

Revision history for this message
wizard (linuxpack) wrote :

The same here, although on Slackware 10.2.
The stock 2.6.13 kernel from the slackware instalation
disks was working perfectly.
The touchpad was detected as ImPS/2, and the "touch-and-drag".
was working ok.
A new compile of 2.6.16.20 broke the things.
The new kernel detected the touchpad as SynPS/2 and
the "touch-and-drag" was not functional.
After compiling the ps2 mouse support as module
(CONFIG_MOUSE_PS2=m) everything was ok.
I do not know why the thing was not working when
compiled into the kernel.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.