Bug 72841 - Unable to map touch device to output
Summary: Unable to map touch device to output
Status: VERIFIED INVALID
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-18 19:33 UTC by U. Artie Eoff
Modified: 2014-01-07 17:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
weston log (5.10 KB, text/plain)
2013-12-18 19:34 UTC, U. Artie Eoff
Details
weston udev rules (158 bytes, text/plain)
2013-12-18 19:38 UTC, U. Artie Eoff
Details

Description U. Artie Eoff 2013-12-18 19:33:21 UTC
Weston does not seem to honor WL_OUTPUT setting in udev rules anymore.  When WL_OUTPUT is specified, WAYLAND_DEBUG does not indicate any touch events occur when touching the device.  However, if I remove the WL_OUTPUT directive from the udev rules, WAYLAND_DEBUG shows touch events.

Reproduced with the following setup:

A calibrated single touchscreen device plugged into VGA1.
$ lsusb
  Bus 002 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen

kernel 3.11.10-301.fc20.x86_64
systemd (master) heads/master-0-g63966da
wayland (master) 1.3.91-0-g01bde63
drm (master) libdrm-2.4.50-0-g4c5de72
mesa (master) heads/master-0-ga9bf599
libva (master) libva-1.2.1-0-g88ed1eb
intel-driver (master) 1.2.1-0-g8f306e3
weston (master) heads/master-0-gdf42a80
Comment 1 U. Artie Eoff 2013-12-18 19:34:36 UTC
Created attachment 90944 [details]
weston log
Comment 2 U. Artie Eoff 2013-12-18 19:35:56 UTC
The weston log shows messages:

touch event received with 0 points downbut no surface focused

while occasionally getting a wl_touch@29.up(4, 120806958, 0) event.
Comment 3 U. Artie Eoff 2013-12-18 19:38:49 UTC
Created attachment 90945 [details]
weston udev rules
Comment 4 U. Artie Eoff 2013-12-18 20:05:14 UTC
Seems to work fine with a multitouch device
Comment 5 U. Artie Eoff 2014-01-07 17:07:55 UTC
Root caused this issue to a faulty single-touch display device.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.