← Back to team overview

touch-packages team mailing list archive

[Bug 1398296] Re: Mir server crashes with "std::exception::what: Failed to get front buffer object" when trying to fullscreen a surface

 

mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium


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

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

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

Title:
  Mir server crashes with "std::exception::what: Failed to get front
  buffer object" when trying to fullscreen a surface

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir server crashes with "std::exception::what: Failed to get front
  buffer object" when trying to fullscreen/bypass a surface in
  multimonitor clone mode.

  ERROR: /home/dan/bzr/mir/fullscreen/src/platform/fatal/fatal.cpp(55): Throw in function void mir::fatal_error_except(const char*, ...)
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
  std::exception::what: Failed to get front buffer object

  Mesa only has a fixed limit of (four?) front framebuffer objects
  available. So somehow the combination of fullscreen bypass and
  multimonitor is making us ask for more than that... (?)

  Sorry I don't have a test case to reproduce it easily yet without
  using my own custom branch.

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