Actually I would not be surprised if we did still have a bug like this. The team would not have noticed it for several reasons: * We don't have any keyboard/typing-related demo clients. * We don't use XMir regularly * Touch input could be suffering similar lag and we would not notice because touch events are much more numerous and more likely to be flushed adequately to keep Ubuntu-touch moving.
Our MultithreadedCompositor's frame scheduling logic is still somewhat suspicious. It gets the number of frames to schedule from the BufferQueue, but that function of the buffer queue is apparently racy by design, and may not return a realistically high enough value adequate to schedule enough frames. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1295851 Title: Input lag after last update Status in Mir: Incomplete Status in XMir: Incomplete Status in “mir” package in Ubuntu: Incomplete Bug description: Seems some recent update in trusty introduced an input lag in xmir again :( I am using an Intel Hashwell chipset, which has been working perfectly so far... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1295851/+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
