This bug was fixed in the package mir - 0.19.0+16.04.20160128-0ubuntu1
---------------
mir (0.19.0+16.04.20160128-0ubuntu1) xenial; urgency=medium
[ Brandon Schaefer ]
* New upstream release 0.19.0
- API summary:
. mirclient abi unchanged at 9
. mirserver abi bumped to 37
. mircommon abi unchanged at 5
. mirplatform abi unchanged at 11
. mirprotobuf abi unchanged at 3
. mirplatformgraphics abi bumped to 7
. mirclientplatform abi bumped to 4
. mirinputplatform abi bumped to 5
. mircookie abi bumped to 2
- Bug fix:
. Mir servers crash on mouse input (LP: #1528438)
. Pinch to zoom not working reliably (LP: #1531517)
. Passing DisplayConfiguration scale property from
nested server to host appears to not work (LP: #1535780)
. Various TSan reports when running test suite
on a mir tsan enabled build (LP: #1523647)
. Buffer leak during repeated mirscreencasts
causes server to be killed (LP: #1523900)
. Cursor now displays correctly (LP: #1526779)
.ProgramOption::parse_file() reports problems to cerr (LP: #1190165)
. Nested servers can select wrong platform (LP: #1515558)
. There seems to be missing RTTI information
when linking with UBSan enabled (LP: #1521930)
. Mir threadsanitizer build fails with GCC (LP: #1522581)
. After "make install" mir_demo_server cannot
find shared object file in /usr/local/lib (LP: #1522836)
. Fixed a test in TestClientInput (LP: #1523965)
. Mir servers choose graphics-dummy (or no driver at all)
over mesa-kms on a desktop (LP: #1528082)
. Function mir_event_get_close_surface_event is never used (LP: #1447690)
. mir::input::Surface::consume(MirEvent const& event)
should not take a reference to an opaque type (LP: #1450797)
. lintian: E: mir-doc: privacy-breach-logo (LP: #1483471)
[ CI Train Bot ]
* No-change rebuild.
-- Brandon Schaefer <ci-train-...@canonical.com> Thu, 28 Jan 2016
12:19:47 +0000
** Changed in: mir (Ubuntu)
Status: Triaged => 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/1528082
Title:
[regression] Mir servers choose graphics-dummy (or no driver at all)
over mesa-kms on a desktop
Status in Mir:
Fix Committed
Status in Mir 0.18 series:
Fix Committed
Status in mir package in Ubuntu:
Fix Released
Bug description:
Mir demo servers fail to start without additional help.
Running the latest code on a xenial system, I find the Mir demo
servers fail to start when run from ssh and I am logged into X (or on
the login screen):
[1450665937.536318] mirserver: Selected driver: dummy (version 0.19.0)
...
ERROR: /home/dan/bzr/mir/trunk/src/renderers/gl/renderer.cpp(51): Throw in
function
mir::renderer::gl::CurrentRenderTarget::CurrentRenderTarget(mir::graphics::DisplayBuffer*)
Dynamic exception type:
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error>
>
std::exception::what: DisplayBuffer does not support GL rendering
This is obviously wrong, because for Mir to choose the dummy driver
means mesa-kms has returned a platform priority of zero (unsupported).
Mesa-kms is not "unsupported", it's the right platform!
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1528082/+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
