Which makes me wonder why was unity8 the first team summoned to
investigate it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking
I guess because we initially thought the unity8 crash was causing the
issue. It seems you’ve been able to observe the issue without a crash
though, which would indicate that the issue might be somewhere else in
the stack.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
When running the autopilot tests for ubuntu-system-settings, at some
point it fails to enter text using the OSK. It works fine for smaller
subsets of the tests, but not a full run. It simply stops entering text
- with keyboard.write. Once it gets in this state, it
** Branch linked: lp:~ken-vandine/ubuntu-system-settings/search_text_fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot
It seems be related to a test failure that puts the fake keyboard into a
bad state. The only way to fix that state is by restarting unity8. I'm
not sure what that has to do with unity8, but somehow restarting it
clears it up. In the case of settings there was a real failure buried
in the noise
But still, entering text via a physical keyboard should still work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests
I reboot the phone and run:
$ autopilot3 run
ubuntu_system_settings.tests.test_search.SearchTestCases.test_search_filter_results
And it fails:
testtools.matchers._impl.MismatchError: After 10.0 seconds test on
TextField.text failed: 'Sound' != dbus.String('Som', variant_level=1)
The test
So the problem is that unity-system-compositor is dropping the uinput
fake kbd events from autopilot, instead of forwarding them to unity8.
[1435688811.380008] android-input: [InputDispatcher]Dropping event because
there is no focused window or focused application.
** No longer affects:
** Summary changed:
- unity8 crash breaking autopilot tests entering text with OSK
+ unity8 crash breaking autopilot tests entering text
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Daniel d'Andrada (dandrader)
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in
Ran autopilot3 run ubuntu_system_settings with Ubuntu 15.04 (r176) on
mako
Got 38 test failures but unity8 didn't crash and I could still type
normally on the virtual keyboard afterwards.
I was running a debug build of unity8 under gdb. With very nasty bugs
this has an influence.
--
You
I am seeing the same issue intermittently when running the webbrowser_app test
suite on devices (both in CI runs on mako and locally on my krillin). See e.g.
https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/2759/.
At some point during the test run, something happens and
** Changed in: unity8 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering
It seems I was debugging something similar with rhuddie the other day
(without solution). In case it's useful I'll mention it here:
What I observed was the test in question would stop then start the
maliit-server, then the test immediately clicked on a text input and
failed as the OSK never came
Added Mirv as recent Qt landings may be implicated?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity8 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Link to a CI log:
https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily-mako/117/testReport/junit/ubuntu_system_settings.tests.test_cellular/DualSimCellularTestCase/test_change_sim1_name/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
17 matches
Mail list logo
