nested mir_demo_server crashes on startup
Bug #1570362 reported by
Andreas Pokorny
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Fix Released
|
High
|
Andreas Pokorny | ||
| mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Launch a mir_demo_server
sudo ./bin/mir_
and a nested one:
./bin/mir_
The nested server receives the input devices and attempts to access the Touchpad and Mouse configurations but does not ensure that the configuration is actually available. So it aborts in an attempt to access the content of the optional value. The configuration is missing since the client API for that has not yet been proposed..
Related branches
| description: | updated |
| Changed in mir: | |
| assignee: | nobody → Andreas Pokorny (andreas-pokorny) |
| Changed in mir: | |
| status: | New → Triaged |
| status: | Triaged → In Progress |
| importance: | Undecided → High |
| Changed in mir: | |
| milestone: | none → 0.22.0 |
Revision history for this message
| Mir CI Bot (mir-ci-bot) wrote | #1 |
| Changed in mir: | |
| status: | In Progress → Fix Committed |
| Changed in mir: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in mir (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.22.0