nexus10: unity-system-compositor crashes while turning display on with power key [std::exception::what: error turning display on. rc = fffffff0]

Bug #1478231 reported by Andreas Pokorny
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Won't Fix
Medium
Unassigned
mir-android-platform
New
Undecided
Unassigned
mir (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

unity-system-compositor-log (still on top of 0.13.3 - without 0.14.0) with exception that causes the crash:

[1437824578.379250] mirplatform: Found graphics driver: android
[1437824578.379366] mirplatform: Found graphics driver: dummy
[1437824578.390219] Server: Starting
[1437824578.393296] Loader: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/server-platform
[1437824578.393433] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-stub.so
[1437824578.394298] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.2
[1437824578.394348] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-dummy.so
[1437824578.399155] mirplatform: Found graphics driver: android
[1437824578.399198] mirplatform: Found graphics driver: dummy
[1437824578.399436] Platform Loader: Selected driver: android (version 0.13.3)
[1437824579.150982] mirserver: Using software cursor
GL_VENDOR = ARM
GL_RENDERER = Mali-T604
GL_VERSION = OpenGL ES 3.0
dm_connection_start
[1437824579.197658] GL: vendor: ARM
[1437824579.197683] GL: renderer: Mali-T604
[1437824579.197691] GL: version: OpenGL ES 3.0
[1437824579.197699] GL: SL version: OpenGL ES GLSL ES 3.00
[1437824579.197712] GL: max texture size = 8192
[1437824579.197735] GL: framebuffer bits: RGBA=8888, depth=0, stencil=0
[1437824579.203708] DisplayServer: Mir version 0.13.3
set_active_session 'session-0'
Opening session eglspinner
Opening session session-0
Closing session session-0
Opening session session-0
Closing session eglspinner
Current active output is 2560x1600 +0+0
Server supports 3 of 6 surface pixel formats. Using format: 1
Signal 15 received. Good night.
Closing session session-0
ERROR: /build/buildd/mir-0.13.3+15.04.20150617/src/platforms/android/server/real_hwc_wrapper.cpp(156): Throw in function virtual void mir::graphics::android::RealHwcWrapper::display_on(mir::graphics::android::DisplayName) const
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
std::exception::what: error turning display on. rc = fffffff0

Can't get connection

A manual restart of lightdm resolves the issue. usc starts up fine and is able to turn the display on. Sometimes afer waiting long enough lightdm seems to become aware of the situation and respawns unity-system-compositor. So we might derive another bug for lightdm - as it takes far too long to detect the crash.

I havent tried yet 0.14.0 - but it should happen there too.

Tags: android
Revision history for this message
Andreas Pokorny (andreas-pokorny) wrote :

The restarting sometimes seems to fail too. I just left the device alone for a few minutes, and the backlight started to flash.

Revision history for this message
Andreas Pokorny (andreas-pokorny) wrote : Re: nexus10: unity-system-compositor crashes while turning display on with power key

Oh seems like I have fix/workaround.

summary: - unity-system-compositor crashes while turning display on with power key
+ nexus10: unity-system-compositor crashes while turning display on with
+ power key
Changed in mir:
assignee: nobody → Andreas Pokorny (andreas-pokorny)
importance: Undecided → Critical
milestone: none → 0.15.0
tags: added: android
summary: nexus10: unity-system-compositor crashes while turning display on with
- power key
+ power key [std::exception::what: error turning display on. rc =
+ fffffff0]
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I can only seem to get channel "devel" (vivid) booting on the Nexus 10. Any trick to getting devel-proposed (wily) going? Do I need to do a manual command-line dist upgrade?

Revision history for this message
Kevin DuBois (kdub) wrote :

what is the fix?

Revision history for this message
Kevin DuBois (kdub) wrote :

also, nexus 10 has a low need for support right now, maybe 'high' is a better priority, if it only affects this particular device.

Revision history for this message
kevin gunn (kgunn72) wrote :

yeah, nexus10 is not a hard reference target. I believe foundation team considers it 'unofficial' in fact.

Changed in mir:
importance: Critical → High
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Our wikis suggest Nexus 10 is a first class device still. I'm not sure that's accurate...
https://developer.ubuntu.com/en/start/ubuntu-for-devices/devices/
https://wiki.ubuntu.com/Touch/Devices

Changed in mir:
milestone: 0.15.0 → 0.16.0
Changed in mir:
milestone: 0.16.0 → 0.17.0
Changed in mir:
assignee: Andreas Pokorny (andreas-pokorny) → nobody
Revision history for this message
Andreas Pokorny (andreas-pokorny) wrote :

@kdub: Adding something to not throwing but log the failure to blank.. This made the system successfully turn the screen on and off but after a time it still started to flicker..

Changed in mir:
milestone: 0.17.0 → 0.18.0
Kevin DuBois (kdub)
Changed in mir:
milestone: 0.18.0 → 0.19.0
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Dropped importance. N10 is likely not a supported device. And nobody seems to have a problem with this bug having been mostly ignored for over 100 days.

Changed in mir:
importance: High → Medium
milestone: 0.19.0 → none
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 mir (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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