Comment 15 for bug 1290416

The stack trace in comment 9 reveals the problem [Thread 22 (Thread 0xad8ff450 (LWP 2105)):]. An exception has happened (somewhere!?) and Mir is in the process of unwinding and exiting cleanly. However this process is blocked in unity-mir. Obviously it should not block.

So the first problem we can see is that unity-mir's SessionListener::stopping() is hung and failing to return. The second problem seems like it was probably an exception but we can't tell what that was. A stdout/err log from unity8 would help. But what would help more would be for unity-mir to not hang in this situation so we can probably get a crash and core file.