U1 login window opens behind pay-ui window
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
Michał Sawicz | ||
qtmir (Ubuntu) |
Invalid
|
Critical
|
Daniel d'Andrada | ||
unity8 (Ubuntu) |
Fix Released
|
Critical
|
Daniel d'Andrada |
Bug Description
In today's phone images, a very basic test case fails: Purchasing an app on a freshly-flashed phone.
Specifically, after tapping the app's price button to initiate a purchase, the pay-ui's "Loading..." dialog appears and never disappears or times out. If I hit its "Cancel" button, I see the U1 login window. Completing the login then returns the view to the app's summary screen in the click store.
What's supposed to happen is:
- Tap the price button.
- Get a U1 login window.
- Complete the login.
- Get a payment confirmation window.
I'm not completely sure what causes this, but it looks like the U1 login window is simply appearing underneath the pay-ui dialog instead of above it. Dobey found this error in the logs:
2016-05-26 20:34:53,467 - WARNING - QWindow:
This should probably be fixed before OTA12, since it's a step backward in the first-time app purchase flow.
Related branches
- Unity8 CI Bot: Needs Fixing (continuous-integration)
- Nick Dedekind (community): Approve
-
Diff: 212 lines (+78/-21)5 files modifiedqml/Stages/ApplicationWindow.qml (+26/-10)
tests/mocks/Unity/Application/MirSurfaceListModel.cpp (+11/-1)
tests/mocks/Unity/Application/MirSurfaceListModel.h (+1/-0)
tests/qmltests/Stages/ApplicationCheckBox.qml (+1/-1)
tests/qmltests/Stages/tst_ApplicationWindow.qml (+39/-9)
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
assignee: | nobody → Michał Sawicz (saviq) |
importance: | Undecided → Critical |
milestone: | none → 12 |
Changed in canonical-devices-system-image: | |
status: | Confirmed → Triaged |
Changed in qtmir (Ubuntu): | |
importance: | Undecided → Critical |
Changed in unity8 (Ubuntu): | |
importance: | Undecided → Critical |
Changed in qtmir (Ubuntu): | |
status: | New → Triaged |
Changed in unity8 (Ubuntu): | |
status: | New → Triaged |
Changed in qtmir (Ubuntu): | |
assignee: | nobody → Daniel d'Andrada (dandrader) |
Changed in unity8 (Ubuntu): | |
assignee: | nobody → Daniel d'Andrada (dandrader) |
Changed in qtmir (Ubuntu): | |
status: | Triaged → In Progress |
Changed in unity8 (Ubuntu): | |
status: | Triaged → In Progress |
Changed in qtmir (Ubuntu): | |
status: | In Progress → Invalid |
Changed in canonical-devices-system-image: | |
status: | Triaged → In Progress |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
I don't think that the log message is that relevant, since qtmir never supported foreign windows.
This looks like a mir/qtmir/unity8 issue in handling trusted sessions (unless something has changed in pay-service?).
Tentatively assigning to qtmir for investigation.