unity8 killed/crash then restart can result in mir unable "could not unblank display"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Critical
|
Kevin DuBois | ||
Unity System Compositor |
Fix Released
|
High
|
Alberto Aguirre | ||
powerd |
Fix Released
|
Medium
|
Ricardo Mendoza | ||
unity-mir |
Fix Released
|
Medium
|
Gerry Boland |
Bug Description
Note - under normal use of unity/mir this phenomena is not seen (e.g. a user will never see it)
this bug is actually capturing the need for some type of re-initialization state of powerd as it relates to the restart of unity & mir.
for instance in the case where the system is under test, the problem is that if unity8 is killed (and in contagion mir), powerd may still change state independently - which can result in mir both being a) confused about the fb state & b) unable/no control to actually change the fb state
possible solutions
1) unity-mir needs to somehow reinit powerd into a "good state" for mir
or 2) mir needs to talk to powerd directly (altho this would mean contagious changes needed in mir)
related to this bug
https:/
WORKAROUND:
stop powerd
associated blueprint for a more complete solution
https:/
Related branches
- Didier Roche-Tolomelli: Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 61 lines (+11/-4)2 files modifiedsrc/display.c (+10/-3)
src/powerd-internal.h (+1/-1)
Changed in unity-mir: | |
assignee: | nobody → Gerry Boland (gerboland) |
status: | New → Triaged |
importance: | Undecided → High |
Changed in powerd: | |
status: | New → Opinion |
assignee: | nobody → Ricardo Mendoza (ricmm) |
description: | updated |
Changed in mir: | |
importance: | High → Critical |
Changed in unity-mir: | |
importance: | High → Critical |
description: | updated |
Changed in mir: | |
status: | Triaged → Fix Released |
Changed in unity-mir: | |
status: | Triaged → Fix Released |
I get the "Could not unblank display" occasionally on boot (reproduced with build #86), not only when unity8 crashes or is killed. That was reported as bug 1235000 and marked as duplicate of this report.