Would be great if someone could at least respond to this 8+ month old
bug.

We're still suffering from this Qt bug, and have to put in lots of ugly
workarounds to mitigate it.

I'm not sure, should I subscribe someone else to this, and if so, who?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1598173

Title:
  Please consider SRU of "xcb: Compress mouse motion and touch update
  events"

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  A fix for QTBUG-40889 was worked out and submitted at

      https://codereview.qt-project.org/#/c/115531/

  but due to coming in a bit late, was moved to Qt 5.6

      https://codereview.qt-project.org/#/c/126136/

  The bug is about mouse motion event compression malfunctioning, and it
  has grave consequences for some applications, where the flood of
  events make rendering sluggish (e.g. anything based on VTK, but
  probably others).

  ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and
  confirmed it fixes rendering/interaction in VTK applications.

  It is not possible to work around the bug at the application level in
  a satisfactory way, only by resorting to timer-based rendering.

  I suggest an SRU to patch the Ubuntu Qt package with the patch that
  was originally meant for the 5.x branch (first URL above). The patch
  was later integrated in 5.6 where it has been well tested.

  [1] https://bugreports.qt.io/browse/QTBUG-40889
  [2] 
http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+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

Reply via email to