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
Apps bug tracking, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1649077
Title:
[regression] OSK appears blank and/or flickers in the lock screen
Status in Canonical System Image:
Confirmed
Status in Mir:
New
Status in QtMir:
Confirmed
Status in mir package in Ubuntu:
Invalid
Status in qtmir package in Ubuntu:
Confirmed
Status in ubuntu-keyboard package in Ubuntu:
Invalid
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
After using OTA-14 a while, the OSK starts to exhibit a strange
behaviour.
1. It appears blank after a while in the lock screen. You can still
press randomly which then makes the OSK to appear fully. When you
press a character again it starts to flicker.
2. OSK starts to flicker similar to bug #1590765 which was fixed in
OTA-12. It seems to have resurfaced in OTA-14.
Systems Info:
OTA-14 Stable Channel
Devices: E4.5, E5
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649077/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-apps-bugs
Post to : ubuntu-apps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-apps-bugs
More help : https://help.launchpad.net/ListHelp
