Qt timestamps seem off

Bug #1511076 reported by Michael Terry on 2015-10-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
qtmir (Ubuntu)
Michael Terry

Bug Description

In testing a unity8 branch that wanted to make use of QInputEvent timestamps, I discovered that they seem a bit unreliable in Mir (testing on a mako).

I often would get 0. And the timestamps themselves would be all over the place, seemingly overflowing. See https://pastebin.canonical.com/142915/ for a log (the MIKE lines indicate true/false for whether the event is an autorepeat event and then the next number is the Qt timestamp).

Might be an issue with stuffing int64 into a ulong? Or might be something else random. I'm trying to get a tighter test case.

Related branches

Gerry Boland (gerboland) on 2015-10-29
Changed in qtmir (Ubuntu):
status: New → In Progress
assignee: nobody → Michael Terry (mterry)
importance: Undecided → High
Changed in canonical-devices-system-image:
importance: Undecided → High
status: New → Fix Committed
milestone: none → ww46-2015
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qtmir - 0.4.6+16.04.20151102-0ubuntu1

qtmir (0.4.6+16.04.20151102-0ubuntu1) xenial; urgency=medium

  [ Alan Griffiths ]
  * Test harness for MirWindowManager (in preparation for more
    intelligent window management)

  [ CI Train Bot ]
  * New rebuild forced.

  [ Michael Terry ]
  * Support new isTouchApp property to ApplicationInfoInterface and move
    lifecycle policy logic out of qtmir.

  [ Michał Sawicz ]
  * Clean up packaging and fix autopkgtest on armhf

  [ Nick Dedekind ]
  * Hand Qt millisecond timestamps rather than nanosecond. (LP:
    #1510571, #1511076, #1511711)
  * Support server->client visibility change to stop rendering
    (lp:#1475678) (LP: #1475678)

 -- Michał Sawicz <email address hidden> Mon, 02 Nov 2015 11:22:29 +0000

Changed in qtmir (Ubuntu):
status: In Progress → Fix Released
Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers