touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

mir (0.16.0+15.10.20150921.1-0ubuntu1) wily; urgency=medium


** Also affects: mir (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: mir (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mir (Ubuntu)
       Status: New => Fix Released

-- 
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/1493741

Title:
  The MirDisplayConfiguration returned on the client can be incorrect -
  part 2

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Assume that a client is not the active session and reconfigures the
  display.

  The server receives a configure_display() request, notes the config
  the client wants to use and returns the current active display
  configuration.

  Note that it *does not*  change the display configuration.

  The client caches this "active" configuration and will return it from
  mir_connection_create_display_config().

  If the client later becomes the active session the display is
  reconfigured according to the request.

  But as no notification is sent to any clients (including the one that
  made the request) the old "active" configuration is still the one
  returned by  mir_connection_create_display_config().

  NB this is related to, but a different scenario to lp:1491937

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1493741/+subscriptions