touch-packages team mailing list archive

[Michael Sheldon <michael.sheldon@xxxxxxxxxxxxx>]

Just to add in my findings from duplicate bug #1493872:

If the screen is locked after an application has been first opened unity
doesn't remove focus from the app. It does remove focus on subsequent
screen locks. This is what results in the keyboard not being dismissed
if it was displayed prior to the screen being locked.

This can be seen in the application log (e.g. ~/.cache/upstart
/application-legacy-messaging-app-.log), where you would expect to see
the message:

UbuntuWindow::handleSurfaceFocusChange(focused=false)

Indicating that focus has been removed from the app, however this
doesn't happen the first time you lock the screen after starting the
app, only on subsequent locks.

-- 
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/1491034

Title:
  keyboard stays above lockscreen when locking

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  as you can see in:
  http://i.imgur.com/wYr77Gq.png and http://people.canonical.com/~alan/screenshots/device-2015-09-01-164517.png

  having the keyboard expanded and then locking the screen results in
  the keyboard sitting on top of the lockscreen when waking up the
  device ...

  input on the keyboard ends up in the respective app that opened the
  kbd (in my case the terminal) and gets processed as soon as the app
  recieves its SIGCONT signal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491034/+subscriptions