Unity System Compositor crash on Pocket Desktop disconnect

[kevin gunn]

I've seen 2 u-s-c crash instances
1) hitting the power button to blank the screen just as i was disconnecting the slimport cable
crash file: https://drive.google.com/open?id=0B4GvOYxwuvpFRHJsTzNrUEY5YkU
2) allowing the device to blank & sit for a long time (retention mode) and then disconnect slimport cable
crash file: https://drive.google.com/open?id=0B4GvOYxwuvpFYXJGbnNqSzFITnc

[kevin gunn (kgunn72)]

per alf on irc, thinks mir is potentially root of prob for 2)

[Daniel van Vugt (vanvugt)]

Kevin: Would you be able to resubmit those crash files using this technique (on the offending device) so we get can get all the dump info?

   ubuntu-bug <crashfile>

[Daniel van Vugt (vanvugt)]

POWERBUTTON_usr_sbin_unity-system-compositor.0.crash:
Stacktrace:
 #0 0xaf9fed54 in ?? ()
 No symbol table info available.
 #1 0xb644f080 in ?? () from /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.7
 No symbol table info available.
 #2 0xb644edaa in ?? () from /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.7
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)

---
RETENTION_usr_sbin_unity-system-compositor.0.crash:
Stacktrace:
 #0 0x00000000 in ?? ()
 No symbol table info available.
 #1 0xb6463080 in ?? () from /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.7
 No symbol table info available.
 #2 0xb6462daa in ?? () from /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.7
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)

We're lacking symbols and line number information right now. Try resubmitting the crash files using the 'ubuntu-bug' command.

[Daniel van Vugt (vanvugt)]

The Android platform was deleted from lp:mir at revision 4155.