touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

OK, the first bug 1481570 has a fix up for review. That's faulty end-of-
multifinger gesture detection. Probably doesn't apply to Unity, just the
Mir demo server..

The second bug (the Mir part of this one) seems to be a simple matter of
faulty end-of-gesture detection introduced in r2652. The exact problem
seems to be the new SurfaceInputDispatcher::dispatch_touch gesture_owner
logic that was introduced. It assumes there's no shell that might
consume your touch events in handling app-switching gestures. If the
shell does correctly consume those touch events that triggered the app
switch then the gesture_owner logic introduced in r2652 doesn't work and
it keeps delivering touches to the old window (which is now hidden)
instead of the new one.

So that needs fixing in Mir. But it doesn't mean there aren't additional
timing bugs in other components after that... :/

** Changed in: mir
     Assignee: (unassigned) => Daniel van Vugt (vanvugt)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1480654

Title:
  [regression] Input focus delay after switching app back into focus
  since OTA5 (Mir 0.14)

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  i am not sure if it started with OTA4 or OTA5 but since one of the
  recent OTA upgrades my arale takes between half a second and one
  second before an app takes input again when one switches it from
  background back into focus. i'm talking about apps that were only
  sigstopped, not OOM killed here (i.e. no restart involved, just
  sigcont).

  this used to be instant before and gives a weird feeling of
  sluggishness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1480654/+subscriptions