It would be good to get a log with MIR_SERVER_WINDOW_MANAGEMENT_TRACE=on as that ought to log the operation that propagates the exception.
Investigating this with miral-app: the server doesn't crash and nor does the client.
Which is suggestive of a QtMir issue. However, the server fails to shut down after this experiment which clearly can't be QtMir.
It would be good to get a log with MIR_SERVER_ WINDOW_ MANAGEMENT_ TRACE=on as that ought to log the operation that propagates the exception.
Investigating this with miral-app: the server doesn't crash and nor does the client.
Which is suggestive of a QtMir issue. However, the server fails to shut down after this experiment which clearly can't be QtMir.