[Touch-packages] [Bug 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

I think I understand this now. See bug 1661128. Two bugs, one cause.

** Changed in: mir
   Status: Confirmed => In Progress

** Changed in: miral (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: mir
   Importance: Undecided => Medium

** Changed in: mir/0.26
   Importance: Undecided => Medium

** Changed in: mir (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate)

[Daniel van Vugt]

OK, I think I understand this now. Maybe.

The problem is that the unity8 nested server BufferStream has not been
assigned a frame_clock (doesn't know what monitor to sync to), so it's
defaulting to unthrottled behaviour even though the swap interval is 1.

This problem should probably occur with any nested server. However it
was not noticed in testing because it will only be perceptible if your
nested server is also slow enough that its rendering period aliases
visibly with the physical screen.

** Changed in: mir/0.26
   Status: Confirmed => Triaged

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: canonical-devices-system-image
   Status: Confirmed => Triaged

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  Triaged
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Unity8 stutters constantly (like half frame rate) on a high-end
  desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mir (Ubuntu)
   Status: New => Confirmed

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in Mir 0.26 series:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate)

[Daniel van Vugt]

So it seems like the issue is a combination of:
  1. Unity8 using a zero swap interval (somehow, by accident?)
  2. Unity8 taking around 10ms to render each frame -> 100Hz
  3. USC can only take one frame every 16.6ms (60Hz), so will drop half of what 
Unity8 produces.

This yields only 50Hz output to the screen, which is roughly only every
second frame from Unity8 reaching the screen, on an interval that's out
of phase with the screen. So that's the stuttering.

** Changed in: mir
Milestone: 0.26.1 => 1.0.0

** Changed in: mir
   Status: New => In Progress

** Also affects: mir/0.26
   Importance: Undecided
   Status: New

** Changed in: mir/0.26
   Importance: Undecided => High

** Changed in: mir/0.26
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: mir/0.26
Milestone: None => 0.26.1

** Changed in: mir/0.26
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Description changed:

- Unity8 stutters constantly (like half frame rate) on an i7 desktop.
+ Unity8 stutters constantly (like half frame rate) on a high-end desktop.
  
  This regression only happened recently, perhaps due to the introduction
  of Mir 0.26.0.
  
  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Unity8 stutters constantly (like half frame rate) on a high-end
  desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

** Also affects: mir/0.26
   Importance: Undecided
   Status: New

** Changed in: mir/0.26
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: mir/0.26
Milestone: None => 0.26.1

** Changed in: mir
   Status: New => Confirmed

** Changed in: mir/0.26
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in Mir 0.26 series:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: miral (Ubuntu)
   Status: New => Confirmed

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in Mir 0.26 series:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity8 (Ubuntu)
   Status: New => Confirmed

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in Mir 0.26 series:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

** Changed in: mir
Milestone: 0.26.1 => 1.0.0

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in Mir 0.26 series:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate)

[Daniel van Vugt]

And from Unity System Compositor I can get:

[2017-02-02 14:00:54.259614] compositor: Display 0x7fadf0007be0 averaged 53.175 
FPS, 0.000 ms/frame, latency 4.910 ms, 54 frames over 1.015 sec, 100% bypassed
[2017-02-02 14:00:55.260318] compositor: Display 0x7fadf0007be0 averaged 51.963 
FPS, 0.000 ms/frame, latency 5.290 ms, 52 frames over 1.000 sec, 100% bypassed
[2017-02-02 14:00:56.276872] compositor: Display 0x7fadf0007be0 averaged 46.234 
FPS, 0.000 ms/frame, latency 6.132 ms, 47 frames over 1.016 sec, 100% bypassed
[2017-02-02 14:00:57.301813] compositor: Display 0x7fadf0007be0 averaged 53.661 
FPS, 0.000 ms/frame, latency 5.796 ms, 55 frames over 1.024 sec, 100% bypassed
[2017-02-02 14:00:58.310135] compositor: Display 0x7fadf0007be0 averaged 53.554 
FPS, 0.000 ms/frame, latency 5.546 ms, 54 frames over 1.008 sec, 100% bypassed
[2017-02-02 14:00:59.326868] compositor: Display 0x7fadf0007be0 averaged 52.127 
FPS, 0.000 ms/frame, latency 5.053 ms, 53 frames over 1.016 sec, 100% bypassed
[2017-02-02 14:01:00.326897] compositor: Display 0x7fadf0007be0 averaged 39.998 
FPS, 0.000 ms/frame, latency 4.814 ms, 40 frames over 1.000 sec, 100% bypassed
[2017-02-02 14:01:01.326999] compositor: Display 0x7fadf0007be0 averaged 50.994 
FPS, 0.000 ms/frame, latency 5.067 ms, 51 frames over 1.000 sec, 100% bypassed
[2017-02-02 14:01:02.327102] compositor: Display 0x7fadf0007be0 averaged 59.993 
FPS, 0.000 ms/frame, latency 4.097 ms, 60 frames over 1.000 sec, 100% bypassed
[2017-02-02 14:01:03.327407] compositor: Display 0x7fadf0007be0 averaged 58.982 
FPS, 0.000 ms/frame, latency 4.778 ms, 59 frames over 1.000 sec, 100% bypassed
[2017-02-02 14:01:04.327648] compositor: Display 0x7fadf0007be0 averaged 55.986 
FPS, 0.000 ms/frame, latency 5.231 ms, 56 frames over 1.000 sec, 100% bypassed
[2017-02-02 14:01:05.327891] compositor: Display 0x7fadf0007be0 averaged 52.987 
FPS, 0.000 ms/frame, latency 5.004 ms, 53 frames over 1.000 sec, 100% bypassed
[2017-02-02 14:01:06.344845] compositor: Display 0x7fadf0007be0 averaged 49.166 
FPS, 0.000 ms/frame, latency 5.241 ms, 50 frames over 1.016 sec, 100% bypassed
[2017-02-02 14:01:07.345121] compositor: Display 0x7fadf0007be0 averaged 50.985 
FPS, 0.000 ms/frame, latency 5.065 ms, 51 frames over 1.000 sec, 100% bypassed
[2017-02-02 14:01:08.347282] compositor: Display 0x7fadf0007be0 averaged 51.887 
FPS, 0.000 ms/frame, latency 4.079 ms, 52 frames over 1.002 sec, 100% bypassed
[2017-02-02 14:01:09.372834] compositor: Display 0x7fadf0007be0 averaged 52.654 
FPS, 0.000 ms/frame, latency 4.522 ms, 54 frames over 1.025 sec, 100% bypassed
[2017-02-02 14:01:10.380422] compositor: Display 0x7fadf0007be0 averaged 49.623 
FPS, 0.000 ms/frame, latency 4.794 ms, 50 frames over 1.007 sec, 100% bypassed
[2017-02-02 14:01:11.396684] compositor: Display 0x7fadf0007be0 averaged 51.167 
FPS, 0.000 ms/frame, latency 5.505 ms, 52 frames over 1.016 sec, 100% bypassed

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Mir 0.26 series:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Unity8 stutters constantly (like half frame rate) on a high-end
  desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity8 (Ubuntu)
   Status: New => Confirmed

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Unity8 stutters constantly (like half frame rate) on an i7 desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661153] Re: package python-crypto 2.6.1-6build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-crypto 2.6.1-6build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-crypto package in Ubuntu:
  New

Bug description:
  I am unable to install mysql related any package.

  If are sure you want to downgrade to 5.7, remove the file
  /var/lib/mysql/debian-*.flag and try installing again.
  dpkg: error processing archive 
/var/cache/apt/archives/mysql-server-5.7_5.7.14-1+deb.sury.org~trusty+0_amd64.deb
 (--unpack):
   subprocess new pre-installation script returned error exit status 1
  Errors were encountered while processing:
   
/var/cache/apt/archives/mysql-server-5.7_5.7.14-1+deb.sury.org~trusty+0_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-crypto 2.6.1-6build1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Feb  2 10:05:50 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-6build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1661153/+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 1661153] [NEW] package python-crypto 2.6.1-6build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dhiraj Patra]

Public bug reported:

I am unable to install mysql related any package.

If are sure you want to downgrade to 5.7, remove the file
/var/lib/mysql/debian-*.flag and try installing again.
dpkg: error processing archive 
/var/cache/apt/archives/mysql-server-5.7_5.7.14-1+deb.sury.org~trusty+0_amd64.deb
 (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 
/var/cache/apt/archives/mysql-server-5.7_5.7.14-1+deb.sury.org~trusty+0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-crypto 2.6.1-6build1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Feb  2 10:05:50 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: python-crypto
Title: package python-crypto 2.6.1-6build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-crypto (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial

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

Title:
  package python-crypto 2.6.1-6build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-crypto package in Ubuntu:
  New

Bug description:
  I am unable to install mysql related any package.

  If are sure you want to downgrade to 5.7, remove the file
  /var/lib/mysql/debian-*.flag and try installing again.
  dpkg: error processing archive 
/var/cache/apt/archives/mysql-server-5.7_5.7.14-1+deb.sury.org~trusty+0_amd64.deb
 (--unpack):
   subprocess new pre-installation script returned error exit status 1
  Errors were encountered while processing:
   
/var/cache/apt/archives/mysql-server-5.7_5.7.14-1+deb.sury.org~trusty+0_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-crypto 2.6.1-6build1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Feb  2 10:05:50 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-6build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1661153/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

No problem specifically with Qt... System Settings is still silky-smooth
under Mir demo servers:

  mirrun system-settings

So the issue seems to be localised to the Unity8 server/compositor.

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate)

[Daniel van Vugt]

No problem specifically with Qt... System Settings is still silky-smooth
under Mir demo servers:

  mirrun system-settings

So the issue seems to be localised to the Unity8 server/compositor.

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 stutters constantly (like half frame rate) on an i7 desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1560909] Re: Intermittent failure in mir_demo_client_multistream smoke test on krillin

[Daniel van Vugt]

** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
   Status: New => Fix Released

** Changed in: mir (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1560909

Title:
  Intermittent failure in mir_demo_client_multistream smoke test on
  krillin

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Looks unrelated to the MP.

  https://mir-jenkins.ubuntu.com/job/device-runtests-
  mir/device_type=krillin/225/console

  06:50:15 [2016-03-22 06:50:15.228323] GLRenderer: GL max texture size = 4096
  06:50:15 [2016-03-22 06:50:15.228437] GLRenderer: GL framebuffer bits: 
RGBA=, depth=24, stencil=8
  06:50:18 libevdev error in fix_invalid_absinfo: BUG: Device "mtk-tpd" has 
invalid ABS_MT_TRACKING_ID rangeQuitting; have a nice day.
  06:50:19 [2016-03-22 06:50:19.212164] mirserver: Stopping
  06:50:19 I: [FAILED] mir_demo_client_multistream
  06:50:19 [timestamp] End : mir_demo_client_multistream 
2016-03-22T06:50:19+

  Seems the client never acknowledges the SIGTERM

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1560909/+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 1659298] Re: Caught exception at Mir/EGL driver boundary (in setSwapInterval) in clients and tests

[Daniel van Vugt]

** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
   Status: New => Fix Released

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

-- 
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/1659298

Title:
  Caught exception at Mir/EGL driver boundary (in setSwapInterval) in
  clients and tests

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  messages like this have started appearing in logs and test runs:

  root@ubuntu-phablet:/home/phablet/mir/bin# LD_LIBRARY_PATH=../lib 
./mir_demo_client_egltriangle.bin 
  Mir chose pixel format 1.
  Using pixel format 2.
  Current active output is 540x960 +0+0
  [2017-01-25 08:38:53.915333]  AndroidWindow: Caught exception at 
Mir/EGL driver boundary (in setSwapInterval): Dynamic exception type: 
St12system_error
  std::exception::what: Operation not permitted

  The don't appear to be causing test or client smoketest failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1659298/+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 1645115] Re: Auto update frequency isn't proper

[Launchpad Bug Tracker]

[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Auto update frequency isn't proper

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  With Ubuntu 16.04:

  I suspect that security updates aren't installed immediately:

  The file "/var/log/apt/history.log" shows that "/usr/bin/unattended-upgrade" 
is executed every 2-3 days.
  By reading the "Software Updater" app/GUI I see that there are security 
updates available which weren't installed.

  In "Software & Updates", under the "Updates" tab:
  The field "When there are security updates: " is set to the value "Download 
and install automatically".
  Also all checkboxes at the top (below "Install updates from: ") are checked 
(with a V ).

  Note that the file "/etc/apt/apt.conf.d/50unattended-upgrades"
  contains only comments (lines starting with "//").

  Version of unattended-upgrades: 0.90ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1645115/+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 1661030] Re: regession tests failing after stackprofile test is run

[John Johansen]

Alright, so I broke complain mode for execs with
  UBUNTU: SAUCE: apparmor: Fix no_new_privs blocking change_onexec when using 
stacked namespaces

I have a fix and the test kernels are building and will be available in
  http://people.canonical.com/~jj/linux+jj/

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

Title:
  regession tests failing after stackprofile test is run

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #2)

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap
  mkswap: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.
  swapon: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.

  running sd_flags

  running setattr

  running symlink

  running syscall

  running tcp

  running unix_fd_server

  running unix_socket_pathname
  xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw)
  xpass: AF_UNIX pathname socket (dgram); confined client w/ access (rw)

  running unix_socket_abstract

  

[Touch-packages] [Bug 1570327] Re: [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_noticed

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1570327

Title:
  [testsfail]
  ApplicationNotRespondingDetection.failure_to_pong_is_noticed

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/844/consoleFull

  18:51:00 11: [ RUN ] 
ApplicationNotRespondingDetection.failure_to_pong_is_noticed
  18:51:00 11: [2016-04-13 18:50:59.936136] mirserver: Starting
  18:51:00 11: [2016-04-13 18:51:00.526634] mirserver: Selected driver: dummy 
(version 0.22.0)
  18:51:02 11: [2016-04-13 18:51:02.694384] mirserver: Using software cursor
  18:51:03 11: [2016-04-13 18:51:03.829134] mirserver: Initial display 
configuration:
  18:51:03 11: [2016-04-13 18:51:03.876013] mirserver: 1.1: VGA 0.0" 0x0mm
  18:51:03 11: [2016-04-13 18:51:03.894852] mirserver: Current mode 1600x1600 
60.00Hz
  18:51:03 11: [2016-04-13 18:51:03.897768] mirserver: Preferred mode 1600x1600 
60.00Hz
  18:51:03 11: [2016-04-13 18:51:03.900158] mirserver: Logical position +0+0
  18:51:05 11: [2016-04-13 18:51:05.590816] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  18:51:05 11: [2016-04-13 18:51:05.932306] mirserver: Mir version 0.22.0
  18:51:26 11: 
/��BUILDDIR��/mir-0.22.0+xenial862bzr3452/tests/acceptance-tests/test_application_not_responding_detection.cpp:115:
 Failure
  18:51:26 11: Value of: marked_as_unresponsive.wait_for(10s)
  18:51:26 11: Actual: false
  18:51:26 11: Expected: true
  18:51:28 11: [2016-04-13 18:51:28.042141] mirserver: Stopping
  18:51:30 11: [ FAILED ] 
ApplicationNotRespondingDetection.failure_to_pong_is_noticed (30224 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570327/+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 1645284] Re: miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager tiling) are broken by lp:mir

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1645284

Title:
  miral::ActiveOutputsMonitor (and therefore miral-shell --window-
  manager tiling) are broken by lp:mir

Status in Mir:
  Fix Released
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  The change from DisplayConfigurationReport to
  DisplayConfigurationObserver means that downstream can no longer
  subscribe early enough to get the initial display configuration.

  This is because they need call
  "server.the_display_configuration_observer_registrar()" which is not
  available until after the server is initialized.

  The internal reports avoid this by being wired into the
  DefaultServerConfiguration constructor so they are registered at the
  start of initialization.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1645284/+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 1240909] Re: [performance] Restore support for better-than-triple buffering by default.

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1240909

Title:
  [performance] Restore support for better-than-triple buffering by
  default.

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  We really should restore support for double-buffering (or better)
  where possible. Presently we're on triple-buffering all the time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1240909/+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 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1606418

Title:
  PointerConfinement.test_we_update_our_confined_region_on_a_resize

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Randomly fails 1/100 times.
  
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1612/console

  Looking into it, most likely a race with surface resize...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1606418/+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 1591328] Re: Pointer/cursor input lag in unity8 session

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

-- 
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/1591328

Title:
  Pointer/cursor input lag in unity8 session

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Mouse pointer suffers of heavy input lag on my laptop, might also
  affect tablet

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591328/+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 1556142] Re: Changing scale, formFactor or DPI in display configuration causes renderer teardown/recreate unnecessarily

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1556142

Title:
  Changing scale, formFactor or DPI in display configuration causes
  renderer teardown/recreate unnecessarily

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  DisplayConfiguration contains the properties scale, form factor and
  dpi, which is information graphical toolkits can use when drawing
  their UIs.

  However if the shell changes any of these values, it causes the server
  MultiThreadedCompositor to tear down the renderer, release the GL
  context, create a new GL context and build a new renderer. This can
  result in a UI flicker.

  It would be nice to avoid this unnecessary tear-down/recreate cycle
  for DisplayConfiguration changes that don't require it.

  However then, need an API to allow QtMir detect those properties
  changed. Currently QtMir only checks for DisplayConfiguration change
  when the compositor restarts, because no notification API was
  available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1556142/+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 1644062] Re: googletest 1.8.0-2 (on zesty) breaks existing builds [add_library cannot create target "gmock" ...]

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
  cannot create target "gmock" ...]

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Fix Released
Status in cmake-extras package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  Fix Released
Status in googletest package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 1.8.0-2 (from 1.7.0-4), our previously-working
  builds break:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock" because another target with the
 same name already exists.  The existing target is a static library created
 in source directory "/usr/src/googletest/googlemock".  See documentation
 for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


   CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock_main" because another target with
 the same name already exists.  The existing target is a static library
 created in source directory "/usr/src/googletest/googlemock".  See
 documentation for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


   CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
 install TARGETS given target "gmock" which does not exist in this
 directory.

  The CMakeLists.txt in our project that triggers this error does this:

  set(old_cxx_flags ${CMAKE_CXX_FLAGS})
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wno-old-style-cast 
-Wno-missing-field-initializers")
  find_package(GMock)
  set(CMAKE_CXX_FLAGS ${old_cxx_flags})

  This used to work fine, but no breaks on zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644062/+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 1645372] Re: support display scaling slider in unity8

[Daniel van Vugt]

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

-- 
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/1645372

Title:
  support display scaling slider in unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645372/+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 1642504] Re: [regression] mir_proving_server crashes with std::exception::what: add_options() must be called before the_options()

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1642504

Title:
  [regression] mir_proving_server crashes with std::exception::what:
  add_options() must be called before the_options()

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] mir_proving_server (from lp:mir) crashes with:

  $ sudo bin/mir_proving_server
  MIR_CLIENT_PLATFORM_PATH=bin/../lib/client-modules/
  MIR_SERVER_PLATFORM_PATH=bin/../lib/server-modules/
  LD_LIBRARY_PATH=bin/../lib
  exec=bin/mir_proving_server.bin
  [2016-11-17 16:33:52.015996]  eglstream: EGLStream platform is 
unsupported: Missing required extensions: EGL_EXT_platform_device 
EGL_EXT_device_base
  [2016-11-17 16:33:52.016058] mirplatform: Found graphics driver: 
mir:eglstream-kms (version 0.25.0)
  [2016-11-17 16:33:52.016648] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.25.0)
  [2016-11-17 16:33:52.016689] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.25.0)
  [2016-11-17 16:33:52.016838] mirplatform: Found graphics driver: mir:android 
(version 0.25.0)
  [2016-11-17 16:33:52.016965] mirplatform: Found graphics driver: 
mir:stub-graphics (version 0.25.0)
  [2016-11-17 16:33:52.016979] mirplatform: Found graphics driver: 
throw-on-creation (version 0.25.0)
  ERROR: 
/home/dan/bzr/mir/trunk/src/platform/options/default_configuration.cpp(250): 
Throw in function boost::program_options::options_description_easy_init 
mir::options::DefaultConfiguration::add_options()
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: add_options() must be called before the_options()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1642504/+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 1642473] Re: [regression] FTBFS when cross compiling to yakkety from zesty: test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1642473

Title:
  [regression] FTBFS when cross compiling to yakkety from zesty:
  test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] FTBFS when cross compiling to yakkety from zesty:

  [ 66%] Building CXX object 
tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/test_client_extensions.cpp.o
  /home/dan/bzr/mir/trunk/tests/acceptance-tests/test_client_extensions.cpp: In 
member function ‘virtual void 
ClientExtensions_can_load_an_extension_Test::TestBody()’:
  
/home/dan/bzr/mir/trunk/tests/acceptance-tests/test_client_extensions.cpp:34:36:
 error: ‘Ne’ was not declared in this scope
   ASSERT_THAT(ext_raw, Ne(nullptr));
  ^
  
/home/dan/bzr/mir/trunk/tests/acceptance-tests/test_client_extensions.cpp:34:37:
 error: ‘ASSERT_THAT’ was not declared in this scope
   ASSERT_THAT(ext_raw, Ne(nullptr));
   ^
  
/home/dan/bzr/mir/trunk/tests/acceptance-tests/test_client_extensions.cpp:38:55:
 error: ‘StrEq’ was not declared in this scope
   EXPECT_THAT(ext->favorite_flavor(), StrEq("banana"));
 ^
  
/home/dan/bzr/mir/trunk/tests/acceptance-tests/test_client_extensions.cpp:38:56:
 error: ‘EXPECT_THAT’ was not declared in this scope
   EXPECT_THAT(ext->favorite_flavor(), StrEq("banana"));
  ^

  
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1642473/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1570698

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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 1394369] Re: [testsfail] failure in CI in AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1394369

Title:
  [testsfail] failure in CI in
  AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Failure seen in CI, could not reproduce locally:
  
https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid-armhf/190/console

  Test seems to check timing (and today the CI server seemed
  particularly bogged-down).

  Not sure if this is the same root-cause as: lp: #1373826 (which has a
  similar description).

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1394369/+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 1646700] Re: mir_proving_server's four finger swipe to switch apps leaks touch events to the clients

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1646700

Title:
  mir_proving_server's four finger swipe to switch apps leaks touch
  events to the clients

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  mir_proving_server's four finger swipe to switch apps leaks touch
  events to the clients.

  Before the gesture completes, some touch apps (e.g.
  mir_demo_client_target/fingerpaint) incorrectly receive and interpret
  the four-finger touches.

  Is this a regression or did I just never test enough on a large
  touchscreen with touch-sensitive apps?...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1646700/+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 1641166] Re: Server::override_the_coordinate_translator() cannot be effectively used downstream

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1641166

Title:
  Server::override_the_coordinate_translator() cannot be effectively
  used downstream

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Being able to switch the debug APIs on at runtime is needed by Unity8
  to address autopilot issues.

  According to the documentation in
  include/server/mir/scene/coordinate_translator.h the
  CoordinateTranslator interface can be implemented by throwing
  std::runtime_error. Vis:

   * \note It is acceptable for this call to unconditionally throw a 
std::runtime_error.
   *   It is not required for normal functioning of the server or 
clients; clients which
   *   use the debug extension will receive an appropriate failure 
notice.

  However, the relevant code in
  src/server/frontend/protobuf_message_processor.cpp is:

  try
  {
  ...
  }
  catch (mir::frontend::unsupported_feature const&)
  {
  ...
  }

  As mir::frontend::unsupported_feature subclasses std::runtime_error
  this does not correctly handle std::runtime_error.

  Further, as unsupported_feature is not a public class, this can't be
  thrown by downstream code. (Although I suspect throwing an identical
  class with the same name will trick the RTTI implementation.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1641166/+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 1644189] Re: Shell doesn't know when base display config has changed

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1644189

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1643432] Re: [ FAILED ] NestedServer.nested_platform_connects_and_disconnects

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1643432

Title:
  [ FAILED ] NestedServer.nested_platform_connects_and_disconnects

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [ FAILED ] NestedServer.nested_platform_connects_and_disconnects:

  05:45:16 11: [ RUN ] NestedServer.nested_platform_connects_and_disconnects
  ...
  05:45:19 11: [2016-11-21 05:45:19.675640] mirserver: Stopping
  05:45:19 11: [2016-11-21 05:45:19.935809] mirserver: Stopping
  05:45:20 11: 
/<>/mir-0.25.0+xenial2940bzr3835/tests/acceptance-tests/test_nested_mir.cpp:721:
 Failure
  05:45:20 11: Actual function call count doesn't match 
EXPECT_CALL(*mock_session_mediator_report, session_disconnect_called(_))...
  05:45:20 11: Expected: to be called once
  05:45:20 11: Actual: never called - unsatisfied and active
  05:45:20 11: [ FAILED ] NestedServer.nested_platform_connects_and_disconnects 
(4157 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1643432/+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 1586311] Re: [regression] Two fingers in mir_proving_server now resizes/moves app windows (two finger apps unusable)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1586311

Title:
  [regression] Two fingers in mir_proving_server now resizes/moves app
  windows (two finger apps unusable)

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] Two fingers in mir_proving_server now resizes/moves app
  windows (two finger apps unusable)

  Two finger gestures are commonly used by apps for pinch/zoom and
  should never be captured by the shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1586311/+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 1494197] Re: [trusted prompt sessions] Can't open two prompt sessions at the same time

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1494197

Title:
  [trusted prompt sessions] Can't open two prompt sessions at the same
  time

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  current build number: 109
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-10 06:07:46
  version version: 109
  version ubuntu: 20150910
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

  Steps:
  1. Open the note app , and it opens at the regesiter page
  2.Don't sign in the note account and open twitter app

  Expectation:
  After step 2#,we can open the twitter ,and it will at the sign in page

  Actual result:
   we can't open twitter account ,there is a hint that we can only open one 
account at the same time :Account window could not be opened. You can only 
create one account at a time ;please try again after closing all other account 
windows.

  Note: I attached a screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1494197/+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 1644075] Re: [regression] Those mir_demo_client_* which default to fullscreen now ignore the size parameter (-s WIDTHxHEIGHT)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1644075

Title:
  [regression] Those mir_demo_client_* which default to fullscreen now
  ignore the size parameter (-s WIDTHxHEIGHT)

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Those mir_demo_client_* which default to fullscreen now ignore the
  size parameter (-s WIDTHxHEIGHT), instead choosing to stay in
  fullscreen mode.

  This applies to mirvanity too, making testing of windowed client
  latency difficult.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644075/+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 1628794] Re: Valgrind failure on mir_acceptance_tests - leak on incoming buffer in Requests::free_buffer(int)

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1628794

Title:
  Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
  Requests::free_buffer(int)

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Valgrind failure on mir_acceptance_tests - leak in
  mir::client::BufferVault::wire_transfer_inbound(int)

  It's happened twice now. Yesterday on kdub's branch and today on mine:

  05:20:36 9: ==2515== 80 (32 direct, 48 indirect) bytes in 1 blocks are 
definitely lost in loss record 20 of 37
  05:20:36 9: ==2515== at 0x4C2D1AF: operator new(unsigned long) (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  05:20:36 9: ==2515== by 0x54C74F2: NewCallback 
(callback.h:412)
  05:20:36 9: ==2515== by 0x54C74F2: (anonymous 
namespace)::Requests::free_buffer(int) (buffer_stream.cpp:274)
  05:20:36 9: ==2515== by 0x54CDB88: free_buffer (buffer_vault.cpp:111)
  05:20:36 9: ==2515== by 0x54CDB88: 
mir::client::BufferVault::wire_transfer_inbound(int) (buffer_vault.cpp:265)
  05:20:36 9: ==2515== by 0x54D11DD: operator() (functional:2136)
  05:20:36 9: ==2515== by 0x54D11DD: 
mir::client::AtomicCallback<>::operator()() const (atomic_callback.h:56)
  05:20:36 9: ==2515== by 0x54E1128: 
mir::client::rpc::MirProtobufRpcChannel::process_event_sequence(std::__cxx11::basic_string const&) 
(mir_protobuf_rpc_channel.cpp:341)
  05:20:36 9: ==2515== by 0x54E2208: 
mir::client::rpc::MirProtobufRpcChannel::on_data_available() 
(mir_protobuf_rpc_channel.cpp:470)
  05:20:36 9: ==2515== by 0x54E68AD: 
operator() 
(stream_socket_transport.cpp:40)
  05:20:36 9: ==2515== by 0x54E68AD: std::_Function_handler const&), 
mir::client::rpc::TransportObservers::on_data_available()::$_0>::_M_invoke(std::_Any_data
 const&, std::shared_ptr const&) 
(functional:1740)
  05:20:36 9: ==2515== by 0x54E6B7F: operator() (functional:2136)
  05:20:36 9: ==2515== by 0x54E6B7F: 
mir::ThreadSafeList::for_each(std::function const&)> const&) 
(thread_safe_list.h:80)
  05:20:36 9: ==2515== by 0x54E679D: on_data_available 
(stream_socket_transport.cpp:40)
  05:20:36 9: ==2515== by 0x54E679D: 
mir::client::rpc::StreamSocketTransport::dispatch(unsigned int) 
(stream_socket_transport.cpp:208)
  05:20:36 9: ==2515== by 0x5B700E3: 
mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:210)
  05:20:36 9: ==2515== by 0x5B700E3: 
mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) 
(multiplexing_dispatchable.cpp:210)
  05:20:36 9: ==2515== by 0x5B726B6: (anonymous 
namespace)::dispatch_loop(std::__cxx11::basic_string const&, 
std::shared_ptr,
 std::shared_ptr, std::function const&) 
(threaded_dispatcher.cpp:211)
  05:20:36 9: ==2515== by 0x5B7684E: void std::_Bind_simple, 
std::allocator >, 
std::shared_ptr,
 std::shared_ptr, std::function))(std::__cxx11::basic_string const&, 
std::shared_ptr,
 std::shared_ptr, std::function 
const&)>::_M_invoke<0ul, 1ul, 2ul, 3ul>(std::_Index_tuple<0ul, 1ul, 2ul, 3ul>) 
(functional:1399)
  05:20:36 9: ==2515== by 0x695350E: ??? (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.22)
  05:20:36 9: ==2515== by 0x6E3E709: start_thread (pthread_create.c:333)
  05:20:36 9: ==2515== by 0x715D0FE: clone (clone.S:105)
  05:20:36 9: ==2515==
  05:20:36 9: ==2515== 80 (32 direct, 48 indirect) bytes in 1 blocks are 
definitely lost in loss record 21 of 37
  05:20:36 9: ==2515== at 0x4C2D1AF: operator new(unsigned long) (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  05:20:36 9: ==2515== by 0x54C7363: NewCallback 
(callback.h:412)
  05:20:36 9: ==2515== by 0x54C7363: (anonymous 
namespace)::Requests::allocate_buffer(mir::geometry::Size, MirPixelFormat, int) 
(buffer_stream.cpp:262)
  05:20:36 9: ==2515== by 0x54CDBE8: alloc_buffer (buffer_vault.cpp:106)
  05:20:36 9: ==2515== by 0x54CDBE8: 
mir::client::BufferVault::wire_transfer_inbound(int) (buffer_vault.cpp:267)
  05:20:36 9: ==2515== by 0x54D11DD: operator() (functional:2136)
  05:20:36 9: ==2515== by 0x54D11DD: 
mir::client::AtomicCallback<>::operator()() const (atomic_callback.h:56)
  05:20:36 9: ==2515== by 0x54E1128: 
mir::client::rpc::MirProtobufRpcChannel::process_event_sequence(std::__cxx11::basic_string const&) 
(mir_protobuf_rpc_channel.cpp:341)
  05:20:36 9: ==2515== by 0x54E2208: 
mir::client::rpc::MirProtobufRpcChannel::on_data_available() 
(mir_protobuf_rpc_channel.cpp:470)
  05:20:36 9: ==2515== by 0x54E68AD: 
operator() 
(stream_socket_transport.cpp:40)
  05:20:36 9: ==2515== by 0x54E68AD: std::_Function_handler const&), 

[Touch-packages] [Bug 1639749] Re: When pointer motion crosses window borders SurfaceInputDispatcher injected events increase accumulated relative motion

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1639749

Title:
  When pointer motion crosses window borders SurfaceInputDispatcher
  injected events increase accumulated relative motion

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  SurfaceInputDispatcher keeps track of input event targets - for
  historic reason those are called guesture owners - when it detects
  that the receiver of a pointer event is a different window it will
  send enter events to the new window and exit events to the old window.
  Those events contain the same attributes as the original pointer
  event. After sending the enter event the original motion event is also
  dispatched.

  Now if the new window accumulates the pointer events (like the nested
  server) to track a cursor position this tracking will now add the
  relative motion of the original event twice.

  We could decide to not send the original motion event after having
  provided the enter event. But that might not work for cases where the
  original event was a pointer button up/down event. Since we would have
  to emit that state change too. So that leaves us with nullifying the
  relative motion event in one case, or ignoring relative motion in
  enter exit events in our own cursor position tracker..

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1639749/+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 1388490] Re: Frame rate is artificially low on Diamondville Intel Atom systems due to aggressive power management

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1388490

Title:
  Frame rate is artificially low on Diamondville Intel Atom systems due
  to aggressive power management

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Running a server and a few clients on an Atom N270 (requires vivid) is
  very stuttery and apparently limited to around 20 FPS.

  However this limitation is a bug. Firstly I notice the system is still
  70% idle according to top. And if I drag the mouse constantly over a
  surface or move a window constantly, the rendering (of everything)
  becomes perfectly smooth ~60 FPS. Also using --compositor-report=log
  on the Mir server shows the compositor render time even on this very
  weak machine is only 2.6ms.

  So we have a scheduling problem and forcing re-compositing via input
  is working around it. Obviously the clients themselves are not able to
  wake up the compositor frequently enough to ensure new frames get
  scheduled. However if I wake up the compositor using demo-shell mouse
  gestures then all is fast and smooth.

  This seems to be the same kind of scheduling problem also observed on
  higher-end systems when the compositor buffer pipeline is reduced -->
  bug 1377872

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1388490/+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 1624188] Re: [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1624188

Title:
  [  FAILED  ] ClientLatency.throttled_input_rate_yields_lower_latency

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [  FAILED  ] ClientLatency.throttled_input_rate_yields_lower_latency

  This bug has been reported before but those are Fix Released so
  opening a new bug for cleanliness...

  18:28:14 [ RUN  ] ClientLatency.throttled_input_rate_yields_lower_latency
  18:28:14 [2016-09-15 18:28:12.546342] mirserver: Starting
  18:28:14 [2016-09-15 18:28:12.546689] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  18:28:14 [2016-09-15 18:28:12.547778] mirserver: Using software cursor
  18:28:14 [2016-09-15 18:28:12.548236] mirserver: Initial display 
configuration:
  18:28:14 [2016-09-15 18:28:12.549443] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  18:28:14 [2016-09-15 18:28:12.550232] mirserver: Mir version 0.25.0
  18:28:14 [  debug   ] 99 frames sampled, averaging 2.0 frames latency
  18:28:14 [  debug   ]  0:  1  1  1  1  1  1  1  1  1  1
  18:28:14 [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  18:28:14 [  debug   ] 20:  1  1  1  1  1  1  1  1  2  2
  18:28:14 [  debug   ] 30:  2  2  2  3  3  2  2  2  2  2
  18:28:14 [  debug   ] 40:  2  2  2  2  2  2  2  2  2  2
  18:28:14 [  debug   ] 50:  2  2  2  3  3  3  2  3  3  3
  18:28:14 [  debug   ] 60:  2  3  2  3  3  3  2  2  2  2
  18:28:14 [  debug   ] 70:  3  3  3  2  3  3  3  3  3  3
  18:28:14 [  debug   ] 80:  2  3  3  3  2  2  2  2  3  2
  18:28:14 [  debug   ] 90:  3  3  3  3  2  2  3  3  3
  18:28:14 
/<>/mir-0.25.0+yakkety2225bzr3701/tests/acceptance-tests/test_latency.cpp:344:
 Failure
  18:28:14 Value of: observed_latency
  18:28:14 Expected: is <= 1.4
  18:28:14   Actual: 2.0404 (of type float)
  18:28:14 [2016-09-15 18:28:14.782202] mirserver: Stopping
  18:28:14 [  FAILED  ] ClientLatency.throttled_input_rate_yields_lower_latency 
(2252 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2199/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1624188/+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 1576600] Re: Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1576600

Title:
  Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir-on-X mouse input is irregular and stutters a bit, compared to Mir-
  on-KMS.

  Test case:
env MIR_CLIENT_INPUT_RATE=59 mir_demo_client_fingerpaint

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1576600/+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 1634868] Re: Add support for returning monitor EDIDs

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1634868

Title:
  Add support for returning monitor EDIDs

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Add support for returning monitor EDIDs

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1634868/+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 1646704] Re: [regression] Cross compiling from zesty to yakkety fails with *** No rule to make target 'gmock/libs/googlemock/gtest/libgtest.a'

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1646704

Title:
  [regression] Cross compiling from zesty to yakkety fails with *** No
  rule to make target 'gmock/libs/googlemock/gtest/libgtest.a'

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Try cross-compiling from zesty to yakkety:

  $ ./cross-compile-chroot.sh -d yakkety -a host
  ...
  make[2]: *** No rule to make target 'gmock/libs/googlemock/gtest/libgtest.a', 
needed by 'bin/mir_android_diagnostics'.  Stop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1646704/+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 1653789] Re: DisplayConfigurationTest.configure_session_removed_display failure

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1653789

Title:
  DisplayConfigurationTest.configure_session_removed_display failure

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  19:32:28 11: [2017-01-03 19:32:28.499435] mirserver: Session virtual void 
mir_test_framework::ConnectedClientHeadlessServer::SetUp() removed display 
configuration
  19:32:28 11: 
  19:32:28 11: GMOCK WARNING:
  19:32:28 11: Uninteresting mock function call - returning directly.
  19:32:28 11: Function call: session_configuration_removed(@0xbc0ca80 16-byte 
object <00-A8 97-0A 00-00 00-00 F0-A7 97-0A 00-00 00-00>)
  19:32:28 11: Stack trace:
  19:32:38 11: [2017-01-03 19:32:38.595943] mirserver: Stopping
  19:32:38 11: 
/<>/mir-0.26.0+xenial3324bzr3948/tests/acceptance-tests/test_new_display_configuration.cpp:1810:
 Failure
  19:32:38 11: Actual function call count doesn't match EXPECT_CALL(*observer, 
session_configuration_removed(_))...
  19:32:38 11: Expected: to be called once
  19:32:38 11: Actual: never called - unsatisfied and active
  19:32:38 11: [ FAILED ] 
DisplayConfigurationTest.configure_session_removed_display (11053 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3294/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1653789/+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 1656164] Re: Black screen with Raspberry Pi 3 VC4 Mesa driver

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1656164

Title:
  Black screen with Raspberry Pi 3 VC4 Mesa driver

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Using mir 0.25 on a rpi3 using the vc4 mesa driver, a blank screen is
  seen when starting mir_demo_server for example.

  Mir 0.24.1 works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1656164/+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 1656633] Re: i386 FTBFS: src/platforms/eglstream-kms/server/kms_display_configuration.cpp:88:47: error: narrowing conversion of ‘..._drmModeConnector::connector_id’ from ‘uint32_

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1656633

Title:
  i386 FTBFS: src/platforms/eglstream-
  kms/server/kms_display_configuration.cpp:88:47: error: narrowing
  conversion of ‘..._drmModeConnector::connector_id’ from ‘uint32_t {aka
  unsigned int}’ to ‘EGLAttrib {aka int}’ inside { } [-Werror=narrowing]

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  lp:mir fails to build on zesty i386:

  
/home/dan/bzr/mir/trunk/src/platforms/eglstream-kms/server/kms_display_configuration.cpp:
 In function 
‘std::vector 
{anonymous}::create_outputs(int, EGLDisplay)’:
  
/home/dan/bzr/mir/trunk/src/platforms/eglstream-kms/server/kms_display_configuration.cpp:88:47:
 error: narrowing conversion of ‘(& connector)->std::unique_ptr<_Tp, 
_Dp>::operator-><_drmModeConnector, std::function 
>()->_drmModeConnector::connector_id’ from ‘uint32_t {aka unsigned int}’ to 
‘EGLAttrib {aka int}’ inside { } [-Werror=narrowing]
   EGL_DRM_CONNECTOR_EXT, connector->connector_id,
  ~~~^~~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1656633/+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 1651633] Re: EDID data is missing in nested servers

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1651633

Title:
  EDID data is missing in nested servers

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  EDID data is missing in nested servers... or so I believe.

  The first server logs it:
  [2016-12-21 11:37:11.642422] mirserver:   Output 48: DisplayPort connected, 
used
  [2016-12-21 11:37:11.642434] mirserver:   EDID monitor name: DELL U2413
  [2016-12-21 11:37:11.642441] mirserver:   EDID manufacturer: DEL
  [2016-12-21 11:37:11.642448] mirserver:   EDID product code: 61510
  [2016-12-21 11:37:11.642463] mirserver:   Physical size 24.0" 520x320mm
  [2016-12-21 11:37:11.642470] mirserver:   Power is on

  But then the nested server does not:
  [2016-12-21 11:37:14.334128] mirserver:   Output 48: DisplayPort connected, 
used
  [2016-12-21 11:37:14.334142] mirserver:   Physical size 24.0" 520x320mm
  [2016-12-21 11:37:14.334148] mirserver:   Power is on

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651633/+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 1654478] Re: [regression] mir_acceptance_tests' death tests leave behind core files

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1654478

Title:
  [regression] mir_acceptance_tests' death tests leave behind core files

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] mir_acceptance_tests' death tests leave behind core files

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1654478/+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 1654023] Re: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1654023

Title:
  [regression] Development headers reference unknown header
  "mir_toolkit/mir_input_device_types.h" so some clients can't build at
  all any more

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Trying to build GTK+ which uses mircommon and mirclient, I'm getting:

  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmircursor.c:22:
  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"
  ^ 
   
  compilation terminated.
  Makefile:652: recipe for target 'gdkmircursor.lo' failed
  make[4]: *** [gdkmircursor.lo] Error 1
  make[4]: *** Waiting for unfinished jobs
  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdevicemanager.c:25:
  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"
  ^ 
   
  compilation terminated.   

  Makefile:652: recipe for target 'gdkmirdevicemanager.lo' failed   

  make[4]: *** [gdkmirdevicemanager.lo] Error 1 
 
  In file included from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0,
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24,
 
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21,
  
   from 
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22,
   from 
/home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdisplay.c:24:

  
/home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48:
 fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory
   #include "mir_toolkit/mir_input_device_types.h"

  It seems like this header was moved, or possibly it wasn't installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1654023/+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 1651391] Re: Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1651391

Title:
  Package mirtest-dev is missing a dependency on mir-renderer-gl-dev

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  tests/mirtest.pc.in contains the line:

  Requires: mirserver mirplatform mirclient mir-renderer-gl-dev

  But debian/control doesn't have the corresponding dependency on mir-
  renderer-gl-dev

  (I also think that mir-renderer-gl-dev.pc ought to be renamed mir-
  renderer-gl.pc, but that's a secondary issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651391/+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 1654612] Re: Setting the event handler after the surface has been created does nothing

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1654612

Title:
  Setting the event handler after the surface has been created does
  nothing

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Setting the surface spec for the event handler after the surface has
  been created does nothing.

  Reason:

  We dont set the event handler and recreate the input thread!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1654612/+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 1647575] Re: [regression] eglapps now all have window title "default"

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1647575

Title:
  [regression] eglapps now all have window title "default"

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  eglapps now all have window title "default"

  Previously (in Mir 0.24 at least) they each had unique titles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1647575/+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 1658604] Re: Mir FTBFS with MIR_USE_PRECOMPILED_HEADERS=OFF: error: ISO C++11 requires at least one argument for the "..." in a variadic macro [-Werror]

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1658604

Title:
  Mir FTBFS with MIR_USE_PRECOMPILED_HEADERS=OFF: error: ISO C++11
  requires at least one argument for the "..." in a variadic macro
  [-Werror]

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir fails to build (on zesty) using cmake
  -DMIR_USE_PRECOMPILED_HEADERS=OFF

  Several occurrences of:

  error: ISO C++11 requires at least one argument for the "..." in a
  variadic macro [-Werror]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1658604/+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 1653658] Re: Race between MirConnection::released() and MirConnection::~MirConnection() causes deadlocks, possible crashes and memory corruption

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1653658

Title:
  Race between MirConnection::released() and
  MirConnection::~MirConnection() causes deadlocks, possible crashes and
  memory corruption

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Race between MirConnection::released() and
  MirConnection::~MirConnection() causes deadlocks, possible crashes and
  memory corruption.

  This is happening reliably only in one of my branches on krillin,
  where the thread calling released() is deadlocked trying to use
  internal locking primitives that another thread calling ~MirConnection
  is in the process of destructing.

  It appears this is a known problem already judging by this comment:

  MirConnection::~MirConnection() noexcept
  {
  // We don't die while if are pending callbacks (as they touch this).
  // But, if after 500ms we don't get a call, assume it won't happen.
  connect_wait_handle.wait_for_pending(std::chrono::milliseconds(500));

  std::lock_guard lock(mutex);
  surface_map.reset();

  Although that code only waits for connections and doesn't bother to
  wait for releases which are the problem here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1653658/+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 1647573] Re: [ FAILED ] ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1647573

Title:
  [  FAILED  ]
  ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Test failed but really just looks like an assertion failure inside
  pthreads:

  04:22:35 [ RUN  ] 
ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error
  04:22:35
  04:22:35 [WARNING] /usr/src/gtest/src/gtest-death-test.cc:825:: Death tests 
use fork(), which is unsafe particularly in a threaded context. For this test, 
Google Test couldn't detect the number of threads.
  04:22:35 
/<>/mir-0.25.0+xenial3092bzr3867/tests/unit-tests/dispatch/test_threaded_dispatcher.cpp:416:
 Failure
  04:22:35 Death test: { ::mir::test::disable_core_dump(); { { 
md::ThreadedDispatcher* dispatcher; auto dispatchable = 
std::make_shared([]() { delete dispatcher; }); 
dispatchable->trigger(); dispatcher = new md::ThreadedDispatcher("Death 
thread", dispatchable); std::this_thread::sleep_for(10s); } ; } }
  04:22:35 Result: died but not with expected error.
  04:22:35   Expected: .*Destroying ThreadedDispatcher.*
  04:22:35 Actual msg:
  04:22:35 [  DEATH   ] mir_unit_tests.bin: tpp.c:84: 
__pthread_tpp_change_priority: Assertion `new_prio == -1 || (new_prio >= 
fifo_min_prio && new_prio <= fifo_max_prio)' failed.
  04:22:35 [  DEATH   ]
  04:22:35 [  FAILED  ] 
ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error 
(159 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3063/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1647573/+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 1655293] Re: [ FAILED ] RaiseSurfaces.key_event_with_cookie

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1655293

Title:
  [ FAILED ] RaiseSurfaces.key_event_with_cookie

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  08:59:51 11: 
/<>/mir-0.26.0+zesty3446bzr3915/tests/acceptance-tests/test_surface_raise.cpp:198:
 Failure
  08:59:51 11: Expected: mir_surface_get_focus(surface2)
  08:59:51 11: Which is: 0
  08:59:51 11: To be equal to: mir_surface_focused
  08:59:51 11: Which is: 1
  08:59:56 11: [2017-01-10 08:59:56.047566] mirserver: Stopping
  08:59:56 11: [ FAILED ] RaiseSurfaces.key_event_with_cookie (5757 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/3416/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1655293/+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 1651638] Re: [regression] Latency for fullscreen interval 0 clients (e.g. games and benchmarks) increased with the introduction of nested passthrough

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1651638

Title:
  [regression] Latency for fullscreen interval 0 clients (e.g. games and
  benchmarks) increased with the introduction of nested passthrough

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nested fullscreen interval 0 clients in Mir 0.25.0 had higher latency
  than interval 1 nested fullscreen clients.

  I've reproduced this a couple of times and it is concerning:

  Mir 0.25:
     Interval 0: 81ms  <-- regression
     Interval 1: 64ms  <-- improvement

  Mir 0.24:
 Interval 0: 70ms
 Interval 1: 96ms

  It's the obvious green spike in this chart:
  
https://docs.google.com/spreadsheets/d/1RbTVDbx04ohkF4-md3wAlgmxbSI1DttstnT6xdcXhZQ/pubchart?oid=1566479835=interactive

  Although this regression appears to be resolved in the 0.26 series
  (lp:mir) it's serious enough that we should look into finding what the
  cause was so that Mir 0.25.1 can get the same fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651638/+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 1657755] Re: android: overlays no longer are activated

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1657755

Title:
  android: overlays no longer are activated

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  android is using the fallback path with lp:mir ever since activating
  framedropping-by-default in rev3592 (activating the frame timing).
  Android disables overlays to avoid fencing issues (hangs) that can
  happen during framedropping (more info in LP: #1369763)

  This can be seen by running
  mir_demo_server_minimal --compositor-report log
  alongside 
  mir_demo_client_egltriangle  -f

  The overlay % drops from 100 to 0 after rev3592.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1657755/+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 1658605] Re: [regression] Mir cross-compile to vivid/armhf FTBFS with: mock_input_device_hub.h:33:18: error: ‘add_observer’ is not a type

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => 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/1658605

Title:
  [regression] Mir cross-compile to vivid/armhf FTBFS with:
  mock_input_device_hub.h:33:18: error: ‘add_observer’ is not a type

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  xenial$ ./cross-compile-chroot.sh -d vivid -a armhf

  In file included from 
/home/dan/bzr/mir/fixy/tests/unit-tests/input/test_config_changer.cpp:29:0:
  
/home/dan/bzr/mir/fixy/include/test/mir/test/doubles/mock_input_device_hub.h:33:18:
 error: ‘add_observer’ is not a type
   MOCK_METHOD1(add_observer, 
void(std::shared_ptr const&));
^
  
/home/dan/bzr/mir/fixy/include/test/mir/test/doubles/mock_input_device_hub.h:33:88:
 error: ISO C++ forbids declaration of ‘MOCK_METHOD1’ with no type 
[-fpermissive]
   MOCK_METHOD1(add_observer, 
void(std::shared_ptr const&));

  ^
  
/home/dan/bzr/mir/fixy/include/test/mir/test/doubles/mock_input_device_hub.h:34:18:
 error: ‘remove_observer’ is not a type
   MOCK_METHOD1(remove_observer, 
void(std::weak_ptr const&));
^
  ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1658605/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

It appears Unity8 is unthrottled, as in swap interval 0. So when I drag
a window around rapidly it matches the USB mouse event rate rather than
the display's refresh rate. MIR_CLIENT_PERF_REPORT shows:

[2017-02-02 10:29:02.531811] perf: : 131.00 FPS, render time 7.61ms, buffer lag 
22.92ms (4 buffers)
[2017-02-02 10:29:03.547757] perf: : 119.21 FPS, render time 8.36ms, buffer lag 
25.21ms (4 buffers)
[2017-02-02 10:29:04.551850] perf: : 95.61 FPS, render time 10.42ms, buffer lag 
31.74ms (4 buffers)
[2017-02-02 10:29:05.564508] perf: : 96.83 FPS, render time 10.30ms, buffer lag 
30.72ms (4 buffers)
[2017-02-02 10:29:06.579804] perf: : 94.58 FPS, render time 10.54ms, buffer lag 
31.32ms (4 buffers)
[2017-02-02 10:29:07.583854] perf: : 95.61 FPS, render time 10.42ms, buffer lag 
32.15ms (4 buffers)
[2017-02-02 10:29:08.584909] perf: : 131.86 FPS, render time 7.55ms, buffer lag 
22.92ms (4 buffers)
[2017-02-02 10:29:09.589854] perf: : 107.56 FPS, render time 9.26ms, buffer lag 
27.92ms (4 buffers)
[2017-02-02 10:29:10.603679] perf: : 120.43 FPS, render time 8.28ms, buffer lag 
24.52ms (4 buffers)
[2017-02-02 10:29:11.619541] perf: : 117.24 FPS, render time 8.50ms, buffer lag 
25.68ms (4 buffers)
[2017-02-02 10:29:12.628505] perf: : 120.03 FPS, render time 8.31ms, buffer lag 
25.00ms (4 buffers)
[2017-02-02 10:29:13.635706] perf: : 93.34 FPS, render time 10.67ms, buffer lag 
31.79ms (4 buffers)
[2017-02-02 10:29:14.643575] perf: : 122.14 FPS, render time 8.16ms, buffer lag 
24.94ms (4 buffers)
[2017-02-02 10:29:15.643621] perf: : 93.00 FPS, render time 10.72ms, buffer lag 
32.28ms (4 buffers)
[2017-02-02 10:29:16.647720] perf: : 108.56 FPS, render time 9.18ms, buffer lag 
27.95ms (4 buffers)
[2017-02-02 10:29:17.648820] perf: : 92.90 FPS, render time 10.73ms, buffer lag 
32.17ms (4 buffers)

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate)

[Daniel van Vugt]

It appears Unity8 is unthrottled, as in swap interval 0. So when I drag
a window around rapidly it matches the USB mouse event rate rather than
the display's refresh rate. MIR_CLIENT_PERF_REPORT shows:

[2017-02-02 10:29:02.531811] perf: : 131.00 FPS, render time 7.61ms, buffer lag 
22.92ms (4 buffers)
[2017-02-02 10:29:03.547757] perf: : 119.21 FPS, render time 8.36ms, buffer lag 
25.21ms (4 buffers)
[2017-02-02 10:29:04.551850] perf: : 95.61 FPS, render time 10.42ms, buffer lag 
31.74ms (4 buffers)
[2017-02-02 10:29:05.564508] perf: : 96.83 FPS, render time 10.30ms, buffer lag 
30.72ms (4 buffers)
[2017-02-02 10:29:06.579804] perf: : 94.58 FPS, render time 10.54ms, buffer lag 
31.32ms (4 buffers)
[2017-02-02 10:29:07.583854] perf: : 95.61 FPS, render time 10.42ms, buffer lag 
32.15ms (4 buffers)
[2017-02-02 10:29:08.584909] perf: : 131.86 FPS, render time 7.55ms, buffer lag 
22.92ms (4 buffers)
[2017-02-02 10:29:09.589854] perf: : 107.56 FPS, render time 9.26ms, buffer lag 
27.92ms (4 buffers)
[2017-02-02 10:29:10.603679] perf: : 120.43 FPS, render time 8.28ms, buffer lag 
24.52ms (4 buffers)
[2017-02-02 10:29:11.619541] perf: : 117.24 FPS, render time 8.50ms, buffer lag 
25.68ms (4 buffers)
[2017-02-02 10:29:12.628505] perf: : 120.03 FPS, render time 8.31ms, buffer lag 
25.00ms (4 buffers)
[2017-02-02 10:29:13.635706] perf: : 93.34 FPS, render time 10.67ms, buffer lag 
31.79ms (4 buffers)
[2017-02-02 10:29:14.643575] perf: : 122.14 FPS, render time 8.16ms, buffer lag 
24.94ms (4 buffers)
[2017-02-02 10:29:15.643621] perf: : 93.00 FPS, render time 10.72ms, buffer lag 
32.28ms (4 buffers)
[2017-02-02 10:29:16.647720] perf: : 108.56 FPS, render time 9.18ms, buffer lag 
27.95ms (4 buffers)
[2017-02-02 10:29:17.648820] perf: : 92.90 FPS, render time 10.73ms, buffer lag 
32.17ms (4 buffers)

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 stutters constantly (like half frame rate) on an i7 desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

** Changed in: mir
Milestone: None => 0.26.1

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate)

[Daniel van Vugt]

** Changed in: mir
Milestone: None => 0.26.1

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 stutters constantly (like half frame rate) on an i7 desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

See also bug 1661128

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate)

[Daniel van Vugt]

It actually feels like Unity8 has accidentally set swap interval to 2.
In previous Mir releases that would have been ignored, but in Mir 0.26.0
that is now honoured.

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 stutters constantly (like half frame rate) on an i7 desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661128] [NEW] [regression] Unity8 stutters constantly (like half frame rate)

[Daniel van Vugt]

Public bug reported:

Unity8 stutters constantly (like half frame rate) on an i7 desktop.

This regression only happened recently, perhaps due to the introduction
of Mir 0.26.0.

Surprisingly though, using the same Mir release I can start a demo
server on another VT and everything is silky-smooth. The problem only
seems to occur with Unity8.

** Affects: canonical-devices-system-image
 Importance: High
 Status: New

** Affects: mir
 Importance: High
 Assignee: Daniel van Vugt (vanvugt)
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: High
 Status: New


** Tags: performance regression

** Also affects: mir
   Importance: Undecided
   Status: New

** Changed in: mir
   Importance: Undecided => High

** Changed in: mir
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Summary changed:

- Unity8 stutters constantly (like half frame rate)
+ [regression] Unity8 stutters constantly (like half frame rate)

-- 
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/1661128

Title:
  [regression] Unity8 stutters constantly (like half frame rate)

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 stutters constantly (like half frame rate) on an i7 desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

Although animations should always be bound to real time. If your
animation changes speed with different vsync rate then the animation
logic that needs fixing. That said, it's useful right now for pointing
to bugs elsewhere in the system...

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

Running a Mir demo server on VT1 has no such trouble. Everything is
silky smooth there. Hmm, something unique about the way Unity8 is
interacting with Mir...

** Also affects: mir
   Importance: Undecided
   Status: New

** Changed in: mir
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661072] Re: mir 0.26 - spinner loading animation, minimize, maximize too fast

[Daniel van Vugt]

Indeed things are slightly weird in Unity8 with Mir 0.26.

Certainly the lag problem is gone(!), but some animations run too fast
and the whole shell is rendering around 20-30Hz despite the fact that
clients like egltriangle report that they get 60Hz.

It feels like Qt apps in a nested shell have accidentally found a way to
bypass vsync. Might be my fault, or it may be some change that has
occurred in Unity8.

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Tags added: unity8-desktop

-- 
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/1661072

Title:
  mir 0.26 - spinner loading animation, minimize, maximize too fast

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in miral package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1564695] Re: The command "who -m" doesn't work

[C de-Avillez]

Setting the coreutils task to invalid. 'who' reports based on wtmp. If
wtmp is not being updated by the applications, this is not a coreutils
issue.

** Changed in: coreutils (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  The command "who -m" doesn't work

Status in GNOME Terminal:
  Unknown
Status in Ubuntu Kylin:
  Incomplete
Status in coreutils package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Incomplete
Status in vte2.91 package in Ubuntu:
  Incomplete

Bug description:
  The command "who -m" doesn't work.

  ps: This bug also exists in ubuntu 16.04 x64 Daily build 20160329

  who -m只能没有作用，执行没有任何输出

  
  Steps:
  1. Install the Ubuntu Kylin 16.04 x64 Daily build 20160329
  2. Boot the system
  3. Open terminal, run the command "who -m"
  --Failed. It doesn't work after run the command. It should show the hostname 
and user asociated with stdin.

  Configuration:
  PC: Dell Vostor
  OS: Ubuntu Kylin 16.04 x64 Daily build 20160329

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1564695/+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 1661030] Re: regession tests failing after stackprofile test is run

[Steve Beattie]

I enabled the apparmor kernel debugging, and this is what shows up in
dmesg:

[ 3526.954133] AppArmor: unconfined exec no attachment
[ 3533.965480] AppArmor: unconfined attached to new label
[ 3533.965485] apparmor: clearing unsafe personality bits. 
/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/environ label=
[ 3533.965547] 
/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/environ

[ 3533.966847] audit: type=1400 audit(1485993479.943:350):
apparmor="ALLOWED" operation="exec"
profile="/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/environ"
name="/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/env_check"
pid=5722 comm="environ" requested_mask="x" denied_mask="x" fsuid=1000
ouid=1000
target="/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/environ//null-/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/env_check"

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

Title:
  regession tests failing after stackprofile test is run

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #2)

  

[Touch-packages] [Bug 1661030] Re: regession tests failing after stackprofile test is run

[Steve Beattie]

Okay, thanks to jj for providing kernels, I've now reproduced this in
zesty with his patch set applied.

It's failing in the 'confined/complain' tests. There's a bug in the
environ.c test that prevents the test harness from detecting/reporting
the failure correctly. When that's fixed, the output looks like:

ok: ENVIRON (elf): ux & regular env
ok: ENVIRON (elf): ux & sensitive env
ok: ENVIRON (elf): Ux & regular env
ok: ENVIRON (elf): Ux & sensitive env
ok: ENVIRON (elf): ix & regular env
ok: ENVIRON (elf): ix & sensitive env
ok: ENVIRON (elf): px & regular env
ok: ENVIRON (elf): px & sensitive env
ok: ENVIRON (elf): Px & regular env
ok: ENVIRON (elf): Px & sensitive env
ok: ENVIRON (elf): unconfined --> confined & regular env
ok: ENVIRON (elf): unconfined --> confined & sensitive env
Error: environ failed. Test 'ENVIRON (elf): confined/complain & regular env' 
was expected to 'pass'. Reason for failure 'FAIL: child failed'
Error: environ failed. Test 'ENVIRON (elf): confined/complain & sensitive env' 
was expected to 'pass'. Reason for failure 'FAIL: child failed'
ok: ENVIRON (shell script): ux & regular env
ok: ENVIRON (shell script): ux & sensitive env
ok: ENVIRON (shell script): Ux & regular env
ok: ENVIRON (shell script): Ux & sensitive env
ok: ENVIRON (shell script): px & regular env
ok: ENVIRON (shell script): px & sensitive env
ok: ENVIRON (shell script): Px & regular env
ok: ENVIRON (shell script): Px & sensitive env
ok: ENVIRON (shell script): ix & regular env
ok: ENVIRON (shell script): ix & sensitive env
ok: ENVIRON (shell script): unconfined --> confined & regular env
ok: ENVIRON (shell script): unconfined --> confined & sensitive env
Error: environ failed. Test 'ENVIRON (shell script): confined/complain & 
regular env' was expected to 'pass'. Reason for failure 'FAIL: child failed'
Error: environ failed. Test 'ENVIRON (shell script): confined/complain & 
sensitive env' was expected to 'pass'. Reason for failure 'FAIL: child failed'
ok: ENVIRON (elf): unconfined setuid helper
ok: ENVIRON (elf): unconfined setuid helper

Examining the individual test, the environ program is attempting to run
the env_check program while confined by a complain mode profile, but is
not permitted to do so. From strace output:

[pid  5706]
execve("/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/env_check",
["/home/ubuntu/tmp/apparmor-2.10.9"..., "FOO=BAR"], [/* 24 vars */]) =
-1 EACCES (Permission denied)

The apparmor audit message is correctly claiming that its allowing it
(but isn't permitted by the loaded policy):

[ 1726.404464] audit: type=1400 audit(1485991672.366:348):
apparmor="ALLOWED" operation="exec"
profile="/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/environ"
name="/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/env_check"
pid=5700 comm="environ" requested_mask="x" denied_mask="x" fsuid=1000
ouid=1000
target="/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/environ//null-/home/ubuntu/tmp/apparmor-2.10.95/tests/regression/apparmor/env_check"

but that doesn't seem to be the case. So I think there's something wonky
in John's patch set.

John, can you take a look at what's going on?

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  regession tests failing after stackprofile test is run

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

 

[Touch-packages] [Bug 1556142] Re: Changing scale, formFactor or DPI in display configuration causes renderer teardown/recreate unnecessarily

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1659039] Re: iproute2 catch up with upstream

[Jon Grimm]

** Changed in: iproute2 (Ubuntu)
 Assignee: (unassigned) => Jon Grimm (jgrimm)

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

Title:
  iproute2 catch up with upstream

Status in iproute2 package in Ubuntu:
  New

Bug description:
  https://answers.launchpad.net/ubuntu/+source/iproute2/+question/445831

  also tons of bugfixes:
  http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/log/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1659039/+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 1240909] Re: [performance] Restore support for better-than-triple buffering by default.

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1576600] Re: Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1570327] Re: [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_noticed

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1591328] Re: Pointer/cursor input lag in unity8 session

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1586311] Re: [regression] Two fingers in mir_proving_server now resizes/moves app windows (two finger apps unusable)

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1624188] Re: [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1394369] Re: [testsfail] failure in CI in AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1494197] Re: [trusted prompt sessions] Can't open two prompt sessions at the same time

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1388490] Re: Frame rate is artificially low on Diamondville Intel Atom systems due to aggressive power management

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1634868] Re: Add support for returning monitor EDIDs

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1646700] Re: mir_proving_server's four finger swipe to switch apps leaks touch events to the clients

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1645372] Re: support display scaling slider in unity8

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1639749] Re: When pointer motion crosses window borders SurfaceInputDispatcher injected events increase accumulated relative motion

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1647573] Re: [ FAILED ] ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1651633] Re: EDID data is missing in nested servers

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1644075] Re: [regression] Those mir_demo_client_* which default to fullscreen now ignore the size parameter (-s WIDTHxHEIGHT)

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1645284] Re: miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager tiling) are broken by lp:mir

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1653789] Re: DisplayConfigurationTest.configure_session_removed_display failure

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1644189] Re: Shell doesn't know when base display config has changed

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1651638] Re: [regression] Latency for fullscreen interval 0 clients (e.g. games and benchmarks) increased with the introduction of nested passthrough

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1643432] Re: [ FAILED ] NestedServer.nested_platform_connects_and_disconnects

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1647575] Re: [regression] eglapps now all have window title "default"

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails 

[Touch-packages] [Bug 1628794] Re: Valgrind failure on mir_acceptance_tests - leak on incoming buffer in Requests::free_buffer(int)

[Launchpad Bug Tracker]

This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1

---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI bumped to 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI unchanged at 14
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI unchanged at 11
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . New/improved toolkit APIs: MirInputConfig and related functions,
MirWindow and related functions, DisplayConfig and related functions,
MirScreencastSpec and related functions,
  . Support for configuring input configuration
  . Introduce toolkit extension mechanism for platform specific APIs.
  . Toolkit extensions for: mesa_drm_auth, set_gbm_device and
window_coordinate_translation
  . Screencasting to a specific MirBuffer.
  . Add DisplayConfigurationController::base_configuration() so downstreams
can get the base configuration. (Weirdly they can already set it.).
  . x11 platform: allow adjustable scale parameter.
  . Added EDID support: client API, server logging and in mirout.
  . mirout: Add newer attributes only available in the new display
config API: scaling factor, subpixel arrangement and form factor.
  . mirout: Log the orientation and logical size of each output too.
  . Replace the mir::Server-overridable Reports with Observers.
  . Add xkbcommon to mirclient.pc Requires.private.
  . Deprecate legacy toolkit APIs that will be removed in Mir 1.0
  . Introduced 'client-side vsync', which dramatically reduces latency
from the client to the screen (particularly for nested servers like
Unity8).
- Bugs fixed:
  . [performance] Restore support for better-than-triple buffering by
default. (LP: #1240909)
  . Frame rate is artificially low on Diamondville Intel Atom systems due
to aggressive power management (LP: #1388490)
  . [testsfail] failure in CI in
AndroidInputReceiverSetup.slow_raw_input_doesnt_cause_frameskipping
(LP: #1394369)
  . [trusted prompt sessions] Can't open two prompt sessions at the same
time (LP: #1494197)
  . Changing scale, formFactor or DPI in display configuration causes
renderer teardown/recreate unnecessarily (LP: #1556142)
  . [testsfail] ApplicationNotRespondingDetection.failure_to_pong_is_
noticed (LP: #1570327)
  . CI failure in TestClientInput.receives_one_touch_event_per_frame
(LP: #1570698)
  . Mir-on-X mouse input is jerky/stuttery compared to Mir-on-KMS
(LP: #1576600)
  . [regression] Two fingers in mir_proving_server now resizes/moves app
windows (two finger apps unusable) (LP: #1586311)
  . Pointer/cursor input lag in unity8 session (LP: #1591328)
  . PointerConfinement.test_we_update_our_confined_region_on_a_resize
(LP: #1606418)
  . [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency
(LP: #1624188)
  . Valgrind failure on mir_acceptance_tests - leak on incoming buffer in
Requests::free_buffer(int) (LP: #1628794)
  . Add support for returning monitor EDIDs (LP: #1634868)
  . When pointer motion crosses window borders SurfaceInputDispatcher
injected events increase accumulated relative motion (LP: #1639749)
  . [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA
dropping_latency_is_closer_to_zero_than_one) (LP: #1640366)
  . Server::override_the_coordinate_translator() cannot be effectively used
downstream (LP: #1641166)
  . [regression] FTBFS when cross compiling to yakkety from zesty:
test_client_extensions.cpp: error: ‘Ne’ was not declared in this scope
(LP: #1642473)
  . [regression] mir_proving_server crashes with std::exception::what:
add_options() must be called before the_options() (LP: #1642504)
  . [ FAILED ] NestedServer.nested_platform_connects_and_disconnects
(LP: #1643432)
  . googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
cannot create target "gmock" ...] (LP: #1644062)
  . [regression] Those mir_demo_client_* which default to fullscreen now
ignore the size parameter (-s WIDTHxHEIGHT) (LP: #1644075)
  . Shell doesn't know when base display config has changed (LP: #1644189)
  . miral::ActiveOutputsMonitor (and therefore miral-shell --window-manager
tiling) are broken by lp:mir (LP: #1645284)
  . mir_proving_server's four finger swipe to switch apps leaks touch
events to the clients (LP: #1646700)
  . [regression] Cross compiling from zesty to yakkety fails