| Thread Previous • Date Previous • Date Next • Thread Next |
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
** Also affects: maliit-framework (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maliit-framework (Ubuntu)
Assignee: (unassigned) => Michael Sheldon (michael-sheldon)
** Changed in: unity8 (Ubuntu)
Status: In Progress => Invalid
--
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/1373985
Title:
unity8-dash doesn't seem to get activated after we leave the lock
screen
Status in “maliit-framework” package in Ubuntu:
In Progress
Status in “unity8” package in Ubuntu:
Invalid
Bug description:
Steps to reproduce the issue:
1 - lock the phone (reboot or have the display off and then turn it back on)
2 - type you password [you're brought to unity8-dash]
3 - 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1373985/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
