As discussed above, the nested server doesn't have enough information to
select the correct drivers and more work is needed on supplying this
from the host before this can be closed.
** Changed in: mir
Status: Fix Committed => Triaged
** Changed in: mir/0.18
Status: Fix Released => Triaged
--
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/1515558
Title:
[regression] Nested servers on mesa-kms select wrong (dummy) guest
platform
Status in Mir:
Triaged
Status in Mir 0.18 series:
Won't Fix
Status in mir package in Ubuntu:
Invalid
Bug description:
$ sudo bin/mir_demo_server --window-manager system-compositor
--display-config sidebyside --vt 1 --arw-file
$ bin/mir_demo_server --host /tmp/mir_socket --display-config clone
...
[1447325929.742637] mirserver: Selected driver: dummy (version 0.18.0)
Seems to be -c 3098 as specifying a dummy --vt parameter is a
workaround
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1515558/+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
