System auto log out when running touchscreen/3-touch-tap or 4-touch-tap

[Scott Hu]

1. Run touchscreen/3-touch-tap test

[Actual result]
System auto log out when running touchscreen/3-touch-tap

[Expected result]
System should not auto log out

[Jerry Kao (jerry.kao)]

Please set importance as "High"

[Po-Hsu Lin (cypressyew)]

Looks like a possible duplicate of bug 1471727

[Pierre Equoy (pieq)]

This does not happen all the time, but enough to make this test quite annoying to pass.

The problem is related to Compiz.

In order to run this test tool, we need to deactivate the Unity Shell temporarily, or else 3-finger tap or 4-finger tap would trigger respectively window move/resize and Dash display. When we re-enable them, it looks like the `manage_compiz_plugin` script crashes the X session, which makes the X session to restart.

The easiest way to avoid this would be to switch back to a manual test for both 3-finger tap and 4-finger tap jobs.

[Jerry Kao (jerry.kao)]

@Pierre

Agree the easiest way is to test manually. But the problem is how to identify the 3-touch-tap and 4-touch-tap are working.

There is no definition about 3-touch-tap gesture in Ubuntu. I can trigger window move/resize when 3-finger tap a window on a touchscreen AIO (JAS-SKL). But if not, should we consider it is a blocker as test case touchscreen/3-touch-tap?

The same as 4-touch-tap. Ubuntu does define 4-finger-tap as "open or close Dash" and we have a test case already. But it is not a blocker test case. We can use touchscreen/multitouch-dash to replace 4-touch-tap, but if the system fail with this case, should it be a critical issue?

We may can use touchscreen/multitouch-dash to replace both 3-touch-tap and 4-touch-tap tests. And change the certification status of touchscreen/multitouch-dash as blocker.

[Po-Hsu Lin (cypressyew)]

Please ignore comment #3, it should be bug 1482176, the one already marked as duplicated.

[Pierre Equoy (pieq)]

In the end, we modified the job so that it gives more time to the script to finish.

This was tested on the faulty device as well as on another one and it seems to work well.

No need to write manual test :)

→ Fixed