touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #126363
[Bug 1518317] Re: Client display configuration is not unapplied when the client doesn't explicitly release its surfaces before disconnecting
** Changed in: mir (Ubuntu)
Importance: Undecided => High
** 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/1518317
Title:
Client display configuration is not unapplied when the client doesn't
explicitly release its surfaces before disconnecting
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
Fix Released
Bug description:
Steps to reproduce (with latest lp:mir r3112):
With multiple screens connected do:
1. bin/mir_demo_server --arw-file // Screens should be in clone mode by default
2. bin/mir_demo_client_display_config -m /tmp/mir_socket
3. Press the 'h' key // Screen should be arranged side-by-side
4. killall -9 mir_demo_client_display_config.bin
Expected: After client is killed the screen should go back to clone mode
Actual: Screens stay in side-by-side mode
Note that if the client terminates normally (e.g. killall
mir_demo_client_display_config.bin) the display configuration is
changed as expected.
Investigation indicates that the problem does not occur only when the
connection is closed abruptly, but in all case where the client
doesn't explicitly release its surface before disconnecting (either
abruptly or normally). To replicate this with a normal disconnection
scenario temporarily remove the mir_surface_release_sync() from
eglapp.cpp, recompile, follow steps 1-3 from above and terminate the
client normally.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1518317/+subscriptions