Unity8 (QtMir) crashed (on login or display change) in TiledDisplayConfigurationPolicy::apply_to() [tileddisplayconfigurationpolicy.cpp:41]
Bug #1560497 reported by
errors.ubuntu.com bug bridge
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtmir (Ubuntu) |
Fix Released
|
High
|
Daniel van Vugt | ||
unity8 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+16.
Related branches
lp:~vanvugt/qtmir/fix-1560497
- Gerry Boland (community): Approve
- Unity8 CI Bot (community): Needs Fixing (continuous-integration)
- Unity Team: Pending requested
-
Diff: 12 lines (+1/-1)1 file modifiedsrc/platforms/mirserver/tileddisplayconfigurationpolicy.cpp (+1/-1)
Changed in unity8 (Ubuntu): | |
status: | New → Invalid |
summary: |
- /usr/bin/unity8:11:TiledDisplayConfigurationPolicy:::std::_Function_handler:std::function:mir::graphics::nested::NestedDisplayConfiguration:::std::for_each + Unity8 crashed in TiledDisplayConfigurationPolicy + [tileddisplayconfigurationpolicy.cpp:41] |
affects: | mir → qtmir |
no longer affects: | mir (Ubuntu) |
summary: |
- Unity8 (QtMir) crashed in TiledDisplayConfigurationPolicy + Unity8 (QtMir) crashed in TiledDisplayConfigurationPolicy::apply_to() [tileddisplayconfigurationpolicy.cpp:41] |
Changed in qtmir: | |
assignee: | nobody → Daniel van Vugt (vanvugt) |
Changed in qtmir (Ubuntu): | |
assignee: | nobody → Daniel van Vugt (vanvugt) |
Changed in qtmir: | |
status: | Triaged → In Progress |
summary: |
- Unity8 (QtMir) crashed in TiledDisplayConfigurationPolicy::apply_to() + Unity8 (QtMir) crashed (on login or display change) in + TiledDisplayConfigurationPolicy::apply_to() [tileddisplayconfigurationpolicy.cpp:41] |
Changed in qtmir (Ubuntu): | |
status: | Triaged → In Progress |
Changed in qtmir: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in qtmir: | |
status: | In Progress → Fix Committed |
Changed in qtmir (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in qtmir: | |
status: | Fix Committed → Fix Released |
no longer affects: | qtmir |
To post a comment you must log in.
It's a simple array overrun in QtMir:
Looks like it's missing a check for the possibility of there being no preferred mode:
output. preferred_ mode_index >= modes.size()
Which is possible, and almost common (particularly on TVs).