upgrade to 1.3.99+git20110116.0e27ce3a-0ubuntu4 breaks touchpad

Same symptoms with an elderly HP Pavilion zv6000, w. ATI Radeon Xpress 200M (5955) graphics and Synaptics touchpad.

Affects both new and previous kernel (2.6.38-5 and 2.6.38-4).

Does the following indicate that the synaptics and evdev modules were not activated? I believe that oine or other of them should be used....This is the tail of the Xorg.0.log after the unsuccessful boot.

  181.206] (II) Power Button: Close
[ 181.206] (II) UnloadModule: "evdev"
[ 181.206] (II) Unloading evdev
[ 181.206] (II) Video Bus: Close
[ 181.206] (II) UnloadModule: "evdev"
[ 181.206] (II) Unloading evdev
[ 181.206] (II) Power Button: Close
[ 181.206] (II) UnloadModule: "evdev"
[ 181.206] (II) Unloading evdev
[ 181.206] (II) AT Translated Set 2 keyboard: Close
[ 181.206] (II) UnloadModule: "evdev"
[ 181.207] (II) Unloading evdev
[ 181.207] (II) UnloadModule: "synaptics"
[ 181.207] (II) Unloading synaptics
[ 181.207] (II) HP WMI hotkeys: Close
[ 181.207] (II) UnloadModule: "evdev"
[ 181.207] (II) Unloading evdev
[ 181.251] ddxSigGiveUp: Closing log

We're getting multiple confirmations of this bug.

Most likely culprit is the multitouch patches that went in today.

I've re-tested today's latest bits on three laptops all running natty, but can't reproduce the problem. Either it's HW-specific, or there's some other aspect / configuration needed to trigger the bug.

Chris and I combed through all the dmesg and Xorg.0.log's, ruled some ideas out but did not spot an obvious error message.

Next action for testers would be to attempt downgrading to the previous xserver. RAOF, would you mind outlining exactly what packages should be downgraded? (Attaching a bash script might save some re-typing).

Ok. None of your logs seem particularly suspicious, and I'm unable to reproduce this locally.

Could you please install the evtest and xinput packages, and run:
"""
sudo evtest /dev/input/event7
"""
and attach the output, then run
"""
xinput test "SynPS/2 Synaptics TouchPad"
"""
and try to move using the touchpad, and attach that output too?

For those who need to use their touchpad while we work out what's happening, here's a quick downgrade script that will temporarily drop you back to the previous versions of the X server, synaptics, and evdev.

Caution: this will break apt - “sudo apt-get -f install” should get apt to upgrade back into a coherent state with the newer, broken X, packages.

attaching evtest (not sure if any use) and the xinput, well no need, nothing happens, ie.
doug@doug-XPS-M1330:~$ xinput test "SynPS/2 Synaptics TouchPad"
that's it

So, an evtest listing of sabdfl's touchpad which also exhibits this problem is:
 ~/ $ sudo evtest /dev/input/event7
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x1b1
Input device name: "SynPS/2 Synaptics TouchPad"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 325 (ToolFinger)
    Event code 330 (Touch)
    Event code 333 (Tool Doubletap)
    Event code 334 (Tool Tripletap)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value 3505
      Min 1472
      Max 5472
    Event code 1 (Y)
      Value 4351
      Min 1408
      Max 4448
    Event code 24 (Pressure)
      Value 0
      Min 0
      Max 255
    Event code 28 (Tool Width)
      Value 0
      Min 0
      Max 15
Testing ... (interrupt to exit)

…which doesn't indicate a semi-multitouch touchpad, which means that's not the hardware difference between working and non-working systems.

What is a bit weird - did a reboot, re-ran evtest and got this

doug@doug-XPS-M1330:~$ sudo evtest /dev/input/event7
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x6 version 0x0
Input device name: "Video Bus"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 224 (Brightness down)
    Event code 225 (Brightness up)
    Event code 227 (?)
    Event code 241 (?)
    Event code 242 (?)
    Event code 243 (?)
    Event code 244 (?)
    Event code 245 (?)
Testing ... (interrupt to exit)

My evtest output:

bilal@bilal-laptop:~/Downloads$ sudo evtest /dev/input/event5
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x25b1
Input device name: "SynPS/2 Synaptics TouchPad"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 325 (ToolFinger)
    Event code 330 (Touch)
    Event code 333 (Tool Doubletap)
    Event code 334 (Tool Tripletap)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value 4235
      Min 1472
      Max 5472
    Event code 1 (Y)
      Value 2440
      Min 1408
      Max 4448
    Event code 24 (Pressure)
      Value 0
      Min 0
      Max 255
    Event code 28 (Tool Width)
      Value 0
      Min 0
      Max 15
Testing ... (interrupt to exit)

Lenovo T61
-
sudo evtest /dev/input/event7
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
Input device name: "TPPS/2 IBM TrackPoint"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 274 (MiddleBtn)
  Event type 2 (Relative)
    Event code 0 (X)
    Event code 1 (Y)
Testing ... (interrupt to exit)
-
Trackpoint is working ok.

It would be very helpful to be able to replay events from an affected device on a different computer. This is possible using utouch-evemu. Please do the following:

1. $ sudo apt-get install utouch-evemu-tools
2. Determine the /dev/input/event* node for your synaptics trackpad
  - You can search for synaptics in /var/log/Xorg.0.log to find the event node
3. Switch to a virtual terminal (VT) by pressing ctrl-alt-f1 or running $ sudo chvt 1
4. log in to the VT
5. $ sudo evemu-describe (insert event node here) > device.prop
6. $ sudo evemu-record (insert event node here) > device.record
7. Swipe a few times on the trackpad
8. Wait for evemu-record to finish
9. Switch back to X by pressing ctrl-alt-f7 or running $ sudo chvt 7 (If that doesn't work, try f8 or f9 or chvt 8 or chvt 9)

evemu-record will end when no activity has occurred for about 10 seconds. So after starting the recording, begin swiping within a few seconds. Then wait until the process finishes.

Attach the device.prop and device.record files to this bug. Check to be sure they

Thanks!

Here is a possible fix for the problem, for someone with 64bit. The package contains a tiny patch which makes utouch not interfere with traditional semi-mt touchpads. Please report back here.

Here are my device.prop and device.record.
Recorded according to Chase's instructions above.

--
Bilal Akhtar - Ubuntu Developer <email address hidden>
IRC nick: cdbs

For those interested, you can reproduce this issue by running:

1. $ sudo evemu-device device.prop
  - This will create a new /dev/input/event* node for the virtual device
2. $ sudo evemu-play (/dev/input/event* node from step 1) < device.record

The device files come from Bilal's attachments above.

It appears this is a bug triggered by a multi-finger, non-mt trackpad. Trackpads that do not give the number of fingers on the surface and multitouch trackpads are unaffected.

I verified that the fix in the debian package resolves the issue, so Bilal, if it does for you too, a new package will be on its way shortly.

Bugfix by Henrik Rydberg (#15) worked for me.

Fix released in upstream utouch-frame 1.1.1.

@RAOF - any chance of a downgrade script for amd64? Simply replacing -i386 with -amd64 in the four packages didn't cut it - I got four "File not found"s.

This bug was fixed in the package utouch-frame - 1.1.1-0ubuntu1

---------------
utouch-frame (1.1.1-0ubuntu1) natty; urgency=low

  [ Henrik Rydberg ]
  * New upstream release.
  * Fixing semi-mt entanglement (LP: #724051)
 -- Chase Douglas <email address hidden> Thu, 24 Feb 2011 11:16:48 -0500

Just manually downloaded the built deb and updated the package, and I can confirm that this is fixed.

Thanks Henrik and Chase.

This getting annoying. The "fixed" package, including libutouch-frame 1.1.1-0ubuntu1, is now available, but will not install without removing compiz and everything depending on it. Trying to remove it warns that xorg, xserver-xorg, xserver...synaptic and so on will be removed as well.

As I have an amd64 machine the script to downgrade doesn't help me; simply replacing -i386 by -amd64 gives me a script that generates "File not found" errors.

How can I go back to a situation where my trackpad works?

The problems you see are due to abi problems with other upgrades, and are not related to this package. You can use "sudo apt-get install libutouch-frame1" to upgrade only the package for the bugfix.

Sorry about the grump. In fact the fixed package does restore the trackpad functionality for me. The compiz-removal was because of an incomplete update that was happening coincidentally. But I was trying to deal with it in Synaptic, which doesn't work very well without a steerable pointer. Adding a USB mouse saved the day.

I am concerned, though, that experimental advances to bring in new functions should not make old functionality impossible to use.

"I am concerned, though, that experimental advances to bring in new functions should not make old functionality impossible to use."

Pretty sure people have been saying this since computer software first existed. ;-)

Anyway, your concern is noted. Some bugs are almost inevitable when doing original development. We're doing what we can to try and resolve issues promptly as they show up.

Touchpad still broken on an eeepc 1000h.

Initially the touchpad works... then something happens and it stops. You need a usb mouse at hand to save the day.

evtest gives

sudo evtest /dev/input/event8

Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x2 product 0xe version 0x0
Input device name: "ETPS/2 Elantech Touchpad"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 325 (ToolFinger)
    Event code 330 (Touch)
    Event code 333 (Tool Doubletap)
    Event code 334 (Tool Tripletap)
    Event code 335 (?)

  Event type 3 (Absolute)
    Event code 0 (X)
      Value 480
      Min 8
      Max 1144
    Event code 1 (Y)
      Value 452
      Min 8
      Max 760
    Event code 16 (Hat0X)
      Value 120
      Min 4
      Max 284
    Event code 17 (Hat0Y)
      Value 113
      Min 4
      Max 188
    Event code 18 (Hat1X)
      Value 217
      Min 4
      Max 284
    Event code 19 (Hat1Y)
      Value 113
      Min 4
      Max 188
Testing ... (interrupt to exit)

and nothing else (even moving the finger on the touchpad)

 xinput test "ETPS/2 Elantech Touchpad" gives no output at all.

Noticed that this bug is marked as "Fix Released" since latest libutouch-frame 1.1.1-0ubuntu1 probably fixes things on machines equipped with SynPS/2 Synaptics TouchPad.
Mine (EEEPC 1000H) has an Elantech touchpad and as already mentioned the proposed fix does not work on it.
What is best? Should I open a new bug report for the Elantech or can the present one be reopened?

@Sergio:

Yes, please open a new bug. This bug was about Synaptics touchpads while yours seems to be a much different issue.

When I try installing libutouch-frame1 it tells me I already have the latest version. But I still have a cursor that jumps around like crazy & intermittently locks up until I press Alt or Esc or some other key combination. I have a Synaptics touchpad, & am using 11.04 amd64.

I reinstalled Ubuntu 11.04 from scratch, and the touchpad now works correctly. So I think it was some parameter not correctly migrated from 10.10 to 11.04

In my case this is a fresh install of 11.04 amd64 on a brand new laptop. So it can't possibly be an upgrade issue.