[android] std::exception::what: Failed to monitor fd: Operation not permitted when unplugging external display in a nested configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Alberto Aguirre | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Using the following nested configuration:
sudo mir_demo_server --arw-file --display-
mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir --display-config sidebyside --input-report log --legacy-
mir_demo_
The nested server occasionally crashes. Excerpt of the last lines in the log:
Input channel destroyed: name='Mir Fingerpaint', fd=34
[1443033760.712569] scene: surface_
Input channel destroyed: name='decoration', fd=38
[1443033760.712935] scene: surface_
[1443033760.713057] scene: surface_
[1443033760.721541] scene: surface_
ERROR: /build/
Dynamic exception type: N5boost16except
std::exception:
Related branches
- Alexandros Frantzis (community): Approve
- Daniel van Vugt: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 171 lines (+85/-22)2 files modifiedsrc/platforms/android/server/display.cpp (+14/-15)
tests/unit-tests/graphics/android/test_display.cpp (+71/-7)
Changed in mir: | |
status: | New → In Progress |
assignee: | nobody → Alberto Aguirre (albaguirre) |
Changed in mir: | |
status: | Fix Committed → Fix Released |
This may be related to https:/ /bugs.launchpad .net/mir/ +bug/1501927
mir 0.16 and lp:mir had better "symptomps" but it all pointed to accessing dead objects which can cause all sort of havoc.