The trigger is the X server resetting - this occurs when the last X client disconnects. This causes the root window to be destroyed and re-created. Thus the Mir surface is destroyed and then (attempted to be) recreated.
This occurs when running XMir inside a Unity 8 session, other cases that were tested were:
- Running XMir inside mir_demo_server (works fine)
- Running Unity 8 directly inside mir_demo_server (works fine)
In the normal use case the X server doesn't reset until you have completed using it - the window manager is constantly connected so the reset does not occur. For this reason this bug is not critical but worth investigating when we have the time.
The trigger is the X server resetting - this occurs when the last X client disconnects. This causes the root window to be destroyed and re-created. Thus the Mir surface is destroyed and then (attempted to be) recreated.
This occurs when running XMir inside a Unity 8 session, other cases that were tested were:
- Running XMir inside mir_demo_server (works fine)
- Running Unity 8 directly inside mir_demo_server (works fine)
In the normal use case the X server doesn't reset until you have completed using it - the window manager is constantly connected so the reset does not occur. For this reason this bug is not critical but worth investigating when we have the time.