touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #126418
[Bug 1515558] Re: [regression] Nested servers on mesa-kms select wrong (dummy) guest platform
** Changed in: mir
Status: Triaged => In Progress
** Changed in: mir
Assignee: Mir development team (mir-team) => Alan Griffiths (alan-griffiths)
** Summary changed:
- [regression] Nested servers on mesa-kms select wrong (dummy) guest platform
+ [regression] Nested servers can select wrong platform
** Description changed:
+ Nested servers do not have the information required to deduce which
+ platform has been selected by the host server. (The host may be a
+ different user with different permissions, with different environment
+ variables and different command-line options.)
+
+ Original scenario:
+
$ 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
+ $ 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
--
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 can select wrong platform
Status in Mir:
In Progress
Status in Mir 0.18 series:
Won't Fix
Status in mir package in Ubuntu:
Invalid
Bug description:
Nested servers do not have the information required to deduce which
platform has been selected by the host server. (The host may be a
different user with different permissions, with different environment
variables and different command-line options.)
Original scenario:
$ 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