dx-packages team mailing list archive

[Daniel d'Andrada <daniel.dandrada@xxxxxxxxxxxxx>]

Excerpt from #xorg-devel:

"""
<dandrader> 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 sends touch events to both clientX and clientY
<daniels> dandrader: yes, events are delivered separately thorough master and slaves - i'd recommend not using slaves for anything at all
<dandrader> daniels, but I believe it should send only to clientY, and only once clientY rejects the touch sequence should clientX finally start receiving the touch events (replayed), right?
<daniels> dandrader: if both clients were listening on a master device, then you'd be right
<dandrader> daniels,  hmm got it. so what I'm seeing is the expected behavior then and I should modify clientX to select events on AllMasterDevices instead of on slaveDevice1
 daniels, is that it?
<daniels> dandrader: exactly
"""

So we have two problems here:
  1- touch ownership mechanics won't work in our situation as Qt is talking directly to the slave devices whereas unity7 is talking to the master devices.
   2- the xserver bug described in my previous comments where it gets confused with such situation and ends up with a borked internal state which ruins mouse pointer emulation

So if we could avoid the situation in item 1 (by changing either Qt or
unity7/"Open Input Fw Grail" code) we might (have to try it out to see)
circumvent the bug in item 2.

-- 
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 emulation from touch breaks with QML app.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Triaged
Status in “unity” package in Ubuntu:
  In Progress
Status in “xorg-server” package in Ubuntu:
  New

Bug description:
  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 check that the touchscreen works for moving windows
  2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1)
  3) Launch the camera app
  4) Touch once inside the camera-app window
  5) Use the touchscreen to drag the camera-app window

  Expected results:
  You can move the camera-app window using the touchscreen

  Actual results:
  You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen

  This only affects touchscreen input - mouse/touchpad input is not
  affected

  This affects all apps written with the SDK (I tried camera-app,
  gallery-app, reminders-app). It's 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Mon Apr 14 14:59:09 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-02 (132 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions