Spoke too soon. It seems the bug reproducible using lp:mir is even worse than the original bug seen with Unity. Using lp:mir you see all the bugs...
1. Focus switch does not occur immediately. You need to start and finish a new gesture before it takes effect (e.g. touch the screen). 2. When the new window eventually comes on top, you still can't interact with it. Not until you do yet another gesture (e.g. touch the screen and release). After that, you can finally interact with the new window. So that's starting to sound like High severity. Although it doesn't appear to be as bad on arale when running Unity (yet). -- 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
