Shell does not get autopilot keyboard input if maliit isn't running
Bug #1238645 reported by
Michał Sawicz
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Expired
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Make sure screen is on (can stop powerd after unlocking unity8 just to make sure), stop unity8 and run:
$ autopilot run unity8.
1 PASSED
Now stop maliit and run the test again:
$ initctl stop maliit-server
$ autopilot run unity8.
1 FAILED
Autopilot seems to be unable to deliver input unless maliit is running.
Exporting
MIR_SERVER_
MIR_SERVER_
Doesn't seem to result in anything.
Related branches
lp:~veebers/unity8/ap_launch_unity_with_upstart
Superseded
for merging
into
lp:unity8
- Michał Sawicz: Needs Fixing
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Thomi Richards (community): Approve
-
Diff: 263 lines (+152/-12)3 files modifieddebian/unity8.install (+1/-0)
tests/autopilot/unity8/shell/tests/__init__.py (+134/-12)
upstart-session/unity8.conf (+17/-0)
lp:~saviq/unity8/workaround-lp1238645
- Michał Sawicz: Disapprove
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Sergio Schvezov: Needs Fixing
-
Diff: 31 lines (+12/-2)1 file modifiedtests/autopilot/unity8/shell/tests/__init__.py (+12/-2)
Changed in unity8: | |
status: | New → In Progress |
assignee: | nobody → Christopher Lee (veebers) |
Changed in mir: | |
status: | Incomplete → Invalid |
no longer affects: | autopilot |
tags: | added: doesnt-need-test |
affects: | unity8 → unity8 (Ubuntu) |
To post a comment you must log in.
Apparently it's because autopilot *uses* maliit to type on mobile devices.
Let's discuss whether it should maybe fall back to uinput - in the mean time I'll make sure maliit is started on unity8 tests.