No, the exception was thrown by libmiral code [miral::BasicWindowManager::info_for()] and caused by synchronisation issues in QtMir code that have been worked around.
Neither the libmiral nor the QtMir code in question is involved in any of the mir-demos.
No, the exception was thrown by libmiral code [miral: :BasicWindowMan ager::info_ for()] and caused by synchronisation issues in QtMir code that have been worked around.
Neither the libmiral nor the QtMir code in question is involved in any of the mir-demos.