Shell does not get autopilot keyboard input if maliit isn't running

[Michał Sawicz]

Make sure screen is on (can stop powerd after unlocking unity8 just to make sure), stop unity8 and run:
$ autopilot run unity8.shell.tests.test_lock_screen.TestLockscreen.test_can_unlock_passphrase_screen

1 PASSED

Now stop maliit and run the test again:
$ initctl stop maliit-server
$ autopilot run unity8.shell.tests.test_lock_screen.TestLockscreen.test_can_unlock_passphrase_screen

1 FAILED

Autopilot seems to be unable to deliver input unless maliit is running.

Exporting
MIR_SERVER_INPUT_REPORT=log
MIR_SERVER_LEGACY_INPUT_REPORT=log

Doesn't seem to result in anything.

[Michał Sawicz (saviq)]

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.

[Michał Sawicz (saviq)]

lp:~veebers/autopilot/add_OSK_keyboard_backend

[Thomi Richards (thomir-deactivatedaccount)]

> Apparently it's because autopilot *uses* maliit to type on mobile devices.

Nope - the UInput backend is higher priority, so the OSK backend won't get used unless uinput is unavailable, for some reason. Of course, the tests you're running might specifically request the OSK backend, but that's not really anything to do with autopilot itself.

> 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.

The backend should raise an exception if it cannot be initialised. In that case, autopilot will fall back to some other backend, unless the OSK driver was specifically requested. If that's not the case, then the bug task against autopilot is valid, and should be fixed. Will leave this to Chris to determine, since he's in this code anyway.

[Christopher Lee (veebers)]

As Thomi has clarified; this really isn't an autopilot issue but a problem when running the unity8 autopilot tests.

I'm marking this as invalid for Autopilot. I'm including functionality in the unity8 autopilot test suite to work better with maliit-server and starting/stopping unity8 etc.

[Timo Jyrinki (timo-jyrinki)]

I guess this also is the reason why unity8.shell.tests.test_lock_screen.TestLockscreen.test_passphrase_screen_wrong_password hangs?

If one runs phablet-test-run -n unity8, it seems to hang eternally at a password screen, and also that ^ test individually does not complete even with a failure (unlike test_can_unlock_passphrase_screen which properly fails). That makes testing unity8 hard since the tests need to be executed one at a time which is slow compared to whole suite run.

[Michał Sawicz (saviq)]

It should bail out after a few dozen seconds... will check...

[Michał Sawicz (saviq)]

Reopening as this is still an issue that we haven't tracked down - just worked around it.

[Launchpad Janitor (janitor)]

[Expired for Unity 8 because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Mir because there has been no activity for 60 days.]