New issue
Advanced search Search tips

Issue 350630 link

Starred by 7 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

x11 touch not enabled for Xinput2 "slave pointers"

Reported by chadm...@gmail.com, Mar 8 2014

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/33.0.1750.146 Chrome/33.0.1750.146 Safari/537.36

Steps to reproduce the problem:
Compile in touchui. Have a touchscreen with xinput "slave pointer". 

What is the expected behavior?
It should process touch events. It doesn't.

What went wrong?
Get mouse focus events, but all touch events are discarded.

Did this work before? No 

Chrome version: 35  Channel: dev
OS Version: Ubuntu 13.10
Flash Version:
 
Labels: Needs-Feedback
@chadmill, can you please elaborate the steps to reproduce so that we can try to reproduce it at our end ?

Comment 2 by chadm...@gmail.com, Mar 10 2014

pucchaka, sure. 

Have hardware like this:
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ eGalax Inc. eGalaxTouch EXC7910-1057-13.00.00	id=10	[slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=11	[slave  keyboard (3)]

Use touch "clicks" or gestures.  Have them not be handled.

I only created this bug report to track a change I submitted for review. Maybe the help I need is in making sure I asked for reviews correctly?

https://codereview.chromium.org/189513008/

Comment 3 by Deleted ...@, Mar 16 2014

I believe I'm suffering of the same issue.
I'm dealing with an embedded device with a touchscreen display.
My software stack is made up of:
1) Linux kernel 3.1.10 (Linux 4 Tegra)
2) Ubuntu Core 13.10
3) Xorg 1.14
4) matchbox-window-manager
5) Chromium 32

This is the output of xinput:

Virtual core pointer id=2                          [master pointer (3)]
    Virtual core XTEST pointer id=4                [slave pointer (2)]
    Logitech USB Receiver id=8                     [slave pointer (2)]
    Pixcir Tango C48 Touchscreen Controller id=9   [slave pointer (2)]
Virtual core keyboard id=3                         [master keyboard (2)]
    Virtual core XTEST keyboard id=5               [slave keyboard (3)]
    gpio-keys id=6                                 [slave keyboard (3)]
    Logitech USB Receiver id=7                     [slave keyboard (3)]

If I run evtest inside the matchbox window manager and xterm I can see up to 5 touch events at the same time (the touchscreen display employ a Pixcir Tango C48, which supports up to 5 touch events). The same stands for xinput test-xi2.
However, when I run Chromium, the touchscreen behaves exactly like a simple mouse and not like a multitouch display.

Comment 4 by Deleted ...@, Jul 4 2014

Have same issue.
Ubuntu 14.04 on ThinkPad Twist s230u.
Kernel 3.13.0-24-generic
X.Org X Server 1.15.1
Google Chrome 36.0.1985.103 beta

xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Atmel Atmel maXTouch Digitizer            id=9    [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=12   [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                     id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Integrated Camera                         id=10   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=11   [slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                    id=14   [slave  keyboard (3)]

Touch screen in Chrome doesn't work at all. Mouse pointer is moving, but click on links does nothing, click on close tab 'x' does nothing, etc...
I'm using an eGalaxTouch capacitive touch screen.

I just upgraded to Trusty (chromium-browser v31 -> v34) and noticed all kinds of weirdness. mousemove no longer worked smoothly, and some multitouch gestures were added? Also sometimes a right-click could be triggered that then made clicking wonky.

Running google-chrome (stable) on v35 was even worse - by default only mousemove was supported (click events no longer showed up). I was able to use --touch-events=enabled and --touch-devices to get things working like v34 but with the same issues.

At the end of the day I found a 3rd party Trusty repo that had v31 and installed that version.

Comment 6 by Deleted ...@, Sep 23 2014

same behavior on Ubuntu 14.04 arm Version 37.0.2062.94 Ubuntu 14.04 (290621).
A mouse needs to be connected to use the menu.
On the touchscreen (HP S230tm with multitouch driver) I can tap on the menu button to open the menu.
I cannot select a menu entry by tapping on it.

It is possible to select an entry (that it gets blue) by sliding in with a finger from outside the open menu onto a menu entry. This will make it selected (blue) but the click event is missing. 
To continue at this point I need to click with a mouse or press enter on the keyboard.


 

Comment 7 by chadm...@gmail.com, Sep 23 2014

schiffsr <schiffsr...@gmail.com>, it would help if you compared to native
Ubuntu package "chromium-browser". Ubuntu carries a patch that tries to fix
this problem, and it would be helpful to know if it works.
I have this problem as well. As long as I name the touch device on the command line everything works EXCEPT any menu selections. It appears that Chrome assumes KDE/X will handle the click and X is assuming Chrome will. Loading chromium-browser from the Utopic (14.10) final beta repos did not make any difference. The menus will not touch although they work fine with mouse or keyboard.

By the way, the following script is useful if your touchscreen doesn't always enumerate as the same device. Just replace maXTouch with whatever your screen shows in the xinput list.

#!/bin/bash
SCREEN=`xinput list | awk '/maXTouch/ { gsub(".*id=",""); print $1 }
'`
exec google-chrome-beta --touch-devices=$SCREEN

This has suddenly stopped working but don't know why. Just to be complete you can also set options like this:

export CHROMIUM_USER_FLAGS=--touch-devices=10   

(or whatever)
Labels: TE-NeedsTriageFromMTV
The issue talks about Linux touch machines, could anyone from MTV give a try.
Project Member

Comment 12 by sheriffbot@chromium.org, Mar 10 2016

Labels: -Needs-Feedback Needs-Review
Owner: pucchakayala@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "pucchakayala@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Assigned)
I am assuming this issue got resolved from your end on Latest Chrome Stable# 50.0.2661.94 and marking 'WontFix' as of now. Please feel free to file a new bug for any further issues with chrome in future.

Sign in to add a comment