Mir fails to start on Nexus 10 - std::exception::what: Could not unblank display
Bug #1203268 reported by
Roman Zonov
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Medium
|
Kevin DuBois | ||
mir (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
http://
Only 3 of 4 Nexus devices can use Mir instead of surfaceflinger.
And it fails to start because display is already unblanked (error by hwcomposer).
Related branches
lp://qastaging/~kdub/mir/n10-support
- Daniel van Vugt: Approve (manual testing)
- PS Jenkins bot (community): Approve (continuous-integration)
- Alexandros Frantzis (community): Approve
- Alan Griffiths: Approve
-
Diff: 2330 lines (+686/-615)36 files modifiedinclude/shared/mir/graphics/android/mir_native_window.h (+1/-0)
include/test/mir_test_doubles/mock_display_device.h (+1/-2)
include/test/mir_test_doubles/mock_framebuffer_bundle.h (+50/-0)
include/test/mir_test_doubles/mock_hwc_composer_device_1.h (+20/-4)
include/test/mir_test_doubles/stub_display_device.h (+4/-2)
src/server/graphics/android/CMakeLists.txt (+1/-1)
src/server/graphics/android/android_buffer_allocator.cpp (+1/-1)
src/server/graphics/android/android_graphic_buffer_allocator.h (+1/-1)
src/server/graphics/android/display_device.h (+4/-3)
src/server/graphics/android/fb_device.cpp (+18/-13)
src/server/graphics/android/fb_device.h (+5/-1)
src/server/graphics/android/framebuffer_bundle.h (+16/-11)
src/server/graphics/android/framebuffers.cpp (+116/-10)
src/server/graphics/android/framebuffers.h (+18/-13)
src/server/graphics/android/graphic_buffer_allocator.h (+1/-1)
src/server/graphics/android/hwc10_device.cpp (+6/-12)
src/server/graphics/android/hwc10_device.h (+6/-4)
src/server/graphics/android/hwc11_device.cpp (+27/-81)
src/server/graphics/android/hwc11_device.h (+8/-5)
src/server/graphics/android/hwc_layerlist.cpp (+8/-0)
src/server/graphics/android/hwc_layerlist.h (+3/-0)
src/server/graphics/android/resource_factory.cpp (+8/-14)
src/server/graphics/android/server_render_window.cpp (+6/-10)
src/server/graphics/android/server_render_window.h (+1/-4)
src/shared/graphics/android/mir_native_window.cpp (+9/-3)
tests/integration-tests/client/test_client_render.cpp (+4/-4)
tests/integration-tests/graphics/android/test_display_integration.cpp (+7/-0)
tests/unit-tests/client/android/test_android_native_window.cpp (+7/-3)
tests/unit-tests/graphics/android/test_fb_device.cpp (+31/-59)
tests/unit-tests/graphics/android/test_fb_simple_swapper.cpp (+179/-106)
tests/unit-tests/graphics/android/test_hwc10_device.cpp (+17/-15)
tests/unit-tests/graphics/android/test_hwc11_device.cpp (+62/-166)
tests/unit-tests/graphics/android/test_hwc_device.cpp (+2/-2)
tests/unit-tests/graphics/android/test_hwc_layerlist.cpp (+24/-3)
tests/unit-tests/graphics/android/test_resource_factory.cpp (+2/-33)
tests/unit-tests/graphics/android/test_server_interpreter.cpp (+12/-28)
Changed in mir: | |
status: | Triaged → New |
Changed in mir: | |
status: | New → Triaged |
summary: |
- Mir not works on Nexus 10 + Mir does not work on Nexus 10 |
tags: | added: nexus10 |
summary: |
- Mir fails to start on Nexus 10 as display is already unblanked + Mir fails to start on Nexus 10 - std::exception::what: Could not unblank + display |
Changed in mir (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Changed in mir: | |
status: | Triaged → Fix Committed |
Changed in mir: | |
milestone: | none → 0.1.2 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
Changed in mir (Ubuntu): | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
Kevin has been working on this as a low priority.