foreground app doesn't get activated after we leave the lock screen

[Daniel d'Andrada]

Steps to reproduce the issue:
1 - Set a passphrase (not pin)
2 - have unity8-dash on the foreground
3 - lock the phone (reboot or have the display off and then turn it back on)
4 - type you password [you're brought to unity8-dash]
5 - tap on the looking glass icon in the top right [search bar text entry shows up with "Search apps" written on it]

Expected outcome:
A blinking cursor caret is displayed on the app search text entry and the VKB comes up.

Actual outcome:
Nothing happens.

Causing unity-8 dash to be refocused, such as bringing the indicators panel down and then back up solves it.

Comments:
Happens with any application that happens to be in the foreground, unity8-dash being just one test case that is easy to reproduce.

[kevin gunn (kgunn72)]

is this N4? or krillin too ?

[Daniel d'Andrada (dandrader)]

> is this N4? or krillin too ?

Both.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel d'Andrada (dandrader)]

The cause of the bug is that maliit-framework is removing focus from the currently focused item after the VKB is hidden. In this particular use case, that happens to be the MirSurfaceItem of the focused app (because we change the focus from the lockscreen text entry to the app surface as soon as the enter is pressed). If maliit is to unfocus anyone (maybe it shouldn't be doing this at all), it should be the item that originally summoned it, not whoever item happens to be the focused one at that time.

#0 QQuickItem::setFocus (this=0x1286560, focus=<optimized out>, reason=Qt::OtherFocusReason) at /home/phablet/packages/qtdeclarative-opensource-src-5.3.0/src/quick/items/qquickitem.cpp:6394
#1 0xb267a958 in MInputContext::imInitiatedHide() () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforminputcontexts/libmaliitphabletplatforminputcontextplugin.so
#2 0xb267f4de in ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforminputcontexts/libmaliitphabletplatforminputcontextplugin.so
#3 0xb64604bc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#4 0xb2687aac in MImServerConnection::imInitiatedHide() () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforminputcontexts/libmaliitphabletplatforminputcontextplugin.so
#5 0xb2688f7e in Inputcontext1Adaptor::imInitiatedHide() () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforminputcontexts/libmaliitphabletplatforminputcontextplugin.so
#6 0xb26899dc in ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforminputcontexts/libmaliitphabletplatforminputcontextplugin.so
#7 0xb2689cc8 in Inputcontext1Adaptor::qt_metacall(QMetaObject::Call, int, void**) ()
   from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforminputcontexts/libmaliitphabletplatforminputcontextplugin.so
#8 0xb3c0162a in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5DBus.so.5

[Gerry Boland (gerboland)]

It's not just dash, but any app which was last focused

[Brendan Donegan (brendan-donegan)]

FTR this happens with camera-app (see https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385462) which as far as I know never tries to do anything with maliit so to my untrained eye it looks like a more general issue.

[Michael Sheldon (michael-sheldon)]

I can confirm that this is definitely a maliit issue, working on a patch now.

[Olli Ries (ories)]

please bring up again when a fix is available so we can "assess" impact

[Brendan Donegan (brendan-donegan)]

This may be making some of our smoke tests fail too

[Selene ToyKeeper (toykeeper)]

I think I've seen this too. Usually what happens for me is... I flash fresh, with developer mode (and thus passphrase security) enabled. I go through the welcome wizard, then the first thing I do on the first boot is try to set my time zone. Sometimes I can't get the OSK to appear until I pull from the right edge to trigger the app switcher, then abort the switch to refocus the current app.

[Ricardo Salveti (rsalveti)]

I could not reproduce this bug with the attempts I tried (both vivid/7 and rtm/140).

In any case, could someone test the packages from http://people.canonical.com/~rsalveti/1373985/ to see if it helps fixing this bug? If so, I can upload it to vivid and create a silo for RTM (until it gets approved).

[Brendan Donegan (brendan-donegan)]

Definitely solves at least https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385462 and https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377817 for me. I would suggest this fix is good

[Launchpad Janitor (janitor)]

This bug was fixed in the package maliit-framework - 0.99.0+git20130923+17fdf86-0ubuntu3

---------------
maliit-framework (0.99.0+git20130923+17fdf86-0ubuntu3) vivid; urgency=medium

  [ Michael Sheldon ]
  * 0012-fix-focus-changes.patch: Only allow maliit to remove focus
    from input fields (LP: #1373985)
 -- Ricardo Salveti de Araujo <email address hidden> Mon, 03 Nov 2014 17:15:21 -0200