touchpad/multitouch-automated does not run

Hello, could you please run, on the affected system:

xinput --list --long > xinput.log

then attach xinput.log to the bug?

With this we can see why the resource thinks it doesn't have a matching device.

If this can help, please find attached the xinput of another laptop that have the same issue.

OK, so the requirement needs this:

xinput.device_class == 'XITouchClass' and xinput.touch_mode == 'dependent'

No devices in the output of xinput_resource have XITouchClass :/ and this comes straight from xinput itself (I even checked the source xinput.log you provided).

From your xinput dump, I notice the pointing device is recognized as "PS/2 Generic Mouse", so I wonder if this is perhaps a configuration problem; for example, for my Dell laptop, I had to blacklist the i2c_hid module for the touchpad to be correctly recognized (it was seen as ps/2 mouse without that).

In any case, since the raw xinput --list information shows that xinput doesn't think the laptop has a multitouch-capable device, I don't think this is a bug in checkbox, since the device is reporting its capabilities incorrectly.

A question that could help here, in the "mouse & touchpad" control panel, is the device identified as a touchpad, or are the touchpad-specific options greyed out?

Thanks!

Yes, it looks like touchpad is recognized as mouse, as attached picture.

Hi Nara and Pierre,

In this case it's not a checkbox bug per se; the resource is reporting the capabilities as it sees them, and that's what the system is also reporting here.

We could try to work around this by also looking at the names of devices connected, and force running of the multitouch tests if a synaptics device is detected, as I don't think synaptics is producing non-multitouch devices anymore, but this would be making an assumption and I'm not too happy with that.

I wonder if maybe by loading some module (or removing a module, like the i2c_hid example I mentioned, this module needs to be blacklisted) we could get the touchpad recognized as multitouch. To verify this, load or remove modules, then restart the X server, and run:

xinput list --long |grep XITouch

it should show at least one device with XITouchClass

@Nara, Pierre

Would you please try vertical scroll of the touchpad?
I suppose they are failed as well now.

@taihsiang

Both vertical and horizontal scroll works well.

I am going to mark this bug as invalid, as the problem was that the touchpad was wrongly recognized as a mouse.

This should be a failure.

I have created a new bug to add a test for it: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1419759

For the units affected by this bug, they are OEM units, which installed OEM image, with proprietary driver installed.
It seems that Synaptics proprietary driver would set two device in xinput:
"syntp" and "PS/2 Generic Mouse"

#11 is the xinput output log

Test a fail system without synaptic proprietary driver. This issue can not be reproduced. There are 2 device with XITouchClass in xinput list --long. So it is a issue about Synaptic proprietary driver.

But the functions of touchpad are all workable. There is no affect to user usage. Since touchpad/singletouch-automated and touchpad/multitouch-automated are untested. The test cases which have dependency with above 2 can not be executed.
This should not be a cert-blocker because the functions are workable. And this does not affect user.

The only effects are 1) QA need to verify those functions manually when test results of the 2 test cases are untested. 2) when QA submit results to cert plan bugs, we need to have a note that touchpad functions are workable.

This is not efficiency and reliable.
For now, all touchpad on laptop should support multi-touch. It would be more convenient and reasonable to remove the dependency.