This bug was fixed in the package qtmir - 0.4.7+16.04.20160212-0ubuntu1
---
qtmir (0.4.7+16.04.20160212-0ubuntu1) xenial; urgency=medium
[ Albert Astals Cid ]
* Provide branch prediction information to the if in compressTimestamp
* Reset start time if the timestamp travels to th
** Branch linked: lp:~ci-train-bot/qtmir/qtmir-ubuntu-xenial-landing-064
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524488
Title:
Manually setting the time into the past makes flickables misbeha
** Branch linked: lp:~aacid/qtmir/timestampsInPast
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524488
Title:
Manually setting the time into the past makes flickables misbehave
To manage notifica
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => Invalid
** Changed in: mir (Ubuntu)
Status: New => Invalid
** Changed in: qtmir (Ubuntu)
Status: New => In Progress
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Albert Astals Cid (aacid)
--
I don't think it's an unity8 bug since other apps (e.g webbrowser or
just this QML snippet http://paste.ubuntu.com/14003581/ ) have the same
problem.
I guess something is storing timestamps somewhere and timestamps being
in the past makes things unhappy.
** Summary changed:
- Manually setting th
