** No longer affects: qtmir
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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
** Changed in: mir
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1649077
Title:
[regression] OSK appears blank and/or flicker
** Changed in: qtmir
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1649077
Title:
[regression] OSK appears blank and/or
This bug was fixed in the package qtmir - 0.5.1+17.04.20170124-0ubuntu1
---
qtmir (0.5.1+17.04.20170124-0ubuntu1) zesty; urgency=medium
[ Gerry Boland ]
* Recalculate MirSurface.visible after first frame swap by client (LP:
#1649077)
[ Lukáš Tinkl ]
* Some assorted cleanu
** Branch linked: lp:~gerboland/qtmir/initial-surface-expose
** Changed in: qtmir (Ubuntu)
Status: Confirmed => In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** Changed in: qtmir
Status: Confirmed => In Progress
** Changed in: qt
** Tags added: osk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 Canon
My mistake. I now can't see how Mir can cause this.
** Changed in: mir
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1649077
Title
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 c
I have a suspicion this bug may manifest after a long period of inactivity
related to the keyboard. I think I had not been writing any messages for more
than 24 hours when I have had noticed it again.
HTH
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
9 matches
Mail list logo