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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions:
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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
ht
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
xserver mouse pointer
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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
xserver mouse
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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packa
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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-pack
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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
xserver mou
** 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
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
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
** 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 DX
Packages, wh
** 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: (
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-pa
@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 DX
Packages, which is subscribed
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 DX
Packages, which is subscribed to unity in
@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 DX
Packages, which is subsc
> 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
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?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https
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
> On my system the touchscreen keeps working after using a QML app. It
still gets gestures (e.g 3 fingers on the screen) but it won't work on
some windows. Furthermore, I can't drag windows by the decoration any
more.
Multifinger gestures keep working because they do not depend on
pointer/mouse ev
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
On my system the touchscreen keeps working after using a QML app. It
still gets gestures (e.g 3 fingers on the screen) but it won't work on
some windows. Furthermore, I can't drag windows by the decoration any
more.
--
You received this bug notification because you are a member of DX
Packages, wh
One thing that smells fishy is that the qml app starts getting touch
events even before compiz/unity7. I think that this should not happen as
the qml app does not subscribe for ownership events (unlike
compiz/unity7) and ownership is offered to compiz/unity7.
So the qml app should only get touch e
dandrader: That seems useful for making a testcase, thanks!
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
Unity does not get touch events
@Daniel, have you tried adding some qDebug() lines in the QT5 libraries
to see if we actually get the touch events and finally ungrab the
device? (the code is in
src/plugins/platforms/xcb/qxcbconnection_xi2.cpp)
Also, it would be interesting to see what XIGrabDevice and
XIUngrabDevice return.
--
Any QML application at all will do (such as "Item
{width:600;height:600}")
What seems to be happening, from what I've learned so far:
- user touches on a qml application
- xserver sends the resulting touch events to both the qmlscene and to
compiz/unity7
- xserver offers ownership to compiz/unit
** Changed in: unity (Ubuntu)
Assignee: Stephen M. Webb (bregma) => Daniel d'Andrada (dandrader)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Here is a test setup:
(1) install ubuntu-clock app
(2) modify /usr/share/gnome-session/sessions/ubuntu.session to remove the
'compiz;' entry so compiz gets started by upstart instead of gnome-session
(3) modify /usr/share/upstart/session/unity7.conf to add the following lines in
the pre-start sc
The problem does not occur in a Gnome Flashback (Compiz) session, so it
is evidently a result of the interaction between the XInput2 touch grabs
used in Unity 7 (through Geis), the passive Xinput touch subscriptions
in Qt, and the pointer emulation in x.org.
Multi-touch pointer emulation in XInput
hmm, and pointer emulation actually still works for other apps when
their windows are focused. You just can't focus them by tapping them.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
htt
So, when you run a QML app and tap on it, it seems that the mouse
pointer emulation dies but multitouch events still flow normally as
unity still responds to 3-finger (window drags, "alt-tab" switch) and
4-finger (show/hide dash, launcher drag) gestures
--
You received this bug notification becau
On a side note: multitouch in xorg is very problematic. Just now I had
to reboot my xps touch screen laptop because the mouse pointer emulation
logic no longer worked (pointer simply disappeared on touch). In another
attempt playing with multitouch, xserver simply crashed and I was sent
back to the
** Summary changed:
- Unity does not get touch events when SDK apps running
+ Unity does not get touch events when QML apps running
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://b
** Tags added: qa-touch
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
Unity does not get touch events when SDK apps running
Status in OEM
** Changed in: unity (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
Unity does not get tou
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority/trusty
Importance: Undecided => Critical
** Changed in: oem-priority/trusty
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of DX
Packages, which is
Olli reproduced this with a simple QML app
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
Unity does not get touch events when SDK apps run
also, happens with a non-SDK app, e.g. from http://qt-
project.org/doc/qt-5/qml-tutorial2.html
import QtQuick 2.0
Item {
id: container
property alias cellColor: rectangle.color
signal clicked(color cellColor)
width: 40; height: 25
Rectangle {
id: rectangle
bo
happens on the XPS12 too once you click _into_ an app
some more observations:
- once the bug is activated (by clicking into the touch app), all touch screen
events seem to be either discarded (when not in the app surface) or consumed
(when in app surface)
- closing the app releases the events an
** Changed in: unity (Ubuntu)
Assignee: (unassigned) => Stephen M. Webb (bregma)
** Changed in: unity (Ubuntu)
Importance: Undecided => High
** Changed in: oem-priority/trusty
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages,
can you reproduce on another touch screen? It seems to work fine on my
XPS12
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
Unity does not
** Tags removed: rls-t-incoming
** Tags added: desktop-touch
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1307701
Title:
Unity does not get touch events
Public bug reported:
When running an SDK app on the desktop, it's not possible to use the
touchscreen to move windows, use the launcher, etc. The SDK app seems to
consume all touchscreen events.
To reproduce:
1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install
14.04 and
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://b
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions
58 matches
Mail list logo
