** Changed in: xorg-server
Status: Confirmed => Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1307701
Title:
xserver mouse pointer emulation from touch breaks with QML app
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/i
When this fixed in 14.04 Trusty Tahr for 14.04.1 (24 July)?
Many "critical" bugs on ReleaseNotes Trusty Tahr page don't fixed presently:
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Known_issues
Installation bugs too:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1066480
https://bugs
** Changed in: oem-priority/trusty
Status: Fix Committed => Fix Released
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpa
This bug was fixed in the package qtbase-opensource-src - 5.2.1+dfsg-
1ubuntu14.2
---
qtbase-opensource-src (5.2.1+dfsg-1ubuntu14.2) trusty; urgency=medium
* debian/patches/xi2-use-master-device.patch:
- Make xi2 select events on master device instead of slaves.
(LP: #1307
The verification of the Stable Release Update for qtbase-opensource-src
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that y
** Changed in: oem-priority/trusty
Status: Triaged => Fix Committed
** Changed in: oem-priority
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/130
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1307701
Title:
xserver mouse pointer emulation from touch breaks with
I can no longer reproduce this with qtbase 5.2.1+dfsg-1ubuntu14.2 - nice
work!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1307701
Title:
xserver mouse pointer emulation from touch bre
Hello Steve, or anyone else affected,
Accepted qtbase-opensource-src into trusty-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/qtbase-opensource-src/5.2.1+dfsg-1ubuntu14.2 in a few hours, and then
in the -proposed repository.
Please help us by testi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bu
qtbase 5.2.1+dfsg-1ubuntu14.2 SRU for trusty is in unapproved queue now
too
(https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/b
This bug was fixed in the package qtbase-opensource-src - 5.2.1+dfsg-
1ubuntu17
---
qtbase-opensource-src (5.2.1+dfsg-1ubuntu17) utopic; urgency=medium
* Disable PCH also on arm64 in addition to armel/armhf (LP: #1318635)
-- Timo JyrinkiTue, 13 May 2014 04:37:13 +
** Chang
** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/qtbase-
opensource-src
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1307701
Title:
xserver mouse pointer emulation from touch b
** Also affects: xorg-server (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: unity (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: qtbase-opensource-src (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: qtbase-ope
Created attachment 98694
xorg-integration-tests testcase try 2
Ok so I've finally isolated the problem. The problem is the XIGrabDevice
on the slave pointer, which is only removed after the touch ends. When
this happens the ButtonRelease call for pointer emulation is never
generated, leading to th
Launchpad has imported 8 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=78345.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Maarten Lankhorst (mlankhorst)
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => High
** Changed in: xorg-server (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a me
Qt still XISelectEvents my "N-Trig Pen stylus" and "N-Trig Pen eraser"
slave devices though. But thankfully no events come from them and thus
peace is maintained :)
** Changed in: unity (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member
I confirm that the Qt from
https://launchpad.net/~canonical-x/+archive/x-staging does
XISelectEvents on the master pointer (instead of the touchscreen slave
device, as previously) and that the resulting behavior of the xserver is
good. Ie., touch ownership mechanics work properly and mouse pointer
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=78345
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which
** Package changed: xorg-server (Ubuntu) => qtbase-opensource-src
(Ubuntu)
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => High
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => In Progress
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (
@Daniel: thanks for taking the time to file an upstream bug report.
I have tested Maarten's latest work on the Qt library, and I can confirm that
it solves the issue on both tablets and non-tablets. Maarten's work is
available here (you only need to update the qt packages):
https://launchpad.net
And here's the upstream bug I reported:
https://bugs.freedesktop.org/show_bug.cgi?id=78345
** Bug watch added: freedesktop.org Bugzilla #78345
https://bugs.freedesktop.org/show_bug.cgi?id=78345
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I've just rebuilt Qt with a partial fix which only covers the "non-
tablet" test case, and I'm glad to report that it solves the problem.
Maarten is working on an all comprehensive fix.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server
@Stephen: I guess that means that your device passes the following
check:
if (tabletData.valuatorInfo.contains(QXcbAtom::AbsX) &&
tabletData.valuatorInfo.contains(QXcbAtom::AbsY) &&
tabletData.valuatorInfo.contains(QXcbAtom::AbsPressure))
which you can check using xinput list-props $dev
I think the XIDeviceEvent.sourceid would tell you from which device it
originates. The XIDeviceEvent.deviceid member would be set to the
master device, which might break things in a straight conversion.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
The code in Qt that subscribes to slave device events is the explicit
tablet-handling code. Checking the code, the touchscreen on my Dell XT2
is being treated as a tablet by the Qt code because it supports a stylus
mode on one of its alternate devices.
It sounds like the bug is in the Qt XCB QPA
> Is there a specific reason for calling XISelectEvents() for each
slave vs using XIAllMasterDevices in QXcbConnection::xi2Select() in Qt?
Would have to dig into Qt code to tell that. But my guess is that
because it exposes QTouchDevice objects to applications. For every
QTouchEvent you can get t
Is there a specific reason for calling XISelectEvents() for each slave
vs using XIAllMasterDevices in QXcbConnection::xi2Select() in Qt?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/130770
Excerpt from #xorg-devel:
"""
daniels, I've the following situation: clientX has a
XISelectEvents(TouchBegin|Update|End, childWindowA, slaveDevice1); clientY has
a XIPassiveGrabDevice(TouchBegin|Update|End|Ownership, rootWindow,
AllMasterDevices)
daniels, when a touch reaches xserver, it send
Attaching detailed xserver log. The following steps were taken:
1- sudo restart lightdm (to restart the X server. so that de have a clean slate)
2- run a very simple qml app with qmlscene
3- tapped on that qmlscene window (touch id 1)
4- tapped on the desktop area (nautilus) (touch id 2)
5- sudo s
xserver packages I used to take the logs above.
** Attachment added: "xserver debian packages with detailed logging of input
events"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/+attachment/4106288/+files/xorg_debug_packages.zip
--
You received this bug notification because
Took the liberty of correcting the bug title as unity does keep getting
touch events. It's the xserver mouse pointer emulation from touch events
that breaks badly.
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
34 matches
Mail list logo