Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.2.1, 5.4.0
-
None
-
Arch Linux with wayland 1.4.0 and weston 1.4.0
Qt release branch, qtwayland stable branch
Description
I noticed that touch was not working. First I found this problem https://codereview.qt-project.org/#change,77229 which prevented the touch device being registered. Second is that if I put a printf in QWaylandInputDevice::Touch::touch_frame I can see that it's never called. So I googled and found this
It's like never getting an EV_SYN from the evdev interface (but I can see SYN_REPORT with evtest). I wonder if we could get by without the touch_frame callback? Otherwise it sounds like Qt and weston will not get along unless weston is fixed to send it?
Attachments
Issue Links
- resulted in
-
QTBUG-66563 Wayland clients start responding to wl_touch.up before wl_touch.frame has been received
- Open
For Gerrit Dashboard: QTBUG-36602 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
93572,3 | Fix touch with Weston | 5.4 | qt/qtwayland | Status: MERGED | +2 | 0 |
93664,2 | Wayland: correct touch location | 5.4 | qt/qtwayland | Status: MERGED | +2 | 0 |