This is caused by the most recent mir/unity-mir landing. From the video
above it's not that the initial input didn't get to the shell and the
app wasn't closed, but in fact it's the last few frames that were not
delivered to the display, resulting in you thinking that you're tapping
on the close button, when in fact you're tapping on the browser icon.
This can be observed in a few ways:
- after tapping close on an app, leave it be for a few seconds and see that
nothing happens until you touch the screen anywhere (e.g. start scrolling)
- after unlocking, wait for the infographics animation to stop, give it a few
seconds and touch the screen - at which point the last few items in the
infographic will show up again
** Summary changed:
- touch input for close app in running apps scope sometimes results in browser
launching
+ Rendering/composition gets stopped early
** Also affects: unity-mir (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293896
Title:
Rendering/composition gets stopped early
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8/+bug/1293896/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
