could it be that you excluded mesa-kms from the build i.e. maybe by still having 'mesa' inside MIR_PLATFORM (CMakeCache.txt). Additionally the why is that log so short. It should mention the other drivers found.. so even if the MIR_PLATFORM is wrong android platform binary should be listed.
-- 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/1474720 Title: [regression] Mir servers crash on start-up. "dummy" graphics driver selected and then: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: [1437011956.469215] mirserver: Selected driver: dummy (version 0.15.0) [1437011956.492673] mirserver: Using software cursor [1437011956.493899] mirserver: Mir version 0.15.0 ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+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