mir-android-platform

Unity System Compositor crash on Pocket Desktop disconnect

Bug #1547523 reported by kevin gunn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Pocket Desktop
Won't Fix
High
Unassigned
Canonical System Image
Won't Fix
Undecided
kevin gunn
Mir
Won't Fix
High
Unassigned
Unity System Compositor
Won't Fix
High
Unassigned
mir-android-platform
New
Undecided
Unassigned
mir (Ubuntu)
Won't Fix
High
Unassigned
unity-system-compositor (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

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

See original description
Tags: android
kevin gunn (kgunn72)
description: updated
Changed in canonical-pocket-desktop:
importance: Undecided → High
Changed in unity-system-compositor (Ubuntu):
importance: Undecided → High
Revision history for this message
kevin gunn (kgunn72) wrote :

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

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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>

summary: - u-s-c crash on pd disconnect
+ Unity System Compositor crash on Pocket Desktop disconnect
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

Changed in mir:
importance: Undecided → High
Changed in unity-system-compositor:
importance: Undecided → High
Changed in mir (Ubuntu):
importance: Undecided → High
tags: added: android
Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
assignee: nobody → kevin gunn (kgunn72)
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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

Changed in mir:
status: New → Won't Fix
Changed in canonical-pocket-desktop:
status: New → Won't Fix
Changed in canonical-devices-system-image:
status: Incomplete → Won't Fix
Changed in unity-system-compositor:
status: New → Won't Fix
Changed in mir (Ubuntu):
status: New → Won't Fix
Changed in unity-system-compositor (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.