That said, Mir 0.17.1 also fails but at least it fails for the right reason -- trying to use mesa-kms...
[1450666238.373712] mirserver: Selected driver: mesa-kms (version 0.17.1) ERROR: /build/mir-sTjxjQ/mir-0.17.1+16.04.20151105.1/src/platforms/mesa/server/common/display_helpers.cpp(256): Throw in function int mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const std::shared_ptr<mir::udev::Context>&) Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> > std::exception::what: Error opening DRM device 22, "Invalid argument"
So the behaviour seem in Mir 0.19 is a step backwards.
That said, Mir 0.17.1 also fails but at least it fails for the right reason -- trying to use mesa-kms...
[1450666238.373712] mirserver: Selected driver: mesa-kms (version 0.17.1) mir-sTjxjQ/ mir-0.17. 1+16.04. 20151105. 1/src/platforms /mesa/server/ common/ display_ helpers. cpp(256) : Throw in function int mir::graphics: :mesa:: helpers: :DRMHelper: :open_drm_ device( const std::shared_ ptr<mir: :udev:: Context> &) exception_ detail: :clone_ impl<boost: :exception_ detail: :error_ info_injector< std::runtime_ error> > :what: Error opening DRM device
ERROR: /build/
Dynamic exception type: boost::
std::exception:
22, "Invalid argument"
So the behaviour seem in Mir 0.19 is a step backwards.