When running in nested mode, some information about the MirSurface class (e.g., the symbol table) in libunityapplicationplugin.so is resolved using libmirclient.so.7 'MirSurface', causing crashes:
$ grep 'binding.*_ZTV10MirSurface' ld-debug.txt
1978: binding file /usr/lib/i386-linux-gnu/libmirclient.so.7 [0] to /usr/lib/i386-linux-gnu/libmirclient.so.7 [0]: normal symbol `_ZTV10MirSurface'
1978: binding file /usr/lib/i386-linux-gnu/qt5/imports/Unity-Mir/Unity/Application/libunityapplicationplugin.so [0] to /usr/lib/i386-linux-gnu/libmirclient.so.7 [0]: normal symbol `_ZTV10MirSurface'
We either need to rename MirSurface to something else (e.g., QMirSurface), or preferably put unity-mir classes in a suitable namespace.
When running in nested mode, some information about the MirSurface class (e.g., the symbol table) in libunityapplica tionplugin. so is resolved using libmirclient.so.7 'MirSurface', causing crashes:
$ grep 'binding. *_ZTV10MirSurfa ce' ld-debug.txt i386-linux- gnu/libmirclien t.so.7 [0] to /usr/lib/ i386-linux- gnu/libmirclien t.so.7 [0]: normal symbol `_ZTV10MirSurface' i386-linux- gnu/qt5/ imports/ Unity-Mir/ Unity/Applicati on/libunityappl icationplugin. so [0] to /usr/lib/ i386-linux- gnu/libmirclien t.so.7 [0]: normal symbol `_ZTV10MirSurface'
1978: binding file /usr/lib/
1978: binding file /usr/lib/
We either need to rename MirSurface to something else (e.g., QMirSurface), or preferably put unity-mir classes in a suitable namespace.