[Touch-packages] [Bug 1524488] Re: Manually setting the time into the past makes flickables misbehave
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 the past (LP: #1524488) [ Daniel d'Andrada ] * Let shell decide the initial surface size (LP: #1532974) * Remove the useless TaskController * Surface Size Hints * Update mir version requirement [ Michał Sawicz ] * Bump unity-api dependencies * Use QStandardPaths to determine QML cache location [ Nick Dedekind ] * Moved test framework into a static library for quicker recompilation. -- Michał SawiczFri, 12 Feb 2016 00:07:26 + ** Changed in: qtmir (Ubuntu) Status: In Progress => Fix Released -- 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/1524488 Title: Manually setting the time into the past makes flickables misbehave Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: Unexpected behavior while testing a U1 silo: TEST CASE 1. Open ubuntu-system-settings, set time manually into the past a few hours 2. Return to scopes 3. Swipe left for next scope EXPECTED Scope swipes left, next scope appears. ACTUAL Stunted swipe appears to register late, fails to switch scope. Please feel free to reassign if the gesture itself is dependent on time? Pathological use case but maybe worth examining if it exposes some pathological codepaths ;) . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1524488/+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
[Touch-packages] [Bug 1524488] Re: Manually setting the time into the past makes flickables misbehave
** Branch linked: lp:~ci-train-bot/qtmir/qtmir-ubuntu-xenial-landing-064 -- 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/1524488 Title: Manually setting the time into the past makes flickables misbehave Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Invalid Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Unexpected behavior while testing a U1 silo: TEST CASE 1. Open ubuntu-system-settings, set time manually into the past a few hours 2. Return to scopes 3. Swipe left for next scope EXPECTED Scope swipes left, next scope appears. ACTUAL Stunted swipe appears to register late, fails to switch scope. Please feel free to reassign if the gesture itself is dependent on time? Pathological use case but maybe worth examining if it exposes some pathological codepaths ;) . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1524488/+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
[Touch-packages] [Bug 1524488] Re: Manually setting the time into the past makes flickables misbehave
** Branch linked: lp:~aacid/qtmir/timestampsInPast -- 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/1524488 Title: Manually setting the time into the past makes flickables misbehave Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Invalid Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Unexpected behavior while testing a U1 silo: TEST CASE 1. Open ubuntu-system-settings, set time manually into the past a few hours 2. Return to scopes 3. Swipe left for next scope EXPECTED Scope swipes left, next scope appears. ACTUAL Stunted swipe appears to register late, fails to switch scope. Please feel free to reassign if the gesture itself is dependent on time? Pathological use case but maybe worth examining if it exposes some pathological codepaths ;) . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1524488/+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
[Touch-packages] [Bug 1524488] Re: Manually setting the time into the past makes flickables misbehave
** 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) -- 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/1524488 Title: Manually setting the time into the past makes flickables misbehave Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Invalid Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Unexpected behavior while testing a U1 silo: TEST CASE 1. Open ubuntu-system-settings, set time manually into the past a few hours 2. Return to scopes 3. Swipe left for next scope EXPECTED Scope swipes left, next scope appears. ACTUAL Stunted swipe appears to register late, fails to switch scope. Please feel free to reassign if the gesture itself is dependent on time? Pathological use case but maybe worth examining if it exposes some pathological codepaths ;) . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1524488/+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
[Touch-packages] [Bug 1524488] Re: Manually setting the time into the past makes flickables misbehave
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 the time into the past makes scopes sluggish, unnavigable + Manually setting the time into the past makes flickables misbehave ** Also affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1524488 Title: Manually setting the time into the past makes flickables misbehave Status in mir package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: Unexpected behavior while testing a U1 silo: TEST CASE 1. Open ubuntu-system-settings, set time manually into the past a few hours 2. Return to scopes 3. Swipe left for next scope EXPECTED Scope swipes left, next scope appears. ACTUAL Stunted swipe appears to register late, fails to switch scope. Please feel free to reassign if the gesture itself is dependent on time? Pathological use case but maybe worth examining if it exposes some pathological codepaths ;) . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1524488/+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