Desktop applications don't get properly resized when launched in staged mode
Bug #1670390 reported by
Daniel d'Andrada
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
In Progress
|
High
|
Michał Sawicz | ||
gtk+3.0 (Ubuntu) |
Fix Released
|
High
|
William Hua | ||
qtmir (Ubuntu) |
Fix Released
|
High
|
Daniel d'Andrada | ||
qtubuntu (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
unity8 (Ubuntu) |
Fix Released
|
High
|
Daniel d'Andrada |
Bug Description
Steps to reproduce the issue:
1 - Put unity8 in staged mode
2 - Launch a desktop application like kate or qtcreator
Expected outcome:
The launched application takes up the entire stage area
Actual outcome:
The launched application starts with some windowed size it wanted to have, not filling the entire stage area. As if launched in desktop mode.
Comments:
Leaving staged mode and going back into it again gets the application to resize correctly and fill the entire stage area.
Going from desktop to staged mode while the desktop application is already running also works fine.
Related branches
lp://staging/~dandrader/qtmir/allowClientResize
- Lukáš Tinkl (community): Abstain
- Unity8 CI Bot (community): Approve (continuous-integration)
- Gerry Boland (community): Approve
-
Diff: 155 lines (+41/-6)8 files modifiedCMakeLists.txt (+1/-1)
debian/control (+2/-2)
debian/gles-patches/convert-to-gles.patch (+1/-1)
src/common/windowmodelnotifier.h (+5/-0)
src/modules/Unity/Application/mirsurface.cpp (+15/-0)
src/modules/Unity/Application/mirsurface.h (+3/-0)
src/platforms/mirserver/windowmanagementpolicy.cpp (+11/-2)
tests/framework/fake_mirsurface.h (+3/-0)
lp://staging/~dandrader/unity8/allowClientResize
- Unity8 CI Bot: Approve (continuous-integration)
- Gerry Boland (community): Approve
- Lukáš Tinkl: Pending requested
-
Diff: 190 lines (+56/-5)6 files modifieddebian/control (+2/-2)
plugins/WindowManager/Window.cpp (+26/-1)
plugins/WindowManager/Window.h (+14/-1)
qml/Stage/Stage.qml (+8/-0)
tests/mocks/Unity/Application/MirSurface.h (+3/-0)
tests/plugins/Unity/Launcher/launchermodeltest.cpp (+3/-1)
description: | updated |
description: | updated |
description: | updated |
Changed in canonical-devices-system-image: | |
milestone: | none → u8c-1 |
assignee: | nobody → Michał Sawicz (saviq) |
importance: | Undecided → High |
Changed in qtubuntu (Ubuntu): | |
importance: | Undecided → High |
tags: | added: gtk-mir |
Changed in gtk+3.0 (Ubuntu): | |
assignee: | nobody → William Hua (attente) |
importance: | Undecided → High |
Changed in qtmir (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Daniel d'Andrada (dandrader) |
Changed in qtmir: | |
status: | New → In Progress |
assignee: | nobody → Daniel d'Andrada (dandrader) |
importance: | Undecided → High |
Changed in qtmir (Ubuntu): | |
importance: | Undecided → High |
Changed in unity8 (Ubuntu): | |
importance: | Undecided → High |
tags: | added: visual-quality |
Changed in gtk+3.0 (Ubuntu): | |
status: | New → Invalid |
Changed in canonical-devices-system-image: | |
status: | New → In Progress |
Changed in gtk+3.0 (Ubuntu): | |
status: | New → Confirmed |
no longer affects: | qtmir |
Changed in gtk+3.0 (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in canonical-devices-system-image: | |
milestone: | u8c-1 → u8c-2 |
To post a comment you must log in.
This sounds like bug 1655804. It may require the same kind of fix: The toolkit needs to register its Mir event callback in the spec prior to window creation to support Unity8 behaviour.