I'm developing a theory related to mirscreencast stealing focus and
triggering a bug in sessions without surfaces...it may be fixed in Mir
0.14 but it doesn't seem like I can test for a few more hours (so
perhaps not until tomorrow)
--
You received this bug notification because you are a member
Just a brief thank you for an interesting bug report, I was on holidays
so I didn't reply earlier. Digesting the messages, it sounds like
nothing yet points to a Qt internal problem? One useful tidbit is that
wily has Qt 5.4.2 while vivid has Qt 5.4.1, so it's useful to compare in
case of
** Branch linked: lp:ubuntu/wily-proposed/ubuntu-system-settings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text
To manage
This bug was fixed in the package ubuntu-system-settings -
0.3+15.10.20150702.3-0ubuntu1
---
ubuntu-system-settings (0.3+15.10.20150702.3-0ubuntu1) wily; urgency=medium
[ CI Train Bot ]
* New rebuild forced.
[ Ken VanDine ]
* Test searching for WiFi instead of Sound,
** Changed in: mir
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text
To manage notifications about
** Changed in: mir
Milestone: None = 0.15.0
** Tags added: input regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text
To
This now seems to affect all automated CI runs for webbrowser-app merge
requests on mako (vivid), thus preventing any automated validation. Can
the importance be bumped to critical?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
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
Daniel: note that when autopilot tests start failing, manually typing
with the OSK works (as you’ve observed), what doesn’t is autopilot’s
write() method that simulates keyboard input.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: unity8 (Ubuntu)
Importance: High = Critical
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
But still, entering text via a physical keyboard should still work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text
To manage
** Branch linked: lp:~ken-vandine/ubuntu-system-settings/search_text_fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text
To manage
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
** 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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text with OSK
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
unity8 crash breaking autopilot tests entering text with OSK
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468029
Title:
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
Bugs, which is
26 matches
Mail list logo
