touch-packages team mailing list archive

[Albert Astals Cid <albert.astals@xxxxxxxxxxxxx>]

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