Comment 10 for bug 1511538
Revision history for this message
| Alan Griffiths (alan-griffiths) wrote | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
This sounds like the cumulative effect of a number of Mir bugs in the display configuration handling that resulted in the surfaces composited by a nested server appearing in the wrong place.
It is plausible that the fixes landed up to -r3056 have resolved this (they certainly address Mir issues in this area) - but I was waiting for the 0.18 release to test with the full stack.