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/1491937
Title:
The MirDisplayConfiguration returned on the client can be incorrect
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
Fix Released
Bug description:
Assume that a client has the active surface and reconfigures the
display.
The server receives a configure_display() request, queues a change to
be executed on the main loop, and returns the current active display
configuration.
Note that it *does not* wait for the main loop to service the change
request so the active configuration can be the one prior to the
change.
The client caches this configuration and will return it from
mir_connection_create_display_config().
One might hope the client would get a notification via
mir_connection_set_display_config_change_callback() when the config is
actually updated, but that doesn't happen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1491937/+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
