← Back to team overview

touch-packages team mailing list archive

[Bug 1359406] Re: mir should not composite/display buffers when an android driver calls ANativeWindow::cancelBuffer

 

Fix committed to lp:mir/0.7 at revision 1877, scheduled for release in
Mir 0.7.0

** Changed in: mir
    Milestone: 0.7.0 => 0.8.0

** Also affects: mir/0.7
   Importance: Undecided
       Status: New

** Changed in: mir/0.7
   Importance: Undecided => High

** Changed in: mir/0.7
       Status: New => Fix Committed

** Changed in: mir/0.7
    Milestone: None => 0.7.0

** Changed in: mir/0.7
     Assignee: (unassigned) => Alberto Aguirre (albaguirre)

** Also affects: mir (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

** Changed in: mir (Ubuntu)
       Status: New => Fix Committed

** Changed in: mir (Ubuntu)
       Status: Fix Committed => Triaged

-- 
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/1359406

Title:
  mir should not composite/display buffers when an android driver calls
  ANativeWindow::cancelBuffer

Status in Mir:
  Fix Committed
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  mir should not composite/display buffers submitted via the android
  platform ANativeWindow::cancelBuffer.

  Some android drivers (like the mali driver in nexus10) will  call
  ANativeWindow::cancelBuffer in the client side at the beginning so a
  blank frame gets posted.

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