** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-landing-049 -- 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: New 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