Rendering/composition gets stopped early
Bug #1293896 reported by
kevin gunn
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Fix Released
|
Critical
|
Alberto Aguirre | ||
| mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| unity-mir (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
build 241 on mako
so i realize this is probably just a matter of tuning, not necessarily a true bug.
but for whatever reason, this seemed very consistent to get the browser to launch, due to my finger being on the browser icon - just after closing whatever app happens to be open.
you can see from the video the redraw of the dash occurs quickly, and how this might happen.
if i was quick to just tap it would not occur (but then also, sometimes the quick jab tap wouldn't register)
not the best video...but this is in effect what was happening.
Related branches
lp:~albaguirre/mir/fix-not-compositing-client-last-posted-buffer-trunk
- PS Jenkins bot (community): Approve (continuous-integration)
- kevin gunn (community): Approve
-
Diff: 13 lines (+1/-1)1 file modifiedsrc/server/compositor/rendering_operator.cpp (+1/-1)
lp:~albaguirre/mir/fix-not-compositing-last-client-posted-buffer
- Daniel van Vugt: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Alan Griffiths: Approve
-
Diff: 16 lines (+1/-1)1 file modifiedsrc/server/compositor/rendering_operator.cpp (+1/-1)
Revision history for this message
| Michał Sawicz (saviq) wrote | #1 |
| summary: |
- touch input for close app in running apps scope sometimes results in - browser launching + Rendering/composition gets stopped early |
| Changed in unity-mir (Ubuntu): | |
| status: | New → Invalid |
| Changed in mir (Ubuntu): | |
| status: | New → In Progress |
| assignee: | nobody → Alberto Aguirre (albaguirre) |
| Changed in unity8: | |
| status: | New → Invalid |
| affects: | unity8 → mir |
| Changed in mir: | |
| assignee: | nobody → Alberto Aguirre (albaguirre) |
| status: | Invalid → In Progress |
| milestone: | none → 0.1.8 |
| Changed in mir (Ubuntu): | |
| status: | In Progress → Triaged |
| status: | Triaged → Confirmed |
| assignee: | Alberto Aguirre (albaguirre) → nobody |
| Changed in mir: | |
| importance: | Undecided → Critical |
| Changed in mir (Ubuntu): | |
| status: | Confirmed → Fix Released |
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #2 |
| Changed in mir: | |
| status: | In Progress → Fix Committed |
| Changed in mir: | |
| status: | Fix Committed → Fix Released |
| status: | Fix Released → Fix Committed |
| Changed in mir: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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