[regression] OSK suppressed in autopilot tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
Michał Sawicz | ||
ubuntu-keyboard (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu) |
Fix Released
|
Critical
|
Josh Arenson |
Bug Description
I’m seeing a large number of webbrowser-app autopilot test failures lately (I think this started 2 or 3 days ago).
Almost all of them expose a traceback like this:
Traceback (most recent call last):
File "/usr/lib/
self.main_
File "/usr/lib/
self.address_
File "/usr/lib/
return f(instance, *args, **kwargs)
File "/usr/lib/
self.write(url)
File "/usr/lib/
self.text_
File "/usr/lib/
return f(instance, *args, **kwargs)
File "/usr/lib/
self.keyboard.
File "/usr/lib/
self._keyboard.
File "/usr/lib/
self.press_
File "/usr/lib/
raise RuntimeError(
RuntimeError: Keyboard is not on screen
This has now been confirmed to occur in all autopilot tests that use the OSK (including the ubuntu-
Related branches
- ubuntu-sdk-build-bot: Approve (continuous-integration)
- Zoltan Balogh: Approve
-
Diff: 28 lines (+10/-1)1 file modifiedtests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_common.py (+10/-1)
- Michael Terry: Approve
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Unity8 CI Bot: Needs Fixing (continuous-integration)
-
Diff: 58 lines (+26/-1)1 file modifiedqml/OrientedShell.qml (+26/-1)
- system-apps-ci-bot: Needs Fixing (continuous-integration)
- PS Jenkins bot: Needs Fixing (continuous-integration)
-
Diff: 1198 lines (+666/-337)12 files modifiedsrc/app/CMakeLists.txt (+3/-1)
src/app/FilteredKeyboardModel.qml (+33/-0)
src/app/browserapplication.cpp (+2/-0)
src/app/qquickshortcut.cpp (+283/-0)
src/app/qquickshortcut_p.h (+109/-0)
src/app/webbrowser/Browser.qml (+200/-258)
src/app/webbrowser/KeyboardShortcut.qml (+0/-25)
src/app/webbrowser/KeyboardShortcuts.qml (+0/-41)
src/app/webbrowser/ListViewHighlight.qml (+2/-3)
src/app/webbrowser/NavigationBar.qml (+10/-7)
tests/autopilot/webbrowser_app/tests/test_keyboard.py (+22/-1)
tests/autopilot/webbrowser_app/tests/test_private.py (+2/-1)
Changed in ubuntu-keyboard (Ubuntu): | |
status: | New → Invalid |
assignee: | Michael Sheldon (michael-sheldon) → nobody |
Changed in unity8 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Josh Arenson (josharenson) |
Changed in unity8 (Ubuntu): | |
importance: | High → Critical |
Changed in canonical-devices-system-image: | |
milestone: | none → ww08-2016 |
status: | New → Confirmed |
importance: | Undecided → Critical |
tags: | added: regression-proposed |
Changed in canonical-devices-system-image: | |
assignee: | nobody → Michał Sawicz (saviq) |
Changed in unity8 (Ubuntu): | |
status: | Triaged → In Progress |
Changed in canonical-devices-system-image: | |
status: | Confirmed → In Progress |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
Given that a new version of ubuntu-keyboard was published on 2016-01-29, that would more or less match when the failures started happening. Could this be a regression in ubuntu-keyboard 0.99.trunk. phablet2+ 16.04.20160128- 0ubuntu1 ?