Seems the sequence that's happening is: many resize events happen, with the last resize event resizing to the same size as the keyboard started with. This triggers a reallocation of a buffer with the same size. The new buffer goes into the driver, and comes out unfilled.
So, its looking like the driver is perhaps making a false assumption about buffer ordering... A good way to resolve might be to only trigger buffer allocation/freeing once we're sure that a size change has happened and a buffer is needed. (this would be more efficient in terms of reducing alloc/free anyways) ** Tags added: krillin -- 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/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Fix Committed Status in Mir: In Progress Status in Mir 0.23 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
