Passing DisplayConfiguration scale property from nested server to host appears to not work
Bug #1535780 reported by
Gerry Boland
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
kevin gunn | ||
Mir |
Fix Released
|
Critical
|
Chris Halse Rogers | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm using code like this in QtMir, implementing a wrapper for DisplayConfigur
void MirDisplayConfi
{
m_wrapped-
conf.
{
});
}
Starting nested server with this, I fail to see the final applied DisplayConfigur
Also, can you please check scale can be set for Android platform. It does work on Mesa/KMS anyway.
Related branches
lp:~kdub/mir/fix-1535780-android
- Alan Griffiths: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Mir CI Bot: Approve (continuous-integration)
-
Diff: 70 lines (+49/-0)2 files modifiedsrc/platforms/android/server/display.cpp (+2/-0)
tests/unit-tests/graphics/android/test_display.cpp (+47/-0)
lp:~raof/mir/nested-scale-setting
- Alan Griffiths: Approve
- Daniel van Vugt: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Mir CI Bot: Approve (continuous-integration)
- Alberto Aguirre (community): Approve
-
Diff: 254 lines (+150/-6)3 files modifiedsrc/server/graphics/nested/nested_display_configuration.cpp (+37/-6)
src/server/graphics/nested/nested_display_configuration.h (+20/-0)
tests/acceptance-tests/test_nested_mir.cpp (+93/-0)
Changed in mir: | |
importance: | Undecided → Critical |
Changed in mir: | |
milestone: | none → 0.19.0 |
Changed in mir: | |
status: | Fix Committed → In Progress |
Changed in mir: | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
importance: | Undecided → Critical |
status: | New → Fix Committed |
assignee: | nobody → kevin gunn (kgunn72) |
milestone: | none → ww04-2016 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
Changed in canonical-devices-system-image: | |
milestone: | ww04-2016 → 9.1 |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Digging into Mir, I'm guessing that the default configuration for Android implemented in mga::FbControl: :active_ config_ for would be to blame, as it fixes the scale & form factor permanently for the internal display at phone & 1.0 respectively.
As I was working on nesting server on android, it may be root cause of this issue.