Merge lp:~alan-griffiths/mir/fix-1717910 into lp:mir
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merged at revision: | 4257 | ||||
| Proposed branch: | lp:~alan-griffiths/mir/fix-1717910 | ||||
| Merge into: | lp:mir | ||||
| Diff against target: |
116 lines (+38/-19) 4 files modified
debian/changelog (+2/-0) examples/miral-kiosk/kiosk_window_manager.cpp (+30/-15) examples/miral-kiosk/kiosk_window_manager.h (+5/-3) include/miral/miral/canonical_window_manager.h (+1/-1) |
||||
| To merge this branch: | bzr merge lp:~alan-griffiths/mir/fix-1717910 | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Mir CI Bot | continuous-integration | Needs Fixing on 2017-09-20 | |
| Gerry Boland | 2017-09-18 | Approve on 2017-09-19 | |
|
Review via email:
|
|||
Commit Message
[miral-kiosk] Apply fullscreen logic when hidden windows are restored. (LP: #1717910)
| Gerry Boland (gerboland) wrote : | # |
No change. Try a command like this:
QT_LOGGING_
Qt is getting the resize event from Mir, but we've never trusted the resize event from Mir as it seldom reflected the next buffer size - so instead we forces a redraw, which pulls a new buffer from Mir, and we check that buffer size to see if it changes. We're not getting any buffer size change.
OFC adopting the new buffer semantics stuff would probably rectify that. But that's non-trivial work
| Alan Griffiths (alan-griffiths) wrote : | # |
> No change. Try a command like this:
>
> QT_LOGGING_
> -linux-
Thanks for that. I had been testing with...
$ miral-app -kiosk
...and that was improved by the changes so far.
| Alan Griffiths (alan-griffiths) wrote : | # |
This seems OK for these test cases:
$ miral-app -kiosk -launcher /usr/lib/
$ miral-app -kiosk
Note that this breaks the following case:
$ miral-app -kiosk -launcher 'gnome-terminal --app-id com.canonical.
But I don't think we should care.
| Alan Griffiths (alan-griffiths) wrote : | # |
> Note that this breaks the following case:
>
> $ miral-app -kiosk -launcher 'gnome-terminal --app-id
> com.canonical.
>
> But I don't think we should care.
Basically, this is the code that should work but replaces incorrect code used to work around a gtk-mir bug.
As gtk-mir is /1/ unmaintained and being disable going forward and /2/ already broken in multiple ways on Xenial I don't think we should worry.
| Gerry Boland (gerboland) wrote : | # |
There is something subtly wrong still. I see a resize flicker for the fancybrowser on startup. Looking at the WM trace, there is a non-fullscreen resize request by Qt of the window while it is hidden that Mir appears to be respecting. See https:/
| Mir CI Bot (mir-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:4257
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Alan Griffiths (alan-griffiths) wrote : | # |
> There is something subtly wrong still. I see a resize flicker for the
> fancybrowser on startup. Looking at the WM trace, there is a non-fullscreen
> resize request by Qt of the window while it is hidden that Mir appears to be
> respecting. See https:/
I don't see that here. But you're right - it doesn't make sense to respect resizing when hidden/hiding and change it once restored. Changed accordingly.
| Mir CI Bot (mir-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:4258
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
https:/
Executed test runs:
FAILURE: https:/
None: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
https:/
Executed test runs:
FAILURE: https:/
None: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
ABORTED: https:/
ABORTED: https:/
SUCCESS: https:/
deb: https:/
ABORTED: https:/
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
https:/
Executed test runs:
FAILURE: https:/
None: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
| Alan Griffiths (alan-griffiths) wrote : | # |
:(
12:13:07 The following tests FAILED:
12:13:07 11 - mir_acceptance_
12:13:07 16 - mir_integration
12:13:07 22 - mir_unit_tests (Failed)
12:13:07 31 - mir_unit_
10:58:41 The following tests FAILED:
10:58:41 9 - mir_acceptance_
10:58:41 14 - mir_integration
10:58:41 20 - mir_unit_tests (Failed)
10:58:41 29 - mir_unit_
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
https:/
Executed test runs:
FAILURE: https:/
None: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
| Alan Griffiths (alan-griffiths) wrote : | # |
And again.
It seems valgrind is reporting errors on artful that were not there yesterday. (And have nothing to do with this MP as I can reproduce on trunk.)
Committing by hand

FAILED: Continuous integration, rev:4254 /mir-jenkins. ubuntu. com/job/ mir-ci/ 3668/ /mir-jenkins. ubuntu. com/job/ build-mir/ 5021/console /mir-jenkins. ubuntu. com/job/ build-0- fetch/5254 /mir-jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= artful/ 5242 /mir-jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= xenial/ 5242 /mir-jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= zesty/5242 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= clang,platform= mesa,release= artful/ 5064/console /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= clang,platform= mesa,release= zesty/5064 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= clang,platform= mesa,release= zesty/5064/ artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= artful/ 5064 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= artful/ 5064/artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= xenial/ 5064 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= xenial/ 5064/artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= zesty/5064 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= zesty/5064/ artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= cross-armhf, compiler= gcc,platform= mesa,release= artful/ 5064 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= cross-armhf, compiler= gcc,platform= mesa,release= artful/ 5064/artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= cross-armhf, compiler= gcc,platform= mesa,release= zesty/5064 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= cross-armhf, compiler= gcc,platform= mesa,release= zesty/5064/ artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= mesa,release= xenial/ 5064 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= mesa,release= xenial/ 5064/artifact/ output/ *zip*/output. zip
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild: /mir-jenkins. ubuntu. com/job/ mir-ci/ 3668/rebuild
https:/