Actually this might be Mir's fault still. The first time the bug was
noticed was when we introduced NBS and the fix back then was to back out
NBS I think. But now I'm actually looking at the NBS code and it seems
like it might be dropping the newest frame from the client without any
guarantee the client (OSK) will ever produce a new one. Not totally
sure, but this might be Mir's fault.
** Changed in: mir
Importance: Undecided => High
** Changed in: mir
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649077
Title:
[regression] OSK appears blank and/or flickers in the lock screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649077/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
