You can see this behaviour running Mir on Mir on the desktop. Run the
following in three terminals:
$ mir_demo_server --window-manager system-compositor --file /tmp/usc-socket
$ mir_demo_server --host /tmp/usc-socket --launch mir_demo_client_egltriangle
$ mirout /tmp/usc-socket rotate inverted
>From the "system-compositor" console we see:
[2017-08-22 10:03:26.875363] mirserver: New display configuration:
[2017-08-22 10:03:26.875375] mirserver: Output 1: unknown connected, used
[2017-08-22 10:03:26.875386] mirserver: Physical size 15.0" 317x211mm
[2017-08-22 10:03:26.875392] mirserver: Power is on
[2017-08-22 10:03:26.875398] mirserver: Current mode 1200x800 60.00Hz
[2017-08-22 10:03:26.875404] mirserver: Preferred mode 1200x800 60.00Hz
[2017-08-22 10:03:26.875410] mirserver: Orientation inverted
[2017-08-22 10:03:26.875416] mirserver: Logical size 1200x800
[2017-08-22 10:03:26.875421] mirserver: Logical position +0+0
[2017-08-22 10:03:26.875430] mirserver: New base display configuration:
[2017-08-22 10:03:26.875437] mirserver: Output 1: unknown connected, used
[2017-08-22 10:03:26.875443] mirserver: Physical size 15.0" 317x211mm
[2017-08-22 10:03:26.875449] mirserver: Power is on
[2017-08-22 10:03:26.875455] mirserver: Current mode 1200x800 60.00Hz
[2017-08-22 10:03:26.875461] mirserver: Preferred mode 1200x800 60.00Hz
[2017-08-22 10:03:26.875466] mirserver: Orientation inverted
[2017-08-22 10:03:26.875472] mirserver: Logical size 1200x800
[2017-08-22 10:03:26.875477] mirserver: Logical position +0+0
So the *base* configuration has been inverted, but now the nested
session re-applies its session configuration...
[2017-08-22 10:03:26.875746] mirserver: Session
nested-mir@:/run/user/1000/mir_socket applied display configuration
[2017-08-22 10:03:26.875757] mirserver: Output 1: unknown connected, used
[2017-08-22 10:03:26.875765] mirserver: Physical size 15.0" 317x211mm
[2017-08-22 10:03:26.875771] mirserver: Power is on
[2017-08-22 10:03:26.875776] mirserver: Current mode 1200x800 60.00Hz
[2017-08-22 10:03:26.875782] mirserver: Preferred mode 1200x800 60.00Hz
[2017-08-22 10:03:26.875794] mirserver: Orientation normal
[2017-08-22 10:03:26.875799] mirserver: Logical size 1200x800
[2017-08-22 10:03:26.875807] mirserver: Logical position +0+0
[2017-08-22 10:03:26.888480] GLRenderer: EGL vendor: Mesa Project
[2017-08-22 10:03:26.888512] GLRenderer: EGL version: 1.4 (DRI2)
[2017-08-22 10:03:26.888518] GLRenderer: EGL client APIs: OpenGL OpenGL_ES
[2017-08-22 10:03:26.888524] GLRenderer: GL vendor: Intel Open Source
Technology Center
[2017-08-22 10:03:26.888530] GLRenderer: GL renderer: Mesa DRI Intel(R)
Sandybridge Desktop
[2017-08-22 10:03:26.888535] GLRenderer: GL version: OpenGL ES 3.0 Mesa 17.0.7
[2017-08-22 10:03:26.888541] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00
[2017-08-22 10:03:26.888548] GLRenderer: GL max texture size = 8192
[2017-08-22 10:03:26.888564] GLRenderer: GL framebuffer bits: RGBA=,
depth=0, stencil=0
[2017-08-22 10:03:26.888673] mirserver: New display configuration:
[2017-08-22 10:03:26.888691] mirserver: Output 1: unknown connected, used
[2017-08-22 10:03:26.888703] mirserver: Physical size 15.0" 317x211mm
[2017-08-22 10:03:26.888715] mirserver: Power is on
[2017-08-22 10:03:26.888725] mirserver: Current mode 1200x800 60.00Hz
[2017-08-22 10:03:26.888733] mirserver: Preferred mode 1200x800 60.00Hz
[2017-08-22 10:03:26.888741] mirserver: Orientation normal
[2017-08-22 10:03:26.888749] mirserver: Logical size 1200x800
[2017-08-22 10:03:26.888757] mirserver: Logical position +0+0
I think this is "as designed": the display configuration of the active
client (in this case the nested Mir session) overrides the base.
You can see the inversion of the base configuration has really been like
this:
$ mir_demo_client_eglcounter -m /tmp/usc-socket -f -o 1
** Changed in: canonical-devices-system-image
Status: New => Invalid
** No longer affects: qtmir (Ubuntu)
** Changed in: mir
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669034
Title:
Display mode changes made directly to the system compositor are not
reflected in the nested Mir server
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669034/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
