Mir

Nested servers don't apply their display configuration at startup

Bug #1492269 reported by Alexandros Frantzis on 2015-09-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
High
Alan Griffiths
0.17
Fix Released
Undecided
Unassigned
mir (Ubuntu)
Undecided
Unassigned

Bug Description

A nested server has its own display configuration policy, which is applied to the display configuration it gets from the host at startup. However, that change is not propagate to the host server, leaving the two servers out of sync.

Note that subsequent configuration changes at the nested server are propagated to the host, it's only the initial config that is the problem.

Related branches

Changed in mir:
assignee: Alexandros Frantzis (afrantzis) → Alan Griffiths (alan-griffiths)
status: New → In Progress
importance: Undecided → High
milestone: none → 0.18.0
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.18.0

Changed in mir:
status: In Progress → Fix Committed
Changed in mir (Ubuntu):
status: New → Fix Released
Kevin DuBois (kdub) on 2015-12-22
Changed in mir:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers