[DRM/GBM] Killing (or crashing) Mir often leaves the screen blank and difficult to recover
Bug #1189770 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Medium
|
Alexandros Frantzis | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Killing (or crashing) Mir often leaves the screen blank and difficult to recover.
When this happens, the only way to get the screen back is to log in remotely (ssh) and run:
sudo chvt 7
Assuming you're running X still...
OLD DESCRIPTION:
When this happens, the only way to get the screen back is to switch to X (Ctrl+Alt+F7) and back again (Ctrl+Alt+F1).
I'm marking this as "regression" of bug 1170643, but I'm not sure that one ever was really fixed.
Related branches
lp://staging/~afrantzis/mir/fix-1189770
- Cemil Azizoglu (community): Approve
- Alan Griffiths: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Daniel van Vugt: Needs Fixing
- Alberto Aguirre (community): Approve
- Kevin DuBois (community): Approve
- Robert Carr (community): Approve
-
Diff: 405 lines (+197/-38)7 files modified3rd_party/android-deps/std/Thread.h (+14/-2)
include/server/mir/run_mir.h (+2/-0)
include/test/mir_test/fake_event_hub.h (+3/-0)
src/server/compositor/multi_threaded_compositor.cpp (+11/-0)
src/server/run_mir.cpp (+22/-0)
tests/acceptance-tests/test_server_shutdown.cpp (+135/-36)
tests/mir_test_doubles/fake_event_hub.cpp (+10/-0)
Changed in mir: | |
status: | New → Triaged |
Changed in mir: | |
importance: | High → Medium |
summary: |
- Killing (or crashing) Mir often leaves the screen blank and difficult to - recover + [DRM/GBM] Killing (or crashing) Mir often leaves the screen blank and + difficult to recover |
Changed in mir: | |
assignee: | nobody → Alexandros Frantzis (afrantzis) |
Changed in mir: | |
milestone: | none → 0.2.0 |
status: | Triaged → In Progress |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
i actually tested this last night - could not reproduce.
the word "often" was used.....any particular demo client ? or any guess at what kind of frequency ?
not a 13.10 issue