--launch-client option locks up DRM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Alexandros Frantzis | ||
mir (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
$ sudo bin/mir_
[Exit server using e.g. Ctrl+Alt+Backspace]
$ sudo bin/mir_
ERROR: /home/alan/
Dynamic exception type: boost::
std::exception:
-22, "Unknown error -22"
The problem doesn't arise if starting the client separately. So I guess using "system()" to start it allows too much to leak between processes.
NB this issue also blocks switching back to X
Related branches
- Daniel van Vugt: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Alan Griffiths: Approve
-
Diff: 221 lines (+89/-10)7 files modifiedinclude/test/mir_test_doubles/mock_drm.h (+1/-0)
src/platform/graphics/mesa/display_helpers.cpp (+8/-1)
tests/mir_test_doubles/mock_drm.cpp (+7/-4)
tests/unit-tests/graphics/mesa/CMakeLists.txt (+1/-0)
tests/unit-tests/graphics/mesa/test_display.cpp (+1/-1)
tests/unit-tests/graphics/mesa/test_drm_helper.cpp (+65/-0)
tests/unit-tests/graphics/mesa/test_platform.cpp (+6/-4)
affects: | mir (Ubuntu) → mir |
Changed in mir: | |
importance: | Undecided → High |
status: | New → Triaged |
summary: |
- "mir_demo_basic_server --launch-client" locks up DRM + --launch-client option locks up DRM |
Changed in mir: | |
status: | Fix Committed → Fix Released |
The problem can be avoided by ensuring that the client exits before the server.