From 1854563 at bugs.launchpad.net  Sun Dec  1 05:41:13 2019
From: 1854563 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 01 Dec 2019 05:41:13 -0000
Subject: [Bug 1854563] Re: Sync materia-gtk-theme 20190315-1 (universe) from
 Debian unstable (main)
References: <157510811257.31064.14015076822460317307.malonedeb@wampee.canonical.com>
Message-ID: <157517887456.31534.12401691196078641672.launchpad@wampee.canonical.com>

** Changed in: materia-gtk-theme (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854563

Title:
  Sync materia-gtk-theme 20190315-1 (universe) from Debian unstable
  (main)

Status in materia-gtk-theme package in Ubuntu:
  New

Bug description:
  Please sync materia-gtk-theme 20190315-1 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    [ Erich Eickmeyer ]
    * Fix Ubiquity theming issue (LP: #1822134)
      - Previous change did not fix issue
    * Fix Ubiquity theming issue (LP: #1822134)

  The Ubuntu change is now upstream.

  Changelog entries since current focal version 20190201-1ubuntu2:

  materia-gtk-theme (20190315-1) unstable; urgency=medium

    * New upstream version 20190315

   -- Sagar Ippalpalli <i.vikram15 at gmail.com>  Sun, 07 Apr 2019 20:33:24
  +0530

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/materia-gtk-theme/+bug/1854563/+subscriptions


From 1854558 at bugs.launchpad.net  Sun Dec  1 09:23:33 2019
From: 1854558 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Sun, 01 Dec 2019 09:23:33 -0000
Subject: [Bug 1854558] Re: Sync octave-dicom 0.2.2-4 (universe) from Debian
 unstable (main)
References: <157510158879.6226.4310686672437145746.malonedeb@gac.canonical.com>
Message-ID: <157519221365.22813.13549971131206485072.malone@chaenomeles.canonical.com>

https://launchpad.net/ubuntu/+source/octave-dicom/0.2.2-4ubuntu1

** Changed in: octave-dicom (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854558

Title:
  Sync octave-dicom 0.2.2-4 (universe) from Debian unstable (main)

Status in octave-dicom package in Ubuntu:
  Fix Released

Bug description:
  Please sync octave-dicom 0.2.2-4 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Build-depend on libgdcm-dev, not libgdcm2-dev.  Closes: #944718.
    * Add explicit build-dependency on cmake.
    * No-change rebuild against libgdcm3.0
    * No-change rebuild against libgdcm3.0

  Dependencies are adjusted in the Debian package too.

  Changelog entries since current focal version 0.2.2-3ubuntu1:

  octave-dicom (0.2.2-4) unstable; urgency=medium

    * d/control: Build-depend on libgdcm-dev.
      Thanks to Steve Langasek, for the patch (Closes: #944718)

   -- Rafael Laboissière <rafael at debian.org>  Fri, 29 Nov 2019 05:48:57
  -0300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/octave-dicom/+bug/1854558/+subscriptions


From 1854487 at bugs.launchpad.net  Mon Dec  2 09:11:56 2019
From: 1854487 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 02 Dec 2019 09:11:56 -0000
Subject: [Bug 1854487] Re: Add Raspberry Pi 4 rev 1.2 entry
References: <157502685027.22967.2893593045960341587.malonedeb@chaenomeles.canonical.com>
Message-ID: <157527791689.6334.10441993348474244045.launchpad@gac.canonical.com>

** Description changed:

  Impact
  ======
  
  A new variant of the Raspberry Pi 4 (revision 1.2) has been released
  (presumably to deal with the USB-C power issue [1]). Without a
  corresponding entry in the flash-kernel database, users of this board
  will receive an error whenever flash-kernel is run (e.g. on kernel
  updates); see LP: #1848790 comment #44 for an example.
  
  [1] https://www.scorpia.co.uk/2019/06/28/pi4-not-working-with-some-
  chargers-or-why-you-need-two-cc-resistors/
  
- 
  Test Case
  =========
  
  * On a Pi 4 Rev 1.2 board, boot an Eoan image (working around LP: #1848790 as necessary)
  * Attempt to run "sudo flash-kernel"
  * Observe the "Unsupported platform" message
- * Run "sudo add-apt-repository ppa:waveform/flash-kernel" to add the PPA containing the test package
+ * Enable proposed
  * Run "sudo apt upgrade" to upgrade the flash-kernel installation
  * Run "sudo flash-kernel" once more, observe no error
- 
  
  Regression Potential
  ====================
  
  Extremely low; the change is a one liner adding a matching "Machine"
  line to the database. It doesn't remove or alter existing lines. The
  worst case scenario is that the Machine line doesn't match the model in
  the device-tree (in which case it'll still produce "Unsupported
  platform").
  
- 
  Other Info
  ==========
  
  The following branch contains the relevant changes:
  https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
  /flash-kernel/+ref/ubuntu/eoan-devel

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854487

Title:
  Add Raspberry Pi 4 rev 1.2 entry

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Eoan:
  Triaged

Bug description:
  Impact
  ======

  A new variant of the Raspberry Pi 4 (revision 1.2) has been released
  (presumably to deal with the USB-C power issue [1]). Without a
  corresponding entry in the flash-kernel database, users of this board
  will receive an error whenever flash-kernel is run (e.g. on kernel
  updates); see LP: #1848790 comment #44 for an example.

  [1] https://www.scorpia.co.uk/2019/06/28/pi4-not-working-with-some-
  chargers-or-why-you-need-two-cc-resistors/

  Test Case
  =========

  * On a Pi 4 Rev 1.2 board, boot an Eoan image (working around LP: #1848790 as necessary)
  * Attempt to run "sudo flash-kernel"
  * Observe the "Unsupported platform" message
  * Enable proposed
  * Run "sudo apt upgrade" to upgrade the flash-kernel installation
  * Run "sudo flash-kernel" once more, observe no error

  Regression Potential
  ====================

  Extremely low; the change is a one liner adding a matching "Machine"
  line to the database. It doesn't remove or alter existing lines. The
  worst case scenario is that the Machine line doesn't match the model
  in the device-tree (in which case it'll still produce "Unsupported
  platform").

  Other Info
  ==========

  The following branch contains the relevant changes:
  https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
  /flash-kernel/+ref/ubuntu/eoan-devel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1854487/+subscriptions


From 1854487 at bugs.launchpad.net  Mon Dec  2 10:14:17 2019
From: 1854487 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 02 Dec 2019 10:14:17 -0000
Subject: [Bug 1854487] Re: Add Raspberry Pi 4 rev 1.2 entry
References: <157502685027.22967.2893593045960341587.malonedeb@chaenomeles.canonical.com>
Message-ID: <157528165794.22148.10662176838348005737.malone@chaenomeles.canonical.com>

Hello Dave, or anyone else affected,

Accepted flash-kernel into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/flash-
kernel/3.98ubuntu5.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: flash-kernel (Ubuntu Eoan)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854487

Title:
  Add Raspberry Pi 4 rev 1.2 entry

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ======

  A new variant of the Raspberry Pi 4 (revision 1.2) has been released
  (presumably to deal with the USB-C power issue [1]). Without a
  corresponding entry in the flash-kernel database, users of this board
  will receive an error whenever flash-kernel is run (e.g. on kernel
  updates); see LP: #1848790 comment #44 for an example.

  [1] https://www.scorpia.co.uk/2019/06/28/pi4-not-working-with-some-
  chargers-or-why-you-need-two-cc-resistors/

  Test Case
  =========

  * On a Pi 4 Rev 1.2 board, boot an Eoan image (working around LP: #1848790 as necessary)
  * Attempt to run "sudo flash-kernel"
  * Observe the "Unsupported platform" message
  * Enable proposed
  * Run "sudo apt upgrade" to upgrade the flash-kernel installation
  * Run "sudo flash-kernel" once more, observe no error

  Regression Potential
  ====================

  Extremely low; the change is a one liner adding a matching "Machine"
  line to the database. It doesn't remove or alter existing lines. The
  worst case scenario is that the Machine line doesn't match the model
  in the device-tree (in which case it'll still produce "Unsupported
  platform").

  Other Info
  ==========

  The following branch contains the relevant changes:
  https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
  /flash-kernel/+ref/ubuntu/eoan-devel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1854487/+subscriptions


From 1827100 at bugs.launchpad.net  Mon Dec  2 14:29:23 2019
From: 1827100 at bugs.launchpad.net (Thadeu Lima de Souza Cascardo)
Date: Mon, 02 Dec 2019 14:29:23 -0000
Subject: [Bug 1827100] Re: bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure
 with linux 5.1.0-1.1
References: <155664853314.14488.459751538800330693.malonedeb@gac.canonical.com>
Message-ID: <157529696699.22072.4884224376647453560.launchpad@soybean.canonical.com>

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to a duplicate bug report (1835197).
https://bugs.launchpad.net/bugs/1827100

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux
  5.1.0-1.1

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Bionic:
  Fix Committed
Status in bcmwl source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The DKMS package won't work with new kernels on bionic.

  [Test case]
  Install and load the modules.

  [Regression potential]
  This might break the functioning of the module.

  -----------------------------------

  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/b/bcmwl/20190429_132741_e6057@/log.gz
      i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/b/bcmwl/20190429_124054_e6057@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1827100/+subscriptions


From corey.bryant at canonical.com  Mon Dec  2 14:41:27 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 02 Dec 2019 14:41:27 -0000
Subject: [Bug 1848286] Please test proposed package
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157529768802.31218.11146093658996729991.malone@wampee.canonical.com>

Hello Wouter, or anyone else affected,

Accepted ceilometer into train-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:train-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-train-needed to verification-train-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-train-failed. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Tags added: verification-train-needed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Committed
Status in ceilometer source package in Eoan:
  Fix Committed
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From corey.bryant at canonical.com  Mon Dec  2 14:43:50 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 02 Dec 2019 14:43:50 -0000
Subject: [Bug 1848286] Please test proposed package
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157529783064.22967.7221796775301859610.malone@chaenomeles.canonical.com>

Hello Wouter, or anyone else affected,

Accepted ceilometer into stein-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:stein-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-stein-needed to verification-stein-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-stein-failed. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: cloud-archive/stein
       Status: Triaged => Fix Committed

** Tags added: verification-stein-needed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Committed
Status in ceilometer source package in Eoan:
  Fix Committed
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From corey.bryant at canonical.com  Mon Dec  2 14:44:41 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 02 Dec 2019 14:44:41 -0000
Subject: [Bug 1848286] Please test proposed package
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157529788124.22533.11767072770789543358.malone@chaenomeles.canonical.com>

Hello Wouter, or anyone else affected,

Accepted ceilometer into rocky-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:rocky-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-rocky-needed to verification-rocky-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-rocky-failed. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: cloud-archive/rocky
       Status: Triaged => Fix Committed

** Tags added: verification-rocky-needed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Committed
Status in ceilometer source package in Eoan:
  Fix Committed
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From 1848286 at bugs.launchpad.net  Mon Dec  2 16:26:49 2019
From: 1848286 at bugs.launchpad.net (Jorge Niedbalski)
Date: Mon, 02 Dec 2019 16:26:49 -0000
Subject: [Bug 1848286] Re: octavia is not reporting metrics like lbaasv2
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157530401004.21495.5976469106599562570.malone@soybean.canonical.com>

I've deployed this bundle[0] with proposed and the following configuration:

1) juju config ceilometer enable-all-pollsters=true
2) sudo systemctl restart ceilometer*
3) sudo ceilometer-upgrade

train
-----
ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
0

ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
72

stein
-----
ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
0

ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
72


rocky
-----
ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
0
ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
72


eoan
-----
ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
0
ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
72


disco
-----
ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
0
ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
72

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Committed
Status in ceilometer source package in Eoan:
  Fix Committed
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From 1848286 at bugs.launchpad.net  Mon Dec  2 16:39:05 2019
From: 1848286 at bugs.launchpad.net (Jorge Niedbalski)
Date: Mon, 02 Dec 2019 16:39:05 -0000
Subject: [Bug 1848286] Re: octavia is not reporting metrics like lbaasv2
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157530474779.21660.16153390339342508779.launchpad@soybean.canonical.com>

** Tags removed: verification-needed verification-needed-disco verification-needed-eoan verification-rocky-needed verification-stein-needed verification-train-needed
** Tags added: verification-done verification-done-disco verification-done-eoan verification-rocky-done verification-stein-done verification-train-done

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Committed
Status in ceilometer source package in Eoan:
  Fix Committed
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From graham.inggs+ubuntu at gmail.com  Mon Dec  2 23:05:34 2019
From: graham.inggs+ubuntu at gmail.com (Graham Inggs)
Date: Mon, 02 Dec 2019 23:05:34 -0000
Subject: [Bug 1854556] Re: Sync vala-panel-appmenu 0.7.3+dfsg1-2 (universe)
 from Debian unstable (main)
References: <157510147913.21696.13243070496686265334.malonedeb@soybean.canonical.com>
Message-ID: <157532793469.7205.15257450008703930403.malone@gac.canonical.com>

This bug was fixed in the package vala-panel-appmenu - 0.7.3+dfsg1-2
Sponsored for hjb48 (hjb)

---------------
vala-panel-appmenu (0.7.3+dfsg1-2) unstable; urgency=medium

  [ Mike Gabriel ]
  * debian/control:
    + Drop from B-D: libpeas-dev.

  [ Martin Wimpress ]
  * debian/control:
    + Drop Recommends: appmenu-qt. It has been removed from the Debian & UBuntu
      archives. https://wiki.debian.org/Qt4Removal
      (Closes: #935978).

 -- Mike Gabriel <sunweaver at debian.org>  Mon, 25 Nov 2019 21:11:13 +0100

** Changed in: vala-panel-appmenu (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854556

Title:
  Sync vala-panel-appmenu 0.7.3+dfsg1-2 (universe) from Debian unstable
  (main)

Status in vala-panel-appmenu package in Ubuntu:
  Fix Released

Bug description:
  Please sync vala-panel-appmenu 0.7.3+dfsg1-2 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Drop recommends on obsolete appmenu-qt.
    * Drop recommends on obsolete appmenu-qt.

  Changes included in Debian package too, it no longer recommends the
  old package.

  Changelog entries since current focal version 0.7.3+dfsg1-1ubuntu1:

  vala-panel-appmenu (0.7.3+dfsg1-2) unstable; urgency=medium

    [ Mike Gabriel ]
    * debian/control:
      + Drop from B-D: libpeas-dev.

    [ Martin Wimpress ]
    * debian/control:
      + Drop Recommends: appmenu-qt. It has been removed from the Debian & UBuntu
        archives. https://wiki.debian.org/Qt4Removal
        (Closes: #935978).

   -- Mike Gabriel <sunweaver at debian.org>  Mon, 25 Nov 2019 21:11:13
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vala-panel-appmenu/+bug/1854556/+subscriptions


From graham.inggs+ubuntu at gmail.com  Mon Dec  2 23:02:33 2019
From: graham.inggs+ubuntu at gmail.com (Graham Inggs)
Date: Mon, 02 Dec 2019 23:02:33 -0000
Subject: [Bug 1854555] Re: Sync lwt 4.3.0-2 (universe) from Debian unstable
 (main)
References: <157510141574.31064.3046553856640334817.malonedeb@wampee.canonical.com>
Message-ID: <157532775306.6406.17846919946269503922.malone@gac.canonical.com>

Missing build dependencies: ocaml-nox (>= 4.08.1-4~)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854555

Title:
  Sync lwt 4.3.0-2 (universe) from Debian unstable (main)

Status in lwt package in Ubuntu:
  New

Bug description:
  Please sync lwt 4.3.0-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Upload back in sync with Debian
    * Upload back in sync with Debian
    * Re-enable glib bindings, needed for zeroinstall-injector

  Looks like the changes were reverted again, effectively empty delta.

  Changelog entries since current focal version 2.7.1-7ubuntu2:

  lwt (4.3.0-2) unstable; urgency=medium

    * Comment out page_size test, which does not pass on all
  architectures

   -- Stéphane Glondu <glondu at debian.org>  Mon, 11 Nov 2019 11:20:36
  +0100

  lwt (4.3.0-1) unstable; urgency=medium

    * New upstream release
      - SSL bindings have been moved to a different package, drop binary
        packages liblwt-ssl-ocaml{,-dev}
      - drop liblwt-ocaml-doc which has been empty for a while

   -- Stéphane Glondu <glondu at debian.org>  Fri, 08 Nov 2019 16:34:06
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lwt/+bug/1854555/+subscriptions


From graham.inggs+ubuntu at gmail.com  Tue Dec  3 05:56:23 2019
From: graham.inggs+ubuntu at gmail.com (Graham Inggs)
Date: Tue, 03 Dec 2019 05:56:23 -0000
Subject: [Bug 1854557] Re: Sync opencv 4.1.2+dfsg-5 (universe) from Debian
 unstable (main)
References: <157510153419.21811.11915855367562323451.malonedeb@soybean.canonical.com>
Message-ID: <157535258319.31024.11522847957093093213.malone@wampee.canonical.com>

Published on 2019-11-30
Copied from debian sid in Primary Archive for Debian GNU/Linux by Gianfranco Costamagna 

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854557

Title:
  Sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main)

Status in opencv package in Ubuntu:
  Fix Released

Bug description:
  Please sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Move from libgdcm2-dev to libgdcm-dev.
    * No-change rebuild against libgdcm3.0
    * Rebuild against new libproj15.

  The Debian package has changed to libgdcm-dev too.

  Changelog entries since current focal version 4.1.2+dfsg-4ubuntu3:

  opencv (4.1.2+dfsg-5) unstable; urgency=medium

    [ Bas Couwenberg ]
    * Replace libgdbm2-dev with libgdbm-dev,
      and libvtkgdcm2-dev with libvtkgdcm-dev. (closes: #944341)

    [ Mo Zhou ]
    * Add AVX512_COMMON to amd64 dispatch list, and VFPV3,NEON to arm64 list.
    * Exclude gdcm development packages from B-D on non-release architectures.

    [ Gianfranco Costamagna ]
    * Remove builddir-static to save some space (Closes: #943706)

   -- Mo Zhou <cdluminate at gmail.com>  Sun, 24 Nov 2019 16:08:26 +0800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1854557/+subscriptions


From 1841191 at bugs.launchpad.net  Tue Dec  3 06:21:55 2019
From: 1841191 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Dec 2019 06:21:55 -0000
Subject: [Bug 1841191] [NEW] "error: failed to acquire package cache lock" in
 sbuild
References: <156657062036.7351.9712908487120178780.malonedeb@gac.canonical.com>
Message-ID: <157535411653.30988.13393963218365521248.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Olivier Tilloy (osomon):

Upstream issue: https://github.com/rust-lang/cargo/issues/7147

This breaks firefox and thunderbird builds in eoan:

    export CARGO_HOME=/<<BUILDDIR>>/thunderbird-68.0+build4/third_party/cbindgen/.cargo; \
    cargo install --path . --bin cbindgen --root ../../cbindgen
    error: failed to acquire package cache lock

    Caused by:
      failed to open: /sbuild-nonexistent/.cargo/.package-cache

    Caused by:
      Permission denied (os error 13)

The following commit needs to be backported as a distro patch:
https://github.com/rust-
lang/cargo/commit/2b21fa68368f13b43f4c34886116df2e1b9d276e

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cargo 0.37.0-3ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Fri Aug 23 14:24:46 2019
SourcePackage: cargo
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: cargo (Ubuntu)
     Importance: Undecided
     Assignee: Canonical Foundations Team (canonical-foundations)
         Status: Fix Released

** Affects: cargo (Ubuntu Xenial)
     Importance: Undecided
     Assignee: Canonical Foundations Team (canonical-foundations)
         Status: Fix Committed

** Affects: cargo (Ubuntu Bionic)
     Importance: Undecided
     Assignee: Canonical Foundations Team (canonical-foundations)
         Status: Fix Committed

** Affects: cargo (Ubuntu Disco)
     Importance: Undecided
     Assignee: Canonical Foundations Team (canonical-foundations)
         Status: Fix Committed


** Tags: amd64 apport-bug eoan
-- 
"error: failed to acquire package cache lock" in sbuild
https://bugs.launchpad.net/bugs/1841191
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From olivier.tilloy at canonical.com  Tue Dec  3 06:20:04 2019
From: olivier.tilloy at canonical.com (Olivier Tilloy)
Date: Tue, 03 Dec 2019 06:20:04 -0000
Subject: [Bug 1841191] Re: "error: failed to acquire package cache lock" in
 sbuild
References: <156657062036.7351.9712908487120178780.malonedeb@gac.canonical.com>
Message-ID: <157535400490.22191.1439271464929705073.malone@soybean.canonical.com>

** Patch added: "debdiff for disco"
   https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+attachment/5309501/+files/cargo-disco.debdiff

** Changed in: cargo (Ubuntu Xenial)
       Status: Fix Committed => In Progress

** Changed in: cargo (Ubuntu Disco)
       Status: Fix Committed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1841191

Title:
  "error: failed to acquire package cache lock" in sbuild

Status in cargo package in Ubuntu:
  Fix Released
Status in cargo source package in Xenial:
  In Progress
Status in cargo source package in Bionic:
  Fix Committed
Status in cargo source package in Disco:
  In Progress

Bug description:
  Upstream issue: https://github.com/rust-lang/cargo/issues/7147

  This breaks firefox and thunderbird builds in eoan:

      export CARGO_HOME=/<<BUILDDIR>>/thunderbird-68.0+build4/third_party/cbindgen/.cargo; \
      cargo install --path . --bin cbindgen --root ../../cbindgen
      error: failed to acquire package cache lock

      Caused by:
        failed to open: /sbuild-nonexistent/.cargo/.package-cache

      Caused by:
        Permission denied (os error 13)

  The following commit needs to be backported as a distro patch:
  https://github.com/rust-
  lang/cargo/commit/2b21fa68368f13b43f4c34886116df2e1b9d276e

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cargo 0.37.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 23 14:24:46 2019
  SourcePackage: cargo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+subscriptions


From olivier.tilloy at canonical.com  Tue Dec  3 09:24:54 2019
From: olivier.tilloy at canonical.com (Olivier Tilloy)
Date: Tue, 03 Dec 2019 09:24:54 -0000
Subject: [Bug 1841191] Re: "error: failed to acquire package cache lock" in
 sbuild
References: <156657062036.7351.9712908487120178780.malonedeb@gac.canonical.com>
Message-ID: <157536509492.30988.6469671269761127124.malone@wampee.canonical.com>

** Description changed:

+ [Impact]
+ 
+ All packages using cargo (rust's package manager) to build in Launchpad will FTBFS because cargo tries to acquire a lock on $HOME/.cargo, but $HOME is set to /sbuild-nonexistent in sbuild.
+ This includes the thunderbird 60.9.1+build1 SRU tracked by bug #1850651.
+ 
+ 
+ [Test Case]
+ 
+ In a xenial/disco virtual machine:
+ 
+   sudo apt install cargo
+   cd `mktemp -d`
+   export HOME=/nonexistent
+   cargo init --name foobar
+   cargo build
+ 
+ This should succeed. With the unpatched version currently in
+ xenial/disco, it fails with "error: failed to acquire package cache
+ lock".
+ 
+ 
+ [Regression Potential]
+ 
+ Low. This cherry-picks one single upstream commit that addresses only
+ this bug.
+ 
+ 
+ [Original Description]
+ 
  Upstream issue: https://github.com/rust-lang/cargo/issues/7147
  
  This breaks firefox and thunderbird builds in eoan:
  
      export CARGO_HOME=/<<BUILDDIR>>/thunderbird-68.0+build4/third_party/cbindgen/.cargo; \
      cargo install --path . --bin cbindgen --root ../../cbindgen
      error: failed to acquire package cache lock
  
      Caused by:
        failed to open: /sbuild-nonexistent/.cargo/.package-cache
  
      Caused by:
        Permission denied (os error 13)
  
  The following commit needs to be backported as a distro patch:
  https://github.com/rust-
  lang/cargo/commit/2b21fa68368f13b43f4c34886116df2e1b9d276e
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cargo 0.37.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 23 14:24:46 2019
  SourcePackage: cargo
  UpgradeStatus: No upgrade log present (probably fresh install)

** Patch removed: "debdiff for xenial"
   https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+attachment/5309499/+files/cargo-xenial.debdiff

** Patch removed: "debdiff for disco"
   https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+attachment/5309501/+files/cargo-disco.debdiff

** Patch removed: "debdiff for disco"
   https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+attachment/5309500/+files/cargo-disco.debdiff

** Patch added: "debdiff for xenial"
   https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+attachment/5309515/+files/cargo-xenial.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1841191

Title:
  "error: failed to acquire package cache lock" in sbuild

Status in cargo package in Ubuntu:
  Fix Released
Status in cargo source package in Xenial:
  In Progress
Status in cargo source package in Bionic:
  Fix Committed
Status in cargo source package in Disco:
  In Progress

Bug description:
  [Impact]

  All packages using cargo (rust's package manager) to build in Launchpad will FTBFS because cargo tries to acquire a lock on $HOME/.cargo, but $HOME is set to /sbuild-nonexistent in sbuild.
  This includes the thunderbird 60.9.1+build1 SRU tracked by bug #1850651.

  
  [Test Case]

  In a xenial/disco virtual machine:

    sudo apt install cargo
    cd `mktemp -d`
    export HOME=/nonexistent
    cargo init --name foobar
    cargo build

  This should succeed. With the unpatched version currently in
  xenial/disco, it fails with "error: failed to acquire package cache
  lock".

  
  [Regression Potential]

  Low. This cherry-picks one single upstream commit that addresses only
  this bug.

  
  [Original Description]

  Upstream issue: https://github.com/rust-lang/cargo/issues/7147

  This breaks firefox and thunderbird builds in eoan:

      export CARGO_HOME=/<<BUILDDIR>>/thunderbird-68.0+build4/third_party/cbindgen/.cargo; \
      cargo install --path . --bin cbindgen --root ../../cbindgen
      error: failed to acquire package cache lock

      Caused by:
        failed to open: /sbuild-nonexistent/.cargo/.package-cache

      Caused by:
        Permission denied (os error 13)

  The following commit needs to be backported as a distro patch:
  https://github.com/rust-
  lang/cargo/commit/2b21fa68368f13b43f4c34886116df2e1b9d276e

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cargo 0.37.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 23 14:24:46 2019
  SourcePackage: cargo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+subscriptions


From olivier.tilloy at canonical.com  Tue Dec  3 09:25:19 2019
From: olivier.tilloy at canonical.com (Olivier Tilloy)
Date: Tue, 03 Dec 2019 09:25:19 -0000
Subject: [Bug 1841191] Re: "error: failed to acquire package cache lock" in
 sbuild
References: <156657062036.7351.9712908487120178780.malonedeb@gac.canonical.com>
Message-ID: <157536511930.6334.1794159072889853345.malone@gac.canonical.com>

** Patch added: "debdiff for disco"
   https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+attachment/5309516/+files/cargo-disco.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1841191

Title:
  "error: failed to acquire package cache lock" in sbuild

Status in cargo package in Ubuntu:
  Fix Released
Status in cargo source package in Xenial:
  In Progress
Status in cargo source package in Bionic:
  Fix Committed
Status in cargo source package in Disco:
  In Progress

Bug description:
  [Impact]

  All packages using cargo (rust's package manager) to build in Launchpad will FTBFS because cargo tries to acquire a lock on $HOME/.cargo, but $HOME is set to /sbuild-nonexistent in sbuild.
  This includes the thunderbird 60.9.1+build1 SRU tracked by bug #1850651.

  
  [Test Case]

  In a xenial/disco virtual machine:

    sudo apt install cargo
    cd `mktemp -d`
    export HOME=/nonexistent
    cargo init --name foobar
    cargo build

  This should succeed. With the unpatched version currently in
  xenial/disco, it fails with "error: failed to acquire package cache
  lock".

  
  [Regression Potential]

  Low. This cherry-picks one single upstream commit that addresses only
  this bug.

  
  [Original Description]

  Upstream issue: https://github.com/rust-lang/cargo/issues/7147

  This breaks firefox and thunderbird builds in eoan:

      export CARGO_HOME=/<<BUILDDIR>>/thunderbird-68.0+build4/third_party/cbindgen/.cargo; \
      cargo install --path . --bin cbindgen --root ../../cbindgen
      error: failed to acquire package cache lock

      Caused by:
        failed to open: /sbuild-nonexistent/.cargo/.package-cache

      Caused by:
        Permission denied (os error 13)

  The following commit needs to be backported as a distro patch:
  https://github.com/rust-
  lang/cargo/commit/2b21fa68368f13b43f4c34886116df2e1b9d276e

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cargo 0.37.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 23 14:24:46 2019
  SourcePackage: cargo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+subscriptions


From 1854487 at bugs.launchpad.net  Tue Dec  3 14:43:36 2019
From: 1854487 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Tue, 03 Dec 2019 14:43:36 -0000
Subject: [Bug 1854487] Re: Add Raspberry Pi 4 rev 1.2 entry
References: <157502685027.22967.2893593045960341587.malonedeb@chaenomeles.canonical.com>
Message-ID: <157538421659.7009.4010205465383190262.malone@gac.canonical.com>

We were not able to fully verify this bugfix yet (due to not having the
required device), but since the change is really small, Brian did a
quick sanity smoke test of it on a regular Pi4 device. Nothing seemed to
be broken so that should be enough.

We will be extensively testing flash-kernel as part of the new images
we'll be building once this lands.

** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-done-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854487

Title:
  Add Raspberry Pi 4 rev 1.2 entry

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Eoan:
  Fix Committed

Bug description:
  Impact
  ======

  A new variant of the Raspberry Pi 4 (revision 1.2) has been released
  (presumably to deal with the USB-C power issue [1]). Without a
  corresponding entry in the flash-kernel database, users of this board
  will receive an error whenever flash-kernel is run (e.g. on kernel
  updates); see LP: #1848790 comment #44 for an example.

  [1] https://www.scorpia.co.uk/2019/06/28/pi4-not-working-with-some-
  chargers-or-why-you-need-two-cc-resistors/

  Test Case
  =========

  * On a Pi 4 Rev 1.2 board, boot an Eoan image (working around LP: #1848790 as necessary)
  * Attempt to run "sudo flash-kernel"
  * Observe the "Unsupported platform" message
  * Enable proposed
  * Run "sudo apt upgrade" to upgrade the flash-kernel installation
  * Run "sudo flash-kernel" once more, observe no error

  Regression Potential
  ====================

  Extremely low; the change is a one liner adding a matching "Machine"
  line to the database. It doesn't remove or alter existing lines. The
  worst case scenario is that the Machine line doesn't match the model
  in the device-tree (in which case it'll still produce "Unsupported
  platform").

  Other Info
  ==========

  The following branch contains the relevant changes:
  https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
  /flash-kernel/+ref/ubuntu/eoan-devel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1854487/+subscriptions


From brian at ubuntu.com  Tue Dec  3 14:58:22 2019
From: brian at ubuntu.com (Brian Murray)
Date: Tue, 03 Dec 2019 14:58:22 -0000
Subject: [Bug 1854487] Re: Add Raspberry Pi 4 rev 1.2 entry
References: <157502685027.22967.2893593045960341587.malonedeb@chaenomeles.canonical.com>
Message-ID: <157538510288.22328.7123901835493358502.malone@chaenomeles.canonical.com>

For the record my testing involved installing flash-kernel from
-proposed, running sudo flash-kernel, rebooting, installing the new
kernel from -proposed (which runs flash-kernel) and then rebooting
again. I saw no error messages from flash-kernel and rebooted
successfully each time.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854487

Title:
  Add Raspberry Pi 4 rev 1.2 entry

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Eoan:
  Fix Released

Bug description:
  Impact
  ======

  A new variant of the Raspberry Pi 4 (revision 1.2) has been released
  (presumably to deal with the USB-C power issue [1]). Without a
  corresponding entry in the flash-kernel database, users of this board
  will receive an error whenever flash-kernel is run (e.g. on kernel
  updates); see LP: #1848790 comment #44 for an example.

  [1] https://www.scorpia.co.uk/2019/06/28/pi4-not-working-with-some-
  chargers-or-why-you-need-two-cc-resistors/

  Test Case
  =========

  * On a Pi 4 Rev 1.2 board, boot an Eoan image (working around LP: #1848790 as necessary)
  * Attempt to run "sudo flash-kernel"
  * Observe the "Unsupported platform" message
  * Enable proposed
  * Run "sudo apt upgrade" to upgrade the flash-kernel installation
  * Run "sudo flash-kernel" once more, observe no error

  Regression Potential
  ====================

  Extremely low; the change is a one liner adding a matching "Machine"
  line to the database. It doesn't remove or alter existing lines. The
  worst case scenario is that the Machine line doesn't match the model
  in the device-tree (in which case it'll still produce "Unsupported
  platform").

  Other Info
  ==========

  The following branch contains the relevant changes:
  https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
  /flash-kernel/+ref/ubuntu/eoan-devel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1854487/+subscriptions


From 1854487 at bugs.launchpad.net  Tue Dec  3 15:05:54 2019
From: 1854487 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Dec 2019 15:05:54 -0000
Subject: [Bug 1854487] Re: Add Raspberry Pi 4 rev 1.2 entry
References: <157502685027.22967.2893593045960341587.malonedeb@chaenomeles.canonical.com>
Message-ID: <157538555837.8939.16798730909315596472.malone@ackee.canonical.com>

This bug was fixed in the package flash-kernel - 3.98ubuntu5.3

---------------
flash-kernel (3.98ubuntu5.3) eoan; urgency=medium

  * Add support for the Raspberry Pi 4 rev 1.2 board (LP: #1854487)

flash-kernel (3.98ubuntu5.2) eoan; urgency=medium

  * Reverted updated pi bootscript to work around boot regression in proposed
    eoan image (LP: #1854347).

 -- Dave Jones <dave.jones at canonical.com>  Fri, 29 Nov 2019 16:33:13
+0000

** Changed in: flash-kernel (Ubuntu Eoan)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854487

Title:
  Add Raspberry Pi 4 rev 1.2 entry

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Eoan:
  Fix Released

Bug description:
  Impact
  ======

  A new variant of the Raspberry Pi 4 (revision 1.2) has been released
  (presumably to deal with the USB-C power issue [1]). Without a
  corresponding entry in the flash-kernel database, users of this board
  will receive an error whenever flash-kernel is run (e.g. on kernel
  updates); see LP: #1848790 comment #44 for an example.

  [1] https://www.scorpia.co.uk/2019/06/28/pi4-not-working-with-some-
  chargers-or-why-you-need-two-cc-resistors/

  Test Case
  =========

  * On a Pi 4 Rev 1.2 board, boot an Eoan image (working around LP: #1848790 as necessary)
  * Attempt to run "sudo flash-kernel"
  * Observe the "Unsupported platform" message
  * Enable proposed
  * Run "sudo apt upgrade" to upgrade the flash-kernel installation
  * Run "sudo flash-kernel" once more, observe no error

  Regression Potential
  ====================

  Extremely low; the change is a one liner adding a matching "Machine"
  line to the database. It doesn't remove or alter existing lines. The
  worst case scenario is that the Machine line doesn't match the model
  in the device-tree (in which case it'll still produce "Unsupported
  platform").

  Other Info
  ==========

  The following branch contains the relevant changes:
  https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
  /flash-kernel/+ref/ubuntu/eoan-devel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1854487/+subscriptions


From 1854487 at bugs.launchpad.net  Tue Dec  3 15:06:01 2019
From: 1854487 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Tue, 03 Dec 2019 15:06:01 -0000
Subject: [Bug 1854487] Update Released
References: <157502685027.22967.2893593045960341587.malonedeb@chaenomeles.canonical.com>
Message-ID: <157538556202.21735.13107743235831579605.malone@soybean.canonical.com>

The verification of the Stable Release Update for flash-kernel has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854487

Title:
  Add Raspberry Pi 4 rev 1.2 entry

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Eoan:
  Fix Released

Bug description:
  Impact
  ======

  A new variant of the Raspberry Pi 4 (revision 1.2) has been released
  (presumably to deal with the USB-C power issue [1]). Without a
  corresponding entry in the flash-kernel database, users of this board
  will receive an error whenever flash-kernel is run (e.g. on kernel
  updates); see LP: #1848790 comment #44 for an example.

  [1] https://www.scorpia.co.uk/2019/06/28/pi4-not-working-with-some-
  chargers-or-why-you-need-two-cc-resistors/

  Test Case
  =========

  * On a Pi 4 Rev 1.2 board, boot an Eoan image (working around LP: #1848790 as necessary)
  * Attempt to run "sudo flash-kernel"
  * Observe the "Unsupported platform" message
  * Enable proposed
  * Run "sudo apt upgrade" to upgrade the flash-kernel installation
  * Run "sudo flash-kernel" once more, observe no error

  Regression Potential
  ====================

  Extremely low; the change is a one liner adding a matching "Machine"
  line to the database. It doesn't remove or alter existing lines. The
  worst case scenario is that the Machine line doesn't match the model
  in the device-tree (in which case it'll still produce "Unsupported
  platform").

  Other Info
  ==========

  The following branch contains the relevant changes:
  https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
  /flash-kernel/+ref/ubuntu/eoan-devel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1854487/+subscriptions


From 1841191 at bugs.launchpad.net  Tue Dec  3 17:34:52 2019
From: 1841191 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Tue, 03 Dec 2019 17:34:52 -0000
Subject: [Bug 1841191] Re: "error: failed to acquire package cache lock" in
 sbuild
References: <156657062036.7351.9712908487120178780.malonedeb@gac.canonical.com>
Message-ID: <157539449310.31610.8239443333726429883.malone@wampee.canonical.com>

Hello Olivier, or anyone else affected,

Accepted cargo into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cargo/0.37.0-3ubuntu1~19.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: cargo (Ubuntu Disco)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1841191

Title:
  "error: failed to acquire package cache lock" in sbuild

Status in cargo package in Ubuntu:
  Fix Released
Status in cargo source package in Xenial:
  In Progress
Status in cargo source package in Bionic:
  Fix Committed
Status in cargo source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  All packages using cargo (rust's package manager) to build in Launchpad will FTBFS because cargo tries to acquire a lock on $HOME/.cargo, but $HOME is set to /sbuild-nonexistent in sbuild.
  This includes the thunderbird 60.9.1+build1 SRU tracked by bug #1850651.

  
  [Test Case]

  In a xenial/disco virtual machine:

    sudo apt install cargo
    cd `mktemp -d`
    export HOME=/nonexistent
    cargo init --name foobar
    cargo build

  This should succeed. With the unpatched version currently in
  xenial/disco, it fails with "error: failed to acquire package cache
  lock".

  
  [Regression Potential]

  Low. This cherry-picks one single upstream commit that addresses only
  this bug.

  
  [Original Description]

  Upstream issue: https://github.com/rust-lang/cargo/issues/7147

  This breaks firefox and thunderbird builds in eoan:

      export CARGO_HOME=/<<BUILDDIR>>/thunderbird-68.0+build4/third_party/cbindgen/.cargo; \
      cargo install --path . --bin cbindgen --root ../../cbindgen
      error: failed to acquire package cache lock

      Caused by:
        failed to open: /sbuild-nonexistent/.cargo/.package-cache

      Caused by:
        Permission denied (os error 13)

  The following commit needs to be backported as a distro patch:
  https://github.com/rust-
  lang/cargo/commit/2b21fa68368f13b43f4c34886116df2e1b9d276e

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cargo 0.37.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 23 14:24:46 2019
  SourcePackage: cargo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+subscriptions


From 1841191 at bugs.launchpad.net  Tue Dec  3 17:42:15 2019
From: 1841191 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Tue, 03 Dec 2019 17:42:15 -0000
Subject: [Bug 1841191] Re: "error: failed to acquire package cache lock" in
 sbuild
References: <156657062036.7351.9712908487120178780.malonedeb@gac.canonical.com>
Message-ID: <157539493535.22400.17969729362232749432.malone@chaenomeles.canonical.com>

Hello Olivier, or anyone else affected,

Accepted cargo into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cargo/0.37.0-3ubuntu1~16.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: cargo (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1841191

Title:
  "error: failed to acquire package cache lock" in sbuild

Status in cargo package in Ubuntu:
  Fix Released
Status in cargo source package in Xenial:
  Fix Committed
Status in cargo source package in Bionic:
  Fix Committed
Status in cargo source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  All packages using cargo (rust's package manager) to build in Launchpad will FTBFS because cargo tries to acquire a lock on $HOME/.cargo, but $HOME is set to /sbuild-nonexistent in sbuild.
  This includes the thunderbird 60.9.1+build1 SRU tracked by bug #1850651.

  
  [Test Case]

  In a xenial/disco virtual machine:

    sudo apt install cargo
    cd `mktemp -d`
    export HOME=/nonexistent
    cargo init --name foobar
    cargo build

  This should succeed. With the unpatched version currently in
  xenial/disco, it fails with "error: failed to acquire package cache
  lock".

  
  [Regression Potential]

  Low. This cherry-picks one single upstream commit that addresses only
  this bug.

  
  [Original Description]

  Upstream issue: https://github.com/rust-lang/cargo/issues/7147

  This breaks firefox and thunderbird builds in eoan:

      export CARGO_HOME=/<<BUILDDIR>>/thunderbird-68.0+build4/third_party/cbindgen/.cargo; \
      cargo install --path . --bin cbindgen --root ../../cbindgen
      error: failed to acquire package cache lock

      Caused by:
        failed to open: /sbuild-nonexistent/.cargo/.package-cache

      Caused by:
        Permission denied (os error 13)

  The following commit needs to be backported as a distro patch:
  https://github.com/rust-
  lang/cargo/commit/2b21fa68368f13b43f4c34886116df2e1b9d276e

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cargo 0.37.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 23 14:24:46 2019
  SourcePackage: cargo
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+subscriptions


From brian at ubuntu.com  Wed Dec  4 00:36:52 2019
From: brian at ubuntu.com (Brian Murray)
Date: Wed, 04 Dec 2019 00:36:52 -0000
Subject: [Bug 1854487] Re: Add Raspberry Pi 4 rev 1.2 entry
References: <157502685027.22967.2893593045960341587.malonedeb@chaenomeles.canonical.com>
Message-ID: <157541981217.22270.875018778242109709.malone@soybean.canonical.com>

This has worked for a user with a v1.2 Raspberry Pi 4 as seen here:

https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1848790/comments/55

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854487

Title:
  Add Raspberry Pi 4 rev 1.2 entry

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Eoan:
  Fix Released

Bug description:
  Impact
  ======

  A new variant of the Raspberry Pi 4 (revision 1.2) has been released
  (presumably to deal with the USB-C power issue [1]). Without a
  corresponding entry in the flash-kernel database, users of this board
  will receive an error whenever flash-kernel is run (e.g. on kernel
  updates); see LP: #1848790 comment #44 for an example.

  [1] https://www.scorpia.co.uk/2019/06/28/pi4-not-working-with-some-
  chargers-or-why-you-need-two-cc-resistors/

  Test Case
  =========

  * On a Pi 4 Rev 1.2 board, boot an Eoan image (working around LP: #1848790 as necessary)
  * Attempt to run "sudo flash-kernel"
  * Observe the "Unsupported platform" message
  * Enable proposed
  * Run "sudo apt upgrade" to upgrade the flash-kernel installation
  * Run "sudo flash-kernel" once more, observe no error

  Regression Potential
  ====================

  Extremely low; the change is a one liner adding a matching "Machine"
  line to the database. It doesn't remove or alter existing lines. The
  worst case scenario is that the Machine line doesn't match the model
  in the device-tree (in which case it'll still produce "Unsupported
  platform").

  Other Info
  ==========

  The following branch contains the relevant changes:
  https://code.launchpad.net/~waveform/ubuntu/+source/flash-kernel/+git
  /flash-kernel/+ref/ubuntu/eoan-devel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1854487/+subscriptions


From 1842167 at bugs.launchpad.net  Wed Dec  4 16:16:19 2019
From: 1842167 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 04 Dec 2019 16:16:19 -0000
Subject: [Bug 1842167] [NEW] Default list of stations entry for "WSUM 91.7 FM
 (University of Wisconsin) has an outdated URL
References: <156723706522.6124.12294142371125705385.malonedeb@soybean.canonical.com>
Message-ID: <157547618043.7124.8987604839839254512.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Sebastien Bacher (seb128):

Update:  A patch has been posted - who can apply it?

The stock URL does no longer have an DNS-record.

(Stock URL is "http://vu.wsum.wisc.edu/wsumlive.m3u").

The new URL appears to be:

http://stream.studio.wsum.wisc.edu/wsum128

A workaround, is to rightclick the station, choose "properties", which
will popup a window with information about the station. Click the
"details" tab in the popup window, and replace the URL with the one
above, and close the the popup window.

I think at least one of the other URL's might need an update, but I
haven't looked into that yet.

Additional information per request:

(1)
$ lsb_release -rd
Description:	Ubuntu 19.04
Release:	19.04

(2)
$ rhythmbox --version
rhythmbox 3.4.3

$ apt-cache policy rhythmbox
rhythmbox:
  Installeret: 3.4.3-1ubuntu1
  Kandidat:    3.4.3-1ubuntu1
  Versionstabel:
 *** 3.4.3-1ubuntu1 500
        500 http://ny-mirrors.evowise.com/ubuntu disco/main amd64 Packages
        100 /var/lib/dpkg/status
     3.3-1ubuntu7 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

(3) I obviously expected the URL to up to date.

(4) I found that the URL was out of date.

** Affects: rhythmbox
     Importance: Unknown
         Status: New

** Affects: rhythmbox (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: bionic disco
-- 
Default list of stations entry for "WSUM 91.7 FM (University of Wisconsin) has an outdated URL
https://bugs.launchpad.net/bugs/1842167
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From adam.collard at canonical.com  Wed Dec  4 17:47:44 2019
From: adam.collard at canonical.com (Adam Collard)
Date: Wed, 04 Dec 2019 17:47:44 -0000
Subject: [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
References: <150247883061.17099.2020071136944741893.malonedeb@gac.canonical.com>
Message-ID: <157548166671.6824.15808581190121799615.launchpad@gac.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1710278

Title:
  [2.3a1] named stuck on reload, DNS broken

Status in BIND:
  Fix Released
Status in MAAS:
  Fix Released
Status in MAAS 2.2 series:
  Fix Released
Status in MAAS 2.4 series:
  Fix Committed
Status in MAAS 2.6 series:
  Fix Released
Status in MAAS 2.7 series:
  Fix Released
Status in bind9 package in Ubuntu:
  In Progress
Status in maas package in Ubuntu:
  Confirmed
Status in bind9 source package in Xenial:
  In Progress
Status in bind9 source package in Bionic:
  In Progress
Status in maas source package in Bionic:
  In Progress
Status in bind9 source package in Disco:
  In Progress
Status in bind9 source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * systemd thinks the service is running, but it does not respond to
  any commands or requests. Also, it doesn't respond to signals other
  than kill -9. service restarts hang, rndc hangs.

   * being that the deadlock is in bind9 that ships in bionic the issue
  needs to be backported to 2.4.3 so MAAS from the archive in bionic can
  handle the deadlock and get bind9 unstuck.

   * change in MAAS watches for this case to occur with bind9, then MAAS
  will force kill the service and restart it.

  [Test Case]

   * very hard to reproduce but the issue occurs when bind9 deadlocks,
  it response to nothing over the network or rndc. SIGTERM does not kill
  it only SIGKILL works to force kill the process and get systemd to
  restart it.

  
  [Regression Potential] 

   * possible that bind9 will not be started correctly or possible that
  bind9 will be placed into a forever restart loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions


From 1842167 at bugs.launchpad.net  Thu Dec  5 03:55:22 2019
From: 1842167 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 05 Dec 2019 03:55:22 -0000
Subject: [Bug 1842167] Re: Default list of stations entry for "WSUM 91.7 FM
 (University of Wisconsin) has an outdated URL
References: <156723706522.6124.12294142371125705385.malonedeb@soybean.canonical.com>
Message-ID: <157551812351.22692.6919103371928711625.launchpad@chaenomeles.canonical.com>

** Changed in: rhythmbox (Ubuntu)
   Importance: Undecided => Low

** Tags added: patch patch-forwarded-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842167

Title:
  Default list of stations entry for "WSUM 91.7 FM (University of
  Wisconsin) has an outdated URL

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  Update:  A patch has been posted - who can apply it?

  The stock URL does no longer have an DNS-record.

  (Stock URL is "http://vu.wsum.wisc.edu/wsumlive.m3u").

  The new URL appears to be:

  http://stream.studio.wsum.wisc.edu/wsum128

  A workaround, is to rightclick the station, choose "properties", which
  will popup a window with information about the station. Click the
  "details" tab in the popup window, and replace the URL with the one
  above, and close the the popup window.

  I think at least one of the other URL's might need an update, but I
  haven't looked into that yet.

  Additional information per request:

  (1)
  $ lsb_release -rd
  Description:	Ubuntu 19.04
  Release:	19.04

  (2)
  $ rhythmbox --version
  rhythmbox 3.4.3

  $ apt-cache policy rhythmbox
  rhythmbox:
    Installeret: 3.4.3-1ubuntu1
    Kandidat:    3.4.3-1ubuntu1
    Versionstabel:
   *** 3.4.3-1ubuntu1 500
          500 http://ny-mirrors.evowise.com/ubuntu disco/main amd64 Packages
          100 /var/lib/dpkg/status
       3.3-1ubuntu7 500
          500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  (3) I obviously expected the URL to up to date.

  (4) I found that the URL was out of date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1842167/+subscriptions


From 1854689 at bugs.launchpad.net  Thu Dec  5 06:37:35 2019
From: 1854689 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 05 Dec 2019 06:37:35 -0000
Subject: [Bug 1854689] [NEW] BlueZ 5.52 release
References: <157526921040.6334.11536417789885422275.malonedeb@gac.canonical.com>
Message-ID: <157552785541.31610.1089365236546764666.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Daniel van Vugt (vanvugt):

BlueZ 5.52 release:
http://www.bluez.org/release-of-bluez-5-52/

** Affects: bluez (Ubuntu)
     Importance: Medium
     Assignee: Daniel van Vugt (vanvugt)
         Status: In Progress


** Tags: focal
-- 
BlueZ 5.52 release
https://bugs.launchpad.net/bugs/1854689
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1827100 at bugs.launchpad.net  Thu Dec  5 12:51:58 2019
From: 1827100 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 05 Dec 2019 12:51:58 -0000
Subject: [Bug 1827100] Re: bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure
 with linux 5.1.0-1.1
References: <155664853314.14488.459751538800330693.malonedeb@gac.canonical.com>
Message-ID: <157555032082.8939.17597335857832707844.malone@ackee.canonical.com>

This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-
0ubuntu5~18.04.1

---------------
bcmwl (6.30.223.271+bdcom-0ubuntu5~18.04.1) bionic; urgency=medium

  [ Seth Forshee ]
  * debian/dkms.conf.in,
    debian/patches/0027-add-support-for-linux-5.1.patch (LP: #1827100):
    - Add support for Linux 5.1.

 -- Marcelo Henrique Cerri <marcelo.cerri at canonical.com>  Wed, 13 Nov
2019 11:05:32 -0300

** Changed in: bcmwl (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to a duplicate bug report (1835197).
https://bugs.launchpad.net/bugs/1827100

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux
  5.1.0-1.1

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Bionic:
  Fix Released
Status in bcmwl source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The DKMS package won't work with new kernels on bionic.

  [Test case]
  Install and load the modules.

  [Regression potential]
  This might break the functioning of the module.

  -----------------------------------

  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/b/bcmwl/20190429_132741_e6057@/log.gz
      i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/b/bcmwl/20190429_124054_e6057@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1827100/+subscriptions


From 1827100 at bugs.launchpad.net  Thu Dec  5 12:52:02 2019
From: 1827100 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Dec 2019 12:52:02 -0000
Subject: [Bug 1827100] Update Released
References: <155664853314.14488.459751538800330693.malonedeb@gac.canonical.com>
Message-ID: <157555032220.7205.1837536557474058690.malone@gac.canonical.com>

The verification of the Stable Release Update for bcmwl has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to a duplicate bug report (1835197).
https://bugs.launchpad.net/bugs/1827100

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux
  5.1.0-1.1

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Bionic:
  Fix Released
Status in bcmwl source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The DKMS package won't work with new kernels on bionic.

  [Test case]
  Install and load the modules.

  [Regression potential]
  This might break the functioning of the module.

  -----------------------------------

  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/b/bcmwl/20190429_132741_e6057@/log.gz
      i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/b/bcmwl/20190429_124054_e6057@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1827100/+subscriptions


From 1855475 at bugs.launchpad.net  Fri Dec  6 20:28:34 2019
From: 1855475 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 06 Dec 2019 20:28:34 -0000
Subject: [Bug 1855475] [NEW] autopkgtest regression triggered by
 ruby-defaults/1:2.5.2
References: <157565769389.21696.9148911649374236461.malonedeb@soybean.canonical.com>
Message-ID: <157566411506.6454.2238321544325165772.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

ruby-riddle version 2.3.1-1ubuntu1 had a regression in focal after ruby-
defaults/1:2.5.2 in all architectures, as you can see here [1][2].

[1] http://autopkgtest.ubuntu.com/packages/r/ruby-riddle
[2] http://autopkgtest.ubuntu.com/packages/r/ruby-riddle/focal/amd64

** Affects: ruby-riddle (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: patch
-- 
autopkgtest regression triggered by ruby-defaults/1:2.5.2
https://bugs.launchpad.net/bugs/1855475
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1855475 at bugs.launchpad.net  Fri Dec  6 20:28:35 2019
From: 1855475 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Fri, 06 Dec 2019 20:28:35 -0000
Subject: [Bug 1855475] Re: autopkgtest regression triggered by
 ruby-defaults/1:2.5.2
References: <157565769389.21696.9148911649374236461.malonedeb@soybean.canonical.com>
Message-ID: <157566411539.21375.2956192409764704033.malone@soybean.canonical.com>

The attachment "debdiff" seems to be a debdiff.  The ubuntu-sponsors
team has been subscribed to the bug report so that they can review and
hopefully sponsor the debdiff.  If the attachment isn't a patch, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855475

Title:
  autopkgtest regression triggered by ruby-defaults/1:2.5.2

Status in ruby-riddle package in Ubuntu:
  New

Bug description:
  ruby-riddle version 2.3.1-1ubuntu1 had a regression in focal after
  ruby-defaults/1:2.5.2 in all architectures, as you can see here
  [1][2].

  [1] http://autopkgtest.ubuntu.com/packages/r/ruby-riddle
  [2] http://autopkgtest.ubuntu.com/packages/r/ruby-riddle/focal/amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-riddle/+bug/1855475/+subscriptions


From 1855468 at bugs.launchpad.net  Fri Dec  6 20:49:29 2019
From: 1855468 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 06 Dec 2019 20:49:29 -0000
Subject: [Bug 1855468] [NEW] Version 2.2.11 does not support MySQL 8 clients
References: <157565518794.21540.17127031191078848707.malonedeb@soybean.canonical.com>
Message-ID: <157566537091.23007.13568299810625752339.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Lucas Kanashiro (lucaskanashiro):

sphinxsearch package version 2.2.11-2build1 was rebuilt during MySQL 8
transition (as all MySQL related packages, like clients), however, its
handshake implementation of MySQL protocol does not support MySQL 8
clients, not allowing connections. According to upstream release notes,
it was fixed in version 3.1.1:
http://sphinxsearch.com/docs/sphinx3.html#version-3.1.1-17-oct-2018

Steps to reproduce this issue in a brand new LXD container (focal-
amd64):

$ apt install sphinxsearch ruby-mysql2 -y
$ cp /etc/sphinxsearch/sphinx.conf.dist /etc/sphinxsearch/sphinx.conf
$ searchd --config /etc/sphinxsearch/sphinx.conf      // ignore the warnings, not relevant to this bug
$ irb
irb(main):001:0> require 'mysql2'
=> true
irb(main):002:0> Mysql2::Client.new(:host => '127.0.0.1', :port => 9306)
Traceback (most recent call last):
        5: from /usr/bin/irb:11:in `<main>'
        4: from (irb):2
        3: from (irb):2:in `new'
        2: from /usr/lib/ruby/vendor_ruby/mysql2/client.rb:90:in `initialize'
        1: from /usr/lib/ruby/vendor_ruby/mysql2/client.rb:90:in `connect'
Mysql2::Error (Unknown MySQL error)


You should get the same result with other MySQL clients rebuilt against MySQL 8.

Here is also the patch applied by manticoresearch (sphinxsearch fork) to
fix this issue:
https://github.com/manticoresoftware/manticoresearch/commit/ed98fdd7230c1d7298e1000fd10812338c6ba698

** Affects: sphinxsearch (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: patch
-- 
Version 2.2.11 does not support MySQL 8 clients
https://bugs.launchpad.net/bugs/1855468
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1855468 at bugs.launchpad.net  Fri Dec  6 20:56:22 2019
From: 1855468 at bugs.launchpad.net (Lucas Kanashiro)
Date: Fri, 06 Dec 2019 20:56:22 -0000
Subject: [Bug 1855468] Re: Version 2.2.11 does not support MySQL 8 clients
References: <157565518794.21540.17127031191078848707.malonedeb@soybean.canonical.com>
Message-ID: <157566578233.31178.10122253725452311464.malone@wampee.canonical.com>

This patch will also fix part of this ruby-riddle regression [1] which
is holding ruby-defaults version 1:2.5.2 in proposed.

[1] https://bugs.launchpad.net/ubuntu/+source/ruby-riddle/+bug/1855475

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855468

Title:
  Version 2.2.11 does not support MySQL 8 clients

Status in sphinxsearch package in Ubuntu:
  New

Bug description:
  sphinxsearch package version 2.2.11-2build1 was rebuilt during MySQL 8
  transition (as all MySQL related packages, like clients), however, its
  handshake implementation of MySQL protocol does not support MySQL 8
  clients, not allowing connections. According to upstream release
  notes, it was fixed in version 3.1.1:
  http://sphinxsearch.com/docs/sphinx3.html#version-3.1.1-17-oct-2018

  Steps to reproduce this issue in a brand new LXD container (focal-
  amd64):

  $ apt install sphinxsearch ruby-mysql2 -y
  $ cp /etc/sphinxsearch/sphinx.conf.dist /etc/sphinxsearch/sphinx.conf
  $ searchd --config /etc/sphinxsearch/sphinx.conf      // ignore the warnings, not relevant to this bug
  $ irb
  irb(main):001:0> require 'mysql2'
  => true
  irb(main):002:0> Mysql2::Client.new(:host => '127.0.0.1', :port => 9306)
  Traceback (most recent call last):
          5: from /usr/bin/irb:11:in `<main>'
          4: from (irb):2
          3: from (irb):2:in `new'
          2: from /usr/lib/ruby/vendor_ruby/mysql2/client.rb:90:in `initialize'
          1: from /usr/lib/ruby/vendor_ruby/mysql2/client.rb:90:in `connect'
  Mysql2::Error (Unknown MySQL error)

  
  You should get the same result with other MySQL clients rebuilt against MySQL 8.

  Here is also the patch applied by manticoresearch (sphinxsearch fork)
  to fix this issue:
  https://github.com/manticoresoftware/manticoresearch/commit/ed98fdd7230c1d7298e1000fd10812338c6ba698

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sphinxsearch/+bug/1855468/+subscriptions


From 1855475 at bugs.launchpad.net  Sat Dec  7 14:59:51 2019
From: 1855475 at bugs.launchpad.net (Lucas Kanashiro)
Date: Sat, 07 Dec 2019 14:59:51 -0000
Subject: [Bug 1855475] Re: autopkgtest regression triggered by
 ruby-defaults/1:2.5.2
References: <157565769389.21696.9148911649374236461.malonedeb@soybean.canonical.com>
Message-ID: <157573079135.6262.13374096843903196454.malone@gac.canonical.com>

debdiff was updated since ruby-riddle version 2.3.1-2 was imported from
Debian.

** Attachment added: "debdiff"
   https://bugs.launchpad.net/ubuntu/+source/ruby-riddle/+bug/1855475/+attachment/5310518/+files/debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855475

Title:
  autopkgtest regression triggered by ruby-defaults/1:2.5.2

Status in ruby-riddle package in Ubuntu:
  New

Bug description:
  ruby-riddle version 2.3.1-1ubuntu1 had a regression in focal after
  ruby-defaults/1:2.5.2 in all architectures, as you can see here
  [1][2].

  [1] http://autopkgtest.ubuntu.com/packages/r/ruby-riddle
  [2] http://autopkgtest.ubuntu.com/packages/r/ruby-riddle/focal/amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-riddle/+bug/1855475/+subscriptions


From 1855468 at bugs.launchpad.net  Sat Dec  7 21:17:11 2019
From: 1855468 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 07 Dec 2019 21:17:11 -0000
Subject: [Bug 1855468] Re: Version 2.2.11 does not support MySQL 8 clients
References: <157565518794.21540.17127031191078848707.malonedeb@soybean.canonical.com>
Message-ID: <157575343429.8946.16561681815391917656.malone@ackee.canonical.com>

This bug was fixed in the package sphinxsearch - 2.2.11-2ubuntu1

---------------
sphinxsearch (2.2.11-2ubuntu1) focal; urgency=medium

  * Fix handshake implementation of MySQL protocol to support MySQL 8
    clients. (LP: #1855468)

 -- Lucas Kanashiro <lucas.kanashiro at canonical.com>  Fri, 06 Dec 2019
14:38:22 -0300

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855468

Title:
  Version 2.2.11 does not support MySQL 8 clients

Status in sphinxsearch package in Ubuntu:
  Fix Released

Bug description:
  sphinxsearch package version 2.2.11-2build1 was rebuilt during MySQL 8
  transition (as all MySQL related packages, like clients), however, its
  handshake implementation of MySQL protocol does not support MySQL 8
  clients, not allowing connections. According to upstream release
  notes, it was fixed in version 3.1.1:
  http://sphinxsearch.com/docs/sphinx3.html#version-3.1.1-17-oct-2018

  Steps to reproduce this issue in a brand new LXD container (focal-
  amd64):

  $ apt install sphinxsearch ruby-mysql2 -y
  $ cp /etc/sphinxsearch/sphinx.conf.dist /etc/sphinxsearch/sphinx.conf
  $ searchd --config /etc/sphinxsearch/sphinx.conf      // ignore the warnings, not relevant to this bug
  $ irb
  irb(main):001:0> require 'mysql2'
  => true
  irb(main):002:0> Mysql2::Client.new(:host => '127.0.0.1', :port => 9306)
  Traceback (most recent call last):
          5: from /usr/bin/irb:11:in `<main>'
          4: from (irb):2
          3: from (irb):2:in `new'
          2: from /usr/lib/ruby/vendor_ruby/mysql2/client.rb:90:in `initialize'
          1: from /usr/lib/ruby/vendor_ruby/mysql2/client.rb:90:in `connect'
  Mysql2::Error (Unknown MySQL error)

  
  You should get the same result with other MySQL clients rebuilt against MySQL 8.

  Here is also the patch applied by manticoresearch (sphinxsearch fork)
  to fix this issue:
  https://github.com/manticoresoftware/manticoresearch/commit/ed98fdd7230c1d7298e1000fd10812338c6ba698

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sphinxsearch/+bug/1855468/+subscriptions


From 1855475 at bugs.launchpad.net  Sun Dec  8 00:02:05 2019
From: 1855475 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 08 Dec 2019 00:02:05 -0000
Subject: [Bug 1855475] Re: autopkgtest regression triggered by
 ruby-defaults/1:2.5.2
References: <157565769389.21696.9148911649374236461.malonedeb@soybean.canonical.com>
Message-ID: <157576332794.8939.10773818286891869668.malone@ackee.canonical.com>

This bug was fixed in the package ruby-riddle - 2.3.1-2ubuntu2

---------------
ruby-riddle (2.3.1-2ubuntu2) focal; urgency=medium

  * Fix DEP-8 tests regression (LP: #1855475)
    - B-d on sphinxsearch >= 2.2.11-2ubuntu1 which has support for MySQL 8
      clients, in this case ruby-mysql2.

 -- Lucas Kanashiro <lucas.kanashiro at canonical.com>  Sat, 07 Dec 2019
11:30:20 -0300

** Changed in: ruby-riddle (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855475

Title:
  autopkgtest regression triggered by ruby-defaults/1:2.5.2

Status in ruby-riddle package in Ubuntu:
  Fix Released

Bug description:
  ruby-riddle version 2.3.1-1ubuntu1 had a regression in focal after
  ruby-defaults/1:2.5.2 in all architectures, as you can see here
  [1][2].

  [1] http://autopkgtest.ubuntu.com/packages/r/ruby-riddle
  [2] http://autopkgtest.ubuntu.com/packages/r/ruby-riddle/focal/amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-riddle/+bug/1855475/+subscriptions


From 1855594 at bugs.launchpad.net  Sun Dec  8 14:45:05 2019
From: 1855594 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 08 Dec 2019 14:45:05 -0000
Subject: [Bug 1855594] [NEW] Sync chromium 78.0.3904.108-1 (universe) from
 Debian unstable (main)
References: <157581630122.6153.649495934122601180.malonedeb@gac.canonical.com>
Message-ID: <157581630524.4226.17227730750696336377.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Amr Ibrahim (amribrahim1987):

Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable
(main)

Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package.
This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one.

All changelog entries:

chromium (78.0.3904.108-1) unstable; urgency=medium

  * New upstream security release.
    - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li
    - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li
  * Disable vaapi on armhf (closes: #944627).

 -- Michael Gilbert <mgilbert at debian.org>  Wed, 20 Nov 2019 23:46:06
+0000

chromium (78.0.3904.97-1) unstable; urgency=medium

  * New upstream security release.
  * Enable vaapi (closes: #940074).
  * Fix crash during profile manager shutdown.
  * Drop libglewmx-dev build dependency (closes: #941050).

 -- Michael Gilbert <mgilbert at debian.org>  Sat, 09 Nov 2019 03:33:52
+0000

chromium (78.0.3904.87-1) unstable; urgency=medium

  * New upstream stable release.
    - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin
    - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong
    - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous
    - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin
    - CVE-2019-5874: External URIs may trigger other browsers. Reported by
      James Lee
    - CVE-2019-5875: URL bar spoof. Reported by Khalil
      Zhani
    - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo
    - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong
    - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong
    - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo
      Kim
    - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu
    - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang
    - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu
    - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu
    - CVE-2019-13662: CSP bypass. Reported by David Erceg
    - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang
    - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell
    - CVE-2019-13665: Multiple file download protection bypass. Reported by
      Jun Kokatsu
    - CVE-2019-13666: Side channel using storage size estimate. Reported by
      Tom Van Goethem
    - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by
      Khalil Zhani
    - CVE-2019-13668: Global window leak via console. Reported by David Erceg
    - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani
    - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong
    - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr
    - CVE-2019-13673: Cross-origin information leak using devtools. Reported
      by David Erceg
    - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani
    - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported
      by Jun Kokatsu
    - CVE-2019-13676: Google URI shown for certificate warning. Reported by
      Wenxu Wu
    - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported
      by Jun Kokatsu
    - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing
    - CVE-2019-13679: User gesture needed for printing. Reported by Conrad
      Irwin
    - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs
      Alkemade
    - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg
    - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu
    - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg
    - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani
    - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon
    - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo
    - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo
      Tiszka
    - CVE-2019-13691: Omnibox spoof. Reported by David Erceg
    - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu
    - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong
    - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin
    - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo
    - CVE-2019-13696: Use-after-free in V8. Reported by Guang Gong
    - CVE-2019-13697: Cross-origin size leak. Reported by Luan Herrera
    - CVE-2019-13699: Use-after-free in media. Reported by Man Yue Mo
    - CVE-2019-13700: Buffer overrun in Blink. Reported by Man Yue Mo
    - CVE-2019-13701: URL spoof in navigation. Reported by David Erceg
    - CVE-2019-13702: Privilege elevation in Installer. Reported by Phillip
      Langlois and Edward Torkington
    - CVE-2019-13703: URL bar spoofing. Reported by Khalil Zhani
    - CVE-2019-13704: CSP bypass. Reported by Jun Kokatsu
    - CVE-2019-13705: Extension permission bypass. Reported by Luan Herrera
    - CVE-2019-13706: Out-of-bounds read in PDFium. Reported by pdknsk
    - CVE-2019-13707: File storage disclosure. Reported by Andrea Palazzo
    - CVE-2019-13708: HTTP authentication spoof. Reported by Khalil Zhani
    - CVE-2019-13709: File download protection bypass. Reported by Zhong
      Zhaochen
    - CVE-2019-13710: File download protection bypass. Reported by
      bernardo.mrod
    - CVE-2019-13711: Cross-context information leak. Reported by David Erceg
    - CVE-2019-13713: Cross-origin data leak. Reported by David Erceg
    - CVE-2019-13714: CSS injection. Reported by Jun Kokatsu
    - CVE-2019-13715: Address bar spoofing. Reported by xisigr
    - CVE-2019-13716: Service worker state error. Reported by Barron Hagerman
    - CVE-2019-13717: Notification obscured. Reported by xisigr
    - CVE-2019-13718: IDN spoof. Reported by Khalil Zhani
    - CVE-2019-13719: Notification obscured. Reported by Khalil Zhani
    - CVE-2019-13720: Use-after-free in audio. Reported by Anton Ivanov and
      Alexey Kulaev
    - CVE-2019-13721: Use-after-free in PDFium. Reported by banananapenguin
  * Drop support for building with gcc 6 and gtk 2.

 -- Michael Gilbert <mgilbert at debian.org>  Sat, 02 Nov 2019 22:30:42
+0000

** Affects: ubuntu
     Importance: Undecided
         Status: New

-- 
Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1855594
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1855594 at bugs.launchpad.net  Sun Dec  8 15:02:40 2019
From: 1855594 at bugs.launchpad.net (Paul White)
Date: Sun, 08 Dec 2019 15:02:40 -0000
Subject: [Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from
 Debian unstable (main)
References: <157581630122.6153.649495934122601180.malonedeb@gac.canonical.com>
Message-ID: <157581736193.4570.16457138738975593623.launchpad@chaenomeles.canonical.com>

** Package changed: ubuntu => chromium-browser (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855594

Title:
  Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable
  (main)

  Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package.
  This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one.

  All changelog entries:

  chromium (78.0.3904.108-1) unstable; urgency=medium

    * New upstream security release.
      - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li
      - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li
    * Disable vaapi on armhf (closes: #944627).

   -- Michael Gilbert <mgilbert at debian.org>  Wed, 20 Nov 2019 23:46:06
  +0000

  chromium (78.0.3904.97-1) unstable; urgency=medium

    * New upstream security release.
    * Enable vaapi (closes: #940074).
    * Fix crash during profile manager shutdown.
    * Drop libglewmx-dev build dependency (closes: #941050).

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 09 Nov 2019 03:33:52
  +0000

  chromium (78.0.3904.87-1) unstable; urgency=medium

    * New upstream stable release.
      - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin
      - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong
      - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous
      - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin
      - CVE-2019-5874: External URIs may trigger other browsers. Reported by
        James Lee
      - CVE-2019-5875: URL bar spoof. Reported by Khalil
        Zhani
      - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong
      - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo
        Kim
      - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu
      - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang
      - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu
      - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu
      - CVE-2019-13662: CSP bypass. Reported by David Erceg
      - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang
      - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell
      - CVE-2019-13665: Multiple file download protection bypass. Reported by
        Jun Kokatsu
      - CVE-2019-13666: Side channel using storage size estimate. Reported by
        Tom Van Goethem
      - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by
        Khalil Zhani
      - CVE-2019-13668: Global window leak via console. Reported by David Erceg
      - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong
      - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr
      - CVE-2019-13673: Cross-origin information leak using devtools. Reported
        by David Erceg
      - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani
      - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported
        by Jun Kokatsu
      - CVE-2019-13676: Google URI shown for certificate warning. Reported by
        Wenxu Wu
      - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported
        by Jun Kokatsu
      - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing
      - CVE-2019-13679: User gesture needed for printing. Reported by Conrad
        Irwin
      - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs
        Alkemade
      - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg
      - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu
      - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg
      - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani
      - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon
      - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo
        Tiszka
      - CVE-2019-13691: Omnibox spoof. Reported by David Erceg
      - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu
      - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong
      - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin
      - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo
      - CVE-2019-13696: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-13697: Cross-origin size leak. Reported by Luan Herrera
      - CVE-2019-13699: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13700: Buffer overrun in Blink. Reported by Man Yue Mo
      - CVE-2019-13701: URL spoof in navigation. Reported by David Erceg
      - CVE-2019-13702: Privilege elevation in Installer. Reported by Phillip
        Langlois and Edward Torkington
      - CVE-2019-13703: URL bar spoofing. Reported by Khalil Zhani
      - CVE-2019-13704: CSP bypass. Reported by Jun Kokatsu
      - CVE-2019-13705: Extension permission bypass. Reported by Luan Herrera
      - CVE-2019-13706: Out-of-bounds read in PDFium. Reported by pdknsk
      - CVE-2019-13707: File storage disclosure. Reported by Andrea Palazzo
      - CVE-2019-13708: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13709: File download protection bypass. Reported by Zhong
        Zhaochen
      - CVE-2019-13710: File download protection bypass. Reported by
        bernardo.mrod
      - CVE-2019-13711: Cross-context information leak. Reported by David Erceg
      - CVE-2019-13713: Cross-origin data leak. Reported by David Erceg
      - CVE-2019-13714: CSS injection. Reported by Jun Kokatsu
      - CVE-2019-13715: Address bar spoofing. Reported by xisigr
      - CVE-2019-13716: Service worker state error. Reported by Barron Hagerman
      - CVE-2019-13717: Notification obscured. Reported by xisigr
      - CVE-2019-13718: IDN spoof. Reported by Khalil Zhani
      - CVE-2019-13719: Notification obscured. Reported by Khalil Zhani
      - CVE-2019-13720: Use-after-free in audio. Reported by Anton Ivanov and
        Alexey Kulaev
      - CVE-2019-13721: Use-after-free in PDFium. Reported by banananapenguin
    * Drop support for building with gcc 6 and gtk 2.

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 02 Nov 2019 22:30:42
  +0000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855594/+subscriptions


From 1855594 at bugs.launchpad.net  Sun Dec  8 19:24:15 2019
From: 1855594 at bugs.launchpad.net (Amr Ibrahim)
Date: Sun, 08 Dec 2019 19:24:15 -0000
Subject: [Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from
 Debian unstable (main)
References: <157581630122.6153.649495934122601180.malonedeb@gac.canonical.com>
Message-ID: <157583305566.4062.3991506160893211163.malone@chaenomeles.canonical.com>

This is a request to sync a new source package from Debian,
independently of the chromium-browser source, which only exists in
Ubuntu and not in Debian. I don't think the chromium-browser source
works here, it has to remain as it is after 20.04 LTS for the transition
to the chromium snap to fully happen.

** Package changed: chromium-browser (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855594

Title:
  Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)

Status in Ubuntu:
  New

Bug description:
  Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable
  (main)

  Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package.
  This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one.

  All changelog entries:

  chromium (78.0.3904.108-1) unstable; urgency=medium

    * New upstream security release.
      - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li
      - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li
    * Disable vaapi on armhf (closes: #944627).

   -- Michael Gilbert <mgilbert at debian.org>  Wed, 20 Nov 2019 23:46:06
  +0000

  chromium (78.0.3904.97-1) unstable; urgency=medium

    * New upstream security release.
    * Enable vaapi (closes: #940074).
    * Fix crash during profile manager shutdown.
    * Drop libglewmx-dev build dependency (closes: #941050).

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 09 Nov 2019 03:33:52
  +0000

  chromium (78.0.3904.87-1) unstable; urgency=medium

    * New upstream stable release.
      - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin
      - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong
      - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous
      - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin
      - CVE-2019-5874: External URIs may trigger other browsers. Reported by
        James Lee
      - CVE-2019-5875: URL bar spoof. Reported by Khalil
        Zhani
      - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong
      - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo
        Kim
      - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu
      - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang
      - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu
      - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu
      - CVE-2019-13662: CSP bypass. Reported by David Erceg
      - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang
      - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell
      - CVE-2019-13665: Multiple file download protection bypass. Reported by
        Jun Kokatsu
      - CVE-2019-13666: Side channel using storage size estimate. Reported by
        Tom Van Goethem
      - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by
        Khalil Zhani
      - CVE-2019-13668: Global window leak via console. Reported by David Erceg
      - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong
      - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr
      - CVE-2019-13673: Cross-origin information leak using devtools. Reported
        by David Erceg
      - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani
      - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported
        by Jun Kokatsu
      - CVE-2019-13676: Google URI shown for certificate warning. Reported by
        Wenxu Wu
      - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported
        by Jun Kokatsu
      - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing
      - CVE-2019-13679: User gesture needed for printing. Reported by Conrad
        Irwin
      - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs
        Alkemade
      - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg
      - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu
      - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg
      - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani
      - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon
      - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo
        Tiszka
      - CVE-2019-13691: Omnibox spoof. Reported by David Erceg
      - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu
      - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong
      - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin
      - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo
      - CVE-2019-13696: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-13697: Cross-origin size leak. Reported by Luan Herrera
      - CVE-2019-13699: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13700: Buffer overrun in Blink. Reported by Man Yue Mo
      - CVE-2019-13701: URL spoof in navigation. Reported by David Erceg
      - CVE-2019-13702: Privilege elevation in Installer. Reported by Phillip
        Langlois and Edward Torkington
      - CVE-2019-13703: URL bar spoofing. Reported by Khalil Zhani
      - CVE-2019-13704: CSP bypass. Reported by Jun Kokatsu
      - CVE-2019-13705: Extension permission bypass. Reported by Luan Herrera
      - CVE-2019-13706: Out-of-bounds read in PDFium. Reported by pdknsk
      - CVE-2019-13707: File storage disclosure. Reported by Andrea Palazzo
      - CVE-2019-13708: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13709: File download protection bypass. Reported by Zhong
        Zhaochen
      - CVE-2019-13710: File download protection bypass. Reported by
        bernardo.mrod
      - CVE-2019-13711: Cross-context information leak. Reported by David Erceg
      - CVE-2019-13713: Cross-origin data leak. Reported by David Erceg
      - CVE-2019-13714: CSS injection. Reported by Jun Kokatsu
      - CVE-2019-13715: Address bar spoofing. Reported by xisigr
      - CVE-2019-13716: Service worker state error. Reported by Barron Hagerman
      - CVE-2019-13717: Notification obscured. Reported by xisigr
      - CVE-2019-13718: IDN spoof. Reported by Khalil Zhani
      - CVE-2019-13719: Notification obscured. Reported by Khalil Zhani
      - CVE-2019-13720: Use-after-free in audio. Reported by Anton Ivanov and
        Alexey Kulaev
      - CVE-2019-13721: Use-after-free in PDFium. Reported by banananapenguin
    * Drop support for building with gcc 6 and gtk 2.

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 02 Nov 2019 22:30:42
  +0000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1855594/+subscriptions


From 1848286 at bugs.launchpad.net  Mon Dec  9 08:28:26 2019
From: 1848286 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 09 Dec 2019 08:28:26 -0000
Subject: [Bug 1848286] Re: octavia is not reporting metrics like lbaasv2
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157588011041.8939.4730757518413059673.malone@ackee.canonical.com>

This bug was fixed in the package ceilometer - 1:13.0.0-0ubuntu1.1

---------------
ceilometer (1:13.0.0-0ubuntu1.1) eoan; urgency=medium

  * d/gbp.conf: Create stable/train branch.
  * d/p/add-loadbalancer-resource-type.patch: Enable load balancer metrics,
    allowing gnocchi to capture measurement data for octavia load balancers
    (LP: #1848286).

 -- Corey Bryant <corey.bryant at canonical.com>  Wed, 27 Nov 2019 09:23:05
-0500

** Changed in: ceilometer (Ubuntu Eoan)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From 1848286 at bugs.launchpad.net  Mon Dec  9 08:28:33 2019
From: 1848286 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 09 Dec 2019 08:28:33 -0000
Subject: [Bug 1848286] Update Released
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157588011352.5173.13097229211239188733.malone@chaenomeles.canonical.com>

The verification of the Stable Release Update for ceilometer has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From 1848286 at bugs.launchpad.net  Mon Dec  9 08:28:49 2019
From: 1848286 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 09 Dec 2019 08:28:49 -0000
Subject: [Bug 1848286] Re: octavia is not reporting metrics like lbaasv2
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157588013238.8939.13884593977768358920.malone@ackee.canonical.com>

This bug was fixed in the package ceilometer - 1:12.0.0-0ubuntu1.1

---------------
ceilometer (1:12.0.0-0ubuntu1.1) disco; urgency=medium

  * d/gbp.conf: Create stable/stein branch.
  * d/control: Add python-oslo.upgradecheck BD.
  * d/p/add-loadbalancer-resource-type.patch: Enable load balancer metrics,
    allowing gnocchi to capture measurement data for octavia load balancers
    (LP: #1848286).

 -- Corey Bryant <corey.bryant at canonical.com>  Wed, 27 Nov 2019 09:44:08
-0500

** Changed in: ceilometer (Ubuntu Disco)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From daniel.van.vugt at canonical.com  Mon Dec  9 09:41:56 2019
From: daniel.van.vugt at canonical.com (Daniel van Vugt)
Date: Mon, 09 Dec 2019 09:41:56 -0000
Subject: [Bug 1854689] Re: BlueZ 5.52 release
References: <157526921040.6334.11536417789885422275.malonedeb@gac.canonical.com>
Message-ID: <157588451688.3958.11331351274221449313.malone@chaenomeles.canonical.com>

Seb just pointed out this needs redoing because this appeared over the weekend:
https://launchpad.net/ubuntu/+source/bluez/5.51-0ubuntu2

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854689

Title:
  BlueZ 5.52 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  BlueZ 5.52 release:
  http://www.bluez.org/release-of-bluez-5-52/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+subscriptions


From 1854689 at bugs.launchpad.net  Mon Dec  9 10:09:11 2019
From: 1854689 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 09 Dec 2019 10:09:11 -0000
Subject: [Bug 1854689] [NEW] BlueZ 5.52 release
References: <157526921040.6334.11536417789885422275.malonedeb@gac.canonical.com>
Message-ID: <157588615196.18297.8110656870591540399.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Daniel van Vugt (vanvugt):

BlueZ 5.52 release:
http://www.bluez.org/release-of-bluez-5-52/

** Affects: bluez (Ubuntu)
     Importance: Medium
     Assignee: Daniel van Vugt (vanvugt)
         Status: In Progress


** Tags: focal
-- 
BlueZ 5.52 release
https://bugs.launchpad.net/bugs/1854689
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From corey.bryant at canonical.com  Mon Dec  9 13:39:00 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 09 Dec 2019 13:39:00 -0000
Subject: [Bug 1848286] Update Released
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157589874103.7085.12283913786855861026.malone@gac.canonical.com>

The verification of the Stable Release Update for ceilometer has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From corey.bryant at canonical.com  Mon Dec  9 13:39:03 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 09 Dec 2019 13:39:03 -0000
Subject: [Bug 1848286] Re: octavia is not reporting metrics like lbaasv2
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157589874377.18138.4718238391156040255.malone@wampee.canonical.com>

This bug was fixed in the package ceilometer - 1:13.0.0-0ubuntu1.1~cloud0
---------------

 ceilometer (1:13.0.0-0ubuntu1.1~cloud0) bionic-train; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 ceilometer (1:13.0.0-0ubuntu1.1) eoan; urgency=medium
 .
   * d/gbp.conf: Create stable/train branch.
   * d/p/add-loadbalancer-resource-type.patch: Enable load balancer metrics,
     allowing gnocchi to capture measurement data for octavia load balancers
     (LP: #1848286).


** Changed in: cloud-archive/train
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From corey.bryant at canonical.com  Mon Dec  9 13:39:36 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 09 Dec 2019 13:39:36 -0000
Subject: [Bug 1848286] Update Released
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157589877624.7537.4372501955183733684.malone@soybean.canonical.com>

The verification of the Stable Release Update for ceilometer has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From corey.bryant at canonical.com  Mon Dec  9 13:39:37 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 09 Dec 2019 13:39:37 -0000
Subject: [Bug 1848286] Re: octavia is not reporting metrics like lbaasv2
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157589877798.5254.11926927604643859191.malone@chaenomeles.canonical.com>

This bug was fixed in the package ceilometer - 1:12.0.0-0ubuntu1.1~cloud0
---------------

 ceilometer (1:12.0.0-0ubuntu1.1~cloud0) bionic-stein; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 ceilometer (1:12.0.0-0ubuntu1.1) disco; urgency=medium
 .
   * d/gbp.conf: Create stable/stein branch.
   * d/control: Add python-oslo.upgradecheck BD.
   * d/p/add-loadbalancer-resource-type.patch: Enable load balancer metrics,
     allowing gnocchi to capture measurement data for octavia load balancers
     (LP: #1848286).


** Changed in: cloud-archive/stein
       Status: Fix Committed => Fix Released

** No longer affects: cloud-archive/ussuri

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From corey.bryant at canonical.com  Mon Dec  9 13:40:58 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 09 Dec 2019 13:40:58 -0000
Subject: [Bug 1848286] Update Released
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157589885815.4676.4152136967094133131.malone@chaenomeles.canonical.com>

The verification of the Stable Release Update for ceilometer has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From corey.bryant at canonical.com  Mon Dec  9 13:41:00 2019
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 09 Dec 2019 13:41:00 -0000
Subject: [Bug 1848286] Re: octavia is not reporting metrics like lbaasv2
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <157589886053.4729.1649071731973664090.malone@chaenomeles.canonical.com>

This bug was fixed in the package ceilometer - 1:11.0.1-0ubuntu2~cloud1
---------------

 ceilometer (1:11.0.1-0ubuntu2~cloud1) bionic-rocky; urgency=medium
 .
   * d/p/add-loadbalancer-resource-type.patch: Enable load balancer metrics,
     allowing gnocchi to capture measurement data for octavia load balancers
     (LP: #1848286).


** Changed in: cloud-archive/rocky
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1848286/+subscriptions


From 1733321 at bugs.launchpad.net  Tue Dec 10 14:45:27 2019
From: 1733321 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 10 Dec 2019 14:45:27 -0000
Subject: [Bug 1733321] [NEW] network-manager ADT tests fail with on ppc64el
 with artful/linux 4.13.0.17.18
References: <151118157603.13514.8949741665376773525.malonedeb@wampee.canonical.com>
Message-ID: <157598912765.18833.13751117727304262425.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Martin Wimpress (flexiondotorg):

[Impact]

The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
reports the old state when it's called right after rfkill block/unblock.
Adding a sleep before calling nmcli fixes the issue.

ppc64el ADT log from failed testcase:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-artful/artful/ppc64el/n/network-
manager/20171120_100719_28642@/log.gz

Testcase output:
-----
autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
  AR      /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
  CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
  LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
ERROR: NM could not track device state.
autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - results - - - - - - - - - -
killswitches-no-urfkill FAIL non-zero exit status 1
-----

Package versions [artful/ppc64el]:
network-manager 1.8.4-1ubuntu3
linux-meta 4.13.0.17.18


[Test Case]

2.1. Download network-manager package source code
$ apt-get source network-manager

2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill


[Regression Potential]

No regression potential. The fix touches only the testcase shipped with
the source package and it doesn't change the binary package. The sleep
time added is very small, so no possibility of causing testcase timeout.


[Other Info]

On ppc64el architecture, it was observed that a fix for systemd is also
needed (see bug 1734908) for the testcase to be successful.

** Affects: network-manager (Ubuntu)
     Importance: Medium
         Status: New

** Affects: network-manager (Ubuntu Artful)
     Importance: Medium
         Status: Won't Fix

** Affects: network-manager (Ubuntu Disco)
     Importance: Medium
         Status: New

** Affects: network-manager (Ubuntu Eoan)
     Importance: Medium
         Status: New

** Affects: network-manager (Ubuntu Focal)
     Importance: Medium
         Status: New


** Tags: artful
-- 
network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
https://bugs.launchpad.net/bugs/1733321
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From olivier.tilloy at canonical.com  Tue Dec 10 16:11:58 2019
From: olivier.tilloy at canonical.com (Olivier Tilloy)
Date: Tue, 10 Dec 2019 16:11:58 -0000
Subject: [Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from
 Debian unstable (main)
References: <157581630122.6153.649495934122601180.malonedeb@gac.canonical.com>
Message-ID: <157599431895.19011.16876439108111843409.malone@wampee.canonical.com>

This seems technically feasible, as there is no "chromium" source
package in Ubuntu. It would probably be confusing though, from an end-
user perspective.

Amr Ibrahim, have you tested the existing Debian package in Ubuntu?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855594

Title:
  Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)

Status in Ubuntu:
  New

Bug description:
  Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable
  (main)

  Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package.
  This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one.

  All changelog entries:

  chromium (78.0.3904.108-1) unstable; urgency=medium

    * New upstream security release.
      - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li
      - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li
    * Disable vaapi on armhf (closes: #944627).

   -- Michael Gilbert <mgilbert at debian.org>  Wed, 20 Nov 2019 23:46:06
  +0000

  chromium (78.0.3904.97-1) unstable; urgency=medium

    * New upstream security release.
    * Enable vaapi (closes: #940074).
    * Fix crash during profile manager shutdown.
    * Drop libglewmx-dev build dependency (closes: #941050).

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 09 Nov 2019 03:33:52
  +0000

  chromium (78.0.3904.87-1) unstable; urgency=medium

    * New upstream stable release.
      - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin
      - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong
      - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous
      - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin
      - CVE-2019-5874: External URIs may trigger other browsers. Reported by
        James Lee
      - CVE-2019-5875: URL bar spoof. Reported by Khalil
        Zhani
      - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong
      - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo
        Kim
      - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu
      - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang
      - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu
      - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu
      - CVE-2019-13662: CSP bypass. Reported by David Erceg
      - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang
      - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell
      - CVE-2019-13665: Multiple file download protection bypass. Reported by
        Jun Kokatsu
      - CVE-2019-13666: Side channel using storage size estimate. Reported by
        Tom Van Goethem
      - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by
        Khalil Zhani
      - CVE-2019-13668: Global window leak via console. Reported by David Erceg
      - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong
      - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr
      - CVE-2019-13673: Cross-origin information leak using devtools. Reported
        by David Erceg
      - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani
      - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported
        by Jun Kokatsu
      - CVE-2019-13676: Google URI shown for certificate warning. Reported by
        Wenxu Wu
      - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported
        by Jun Kokatsu
      - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing
      - CVE-2019-13679: User gesture needed for printing. Reported by Conrad
        Irwin
      - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs
        Alkemade
      - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg
      - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu
      - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg
      - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani
      - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon
      - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo
        Tiszka
      - CVE-2019-13691: Omnibox spoof. Reported by David Erceg
      - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu
      - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong
      - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin
      - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo
      - CVE-2019-13696: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-13697: Cross-origin size leak. Reported by Luan Herrera
      - CVE-2019-13699: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13700: Buffer overrun in Blink. Reported by Man Yue Mo
      - CVE-2019-13701: URL spoof in navigation. Reported by David Erceg
      - CVE-2019-13702: Privilege elevation in Installer. Reported by Phillip
        Langlois and Edward Torkington
      - CVE-2019-13703: URL bar spoofing. Reported by Khalil Zhani
      - CVE-2019-13704: CSP bypass. Reported by Jun Kokatsu
      - CVE-2019-13705: Extension permission bypass. Reported by Luan Herrera
      - CVE-2019-13706: Out-of-bounds read in PDFium. Reported by pdknsk
      - CVE-2019-13707: File storage disclosure. Reported by Andrea Palazzo
      - CVE-2019-13708: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13709: File download protection bypass. Reported by Zhong
        Zhaochen
      - CVE-2019-13710: File download protection bypass. Reported by
        bernardo.mrod
      - CVE-2019-13711: Cross-context information leak. Reported by David Erceg
      - CVE-2019-13713: Cross-origin data leak. Reported by David Erceg
      - CVE-2019-13714: CSS injection. Reported by Jun Kokatsu
      - CVE-2019-13715: Address bar spoofing. Reported by xisigr
      - CVE-2019-13716: Service worker state error. Reported by Barron Hagerman
      - CVE-2019-13717: Notification obscured. Reported by xisigr
      - CVE-2019-13718: IDN spoof. Reported by Khalil Zhani
      - CVE-2019-13719: Notification obscured. Reported by Khalil Zhani
      - CVE-2019-13720: Use-after-free in audio. Reported by Anton Ivanov and
        Alexey Kulaev
      - CVE-2019-13721: Use-after-free in PDFium. Reported by banananapenguin
    * Drop support for building with gcc 6 and gtk 2.

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 02 Nov 2019 22:30:42
  +0000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1855594/+subscriptions


From 1855893 at bugs.launchpad.net  Tue Dec 10 16:27:25 2019
From: 1855893 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 10 Dec 2019 16:27:25 -0000
Subject: [Bug 1855893] [NEW] Properly let PCM leave suspended state when
 hardware doesn't support PCM resume
References: <157598921477.7721.14604770826784008639.malonedeb@soybean.canonical.com>
Message-ID: <157599524589.6582.6788844669972533468.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

[Impact]
Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

[Fix]
According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume.
For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal.

[Test]
1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
2. Suspend/resume.
3. See if microphone still works in those apps.
I can the issue is fixed after each suspend/resume cycle.

[Regression Potential]
Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test.

** Affects: hwe-next
     Importance: Undecided
         Status: New

** Affects: pulseaudio (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: oem-priority originate-from-1849812 patch somerville
-- 
Properly let PCM leave suspended state when hardware doesn't support PCM resume
https://bugs.launchpad.net/bugs/1855893
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1855893 at bugs.launchpad.net  Tue Dec 10 16:27:26 2019
From: 1855893 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Tue, 10 Dec 2019 16:27:26 -0000
Subject: [Bug 1855893] Re: Properly let PCM leave suspended state when
 hardware doesn't support PCM resume
References: <157598921477.7721.14604770826784008639.malonedeb@soybean.canonical.com>
Message-ID: <157599524697.6933.5524831016912271058.malone@gac.canonical.com>

The attachment "pulseaudio_11.1-1ubuntu7.6.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855893

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions


From 1834138 at bugs.launchpad.net  Wed Dec 11 01:48:15 2019
From: 1834138 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 11 Dec 2019 01:48:15 -0000
Subject: [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with
 only unavailable ports
References: <156144244269.31021.1553467580133274436.malonedeb@soybean.canonical.com>
Message-ID: <157602890402.30696.182155404790264473.malone@ackee.canonical.com>

This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.5

---------------
pulseaudio (1:11.1-1ubuntu7.5) bionic; urgency=medium

  * Update snap policy to make access to audio recording conditional on
    plugging the "pulseaudio" or "audio-record" interfaces (LP: #1781428):
    - 0700-modules-add-snappy-policy-module.patch: rewrite to query
      snapd for the client's plugged interfaces.
    - 0701-enable-snap-policy-module.patch: enable the module in the
      default configuration.
    - Build depend on libsnapd-glib-dev.
  * Remove module-trust-store patch set:
    - 0409-Trust-store-patch.patch: trimmed down to pulsecore changes.
    - 0410-Add-thread-to-activate-trust-store-interface.patch: removed.
    - 0417-increase-timeout-check-apparmor.patch: removed.

 -- James Henstridge <james.henstridge at canonical.com>  Wed, 05 Nov 2019
17:16:25 +0800

** Changed in: pulseaudio (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1834138

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions


From 1733321 at bugs.launchpad.net  Wed Dec 11 02:04:50 2019
From: 1733321 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 11 Dec 2019 02:04:50 -0000
Subject: [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with
 artful/linux 4.13.0.17.18
References: <151118157603.13514.8949741665376773525.malonedeb@wampee.canonical.com>
Message-ID: <157602989155.6994.8648847928641170593.launchpad@soybean.canonical.com>

** Tags added: testcase

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1733321

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  New
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -----
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [-----------------------
  make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR      /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC      /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: -----------------------]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -----

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions


From 1855594 at bugs.launchpad.net  Wed Dec 11 02:08:52 2019
From: 1855594 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 11 Dec 2019 02:08:52 -0000
Subject: [Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from
 Debian unstable (main)
References: <157581630122.6153.649495934122601180.malonedeb@gac.canonical.com>
Message-ID: <157603013327.4676.94306754947349398.launchpad@chaenomeles.canonical.com>

** Changed in: ubuntu
   Importance: Undecided => Wishlist

** Package changed: ubuntu => chromium (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855594

Title:
  Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)

Status in chromium package in Ubuntu:
  New

Bug description:
  Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable
  (main)

  Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package.
  This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one.

  All changelog entries:

  chromium (78.0.3904.108-1) unstable; urgency=medium

    * New upstream security release.
      - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li
      - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li
    * Disable vaapi on armhf (closes: #944627).

   -- Michael Gilbert <mgilbert at debian.org>  Wed, 20 Nov 2019 23:46:06
  +0000

  chromium (78.0.3904.97-1) unstable; urgency=medium

    * New upstream security release.
    * Enable vaapi (closes: #940074).
    * Fix crash during profile manager shutdown.
    * Drop libglewmx-dev build dependency (closes: #941050).

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 09 Nov 2019 03:33:52
  +0000

  chromium (78.0.3904.87-1) unstable; urgency=medium

    * New upstream stable release.
      - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin
      - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong
      - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous
      - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin
      - CVE-2019-5874: External URIs may trigger other browsers. Reported by
        James Lee
      - CVE-2019-5875: URL bar spoof. Reported by Khalil
        Zhani
      - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong
      - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo
        Kim
      - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu
      - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang
      - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu
      - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu
      - CVE-2019-13662: CSP bypass. Reported by David Erceg
      - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang
      - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell
      - CVE-2019-13665: Multiple file download protection bypass. Reported by
        Jun Kokatsu
      - CVE-2019-13666: Side channel using storage size estimate. Reported by
        Tom Van Goethem
      - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by
        Khalil Zhani
      - CVE-2019-13668: Global window leak via console. Reported by David Erceg
      - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong
      - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr
      - CVE-2019-13673: Cross-origin information leak using devtools. Reported
        by David Erceg
      - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani
      - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported
        by Jun Kokatsu
      - CVE-2019-13676: Google URI shown for certificate warning. Reported by
        Wenxu Wu
      - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported
        by Jun Kokatsu
      - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing
      - CVE-2019-13679: User gesture needed for printing. Reported by Conrad
        Irwin
      - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs
        Alkemade
      - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg
      - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu
      - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg
      - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani
      - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon
      - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo
        Tiszka
      - CVE-2019-13691: Omnibox spoof. Reported by David Erceg
      - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu
      - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong
      - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin
      - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo
      - CVE-2019-13696: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-13697: Cross-origin size leak. Reported by Luan Herrera
      - CVE-2019-13699: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13700: Buffer overrun in Blink. Reported by Man Yue Mo
      - CVE-2019-13701: URL spoof in navigation. Reported by David Erceg
      - CVE-2019-13702: Privilege elevation in Installer. Reported by Phillip
        Langlois and Edward Torkington
      - CVE-2019-13703: URL bar spoofing. Reported by Khalil Zhani
      - CVE-2019-13704: CSP bypass. Reported by Jun Kokatsu
      - CVE-2019-13705: Extension permission bypass. Reported by Luan Herrera
      - CVE-2019-13706: Out-of-bounds read in PDFium. Reported by pdknsk
      - CVE-2019-13707: File storage disclosure. Reported by Andrea Palazzo
      - CVE-2019-13708: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13709: File download protection bypass. Reported by Zhong
        Zhaochen
      - CVE-2019-13710: File download protection bypass. Reported by
        bernardo.mrod
      - CVE-2019-13711: Cross-context information leak. Reported by David Erceg
      - CVE-2019-13713: Cross-origin data leak. Reported by David Erceg
      - CVE-2019-13714: CSS injection. Reported by Jun Kokatsu
      - CVE-2019-13715: Address bar spoofing. Reported by xisigr
      - CVE-2019-13716: Service worker state error. Reported by Barron Hagerman
      - CVE-2019-13717: Notification obscured. Reported by xisigr
      - CVE-2019-13718: IDN spoof. Reported by Khalil Zhani
      - CVE-2019-13719: Notification obscured. Reported by Khalil Zhani
      - CVE-2019-13720: Use-after-free in audio. Reported by Anton Ivanov and
        Alexey Kulaev
      - CVE-2019-13721: Use-after-free in PDFium. Reported by banananapenguin
    * Drop support for building with gcc 6 and gtk 2.

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 02 Nov 2019 22:30:42
  +0000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1855594/+subscriptions


From 1854689 at bugs.launchpad.net  Wed Dec 11 02:13:47 2019
From: 1854689 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 11 Dec 2019 02:13:47 -0000
Subject: [Bug 1854689] Re: BlueZ 5.52 release
References: <157526921040.6334.11536417789885422275.malonedeb@gac.canonical.com>
Message-ID: <157603042840.4729.849507637012817740.launchpad@chaenomeles.canonical.com>

** Tags added: upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854689

Title:
  BlueZ 5.52 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  BlueZ 5.52 release:
  http://www.bluez.org/release-of-bluez-5-52/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+subscriptions


From 1855893 at bugs.launchpad.net  Wed Dec 11 02:24:22 2019
From: 1855893 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 11 Dec 2019 02:24:22 -0000
Subject: [Bug 1855893] Re: Properly let PCM leave suspended state when
 hardware doesn't support PCM resume
References: <157598921477.7721.14604770826784008639.malonedeb@soybean.canonical.com>
Message-ID: <157603106356.4168.5012261154841393520.launchpad@chaenomeles.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855893

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions


From woodrow.shen at canonical.com  Wed Dec 11 02:56:15 2019
From: woodrow.shen at canonical.com (Woodrow Shen)
Date: Wed, 11 Dec 2019 02:56:15 -0000
Subject: [Bug 1831733] Re: ledmon incorrectly sets the status LED
References: <155973431268.7669.7422180376393685843.malonedeb@wampee.canonical.com>
Message-ID: <157603297542.6298.13250270545012309492.malone@gac.canonical.com>

The upstream version 0.93 is landed in focal now:

ledmon (0.93-3) unstable; urgency=medium

  * Fix 32bit compilation error to prevent shift-count-overflow.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1831733

Title:
  ledmon incorrectly sets the status LED

Status in OEM Priority Project:
  Confirmed
Status in ledmon package in Ubuntu:
  Confirmed

Bug description:
  Description:

  After creating the RAID volume, deleting it and creating second RAID
  volume (with same disks as with first volume but with less disks'
  count), LED statuses on disks left in container are ‘failure’.

  Steps to reproduce:
  1.	Turn on ledmon:
  # ledmon --all

  2.	Create RAID container:
  # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=3 /dev/nvme5n1 /dev/nvme4n1 /dev/nvme2n1 --run –force

  3.	Create first RAID volume:
  # mdadm --create /dev/md/Volume --level=5 --chunk 64 --raid-devices=3 /dev/nvme5n1 /dev/nvme4n1 /dev/nvme2n1 --run –force

  4.	Stop first RAID volume:
  # mdadm --stop /dev/md/Volume

  5.	Delete first RAID volume:
  # mdadm --kill-subarray=0 /dev/md127

  6.	Create second RAID volume in the same container (with less disks' count than first RAID, using the sane disks as in the first volume):
  # mdadm --create /dev/md/Volume --level=1 --raid-devices=2 /dev/nvme5n1 /dev/nvme4n1 --run

  7.      Verify status LED on container member disks which are not part
  of second RAID volume.

  Expected results: 
  Disks from container which are not in the second volume should have ‘normal’ status LED.

  Actual results: 
  Disks from container which are not in the second volume have ‘failure’ status LED.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1831733/+subscriptions


From superm1 at ubuntu.com  Wed Dec 11 17:38:21 2019
From: superm1 at ubuntu.com (Mario Limonciello)
Date: Wed, 11 Dec 2019 17:38:21 -0000
Subject: [Bug 1820768] Re: [SRU] support new cab and new docking firmware
 upgrade in fwupd 1.2.10
References: <155295081031.32044.4189733535399473960.malonedeb@soybean.canonical.com>
Message-ID: <157608590174.18612.11058982306960871725.malone@wampee.canonical.com>

Hello, any updates on this?  It would be good to get any review comments
because the SRU will need to be modified again to include this as well:
https://github.com/fwupd/fwupd/commit/004a0624d05211e8436060bb7af6b0c6f2d805a3

(See https://blogs.gnome.org/hughsie/2019/12/11/improving-the-security-
model-of-the-lvfs/ for more details)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Triaged
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  New
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  I
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show
  II.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.
  III.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions


From yc.cheng at canonical.com  Thu Dec 12 08:37:00 2019
From: yc.cheng at canonical.com (Yuan-Chen Cheng)
Date: Thu, 12 Dec 2019 08:37:00 -0000
Subject: [Bug 1820768] Re: [SRU] support new cab and new docking firmware
 upgrade in fwupd 1.2.10
References: <155295081031.32044.4189733535399473960.malonedeb@soybean.canonical.com>
Message-ID: <157613982076.18138.15819798285321243553.malone@wampee.canonical.com>

@Timo and Steve, for the patch in #30, I simply put the commit in
debian/patch and modify series, then it can be perperly built.

The testing ppa build is in https://launchpad.net/~ycheng-
twn/+archive/ubuntu/fwupd-1.2.10-4 (without Timo's make up).

Per my reading of the blog article, we should include that patch for
releases that's not EOL.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Triaged
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  New
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  I
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show
  II.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.
  III.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions


From seb128 at ubuntu.com  Thu Dec 12 08:46:21 2019
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Thu, 12 Dec 2019 08:46:21 -0000
Subject: [Bug 1854689] Re: BlueZ 5.52 release
References: <157526921040.6334.11536417789885422275.malonedeb@gac.canonical.com>
Message-ID: <157614038263.7161.13148492647158962509.launchpad@soybean.canonical.com>

** Changed in: bluez (Ubuntu)
       Status: In Progress => Won't Fix

** Changed in: bluez (Ubuntu)
       Status: Won't Fix => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854689

Title:
  BlueZ 5.52 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  BlueZ 5.52 release:
  http://www.bluez.org/release-of-bluez-5-52/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+subscriptions


From 1810154 at bugs.launchpad.net  Thu Dec 12 12:53:21 2019
From: 1810154 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 12 Dec 2019 12:53:21 -0000
Subject: [Bug 1810154] [NEW] ply_boot_client_process_incoming_replies:
 Assertion `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157615520151.4008.10391249090247074396.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Sebastien Bacher (seb128):

ubuntu cosmic
plymouth 0.9.3-1ubuntu10
initramfs-tools 0.131ubuntu15

I'm trying to get a password prompt working in the initramfs via
plymouth, but I get an assertion error.

This is the sample command I'm running:
plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

And this is the output I get:
[./plymouth.c:463]                           on_password_request:Password request
[ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
[ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
[./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
[ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
[ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
[ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
[ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
Aborted


plymouth --ping returns 0. It doesn't matter which --command I try.

** Affects: plymouth (Ubuntu)
     Importance: Medium
         Status: Confirmed


** Tags: patch
-- 
ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed
https://bugs.launchpad.net/bugs/1810154
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From seb128 at ubuntu.com  Thu Dec 12 12:53:27 2019
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Thu, 12 Dec 2019 12:53:27 -0000
Subject: [Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion
 `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157615520818.6663.2821659210855570402.launchpad@soybean.canonical.com>

** Changed in: plymouth (Ubuntu)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  
  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From 1856084 at bugs.launchpad.net  Thu Dec 12 20:26:00 2019
From: 1856084 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 12 Dec 2019 20:26:00 -0000
Subject: [Bug 1856084] [NEW] Livelock between ZFS evict and writeback threads
References: <157609492769.4570.18057029759074540502.malonedeb@chaenomeles.canonical.com>
Message-ID: <157618236086.7836.5006549052614766533.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

Livelock between ZFS evict and writeback threads

[Impact]
ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

[Description]
For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows:

[72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[72742.070429] mysqld          D    0  5713   2881 0x00000320
[72742.073220] Call Trace:
[72742.075305]  __schedule+0x24e/0x880
[72742.090436]  schedule+0x2c/0x80
[72742.090438]  schedule_preempt_disabled+0xe/0x10
[72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
[72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
[72742.090555]  __mutex_lock_slowpath+0x13/0x20
[72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
[72742.132266]  mutex_lock+0x2f/0x40
[72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
[72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
[72742.152622]  ? mutex_lock+0x12/0x40
[72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
[72742.171450]  zil_commit+0xde/0x150 [zfs]
[72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
[72742.175044]  zpl_fsync+0x80/0x110 [zfs]
[72742.191690]  vfs_fsync_range+0x51/0xb0
[72742.193876]  do_fsync+0x3d/0x70
[72742.195126]  SyS_fsync+0x10/0x20
[72742.211059]  do_syscall_64+0x73/0x130
[72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

It's possible to hit this issue due to a race between the ZFS evict and
writeback threads. If the z_iput task is trying to evict a znode that's
currently sitting in the writeback thread, both will "livelock" each
other and stall the ZIO pipeline, causing other ZFS operations (such as
zil_commit) to hang indefinitely.

This has been documented and fixed upstream in PR#9583 [0]. We need to
pull two fixes from upstream: the first one fixes the zfs_zget() issue
in the writeback thread, while the second fixes a regression on
O_TMPFILE descriptors caused by the first one.

Upstream patches:
 - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
 - Check for unlinked znodes after igrab() (0c46813805f4)

[Test Case]
Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads.

[Regression Potential]
These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low.
Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly.

[0] https://github.com/zfsonlinux/zfs/pull/9583
[1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
[2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

** Affects: zfs-linux (Ubuntu)
     Importance: Medium
     Assignee: Heitor Alves de Siqueira (halves)
         Status: Confirmed

** Affects: zfs-linux (Ubuntu Bionic)
     Importance: Undecided
     Assignee: Heitor Alves de Siqueira (halves)
         Status: Confirmed

** Affects: zfs-linux (Ubuntu Disco)
     Importance: Undecided
     Assignee: Heitor Alves de Siqueira (halves)
         Status: Confirmed

** Affects: zfs-linux (Ubuntu Eoan)
     Importance: Undecided
     Assignee: Heitor Alves de Siqueira (halves)
         Status: Confirmed

** Affects: zfs-linux (Ubuntu Focal)
     Importance: Medium
     Assignee: Heitor Alves de Siqueira (halves)
         Status: Confirmed

** Affects: zfs-linux (Debian)
     Importance: Unknown
         Status: Unknown


** Tags: patch sts sts-sponsor
-- 
Livelock between ZFS evict and writeback threads
https://bugs.launchpad.net/bugs/1856084
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1856084 at bugs.launchpad.net  Thu Dec 12 20:26:01 2019
From: 1856084 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Thu, 12 Dec 2019 20:26:01 -0000
Subject: [Bug 1856084] Re: Livelock between ZFS evict and writeback threads
References: <157609492769.4570.18057029759074540502.malonedeb@chaenomeles.canonical.com>
Message-ID: <157618236138.19188.11270381662348509783.malone@wampee.canonical.com>

The attachment "lp1856084-bionic.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856084

Title:
  Livelock between ZFS evict and writeback threads

Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Disco:
  Confirmed
Status in zfs-linux source package in Eoan:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux package in Debian:
  Unknown

Bug description:
  Livelock between ZFS evict and writeback threads

  [Impact]
  ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows:

  [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  [72742.070429] mysqld          D    0  5713   2881 0x00000320
  [72742.073220] Call Trace:
  [72742.075305]  __schedule+0x24e/0x880
  [72742.090436]  schedule+0x2c/0x80
  [72742.090438]  schedule_preempt_disabled+0xe/0x10
  [72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
  [72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
  [72742.090555]  __mutex_lock_slowpath+0x13/0x20
  [72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
  [72742.132266]  mutex_lock+0x2f/0x40
  [72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
  [72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
  [72742.152622]  ? mutex_lock+0x12/0x40
  [72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
  [72742.171450]  zil_commit+0xde/0x150 [zfs]
  [72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
  [72742.175044]  zpl_fsync+0x80/0x110 [zfs]
  [72742.191690]  vfs_fsync_range+0x51/0xb0
  [72742.193876]  do_fsync+0x3d/0x70
  [72742.195126]  SyS_fsync+0x10/0x20
  [72742.211059]  do_syscall_64+0x73/0x130
  [72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  It's possible to hit this issue due to a race between the ZFS evict
  and writeback threads. If the z_iput task is trying to evict a znode
  that's currently sitting in the writeback thread, both will "livelock"
  each other and stall the ZIO pipeline, causing other ZFS operations
  (such as zil_commit) to hang indefinitely.

  This has been documented and fixed upstream in PR#9583 [0]. We need to
  pull two fixes from upstream: the first one fixes the zfs_zget() issue
  in the writeback thread, while the second fixes a regression on
  O_TMPFILE descriptors caused by the first one.

  Upstream patches:
   - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
   - Check for unlinked znodes after igrab() (0c46813805f4)

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads.

  [Regression Potential]
  These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low.
  Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly.

  [0] https://github.com/zfsonlinux/zfs/pull/9583
  [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
  [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+subscriptions


From 1800566 at bugs.launchpad.net  Thu Dec 12 20:53:47 2019
From: 1800566 at bugs.launchpad.net (Guilherme G. Piccoli)
Date: Thu, 12 Dec 2019 20:53:47 -0000
Subject: [Bug 1800566] Re: Make reset_devices parameter default for kdump and
 decouple kdump systemd service from the KDUMP_CMDLINE_APPEND
References: <154085493301.19676.9585082283877136471.malonedeb@gac.canonical.com>
Message-ID: <157618402818.7059.22832140326764455.launchpad@soybean.canonical.com>

** Also affects: makedumpfile (Ubuntu Focal)
   Importance: High
     Assignee: Guilherme G. Piccoli (gpiccoli)
       Status: In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1800566

Title:
  Make reset_devices parameter default for kdump and decouple kdump
  systemd service from the KDUMP_CMDLINE_APPEND

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Trusty:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Confirmed
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]

  * Kdump does not configure by default the crash kernel to perform a
  device reset by default, by passing the "reset_devices" parameter.
  Also, the systemd service "kdump-tools-dump" is tightly-coupled with
  KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion.

  * Kernel has the "reset_devices" parameter that drivers can opt-in,
  and perform special activity in case this parameter is parsed from
  command-line. For example, in kdump kernels it hints the drivers that
  they are booting from a non-healthy condition and needs to issue some
  form of reset to the adapter, like clearing DMA mapping in their
  firmware for example. Users currently (kernel v5.2) are: aacraid,
  hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

  * The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only 
  reasonable case for removing it is to debug kdump itself.

  
  [Test Case]

  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'reset_devices' parameter:

  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz

  Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit
  =kdump-tools.service" to be removed.

  
  [Regression Potential]

  The regression potential is low, since it doesn't need any changes in
  makedumpfile code and we're only adding a parameter on the crash
  kernel command-line. The risks are related with bad behavior with the
  kernel when using "reset_devices", like if the driver has bugs in this
  path. It's considered safer to have the option (and this way prevent
  problems for booting a unhealthy kernel with potential stuck DMAs in
  the devices) than not having it.

  Regarding the other change, about the systemd service, it'll only
  affect users the are debugging kdump itself and it has no known
  regression potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions


From 1800566 at bugs.launchpad.net  Thu Dec 12 21:01:47 2019
From: 1800566 at bugs.launchpad.net (Guilherme G. Piccoli)
Date: Thu, 12 Dec 2019 21:01:47 -0000
Subject: [Bug 1800566] Re: Make reset_devices parameter default for kdump and
 decouple kdump systemd service from the KDUMP_CMDLINE_APPEND
References: <154085493301.19676.9585082283877136471.malonedeb@gac.canonical.com>
Message-ID: <157618450993.6370.8628387437183774987.launchpad@gac.canonical.com>

** Changed in: makedumpfile (Ubuntu Eoan)
       Status: In Progress => Confirmed

** Changed in: makedumpfile (Ubuntu Focal)
       Status: In Progress => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1800566

Title:
  Make reset_devices parameter default for kdump and decouple kdump
  systemd service from the KDUMP_CMDLINE_APPEND

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Confirmed
Status in makedumpfile source package in Eoan:
  Confirmed
Status in makedumpfile source package in Focal:
  Confirmed

Bug description:
  [Impact]

  * Kdump does not configure by default the crash kernel to perform a
  device reset by default, by passing the "reset_devices" parameter.
  Also, the systemd service "kdump-tools-dump" is tightly-coupled with
  KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion.

  * Kernel has the "reset_devices" parameter that drivers can opt-in,
  and perform special activity in case this parameter is parsed from
  command-line. For example, in kdump kernels it hints the drivers that
  they are booting from a non-healthy condition and needs to issue some
  form of reset to the adapter, like clearing DMA mapping in their
  firmware for example. Users currently (kernel v5.2) are: aacraid,
  hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

  * The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only 
  reasonable case for removing it is to debug kdump itself.

  
  [Test Case]

  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'reset_devices' parameter:

  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz

  Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit
  =kdump-tools.service" to be removed.

  
  [Regression Potential]

  The regression potential is low, since it doesn't need any changes in
  makedumpfile code and we're only adding a parameter on the crash
  kernel command-line. The risks are related with bad behavior with the
  kernel when using "reset_devices", like if the driver has bugs in this
  path. It's considered safer to have the option (and this way prevent
  problems for booting a unhealthy kernel with potential stuck DMAs in
  the devices) than not having it.

  Regarding the other change, about the systemd service, it'll only
  affect users the are debugging kdump itself and it has no known
  regression potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions


From 1810154 at bugs.launchpad.net  Thu Dec 12 23:20:21 2019
From: 1810154 at bugs.launchpad.net (Witold Krecicki)
Date: Thu, 12 Dec 2019 23:20:21 -0000
Subject: [Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion
 `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157619282187.6430.2306386633989952719.malone@soybean.canonical.com>

To clarify, as those questions were asked on IRC:
1. I'm the author of the patch.
2. The bug exists only in Ubuntu, not in upstream version of plymouth - it's caused by the changes included in "misc-changes.patch" (that I'm not touching with at 30 foot pole).

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  
  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From 1856084 at bugs.launchpad.net  Fri Dec 13 14:30:46 2019
From: 1856084 at bugs.launchpad.net (Heitor Alves de Siqueira)
Date: Fri, 13 Dec 2019 14:30:46 -0000
Subject: [Bug 1856084] Re: Livelock between ZFS evict and writeback threads
References: <157609492769.4570.18057029759074540502.malonedeb@chaenomeles.canonical.com>
Message-ID: <157624744671.6190.7006518357252145566.malone@gac.canonical.com>

** Patch added: "lp1856084-focal.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+attachment/5312221/+files/lp1856084-focal.debdiff

** Tags removed: sts-sponsor

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856084

Title:
  Livelock between ZFS evict and writeback threads

Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Disco:
  Confirmed
Status in zfs-linux source package in Eoan:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux package in Debian:
  Unknown

Bug description:
  Livelock between ZFS evict and writeback threads

  [Impact]
  ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows:

  [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  [72742.070429] mysqld          D    0  5713   2881 0x00000320
  [72742.073220] Call Trace:
  [72742.075305]  __schedule+0x24e/0x880
  [72742.090436]  schedule+0x2c/0x80
  [72742.090438]  schedule_preempt_disabled+0xe/0x10
  [72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
  [72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
  [72742.090555]  __mutex_lock_slowpath+0x13/0x20
  [72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
  [72742.132266]  mutex_lock+0x2f/0x40
  [72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
  [72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
  [72742.152622]  ? mutex_lock+0x12/0x40
  [72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
  [72742.171450]  zil_commit+0xde/0x150 [zfs]
  [72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
  [72742.175044]  zpl_fsync+0x80/0x110 [zfs]
  [72742.191690]  vfs_fsync_range+0x51/0xb0
  [72742.193876]  do_fsync+0x3d/0x70
  [72742.195126]  SyS_fsync+0x10/0x20
  [72742.211059]  do_syscall_64+0x73/0x130
  [72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  It's possible to hit this issue due to a race between the ZFS evict
  and writeback threads. If the z_iput task is trying to evict a znode
  that's currently sitting in the writeback thread, both will "livelock"
  each other and stall the ZIO pipeline, causing other ZFS operations
  (such as zil_commit) to hang indefinitely.

  This has been documented and fixed upstream in PR#9583 [0]. We need to
  pull two fixes from upstream: the first one fixes the zfs_zget() issue
  in the writeback thread, while the second fixes a regression on
  O_TMPFILE descriptors caused by the first one.

  Upstream patches:
   - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
   - Check for unlinked znodes after igrab() (0c46813805f4)

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads.

  [Regression Potential]
  These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low.
  Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly.

  [0] https://github.com/zfsonlinux/zfs/pull/9583
  [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
  [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+subscriptions


From 1856084 at bugs.launchpad.net  Fri Dec 13 17:58:32 2019
From: 1856084 at bugs.launchpad.net (Colin Ian King)
Date: Fri, 13 Dec 2019 17:58:32 -0000
Subject: [Bug 1856084] Re: Livelock between ZFS evict and writeback threads
References: <157609492769.4570.18057029759074540502.malonedeb@chaenomeles.canonical.com>
Message-ID: <157625991277.22064.8019272125571906426.malone@gac.canonical.com>

I've checked that the zfs kernel driver builds and it passes the ZFS
regression tests. Patches look good, so I've uploaded these packages.

** Changed in: zfs-linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Eoan)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856084

Title:
  Livelock between ZFS evict and writeback threads

Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Disco:
  Confirmed
Status in zfs-linux source package in Eoan:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux package in Debian:
  Unknown

Bug description:
  Livelock between ZFS evict and writeback threads

  [Impact]
  ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows:

  [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  [72742.070429] mysqld          D    0  5713   2881 0x00000320
  [72742.073220] Call Trace:
  [72742.075305]  __schedule+0x24e/0x880
  [72742.090436]  schedule+0x2c/0x80
  [72742.090438]  schedule_preempt_disabled+0xe/0x10
  [72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
  [72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
  [72742.090555]  __mutex_lock_slowpath+0x13/0x20
  [72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
  [72742.132266]  mutex_lock+0x2f/0x40
  [72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
  [72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
  [72742.152622]  ? mutex_lock+0x12/0x40
  [72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
  [72742.171450]  zil_commit+0xde/0x150 [zfs]
  [72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
  [72742.175044]  zpl_fsync+0x80/0x110 [zfs]
  [72742.191690]  vfs_fsync_range+0x51/0xb0
  [72742.193876]  do_fsync+0x3d/0x70
  [72742.195126]  SyS_fsync+0x10/0x20
  [72742.211059]  do_syscall_64+0x73/0x130
  [72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  It's possible to hit this issue due to a race between the ZFS evict
  and writeback threads. If the z_iput task is trying to evict a znode
  that's currently sitting in the writeback thread, both will "livelock"
  each other and stall the ZIO pipeline, causing other ZFS operations
  (such as zil_commit) to hang indefinitely.

  This has been documented and fixed upstream in PR#9583 [0]. We need to
  pull two fixes from upstream: the first one fixes the zfs_zget() issue
  in the writeback thread, while the second fixes a regression on
  O_TMPFILE descriptors caused by the first one.

  Upstream patches:
   - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
   - Check for unlinked znodes after igrab() (0c46813805f4)

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads.

  [Regression Potential]
  These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low.
  Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly.

  [0] https://github.com/zfsonlinux/zfs/pull/9583
  [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
  [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+subscriptions


From steve.langasek at canonical.com  Fri Dec 13 19:55:14 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 13 Dec 2019 19:55:14 -0000
Subject: [Bug 1820768] Re: [SRU] support new cab and new docking firmware
 upgrade in fwupd 1.2.10
References: <155295081031.32044.4189733535399473960.malonedeb@soybean.canonical.com>
Message-ID: <157626691674.5424.5180386033836814172.launchpad@chaenomeles.canonical.com>

** Description changed:

  * Impact
  
  Bios vendor is pushing to put the new design into cab file, and also new
  docking DW19 needs the new fwupd to support it.
  
  That needs new fwupd to support.
  
  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.
  
  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.
  
  * Test case
  
- I
+ A.
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show
- II.
+ 
+ B.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.
- III.
+ 
+ C.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one
+ 
+ D.
+ 1. Install an 18.04 Ubuntu Desktop system.
+ 2. Enable bionic-proposed.
+ 3. Run update-manager.
+ 4. Ensure that the fwupd and fwupd-signed packages are installed without error.
  
  * Regression potential
  
  Since the upstream maintainer is back up this upgrade, and he also works
  in a major computer vendor and works closely with the BIOS team, it
  should be fairly low risk.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Triaged
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  New
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  A.
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show

  B.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.

  C.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  D.
  1. Install an 18.04 Ubuntu Desktop system.
  2. Enable bionic-proposed.
  3. Run update-manager.
  4. Ensure that the fwupd and fwupd-signed packages are installed without error.

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions


From steve.langasek at canonical.com  Fri Dec 13 20:08:52 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 13 Dec 2019 20:08:52 -0000
Subject: [Bug 1820768] Re: [SRU] support new cab and new docking firmware
 upgrade in fwupd 1.2.10
References: <155295081031.32044.4189733535399473960.malonedeb@soybean.canonical.com>
Message-ID: <157626773234.6994.3731799469276450222.malone@soybean.canonical.com>

I have added an explicit test case for the packaging changes, since that
is a large part of why this SRU has taken as long to sort out - we need
to ensure that the package upgrades work correctly.

This test case uses update-manager, and NOT apt-get, because the
behavior is different between the two regarding the removal of packages.
I think the current upload will actually FAIL verification, because
there is a Breaks: from the new fwupdate to fwupdate-signed, and
fwupdate-signed is also installed by default.  I expect update-manager
to refuse to upgrade fwupdate in order to avoid removing fwupdate-
signed.

There is also a bug in the packaging, which is that fwupdate has an
unversioned Breaks: against fwupdate-signed; if this is required, it
should be an unversioned Conflicts: instead.  However, per the previous
comment, I think we probably need to do something else here (such as
making fwupdate-signed also be a dummy package built from fwupdate
source which depends on fwupd-signed, or dropping the Breaks: entirely
and ignoring the fact that fwupdate-signed is kept on disk, if that is
appropriate).

Finally, I see that fwupd is introducing a Recommends: on bolt,
tpm2-tools, and tpm2-abrmd in addition to fwupd-signed.  This is not
allowed; tpm2-abrmd and tpm2-tools are in universe in bionic.  Also,
while bolt is in main, in bionic it is only in the ubuntu-desktop task
(via a Recommends: from gnome-shell), whereas fwupdate is a recommends
of all of the desktop metapackages.  We cannot promote bolt to be pulled
into all of the desktop flavor images in SRU without discussion with the
flavor teams.

I will reupload fwupd to drop these added Recommends.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Triaged
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  New
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  A.
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show

  B.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.

  C.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  D.
  1. Install an 18.04 Ubuntu Desktop system.
  2. Enable bionic-proposed.
  3. Run update-manager.
  4. Ensure that the fwupd and fwupd-signed packages are installed without error.

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions


From steve.langasek at canonical.com  Fri Dec 13 20:12:50 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 13 Dec 2019 20:12:50 -0000
Subject: [Bug 1820768] Re: [SRU] support new cab and new docking firmware
 upgrade in fwupd 1.2.10
References: <155295081031.32044.4189733535399473960.malonedeb@soybean.canonical.com>
Message-ID: <157626797072.5481.10501926454197294136.malone@chaenomeles.canonical.com>

Sorry, I was looking at a wrong path in the diff and it seems the tpm2-*
Recommends: are only present in contrib/debian/control.in, not in
debian/control.in.  So that was done correctly and doesn't need
changing.  I'll still be dropping the Recommends: on bolt however.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Triaged
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  New
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  A.
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show

  B.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.

  C.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  D.
  1. Install an 18.04 Ubuntu Desktop system.
  2. Enable bionic-proposed.
  3. Run update-manager.
  4. Ensure that the fwupd and fwupd-signed packages are installed without error.

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions


From steve.langasek at canonical.com  Fri Dec 13 20:16:00 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 13 Dec 2019 20:16:00 -0000
Subject: [Bug 1820768] Proposed package upload rejected
References: <155295081031.32044.4189733535399473960.malonedeb@soybean.canonical.com>
Message-ID: <157626816055.8106.17991488987649293174.malone@soybean.canonical.com>

An upload of fwupd to bionic-proposed has been rejected from the upload
queue for the following reason: "reuploading without additional bolt
recommends".

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Triaged
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  New
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  A.
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show

  B.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.

  C.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  D.
  1. Install an 18.04 Ubuntu Desktop system.
  2. Enable bionic-proposed.
  3. Run update-manager.
  4. Ensure that the fwupd and fwupd-signed packages are installed without error.

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions


From steve.langasek at canonical.com  Fri Dec 13 20:21:07 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 13 Dec 2019 20:21:07 -0000
Subject: [Bug 1820768] Proposed package upload rejected
References: <155295081031.32044.4189733535399473960.malonedeb@soybean.canonical.com>
Message-ID: <157626846752.18558.4164721968097409116.malone@wampee.canonical.com>

An upload of fwupd to bionic-proposed has been rejected from the upload
queue for the following reason: "wtf g".

** Changed in: fwupd (Ubuntu Bionic)
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Fix Committed
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  New
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  A.
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show

  B.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.

  C.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  D.
  1. Install an 18.04 Ubuntu Desktop system.
  2. Enable bionic-proposed.
  3. Run update-manager.
  4. Ensure that the fwupd and fwupd-signed packages are installed without error.

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions


From steve.langasek at canonical.com  Fri Dec 13 20:26:09 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 13 Dec 2019 20:26:09 -0000
Subject: [Bug 1820768] Please test proposed package
References: <155295081031.32044.4189733535399473960.malonedeb@soybean.canonical.com>
Message-ID: <157626876959.22755.14049483040101093294.malone@gac.canonical.com>

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/fwupd/1.2.10-1ubuntu2~ubuntu18.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  Triaged
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Fix Committed
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  New
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  A.
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show

  B.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.

  C.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  D.
  1. Install an 18.04 Ubuntu Desktop system.
  2. Enable bionic-proposed.
  3. Run update-manager.
  4. Ensure that the fwupd and fwupd-signed packages are installed without error.

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions


From 1856084 at bugs.launchpad.net  Fri Dec 13 21:34:16 2019
From: 1856084 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 13 Dec 2019 21:34:16 -0000
Subject: [Bug 1856084] Re: Livelock between ZFS evict and writeback threads
References: <157609492769.4570.18057029759074540502.malonedeb@chaenomeles.canonical.com>
Message-ID: <157627285869.8950.10341217996207749238.malone@ackee.canonical.com>

This bug was fixed in the package zfs-linux - 0.8.2-3ubuntu3

---------------
zfs-linux (0.8.2-3ubuntu3) focal; urgency=medium

  * Fix livelock between ZFS evict and writeback threads (LP: #1856084)
    - Upstream ZFS fix 41e1aa2a06f8 ("Break out of zfs_zget early if unlinked
      znode")
    - Upstream ZFS fix 0c46813805f4 ("Check for unlinked znodes after
      igrab()")

 -- Heitor Alves de Siqueira <halves at canonical.com>  Fri, 13 Dec 2019
11:27:39 -0300

** Changed in: zfs-linux (Ubuntu Focal)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856084

Title:
  Livelock between ZFS evict and writeback threads

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Disco:
  Confirmed
Status in zfs-linux source package in Eoan:
  Confirmed
Status in zfs-linux source package in Focal:
  Fix Released
Status in zfs-linux package in Debian:
  Unknown

Bug description:
  Livelock between ZFS evict and writeback threads

  [Impact]
  ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows:

  [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  [72742.070429] mysqld          D    0  5713   2881 0x00000320
  [72742.073220] Call Trace:
  [72742.075305]  __schedule+0x24e/0x880
  [72742.090436]  schedule+0x2c/0x80
  [72742.090438]  schedule_preempt_disabled+0xe/0x10
  [72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
  [72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
  [72742.090555]  __mutex_lock_slowpath+0x13/0x20
  [72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
  [72742.132266]  mutex_lock+0x2f/0x40
  [72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
  [72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
  [72742.152622]  ? mutex_lock+0x12/0x40
  [72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
  [72742.171450]  zil_commit+0xde/0x150 [zfs]
  [72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
  [72742.175044]  zpl_fsync+0x80/0x110 [zfs]
  [72742.191690]  vfs_fsync_range+0x51/0xb0
  [72742.193876]  do_fsync+0x3d/0x70
  [72742.195126]  SyS_fsync+0x10/0x20
  [72742.211059]  do_syscall_64+0x73/0x130
  [72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  It's possible to hit this issue due to a race between the ZFS evict
  and writeback threads. If the z_iput task is trying to evict a znode
  that's currently sitting in the writeback thread, both will "livelock"
  each other and stall the ZIO pipeline, causing other ZFS operations
  (such as zil_commit) to hang indefinitely.

  This has been documented and fixed upstream in PR#9583 [0]. We need to
  pull two fixes from upstream: the first one fixes the zfs_zget() issue
  in the writeback thread, while the second fixes a regression on
  O_TMPFILE descriptors caused by the first one.

  Upstream patches:
   - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
   - Check for unlinked znodes after igrab() (0c46813805f4)

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads.

  [Regression Potential]
  These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low.
  Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly.

  [0] https://github.com/zfsonlinux/zfs/pull/9583
  [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
  [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+subscriptions


From steve.langasek at canonical.com  Sat Dec 14 01:26:37 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Sat, 14 Dec 2019 01:26:37 -0000
Subject: [Bug 1856084] Re: Livelock between ZFS evict and writeback threads
References: <157609492769.4570.18057029759074540502.malonedeb@chaenomeles.canonical.com>
Message-ID: <157628679798.4518.11565569214209802929.malone@chaenomeles.canonical.com>

Hello Heitor, or anyone else affected,

Accepted zfs-linux into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.1-1ubuntu14.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: zfs-linux (Ubuntu Eoan)
       Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856084

Title:
  Livelock between ZFS evict and writeback threads

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Disco:
  Confirmed
Status in zfs-linux source package in Eoan:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Released
Status in zfs-linux package in Debian:
  Unknown

Bug description:
  Livelock between ZFS evict and writeback threads

  [Impact]
  ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows:

  [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  [72742.070429] mysqld          D    0  5713   2881 0x00000320
  [72742.073220] Call Trace:
  [72742.075305]  __schedule+0x24e/0x880
  [72742.090436]  schedule+0x2c/0x80
  [72742.090438]  schedule_preempt_disabled+0xe/0x10
  [72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
  [72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
  [72742.090555]  __mutex_lock_slowpath+0x13/0x20
  [72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
  [72742.132266]  mutex_lock+0x2f/0x40
  [72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
  [72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
  [72742.152622]  ? mutex_lock+0x12/0x40
  [72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
  [72742.171450]  zil_commit+0xde/0x150 [zfs]
  [72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
  [72742.175044]  zpl_fsync+0x80/0x110 [zfs]
  [72742.191690]  vfs_fsync_range+0x51/0xb0
  [72742.193876]  do_fsync+0x3d/0x70
  [72742.195126]  SyS_fsync+0x10/0x20
  [72742.211059]  do_syscall_64+0x73/0x130
  [72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  It's possible to hit this issue due to a race between the ZFS evict
  and writeback threads. If the z_iput task is trying to evict a znode
  that's currently sitting in the writeback thread, both will "livelock"
  each other and stall the ZIO pipeline, causing other ZFS operations
  (such as zil_commit) to hang indefinitely.

  This has been documented and fixed upstream in PR#9583 [0]. We need to
  pull two fixes from upstream: the first one fixes the zfs_zget() issue
  in the writeback thread, while the second fixes a regression on
  O_TMPFILE descriptors caused by the first one.

  Upstream patches:
   - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
   - Check for unlinked znodes after igrab() (0c46813805f4)

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads.

  [Regression Potential]
  These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low.
  Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly.

  [0] https://github.com/zfsonlinux/zfs/pull/9583
  [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
  [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+subscriptions


From steve.langasek at canonical.com  Sat Dec 14 19:01:57 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Sat, 14 Dec 2019 19:01:57 -0000
Subject: [Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion
 `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157635011855.4676.13022956990650979228.launchpad@chaenomeles.canonical.com>

** Description changed:

+ [SRU Justification]
+ An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords.  While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot.
+ 
+ [Test case]
+ 1. Change to VT3 on your system (so that you are not under a graphical login session) and log in.
+ 2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3
+ 3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console.
+ 4. Install the plymouth package from eoan-proposed.
+ 5. Repeat step 2.
+ 6. Observe that you are shown a password prompt.
+ 7. Type something into the field and hit enter.
+ 8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages.
+ 
+ [Regression potential]
+ This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch.  This fixes a crash and has minimal risk of regression.
+ 
+ 
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15
  
  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.
  
  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"
  
  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted
  
- 
  plymouth --ping returns 0. It doesn't matter which --command I try.

** Changed in: plymouth (Ubuntu)
     Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  [SRU Justification]
  An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords.  While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot.

  [Test case]
  1. Change to VT3 on your system (so that you are not under a graphical login session) and log in.
  2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3
  3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console.
  4. Install the plymouth package from eoan-proposed.
  5. Repeat step 2.
  6. Observe that you are shown a password prompt.
  7. Type something into the field and hit enter.
  8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages.

  [Regression potential]
  This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch.  This fixes a crash and has minimal risk of regression.

  
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From 1810154 at bugs.launchpad.net  Sat Dec 14 22:33:20 2019
From: 1810154 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 14 Dec 2019 22:33:20 -0000
Subject: [Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion
 `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157636280299.8950.12510586351535715125.malone@ackee.canonical.com>

This bug was fixed in the package plymouth - 0.9.4git20190712-0ubuntu5

---------------
plymouth (0.9.4git20190712-0ubuntu5) focal; urgency=medium

  * debian/patches/misc-changes.patch: fix an Ubuntu-specific bug in
    handling plymouth ask-for-password with a --command option that results
    in a crash, breaking disk unlocking with zfs.  Thank to Witold Krecicki
    for the fix.  LP: #1810154.

 -- Steve Langasek <steve.langasek at ubuntu.com>  Sat, 14 Dec 2019
10:43:21 -0800

** Changed in: plymouth (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Fix Released

Bug description:
  [SRU Justification]
  An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords.  While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot.

  [Test case]
  1. Change to VT3 on your system (so that you are not under a graphical login session) and log in.
  2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3
  3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console.
  4. Install the plymouth package from eoan-proposed.
  5. Repeat step 2.
  6. Observe that you are shown a password prompt.
  7. Type something into the field and hit enter.
  8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages.

  [Regression potential]
  This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch.  This fixes a crash and has minimal risk of regression.

  
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From 1810154 at bugs.launchpad.net  Mon Dec 16 11:22:59 2019
From: 1810154 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 16 Dec 2019 11:22:59 -0000
Subject: [Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion
 `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157649537939.22432.16886884929035620433.malone@gac.canonical.com>

Hello Andreas, or anyone else affected,

Accepted plymouth into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/plymouth/0.9.4git20190712-0ubuntu4.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: plymouth (Ubuntu Eoan)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Fix Released
Status in plymouth source package in Eoan:
  Fix Committed

Bug description:
  [SRU Justification]
  An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords.  While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot.

  [Test case]
  1. Change to VT3 on your system (so that you are not under a graphical login session) and log in.
  2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3
  3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console.
  4. Install the plymouth package from eoan-proposed.
  5. Repeat step 2.
  6. Observe that you are shown a password prompt.
  7. Type something into the field and hit enter.
  8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages.

  [Regression potential]
  This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch.  This fixes a crash and has minimal risk of regression.

  
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From 1856574 at bugs.launchpad.net  Tue Dec 17 16:21:48 2019
From: 1856574 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 17 Dec 2019 16:21:48 -0000
Subject: [Bug 1856574] [NEW] removal of various autopilot packages
References: <157650561253.19251.3333137627024153118.malonedeb@wampee.canonical.com>
Message-ID: <157659970853.5393.6252064754640698692.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

python-fixtures and python-testtools are not built anymore in focal, but
still referenced by some Ubuntu-only packages.  We need to at least
remove autopilot-legacy if we don't want to re-introduce those package,
and modify autopilot-gtk to build witout the autopilot-legacy b-d.

** Affects: autopilot-gtk (Ubuntu)
     Importance: Medium
     Assignee: Jean-Baptiste Lallement (jibel)
         Status: Fix Committed

** Affects: autopilot-legacy (Ubuntu)
     Importance: Undecided
         Status: New

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

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


** Tags: patch
-- 
removal of various autopilot packages
https://bugs.launchpad.net/bugs/1856574
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1856574 at bugs.launchpad.net  Tue Dec 17 16:21:48 2019
From: 1856574 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Tue, 17 Dec 2019 16:21:48 -0000
Subject: [Bug 1856574] Re: removal of various autopilot packages
References: <157650561253.19251.3333137627024153118.malonedeb@wampee.canonical.com>
Message-ID: <157659970885.3198.11556277290921748173.malone@soybean.canonical.com>

The attachment "autopilot-gtk_1.4_1.6.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856574

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Committed
Status in autopilot-legacy package in Ubuntu:
  New
Status in python-fixtures package in Ubuntu:
  New
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions


From brian at ubuntu.com  Tue Dec 17 20:35:47 2019
From: brian at ubuntu.com (Brian Murray)
Date: Tue, 17 Dec 2019 20:35:47 -0000
Subject: [Bug 1810154] [plymouth/eoan] possible regression found
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157661494794.3464.17928826564114395061.malone@soybean.canonical.com>

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of plymouth from eoan-proposed
was performed and bug 1856712 was found.  Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed-
eoan" tag from this bug report and add the tag "bot-stop-nagging" to bug
1856712 (not this bug). Thanks!

** Tags added: verification-failed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Fix Released
Status in plymouth source package in Eoan:
  Fix Committed

Bug description:
  [SRU Justification]
  An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords.  While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot.

  [Test case]
  1. Change to VT3 on your system (so that you are not under a graphical login session) and log in.
  2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3
  3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console.
  4. Install the plymouth package from eoan-proposed.
  5. Repeat step 2.
  6. Observe that you are shown a password prompt.
  7. Type something into the field and hit enter.
  8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages.

  [Regression potential]
  This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch.  This fixes a crash and has minimal risk of regression.

  
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From daniel.van.vugt at canonical.com  Wed Dec 18 05:23:48 2019
From: daniel.van.vugt at canonical.com (Daniel van Vugt)
Date: Wed, 18 Dec 2019 05:23:48 -0000
Subject: [Bug 1855893] Re: Properly let PCM leave suspended state when
 hardware doesn't support PCM resume
References: <157598921477.7721.14604770826784008639.malonedeb@soybean.canonical.com>
Message-ID: <157664662816.14338.769448768609619706.malone@wampee.canonical.com>

I just noticed the above patch. Now added to git:

https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu-
bionic

Please remember to put proposed changes in git so everyone is working
with the same source.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855893

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions


From daniel.van.vugt at canonical.com  Wed Dec 18 06:36:30 2019
From: daniel.van.vugt at canonical.com (Daniel van Vugt)
Date: Wed, 18 Dec 2019 06:36:30 -0000
Subject: [Bug 1855893] Re: Properly let PCM leave suspended state when
 hardware doesn't support PCM resume
References: <157598921477.7721.14604770826784008639.malonedeb@soybean.canonical.com>
Message-ID: <157665099079.3101.1102536669179645440.malone@soybean.canonical.com>

Also please provide links to upstream changes/bugs in the patch, and/or
here.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855893

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions


From 1855594 at bugs.launchpad.net  Wed Dec 18 06:39:12 2019
From: 1855594 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Dec 2019 06:39:12 -0000
Subject: [Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from
 Debian unstable (main)
References: <157581630122.6153.649495934122601180.malonedeb@gac.canonical.com>
Message-ID: <157665115251.15260.8521807506044898052.malone@wampee.canonical.com>

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855594

Title:
  Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)

Status in chromium package in Ubuntu:
  Confirmed

Bug description:
  Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable
  (main)

  Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package.
  This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one.

  All changelog entries:

  chromium (78.0.3904.108-1) unstable; urgency=medium

    * New upstream security release.
      - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li
      - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li
    * Disable vaapi on armhf (closes: #944627).

   -- Michael Gilbert <mgilbert at debian.org>  Wed, 20 Nov 2019 23:46:06
  +0000

  chromium (78.0.3904.97-1) unstable; urgency=medium

    * New upstream security release.
    * Enable vaapi (closes: #940074).
    * Fix crash during profile manager shutdown.
    * Drop libglewmx-dev build dependency (closes: #941050).

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 09 Nov 2019 03:33:52
  +0000

  chromium (78.0.3904.87-1) unstable; urgency=medium

    * New upstream stable release.
      - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin
      - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong
      - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous
      - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin
      - CVE-2019-5874: External URIs may trigger other browsers. Reported by
        James Lee
      - CVE-2019-5875: URL bar spoof. Reported by Khalil
        Zhani
      - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong
      - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo
        Kim
      - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu
      - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang
      - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu
      - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu
      - CVE-2019-13662: CSP bypass. Reported by David Erceg
      - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang
      - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell
      - CVE-2019-13665: Multiple file download protection bypass. Reported by
        Jun Kokatsu
      - CVE-2019-13666: Side channel using storage size estimate. Reported by
        Tom Van Goethem
      - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by
        Khalil Zhani
      - CVE-2019-13668: Global window leak via console. Reported by David Erceg
      - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong
      - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr
      - CVE-2019-13673: Cross-origin information leak using devtools. Reported
        by David Erceg
      - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani
      - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported
        by Jun Kokatsu
      - CVE-2019-13676: Google URI shown for certificate warning. Reported by
        Wenxu Wu
      - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported
        by Jun Kokatsu
      - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing
      - CVE-2019-13679: User gesture needed for printing. Reported by Conrad
        Irwin
      - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs
        Alkemade
      - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg
      - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu
      - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg
      - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani
      - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon
      - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo
        Tiszka
      - CVE-2019-13691: Omnibox spoof. Reported by David Erceg
      - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu
      - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong
      - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin
      - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo
      - CVE-2019-13696: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-13697: Cross-origin size leak. Reported by Luan Herrera
      - CVE-2019-13699: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13700: Buffer overrun in Blink. Reported by Man Yue Mo
      - CVE-2019-13701: URL spoof in navigation. Reported by David Erceg
      - CVE-2019-13702: Privilege elevation in Installer. Reported by Phillip
        Langlois and Edward Torkington
      - CVE-2019-13703: URL bar spoofing. Reported by Khalil Zhani
      - CVE-2019-13704: CSP bypass. Reported by Jun Kokatsu
      - CVE-2019-13705: Extension permission bypass. Reported by Luan Herrera
      - CVE-2019-13706: Out-of-bounds read in PDFium. Reported by pdknsk
      - CVE-2019-13707: File storage disclosure. Reported by Andrea Palazzo
      - CVE-2019-13708: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13709: File download protection bypass. Reported by Zhong
        Zhaochen
      - CVE-2019-13710: File download protection bypass. Reported by
        bernardo.mrod
      - CVE-2019-13711: Cross-context information leak. Reported by David Erceg
      - CVE-2019-13713: Cross-origin data leak. Reported by David Erceg
      - CVE-2019-13714: CSS injection. Reported by Jun Kokatsu
      - CVE-2019-13715: Address bar spoofing. Reported by xisigr
      - CVE-2019-13716: Service worker state error. Reported by Barron Hagerman
      - CVE-2019-13717: Notification obscured. Reported by xisigr
      - CVE-2019-13718: IDN spoof. Reported by Khalil Zhani
      - CVE-2019-13719: Notification obscured. Reported by Khalil Zhani
      - CVE-2019-13720: Use-after-free in audio. Reported by Anton Ivanov and
        Alexey Kulaev
      - CVE-2019-13721: Use-after-free in PDFium. Reported by banananapenguin
    * Drop support for building with gcc 6 and gtk 2.

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 02 Nov 2019 22:30:42
  +0000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1855594/+subscriptions


From 1847570 at bugs.launchpad.net  Wed Dec 18 06:59:46 2019
From: 1847570 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Dec 2019 06:59:46 -0000
Subject: [Bug 1847570] [NEW] PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157665238717.14604.12250737332783799984.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Daniel van Vugt (vanvugt):

[Impact]

On my freshly installed eoan system I have two output devices:
- HDMI/DisplayPort 2 - GK208 ...
- Line Out - Family 17h ...

When I login into the system pulseaudio always select the "wrong"
one (HDMI) and I need to go to gnome-settings/Sound/Output Device
and switch to "line out". This applies to every login/logout not
just reboots.

[Test Case]

0. Plug in a monitor that supports HDMI audio (one that appears in your
Settings>Sound)

1. Log out and in again.

Verify the default audio device in Settings is still speakers or
headphones. Not the monitor's HDMI audio device.

[Regression Potential]

Low. The fix proposed just reverts to the same code used in PulseAudio
12 and earlier. It has also been released and verified on focal already.

[Workaround]

Comment out:

load-module module-switch-on-port-available
load-module module-switch-on-connect

from /etc/pulse/default.pa

** Affects: pulseaudio
     Importance: Unknown
         Status: New

** Affects: pulseaudio (Ubuntu)
     Importance: Medium
     Assignee: Daniel van Vugt (vanvugt)
         Status: Fix Released

** Affects: pulseaudio (Ubuntu Eoan)
     Importance: Medium
     Assignee: Daniel van Vugt (vanvugt)
         Status: Fix Committed

** Affects: pulseaudio (Ubuntu Focal)
     Importance: Medium
     Assignee: Daniel van Vugt (vanvugt)
         Status: Fix Released


** Tags: eoan focal regression-release
-- 
PulseAudio automatically switches to HDMI sound output on login
https://bugs.launchpad.net/bugs/1847570
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1855594 at bugs.launchpad.net  Wed Dec 18 07:14:35 2019
From: 1855594 at bugs.launchpad.net (Alkis Georgopoulos)
Date: Wed, 18 Dec 2019 07:14:35 -0000
Subject: [Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from
 Debian unstable (main)
References: <157581630122.6153.649495934122601180.malonedeb@gac.canonical.com>
Message-ID: <157665327508.15024.4907414526512784244.malone@wampee.canonical.com>

I came to file this exact issue and I saw that someone has already filed
it; thank you Amr.

If chromium isn't provided in 20.04, then Ubuntu users that opt not to
use snaps will have to install Google's Chrome instead.

I tested the Buster chromium package in Focal and it worked fine.
Specifically, I just had to apt install these packages from Debian:

289896 Nov 22 15:12 chromium-common_78.0.3904.108-1~deb10u1_amd64.deb
55110204 Nov 22 15:12 chromium_78.0.3904.108-1~deb10u1_amd64.deb
176942 Jul 31  2017 libevent-2.1-6_2.1.8-stable-4_amd64.deb
133808 Dec  5  2017 libjpeg62-turbo_1.5.2-2+b1_amd64.deb
800224 Nov 27 12:58 libvpx5_1.7.0-3+deb10u1_amd64.deb

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855594

Title:
  Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)

Status in chromium package in Ubuntu:
  Confirmed

Bug description:
  Please sync chromium 78.0.3904.108-1 (universe) from Debian unstable
  (main)

  Now that the other chromium-browser source package in Ubuntu is just a transitional dummy package to the chromium snap, I guess we can now sync the Debian chromium package.
  This gives the community a chance to maintain a deb chromium package in Ubuntu independent from the snap one.

  All changelog entries:

  chromium (78.0.3904.108-1) unstable; urgency=medium

    * New upstream security release.
      - CVE-2019-13723: Use-after-free in Bluetooth. Reported by Yuxiang Li
      - CVE-2019-13724: Out-of-bounds in Bluetooth. Reported by Yuxiang Li
    * Disable vaapi on armhf (closes: #944627).

   -- Michael Gilbert <mgilbert at debian.org>  Wed, 20 Nov 2019 23:46:06
  +0000

  chromium (78.0.3904.97-1) unstable; urgency=medium

    * New upstream security release.
    * Enable vaapi (closes: #940074).
    * Fix crash during profile manager shutdown.
    * Drop libglewmx-dev build dependency (closes: #941050).

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 09 Nov 2019 03:33:52
  +0000

  chromium (78.0.3904.87-1) unstable; urgency=medium

    * New upstream stable release.
      - CVE-2019-5869: Use-after-free in Blink. Reported by Zhe Jin
      - CVE-2019-5870: Use-after-free in media. Reported by Guang Gong
      - CVE-2019-5871: Heap overflow in Skia. Reported by Anonymous
      - CVE-2019-5872: Use-after-free in Mojo. Reported by Zhe Jin
      - CVE-2019-5874: External URIs may trigger other browsers. Reported by
        James Lee
      - CVE-2019-5875: URL bar spoof. Reported by Khalil
        Zhani
      - CVE-2019-5876: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-5877: Out-of-bounds access in V8. Reported by Guang Gong
      - CVE-2019-5878: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-5879: Extensions can read some local files. Reported by Jinseo
        Kim
      - CVE-2019-5880: SameSite cookie bypass. Reported by Jun Kokatsu
      - CVE-2019-13659: URL spoof. Reported by Lnyas Zhang
      - CVE-2019-13660: Full screen notification overlap. Reported by Wenxu Wu
      - CVE-2019-13661: Full screen notification spoof. Reported by Wenxu Wu
      - CVE-2019-13662: CSP bypass. Reported by David Erceg
      - CVE-2019-13663: IDN spoof. Reported by Lnyas Zhang
      - CVE-2019-13664: CSRF bypass. Reported by thomas "zemnmez" shadwell
      - CVE-2019-13665: Multiple file download protection bypass. Reported by
        Jun Kokatsu
      - CVE-2019-13666: Side channel using storage size estimate. Reported by
        Tom Van Goethem
      - CVE-2019-13667: URI bar spoof when using external app URIs. Reported by
        Khalil Zhani
      - CVE-2019-13668: Global window leak via console. Reported by David Erceg
      - CVE-2019-13669: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13670: V8 memory corruption in regex. Reported by Guang Gong
      - CVE-2019-13671: Dialog box fails to show origin. Reported by xisigr
      - CVE-2019-13673: Cross-origin information leak using devtools. Reported
        by David Erceg
      - CVE-2019-13674: IDN spoofing. Reported by Khalil Zhani
      - CVE-2019-13675: Extensions can be disabled by trailing slash. Reported
        by Jun Kokatsu
      - CVE-2019-13676: Google URI shown for certificate warning. Reported by
        Wenxu Wu
      - CVE-2019-13677: Chrome web store origin needs to be isolated. Reported
        by Jun Kokatsu
      - CVE-2019-13678: Download dialog spoofing. Reported by Ronni Skansing
      - CVE-2019-13679: User gesture needed for printing. Reported by Conrad
        Irwin
      - CVE-2019-13680: IP address spoofing to servers. Reported by Thijs
        Alkemade
      - CVE-2019-13681: Bypass on download restrictions. Reported by David Erceg
      - CVE-2019-13682: Site isolation bypass. Reported by Jun Kokatsu
      - CVE-2019-13683: Exceptions leaked by devtools. Reported by David Erceg
      - CVE-2019-13685: Use-after-free in UI. Reported by Khalil Zhani
      - CVE-2019-13686: Use-after-free in offline pages. Reported by Brendon
      - CVE-2019-13687: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13688: Use-after-free in media. Reported by Man Yue Mo
        Tiszka
      - CVE-2019-13691: Omnibox spoof. Reported by David Erceg
      - CVE-2019-13692: SOP bypass. Reported by Jun Kokatsu
      - CVE-2019-13693: Use-after-free in IndexedDB. Reported by Guang Gong
      - CVE-2019-13694: Use-after-free in WebRTC. Reported by banananapenguin
      - CVE-2019-13695: Use-after-free in audio. Reported by Man Yue Mo
      - CVE-2019-13696: Use-after-free in V8. Reported by Guang Gong
      - CVE-2019-13697: Cross-origin size leak. Reported by Luan Herrera
      - CVE-2019-13699: Use-after-free in media. Reported by Man Yue Mo
      - CVE-2019-13700: Buffer overrun in Blink. Reported by Man Yue Mo
      - CVE-2019-13701: URL spoof in navigation. Reported by David Erceg
      - CVE-2019-13702: Privilege elevation in Installer. Reported by Phillip
        Langlois and Edward Torkington
      - CVE-2019-13703: URL bar spoofing. Reported by Khalil Zhani
      - CVE-2019-13704: CSP bypass. Reported by Jun Kokatsu
      - CVE-2019-13705: Extension permission bypass. Reported by Luan Herrera
      - CVE-2019-13706: Out-of-bounds read in PDFium. Reported by pdknsk
      - CVE-2019-13707: File storage disclosure. Reported by Andrea Palazzo
      - CVE-2019-13708: HTTP authentication spoof. Reported by Khalil Zhani
      - CVE-2019-13709: File download protection bypass. Reported by Zhong
        Zhaochen
      - CVE-2019-13710: File download protection bypass. Reported by
        bernardo.mrod
      - CVE-2019-13711: Cross-context information leak. Reported by David Erceg
      - CVE-2019-13713: Cross-origin data leak. Reported by David Erceg
      - CVE-2019-13714: CSS injection. Reported by Jun Kokatsu
      - CVE-2019-13715: Address bar spoofing. Reported by xisigr
      - CVE-2019-13716: Service worker state error. Reported by Barron Hagerman
      - CVE-2019-13717: Notification obscured. Reported by xisigr
      - CVE-2019-13718: IDN spoof. Reported by Khalil Zhani
      - CVE-2019-13719: Notification obscured. Reported by Khalil Zhani
      - CVE-2019-13720: Use-after-free in audio. Reported by Anton Ivanov and
        Alexey Kulaev
      - CVE-2019-13721: Use-after-free in PDFium. Reported by banananapenguin
    * Drop support for building with gcc 6 and gtk 2.

   -- Michael Gilbert <mgilbert at debian.org>  Sat, 02 Nov 2019 22:30:42
  +0000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1855594/+subscriptions


From 1856574 at bugs.launchpad.net  Wed Dec 18 12:58:25 2019
From: 1856574 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Dec 2019 12:58:25 -0000
Subject: [Bug 1856574] Re: removal of various autopilot packages
References: <157650561253.19251.3333137627024153118.malonedeb@wampee.canonical.com>
Message-ID: <157667390841.26288.5240153528512985843.malone@ackee.canonical.com>

This bug was fixed in the package autopilot-gtk - 1.6.0

---------------
autopilot-gtk (1.6.0) focal; urgency=medium

  * Remove the dependency on python2 version of autopilot (LP: #1856574)
  * Update the dependencies to python3 version of autopilot.
  * Fixed the testsuite.
  * Bump version number and align it with autopilot
  * Update Standards-Version to 4.4.1

 -- Jean-Baptiste Lallement <jean-baptiste.lallement at ubuntu.com>  Tue,
17 Dec 2019 07:55:05 +0100

** Changed in: autopilot-gtk (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856574

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  New
Status in python-fixtures package in Ubuntu:
  New
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions


From seb128 at ubuntu.com  Wed Dec 18 14:46:14 2019
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Wed, 18 Dec 2019 14:46:14 -0000
Subject: [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157668037420.15344.16581971361974538269.malone@wampee.canonical.com>

Uploaded to the SRU queue nowb

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions


From jean-baptiste.lallement at ubuntu.com  Wed Dec 18 16:39:02 2019
From: jean-baptiste.lallement at ubuntu.com (Jean-Baptiste Lallement)
Date: Wed, 18 Dec 2019 16:39:02 -0000
Subject: [Bug 1856574] Re: removal of various autopilot packages
References: <157650561253.19251.3333137627024153118.malonedeb@wampee.canonical.com>
Message-ID: <157668714346.5202.12925039514301561160.launchpad@gac.canonical.com>

** Changed in: autopilot-gtk (Ubuntu)
     Assignee: Jean-Baptiste Lallement (jibel) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856574

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  New
Status in python-fixtures package in Ubuntu:
  New
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions


From 1810154 at bugs.launchpad.net  Thu Dec 19 06:40:59 2019
From: 1810154 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Dec 2019 06:40:59 -0000
Subject: [Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion
 `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157673766078.2622.8344009811745634359.launchpad@soybean.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Fix Released
Status in plymouth source package in Eoan:
  Fix Committed

Bug description:
  [SRU Justification]
  An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords.  While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot.

  [Test case]
  1. Change to VT3 on your system (so that you are not under a graphical login session) and log in.
  2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3
  3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console.
  4. Install the plymouth package from eoan-proposed.
  5. Repeat step 2.
  6. Observe that you are shown a password prompt.
  7. Type something into the field and hit enter.
  8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages.

  [Regression potential]
  This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch.  This fixes a crash and has minimal risk of regression.

  
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From kai.heng.feng at canonical.com  Thu Dec 19 08:51:13 2019
From: kai.heng.feng at canonical.com (Kai-Heng Feng)
Date: Thu, 19 Dec 2019 08:51:13 -0000
Subject: [Bug 1855893] Re: Properly let PCM leave suspended state when
 hardware doesn't support PCM resume
References: <157598921477.7721.14604770826784008639.malonedeb@soybean.canonical.com>
Message-ID: <157674547337.2842.3586904577163049178.malone@soybean.canonical.com>

Doesn't seem to be have an upstream bug.

Here's the upstream commit:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/commit/f7b3537bbf9a6916ee3fd72a82025519b4c346f5

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855893

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions


From seb128 at ubuntu.com  Thu Dec 19 09:26:30 2019
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Thu, 19 Dec 2019 09:26:30 -0000
Subject: [Bug 1855893] Re: Properly let PCM leave suspended state when
 hardware doesn't support PCM resume
References: <157598921477.7721.14604770826784008639.malonedeb@soybean.canonical.com>
Message-ID: <157674759143.27774.11104189242151405519.launchpad@chaenomeles.canonical.com>

** Tags added: rls-bb-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855893

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions


From seb128 at ubuntu.com  Thu Dec 19 09:57:46 2019
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Thu, 19 Dec 2019 09:57:46 -0000
Subject: [Bug 1856574] Re: removal of various autopilot packages
References: <157650561253.19251.3333137627024153118.malonedeb@wampee.canonical.com>
Message-ID: <157674946680.5798.6632919838801661042.malone@gac.canonical.com>

The autopilot-legacy package isn't used anymore so let's remove it from
focal now

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856574

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  New
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions


From seb128 at ubuntu.com  Thu Dec 19 10:00:33 2019
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Thu, 19 Dec 2019 10:00:33 -0000
Subject: [Bug 1856574] Re: removal of various autopilot packages
References: <157650561253.19251.3333137627024153118.malonedeb@wampee.canonical.com>
Message-ID: <157674963389.14374.3637493188470064160.malone@wampee.canonical.com>

autopilot-legacy 1.4.1+17.04.20170305-0ubuntu2 in focal
Comment: deprecated, depends on removed packages, lp: #1856574
Remove [y|N]? y


** Changed in: autopilot-legacy (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856574

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  New
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions


From kleber.souza at canonical.com  Thu Dec 19 11:17:06 2019
From: kleber.souza at canonical.com (Kleber Sacilotto de Souza)
Date: Thu, 19 Dec 2019 11:17:06 -0000
Subject: [Bug 1837886] Re: kpatch 0.5.0-0ubuntu2 ADT test failure with linux
 5.3.0-0.1
References: <156405991404.18485.18350487893200706506.malonedeb@gac.canonical.com>
Message-ID: <157675422730.27964.16344717437057223597.launchpad@chaenomeles.canonical.com>

** Also affects: kpatch (Ubuntu Bionic)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1837886

Title:
  kpatch 0.5.0-0ubuntu2 ADT test failure with linux 5.3.0-0.1

Status in kpatch package in Ubuntu:
  New
Status in kpatch source package in Bionic:
  New

Bug description:
  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/k/kpatch/20190724_125410_41a25@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1837886/+subscriptions


From seb128 at ubuntu.com  Thu Dec 19 11:41:57 2019
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Thu, 19 Dec 2019 11:41:57 -0000
Subject: [Bug 1803136] Re: [SRU] Update to vala 0.40.17 in bionic
References: <154211698943.24625.4758423341389755446.malonedeb@chaenomeles.canonical.com>
Message-ID: <157675571789.2925.9305801190984883744.malone@soybean.canonical.com>

Seems the SRU makes gnome-calculator fail to rebuild. The fix is 
https://gitlab.gnome.org/GNOME/gnome-calculator/merge_requests/17
but it seems problematic that a SRU update leads to source no being rebuildable...

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1803136

Title:
  [SRU] Update to vala 0.40.17 in bionic

Status in vala package in Ubuntu:
  Fix Released
Status in vala source package in Bionic:
  Fix Committed

Bug description:
  The 0.40.x series is maintained as LTS release and will receive
  further bug fix releases in the future. See
  https://wiki.gnome.org/Projects/Vala

  Previous 0.40.8 SRU https://bugs.launchpad.net/bugs/1782122

  Falls under the standing GNOME SRU execption
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  Upstream changes since 0.40.8:

  Vala 0.40.17
  ============
   * Various improvements and bug fixes:
    - vala:
      + Allow direct access to the integer constants of an error-domain [#732]
      + Support static methods in error-domains [#829]
      + vala: Init formal_target_type of built ArrayCreationExpression from
        InitializerList [#835]
      + Add missing closing brace/bracket in to_string() of
        ArrayCreationExpression and InitializerList
      + Reject unary operations on nullable integer/floating/boolean type [#772]
      + Report dedicated error message for params-array parameter mismatch
      + Output "params" qualifier of parameters
      + Fix compatible/disposable check between structs and their subtypes
      + Don't issue a warning for non-public struct fields in bindings
      + No-accessor struct properties in GLib.Object class must be owned
      + Trust "value_owned" when writing property getter and regenerate
        GIDL/GIR-based bindings fix getter ownership of struct properties
    - codegen:
      + Don't cause double-free due append_local_free() in uncaught-errors [#838]
      + Directly use "memmove()" while g_memmove() is deprecated
      + Accept children after generating type specific declarations
      + Preserve full access to delegate variables and its target/destroy cvalues
      + Initialize delegate temp-var which is assigned by property getter
      + Use gtype-boxed API for structs with "g_boxed_free" attribute [#863]
    - ccode: Implicitly register declaration for added CCodeFunction
    - codewriter: Write "weak" modifier for properties
    - girparser/gidlparser: "value_owned = true" by default for property types
    - girparser: Add required copy/free attributes for gtype-boxed structs
      and regenerate GIR-based bindings to pick up copy/free attributes [#863]
    - libvaladoc: Don't traverse into close circles with parent [#829]
    - genie: Creation methods should not be static
    - valadoc: Explicitly pass --pkg libvala at PACKAGE_SUFFIX@ and --pkg libgvc

   * Bindings:
    - avahi-client: Fix "use of possibly unassigned parameter" warnings
    - cairo: Add 1.16 symbols
    - glib-2.0: Fix MutexLocker binding
    - glib-2.0: Use 'GStatBuf' as ctype for 'Stat'
    - glib-2.0: DateTime.from_iso8601() can take a null TimeZone
    - glib-2.0: Set default_value attribute for GLib.pointer
    - gio-2.0: Drop metadata for NativeSocketAddress
    - gio-unix-2.0: Fix DesktopAppInfo.get_string(), UnixFDMessage.steal_fds()
    - gnutls: Fix "use of possibly unassigned parameter" warnings
    - gobject-2.0: Some cherry-picking from GIR generated binding
    - gtk+-3.0: Ownership mismatch of ColorButton.rgba property-accessor [#844]
    - json-glib-1.0: Change abstract methods of Serializable to virtual [#840]
    - libsoup-2.4: soup_auth_new is not a constructor but a factory method [#791]
    - linux: Add more Input and update UserspaceInput bindings [#830]
    - posix: Add *at() calls and related constants [#823]
    - sqlite3: Bind sqlite3_expanded_sql() and sqlite3_normalised_sql()
    - sqlite3: Fix use of possibly unassigned parameter `errmsg'
    - tokyocabinet: Fix deprecation warnings
    - xcb: Fix "missing return statement at end of subroutine body" errors

  Vala 0.40.16
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Always use G_TYPE_CHECK_INSTANCE_TYPE for external symbols
      + When freeing local variables don't stop at "switch" on "continue" [#799]
      + Use array_length of collection variable instead of expression
      + Assign GValue result of function calls to temp-var on copy_value [#819]
      + Real structs are allowed by simple generics and passed as reference [#819]
      + Use G_TYPE_CHECK_INSTANCE_CAST for comparisons with interfaces
      + Include required type-definition when casting from generic pointer [#828]
    - girwriter:
      + Mention that this file is generated and not meant to be modified
      + Properly resolve GLib.TypeInterface instead of hardcoding it
      + Multiple improvements and fixes for e.g. GType classes
    - girparser:
      + Add support for string "ctype" metadata [#793]
      + Skip 'attribute' elements
      + Handle "function-macro" by skipping them [gi#159]
    - parser: Multiple corrections for source-location of code-nodes
    - compiler: Add OptionFlags.NO_ARG to deprecated "--thread" option
    - build: Pass -no-undefined when linking libvalaccodegen [#820]
    - tests: Null-terminate arrays for compatibility test of uint8 / uchar [#809]

   * Bindings:
    - clutter-1.0: Bind Margin, PaintVolume, Point, Rect and Size as struct [#795]
    - cogl-1.0: Fix out-params in Cogl.get_modelview_matrix/projection_matrix/
      bitmasks [#794]
    - glib-2.0: Bind strcmp0 as GLib.CompareFunc<string?> [#810]
    - glib-2.0: Add MappedFile.from_fd constructor [#824]
    - gtk+-3.0: Update to 3.24.9~18177388
    - posix: Fix return-value of mknod() and c-include for tcgetsid()
    - webkit2gtk-4.0: Fix WebContext.initialize_notification_permissions()
    - x11: Fix return type of XInternAtoms and XGetAtomNames bindings
    - xtst: Fix signature of XTest.fake_relative_motion_event()

  Vala 0.40.15
  ============
   * Various improvements and bug fixes:
    - Mark defined constructors of abstract classes as protected
    - codegen:
      + Use guint to represent flags-enum in custom GMarshalFunc
      + Move disconnect error from signal-module to semantic-analyzer pass
      + Use unsigned default value for flags-enum
      + Always assign original variable when consuming instance to destroy [#781]
      + Resolve generics in sizeof-expression of parameter initializer
      + Move implicit GValue cast for comparison to BinaryExpression [#585063]
    - girparser: Create correct output in get_default_lower_case_suffix() [#778]
    - parser: Improve source_reference of expressions and statements
    - vala: Variadic parameters are not supported for async methods
    - vala: Allow assignment of 0U to enum types
    - vala: Use global CodeContext to retrieve root_symbol
    - libvaladoc:
      + Don't try to create a Content.ListItem when there is none
      + Handle missing Content.List.Bullet.ORDERED in switch
      + Handle missing Run.Style.NONE in switch

   * Bindings:
    - libgvc: Some additions and ownership/return-type fixes
    - glib-2.0: Don't annotate dedicated GLib.assert_*() with [Assert] [#769]
    - pango: Fix StringBuilder parameter of scan_word()
    - gobject-introspection-1.0: Fix TypeInfo and TypeTag method references [#778]
    - gstreamer-1.0: Fix TypeFind and TypeFindFactory method references [#778]

  Vala 0.40.14
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Replace some unfortunate asserts with internal error reports
      + Properly handle and catch inner-error of finally-block (#742)
      + Pass lambda expression of variable initializer to signal connect
      + Respect array_length_cname attribute for global fields
    - vala:
   + Check inferred variable_type of LocalVariables
   + Parser doesn't ensure "protected" to be applied on TypeSymbol members
    - girparser: Correctly set array_length_type for delegates returning an array
    - girwriter:
      + Support transfer-ownership="container" for arrays
      + Always use get_gir_name() for TypeSymbols
    - libvaladoc:
      + Don't change the size of an array in-parameter
      + Properly support the output of async constructors (#753)
    - valadoc: Report warning if resources for doclet could not be copied
    - g-i: Fix return value on error in start_discriminator()

   * Bindings:
    - clutter-1.0: Drop deprecated from Actor.pick() (#625)
    - gdk-3.0: Update to 3.24.4+a0129f55
    - gtk+-unix-print-*.0: Fix PrintJob.get_page_ranges(),
      Printer.get_hard_margins()
    - gobject-2.0: Add SignalHandler.disconnect_by_data()
    - poppler-glib: Update to 0.74

  Vala 0.40.13
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Use temp-var for MethodCall with out/ref arguments (#722)
      + Use temp-vars for ellipsis out-arguments to fix memory management (#722)
      + Add default_value for CType to initialize variables if needed (#724)
      + Cast instance parameter for property access in object-initializer
      + Don't check boolean values for (in)equality in GTask API (#726)
      + Properly set annotations field of GDBus*Info struct to NULL
      + Cast instance and result of g_async_initable_new_finish() call
      + Use a parameter-map for creation of delegate declaration [#728]
      + Emit struct declaration typedef before resolving its fields [#318]
      + Don't apply address-of operator on literals when casting to array
    - vala: Report invalid instance member access to property (#605)
    - girparser: Async methods don't allow out-parameters before in-parameters
    - libvaladoc: Build backing Vala.SourceFile for GIRs processed by importer
    - libvaladoc/girimporter: Skip "source-position" elements
    - valadoc: Specify that the "--driver" option is deprecated [#736]
    - compiler: Report deprecated command-line option "--thread"
    - build: Don't leak libvalaccode symbols to libvaladoc
    - Add a basic CONTRIBUTING.md file that links to the relevant Wiki page
    - tests: Fix try_parse() tests to not compare to already free'd memory

   * Bindings:
    - clutter-1.0: Fix BindingPool.override_action()
    - gdk-3.0,gtk+-3.0: Update to 3.24.3+9c8f1478
    - glib-2.0: Use correct array-length-type for returned arrays (#171)
    - gio-2.0: Fix File.replace_contents_bytes_async() (!37)
    - gobject-2.0: Minor syncing from GIR
    - gobject-2.0: Use correct array-length-type for returned arrays
    - gtk+-4.0: Update to 3.94.0+9b15c690
    - libsoup-2.4: Fix Message.add_*_handler() [#731]
    - sqlite3: Correct return C type of Statement.column_text & Value.to_text

  Vala 0.40.12
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Fix method pointer cast if instance isn't at first position
      + Transfer ownership of compact class to DestroysInstance method [#645]
      + Make sure to include declarations for delegate typed parameters
      + Don't emit type_id for enum in non GOBJECT profile
      + Don't emit unused temp variable for element access assignments
      + Actually create method cast for base interface method as needed
      + Mark needle parameter of internal array-contains methods as const [#504]
      + Emit initializer for enum-value into wanted declaration space [#167]
      + Add void to delegate typedef declarations without parameters
      + Emit delegate/enum typedefs to type-declaration section [#318]
      + Always emit constants with initializer-list [#81]
      + Handle non-default AsyncResult parameter position [#709]
    - vala:
      + Copy instance_pos argument from virtual/abstract base methods [#540483]
      + Compact classes don't allow private/class fields and to lock fields
      + Use comment which was already retrieved in parse_declaration()
      + Add missing re-check guards for Do/For/WhileStatement and SwitchLabel
      + Type check for errors require an error expression [#362]
      + Make check_arguments() more verbose and don't bail on first error [#438]
      + Don't emit member access of assignments on static properties [#573]
      + Use clearer error message for automatic properties in interfaces [#656]
      + Break possible endless loop in SymbolResolver.get_type_for_struct() [#444]
    - girwriter: Write glib-type attributes for Enums/Structs with type_id
    - girparser: Skip "source-position" elements and docs in transparent union
    - valadoc:
      + Match property signature with vala's codewriter
      + Sort symbols and members where possible
      + Actually assign type_id of Api.Structs
      + Add type_id to Api.Enum/Interface
      + Skip package dependency if target directory already exists
      + Fix a few errors and warnings in stylesheet
      + Adjust stylesheet to unbreak Epiphany [#644]
    - docs: Use Markdown for README and include build instructions
    - testrunner: Pass buildsystem's CC through to valac

   * Bindings:
    - gio-2.0: Add missing File.new_build_filename()
    - glib-2.0: Add missing Array.set_clear_func() binding
    - glib-2.0: Avoid double-free in GLib.Array if clear_func is set
    - glib-2.0: Add GLib.pointer aka gpointer binding
    - gobject-2.0: Attribute all symbols with cheader_filename = "glib-object.h"
    - gobject-introspection-1.0: Pick up version attribute fixes
    - gdk-x11-3.0,gtk+-3.0: Update to 3.24.2+eb821cb8
    - gtk+-4.0: Update to 3.94.0+a99bd2a4
    - poppler-glib: Update to 0.71

  Vala 0.40.11
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Initialize internal temp-variables used as reference parameter
      + Improve ccode for fixed-length array parameters (#163)
      + Fix regex literal compile flags
      + Add prototype for *_register_type() function
      + Don't emit *_free() of derived compact classes
      + Add prototype for *_new() of abstact compact classes
    - girwriter: Fix ctype of out/ref and array parameters
    - ccode: Fix typo and actually check "end_decls" (#672)
    - abstract syntax tree:
      + Always analyze nodes after they are inserted into the AST
      + Add source_reference to local variable of catch-clause
      + Add missing replace_expression() implementations
      + Fix several construction/parenting issues
      + DataType for GLib.Error should be should resolved as ErrorType
    - testrunner: Reset $run_prefix before generating next test script
    - build: Unconditionally add conditional VALAFLAGS to make bootstrap
    - manual: Update from wiki.gnome.org

   * Bindings:
    - glib-2.0: Computing length once is enough in string.to_utf8()/splice()
    - glib-2.0: Add binding for g_test_add()
    - glib-2.0: Add array length to string.skip (#695)
    - gio-2.0: Result of DBusMessage.get_header() is unowned
    - gobject-2.0,gtk+-*.0: Fix some GLib.Value out/ref parameters
    - gtk+-4.0: Update to 3.94.0+b4b30b49

  Vala 0.40.10
  ============
   * Various improvements and bug fixes:
    - codewriter: Prepend "yield" if is_yield_expression is set on
      MethodCall and ObjectCreationExpression
    - codegen: Fix typo in is_pure_ccode_expression() [#673]
    - gobject-introspection: Fix use after free in scanner [#674]
    - vala: Check if ArrayType supports its given element-type in analyzer pass
    - valadoc: Fix some string escaping which gettext complains about

   * Bindings:
    - Update GIDL-based bindings to fix unsupported type-arguments
    - Add gnome-desktop-3.0 bindings [#668]
    - glib-2.0: Add feature_test_macro details for Time struct's methods
    - glib-2.0: Set DateTime.now () to use local time zone as the default
    - gstreamer: Cherry-pick some fixes from 0.42
    - gtk+-3.0: Update to 3.24.0
    - gtk+-4.0: Update to 3.94.0+d90e2733
    - libxml-2.0: Add missing context parameter in OutputWriteCallback
    - pango: Update to 1.42.3
    - x11: Add binding for XCreateSimpleWindow

  Vala 0.40.9
  ===========
   * Various improvements and bug fixes:
    - girparser: Actually resolve type-arguments to be able to box them if needed
    - girparser: Handle unsupported aliases which could not be fully processed
    - codegen: Free errors after returning them on GDBusMethodInvocation [#657]
    - codegen: Fix invocation of abstract/virtual methods with NoWrapper in
      compact classes
    - vala: Allow read-only properties
    - manual: Update from wiki.gnome.org

   * Bindings:
    - glib-2.0: Add Array.remove*() wrapper to avoid leaking generic elements
    - glib-2.0: Add (u)long.parse/try_parse() and float.parse/try_parse() [#649]
    - glib-2.0: Add return-type of Queue.remove*(), add HashTable.foreach_steal()
    - gtk+-3.0: Update to 3.23.2+6b6e53fd
    - gtk+-4.0: Update to 3.94.0+4e868584
    - webkit2gtk-4.0: Update to 2.20.5

  [Impact]
   * Affects all valac reverse-dependency on buildtime

  [Test Case]
   * Mass-rebuild of rdepends can be found here
     https://launchpad.net/~ricotz/+archive/ubuntu/vala-sru/+packages?batch=200&memo=0&start=0

  [Regression Potential]
   * Not immediately while it requires an rdepend rebuild to manifest.

  [Other Info]
   * Regular upstream maintenance releases are likely to happen every 1-2 months

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1803136/+subscriptions


From ddstreet at canonical.com  Thu Dec 19 17:22:57 2019
From: ddstreet at canonical.com (Dan Streetman)
Date: Thu, 19 Dec 2019 17:22:57 -0000
Subject: [Bug 1741860] Re: Use the kernel default for crashkernel offset
References: <151540317351.26366.455159565897169332.malonedeb@gac.canonical.com>
Message-ID: <157677617775.5706.3134001976860484943.launchpad@gac.canonical.com>

** Also affects: makedumpfile (Ubuntu Focal)
   Importance: High
     Assignee: Connor Kuehl (connork)
       Status: Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1741860

Title:
  Use the kernel default for crashkernel offset

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  Fix Released
Status in makedumpfile source package in Disco:
  Fix Released
Status in makedumpfile source package in Eoan:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * The value chosen for ppc64el of 128MB aligns with that of the
  kernel default. That may change some day, so it would be best to let
  the kernel decide what value it should use. If the value does change
  and the kernel is not allowed to choose a value, this may stop the
  kernel from booting on a production system.

  [Test Case]

   Run `cat /etc/default/grub.d/kdump-tools.cfg`

   * Expected result: there is no offset specified at the end of the
  line (.e.g, @128M).

   * Actual result: For Xenial, Bionic, Disco, and Eoan there are
  offsets specified.

  [Regression Potential]

   * Right now, the offset described in the kdump-tools.cfg aligns with
  that of what the kernel would select, so since they are the same we
  would expect no change in operation.

  
  Original bug description follows:
  -----------------------------------------

  == Comment: #0 - Hari Krishna Bathini <hbathini at in.ibm.com> - 2018-01-08 01:06:41 ==
  ---Problem Description---
  A default offset of 128MB is enforced for crashkernel by kdump-tools utility
  overriding the kernel default.

  While the kernel default offset for crashkernel is also 128MB, that may change
  and the right thing to do would be to let the kernel decide on the offset of
  crashkernel in the default scenario..

  Get rid of "@128M" in kdump-tools.cfg file

  Contact Information = hbathini at in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   # cat /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M at 128M"
  ---

  The offset is specified via kdump-tools where as the kernel may be the right place to
  set an offset by default..

  Userspace tool common name: kdump-tools

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbathini at in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - MAMATHA INAMDAR <mainamdar at in.ibm.com> - 2018-01-08 03:05:05 ==
  This bug is opened to follow-up other bug based on the comment 19
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad 	1676884 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions


From steve.langasek at canonical.com  Fri Dec 20 05:25:56 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 20 Dec 2019 05:25:56 -0000
Subject: [Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion
 `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157681955670.27812.5122657998183584497.launchpad@chaenomeles.canonical.com>

** Tags removed: verification-failed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Fix Released
Status in plymouth source package in Eoan:
  Fix Committed

Bug description:
  [SRU Justification]
  An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords.  While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot.

  [Test case]
  1. Change to VT3 on your system (so that you are not under a graphical login session) and log in.
  2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3
  3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console.
  4. Install the plymouth package from eoan-proposed.
  5. Repeat step 2.
  6. Observe that you are shown a password prompt.
  7. Type something into the field and hit enter.
  8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages.

  [Regression potential]
  This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch.  This fixes a crash and has minimal risk of regression.

  
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From 1803136 at bugs.launchpad.net  Fri Dec 20 13:59:14 2019
From: 1803136 at bugs.launchpad.net (Rico Tzschichholz)
Date: Fri, 20 Dec 2019 13:59:14 -0000
Subject: [Bug 1803136] Re: [SRU] Update to vala 0.40.17 in bionic
References: <154211698943.24625.4758423341389755446.malonedeb@chaenomeles.canonical.com>
Message-ID: <157685035501.15105.2113760885209891360.malone@wampee.canonical.com>

@seb128 The build test went fine at the time:
https://launchpad.net/~ricotz/+archive/ubuntu/vala-
sru/+sourcepub/10687929/+listing-archive-extra

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1803136

Title:
  [SRU] Update to vala 0.40.17 in bionic

Status in vala package in Ubuntu:
  Fix Released
Status in vala source package in Bionic:
  Fix Committed

Bug description:
  The 0.40.x series is maintained as LTS release and will receive
  further bug fix releases in the future. See
  https://wiki.gnome.org/Projects/Vala

  Previous 0.40.8 SRU https://bugs.launchpad.net/bugs/1782122

  Falls under the standing GNOME SRU execption
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  Upstream changes since 0.40.8:

  Vala 0.40.17
  ============
   * Various improvements and bug fixes:
    - vala:
      + Allow direct access to the integer constants of an error-domain [#732]
      + Support static methods in error-domains [#829]
      + vala: Init formal_target_type of built ArrayCreationExpression from
        InitializerList [#835]
      + Add missing closing brace/bracket in to_string() of
        ArrayCreationExpression and InitializerList
      + Reject unary operations on nullable integer/floating/boolean type [#772]
      + Report dedicated error message for params-array parameter mismatch
      + Output "params" qualifier of parameters
      + Fix compatible/disposable check between structs and their subtypes
      + Don't issue a warning for non-public struct fields in bindings
      + No-accessor struct properties in GLib.Object class must be owned
      + Trust "value_owned" when writing property getter and regenerate
        GIDL/GIR-based bindings fix getter ownership of struct properties
    - codegen:
      + Don't cause double-free due append_local_free() in uncaught-errors [#838]
      + Directly use "memmove()" while g_memmove() is deprecated
      + Accept children after generating type specific declarations
      + Preserve full access to delegate variables and its target/destroy cvalues
      + Initialize delegate temp-var which is assigned by property getter
      + Use gtype-boxed API for structs with "g_boxed_free" attribute [#863]
    - ccode: Implicitly register declaration for added CCodeFunction
    - codewriter: Write "weak" modifier for properties
    - girparser/gidlparser: "value_owned = true" by default for property types
    - girparser: Add required copy/free attributes for gtype-boxed structs
      and regenerate GIR-based bindings to pick up copy/free attributes [#863]
    - libvaladoc: Don't traverse into close circles with parent [#829]
    - genie: Creation methods should not be static
    - valadoc: Explicitly pass --pkg libvala at PACKAGE_SUFFIX@ and --pkg libgvc

   * Bindings:
    - avahi-client: Fix "use of possibly unassigned parameter" warnings
    - cairo: Add 1.16 symbols
    - glib-2.0: Fix MutexLocker binding
    - glib-2.0: Use 'GStatBuf' as ctype for 'Stat'
    - glib-2.0: DateTime.from_iso8601() can take a null TimeZone
    - glib-2.0: Set default_value attribute for GLib.pointer
    - gio-2.0: Drop metadata for NativeSocketAddress
    - gio-unix-2.0: Fix DesktopAppInfo.get_string(), UnixFDMessage.steal_fds()
    - gnutls: Fix "use of possibly unassigned parameter" warnings
    - gobject-2.0: Some cherry-picking from GIR generated binding
    - gtk+-3.0: Ownership mismatch of ColorButton.rgba property-accessor [#844]
    - json-glib-1.0: Change abstract methods of Serializable to virtual [#840]
    - libsoup-2.4: soup_auth_new is not a constructor but a factory method [#791]
    - linux: Add more Input and update UserspaceInput bindings [#830]
    - posix: Add *at() calls and related constants [#823]
    - sqlite3: Bind sqlite3_expanded_sql() and sqlite3_normalised_sql()
    - sqlite3: Fix use of possibly unassigned parameter `errmsg'
    - tokyocabinet: Fix deprecation warnings
    - xcb: Fix "missing return statement at end of subroutine body" errors

  Vala 0.40.16
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Always use G_TYPE_CHECK_INSTANCE_TYPE for external symbols
      + When freeing local variables don't stop at "switch" on "continue" [#799]
      + Use array_length of collection variable instead of expression
      + Assign GValue result of function calls to temp-var on copy_value [#819]
      + Real structs are allowed by simple generics and passed as reference [#819]
      + Use G_TYPE_CHECK_INSTANCE_CAST for comparisons with interfaces
      + Include required type-definition when casting from generic pointer [#828]
    - girwriter:
      + Mention that this file is generated and not meant to be modified
      + Properly resolve GLib.TypeInterface instead of hardcoding it
      + Multiple improvements and fixes for e.g. GType classes
    - girparser:
      + Add support for string "ctype" metadata [#793]
      + Skip 'attribute' elements
      + Handle "function-macro" by skipping them [gi#159]
    - parser: Multiple corrections for source-location of code-nodes
    - compiler: Add OptionFlags.NO_ARG to deprecated "--thread" option
    - build: Pass -no-undefined when linking libvalaccodegen [#820]
    - tests: Null-terminate arrays for compatibility test of uint8 / uchar [#809]

   * Bindings:
    - clutter-1.0: Bind Margin, PaintVolume, Point, Rect and Size as struct [#795]
    - cogl-1.0: Fix out-params in Cogl.get_modelview_matrix/projection_matrix/
      bitmasks [#794]
    - glib-2.0: Bind strcmp0 as GLib.CompareFunc<string?> [#810]
    - glib-2.0: Add MappedFile.from_fd constructor [#824]
    - gtk+-3.0: Update to 3.24.9~18177388
    - posix: Fix return-value of mknod() and c-include for tcgetsid()
    - webkit2gtk-4.0: Fix WebContext.initialize_notification_permissions()
    - x11: Fix return type of XInternAtoms and XGetAtomNames bindings
    - xtst: Fix signature of XTest.fake_relative_motion_event()

  Vala 0.40.15
  ============
   * Various improvements and bug fixes:
    - Mark defined constructors of abstract classes as protected
    - codegen:
      + Use guint to represent flags-enum in custom GMarshalFunc
      + Move disconnect error from signal-module to semantic-analyzer pass
      + Use unsigned default value for flags-enum
      + Always assign original variable when consuming instance to destroy [#781]
      + Resolve generics in sizeof-expression of parameter initializer
      + Move implicit GValue cast for comparison to BinaryExpression [#585063]
    - girparser: Create correct output in get_default_lower_case_suffix() [#778]
    - parser: Improve source_reference of expressions and statements
    - vala: Variadic parameters are not supported for async methods
    - vala: Allow assignment of 0U to enum types
    - vala: Use global CodeContext to retrieve root_symbol
    - libvaladoc:
      + Don't try to create a Content.ListItem when there is none
      + Handle missing Content.List.Bullet.ORDERED in switch
      + Handle missing Run.Style.NONE in switch

   * Bindings:
    - libgvc: Some additions and ownership/return-type fixes
    - glib-2.0: Don't annotate dedicated GLib.assert_*() with [Assert] [#769]
    - pango: Fix StringBuilder parameter of scan_word()
    - gobject-introspection-1.0: Fix TypeInfo and TypeTag method references [#778]
    - gstreamer-1.0: Fix TypeFind and TypeFindFactory method references [#778]

  Vala 0.40.14
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Replace some unfortunate asserts with internal error reports
      + Properly handle and catch inner-error of finally-block (#742)
      + Pass lambda expression of variable initializer to signal connect
      + Respect array_length_cname attribute for global fields
    - vala:
   + Check inferred variable_type of LocalVariables
   + Parser doesn't ensure "protected" to be applied on TypeSymbol members
    - girparser: Correctly set array_length_type for delegates returning an array
    - girwriter:
      + Support transfer-ownership="container" for arrays
      + Always use get_gir_name() for TypeSymbols
    - libvaladoc:
      + Don't change the size of an array in-parameter
      + Properly support the output of async constructors (#753)
    - valadoc: Report warning if resources for doclet could not be copied
    - g-i: Fix return value on error in start_discriminator()

   * Bindings:
    - clutter-1.0: Drop deprecated from Actor.pick() (#625)
    - gdk-3.0: Update to 3.24.4+a0129f55
    - gtk+-unix-print-*.0: Fix PrintJob.get_page_ranges(),
      Printer.get_hard_margins()
    - gobject-2.0: Add SignalHandler.disconnect_by_data()
    - poppler-glib: Update to 0.74

  Vala 0.40.13
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Use temp-var for MethodCall with out/ref arguments (#722)
      + Use temp-vars for ellipsis out-arguments to fix memory management (#722)
      + Add default_value for CType to initialize variables if needed (#724)
      + Cast instance parameter for property access in object-initializer
      + Don't check boolean values for (in)equality in GTask API (#726)
      + Properly set annotations field of GDBus*Info struct to NULL
      + Cast instance and result of g_async_initable_new_finish() call
      + Use a parameter-map for creation of delegate declaration [#728]
      + Emit struct declaration typedef before resolving its fields [#318]
      + Don't apply address-of operator on literals when casting to array
    - vala: Report invalid instance member access to property (#605)
    - girparser: Async methods don't allow out-parameters before in-parameters
    - libvaladoc: Build backing Vala.SourceFile for GIRs processed by importer
    - libvaladoc/girimporter: Skip "source-position" elements
    - valadoc: Specify that the "--driver" option is deprecated [#736]
    - compiler: Report deprecated command-line option "--thread"
    - build: Don't leak libvalaccode symbols to libvaladoc
    - Add a basic CONTRIBUTING.md file that links to the relevant Wiki page
    - tests: Fix try_parse() tests to not compare to already free'd memory

   * Bindings:
    - clutter-1.0: Fix BindingPool.override_action()
    - gdk-3.0,gtk+-3.0: Update to 3.24.3+9c8f1478
    - glib-2.0: Use correct array-length-type for returned arrays (#171)
    - gio-2.0: Fix File.replace_contents_bytes_async() (!37)
    - gobject-2.0: Minor syncing from GIR
    - gobject-2.0: Use correct array-length-type for returned arrays
    - gtk+-4.0: Update to 3.94.0+9b15c690
    - libsoup-2.4: Fix Message.add_*_handler() [#731]
    - sqlite3: Correct return C type of Statement.column_text & Value.to_text

  Vala 0.40.12
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Fix method pointer cast if instance isn't at first position
      + Transfer ownership of compact class to DestroysInstance method [#645]
      + Make sure to include declarations for delegate typed parameters
      + Don't emit type_id for enum in non GOBJECT profile
      + Don't emit unused temp variable for element access assignments
      + Actually create method cast for base interface method as needed
      + Mark needle parameter of internal array-contains methods as const [#504]
      + Emit initializer for enum-value into wanted declaration space [#167]
      + Add void to delegate typedef declarations without parameters
      + Emit delegate/enum typedefs to type-declaration section [#318]
      + Always emit constants with initializer-list [#81]
      + Handle non-default AsyncResult parameter position [#709]
    - vala:
      + Copy instance_pos argument from virtual/abstract base methods [#540483]
      + Compact classes don't allow private/class fields and to lock fields
      + Use comment which was already retrieved in parse_declaration()
      + Add missing re-check guards for Do/For/WhileStatement and SwitchLabel
      + Type check for errors require an error expression [#362]
      + Make check_arguments() more verbose and don't bail on first error [#438]
      + Don't emit member access of assignments on static properties [#573]
      + Use clearer error message for automatic properties in interfaces [#656]
      + Break possible endless loop in SymbolResolver.get_type_for_struct() [#444]
    - girwriter: Write glib-type attributes for Enums/Structs with type_id
    - girparser: Skip "source-position" elements and docs in transparent union
    - valadoc:
      + Match property signature with vala's codewriter
      + Sort symbols and members where possible
      + Actually assign type_id of Api.Structs
      + Add type_id to Api.Enum/Interface
      + Skip package dependency if target directory already exists
      + Fix a few errors and warnings in stylesheet
      + Adjust stylesheet to unbreak Epiphany [#644]
    - docs: Use Markdown for README and include build instructions
    - testrunner: Pass buildsystem's CC through to valac

   * Bindings:
    - gio-2.0: Add missing File.new_build_filename()
    - glib-2.0: Add missing Array.set_clear_func() binding
    - glib-2.0: Avoid double-free in GLib.Array if clear_func is set
    - glib-2.0: Add GLib.pointer aka gpointer binding
    - gobject-2.0: Attribute all symbols with cheader_filename = "glib-object.h"
    - gobject-introspection-1.0: Pick up version attribute fixes
    - gdk-x11-3.0,gtk+-3.0: Update to 3.24.2+eb821cb8
    - gtk+-4.0: Update to 3.94.0+a99bd2a4
    - poppler-glib: Update to 0.71

  Vala 0.40.11
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Initialize internal temp-variables used as reference parameter
      + Improve ccode for fixed-length array parameters (#163)
      + Fix regex literal compile flags
      + Add prototype for *_register_type() function
      + Don't emit *_free() of derived compact classes
      + Add prototype for *_new() of abstact compact classes
    - girwriter: Fix ctype of out/ref and array parameters
    - ccode: Fix typo and actually check "end_decls" (#672)
    - abstract syntax tree:
      + Always analyze nodes after they are inserted into the AST
      + Add source_reference to local variable of catch-clause
      + Add missing replace_expression() implementations
      + Fix several construction/parenting issues
      + DataType for GLib.Error should be should resolved as ErrorType
    - testrunner: Reset $run_prefix before generating next test script
    - build: Unconditionally add conditional VALAFLAGS to make bootstrap
    - manual: Update from wiki.gnome.org

   * Bindings:
    - glib-2.0: Computing length once is enough in string.to_utf8()/splice()
    - glib-2.0: Add binding for g_test_add()
    - glib-2.0: Add array length to string.skip (#695)
    - gio-2.0: Result of DBusMessage.get_header() is unowned
    - gobject-2.0,gtk+-*.0: Fix some GLib.Value out/ref parameters
    - gtk+-4.0: Update to 3.94.0+b4b30b49

  Vala 0.40.10
  ============
   * Various improvements and bug fixes:
    - codewriter: Prepend "yield" if is_yield_expression is set on
      MethodCall and ObjectCreationExpression
    - codegen: Fix typo in is_pure_ccode_expression() [#673]
    - gobject-introspection: Fix use after free in scanner [#674]
    - vala: Check if ArrayType supports its given element-type in analyzer pass
    - valadoc: Fix some string escaping which gettext complains about

   * Bindings:
    - Update GIDL-based bindings to fix unsupported type-arguments
    - Add gnome-desktop-3.0 bindings [#668]
    - glib-2.0: Add feature_test_macro details for Time struct's methods
    - glib-2.0: Set DateTime.now () to use local time zone as the default
    - gstreamer: Cherry-pick some fixes from 0.42
    - gtk+-3.0: Update to 3.24.0
    - gtk+-4.0: Update to 3.94.0+d90e2733
    - libxml-2.0: Add missing context parameter in OutputWriteCallback
    - pango: Update to 1.42.3
    - x11: Add binding for XCreateSimpleWindow

  Vala 0.40.9
  ===========
   * Various improvements and bug fixes:
    - girparser: Actually resolve type-arguments to be able to box them if needed
    - girparser: Handle unsupported aliases which could not be fully processed
    - codegen: Free errors after returning them on GDBusMethodInvocation [#657]
    - codegen: Fix invocation of abstract/virtual methods with NoWrapper in
      compact classes
    - vala: Allow read-only properties
    - manual: Update from wiki.gnome.org

   * Bindings:
    - glib-2.0: Add Array.remove*() wrapper to avoid leaking generic elements
    - glib-2.0: Add (u)long.parse/try_parse() and float.parse/try_parse() [#649]
    - glib-2.0: Add return-type of Queue.remove*(), add HashTable.foreach_steal()
    - gtk+-3.0: Update to 3.23.2+6b6e53fd
    - gtk+-4.0: Update to 3.94.0+4e868584
    - webkit2gtk-4.0: Update to 2.20.5

  [Impact]
   * Affects all valac reverse-dependency on buildtime

  [Test Case]
   * Mass-rebuild of rdepends can be found here
     https://launchpad.net/~ricotz/+archive/ubuntu/vala-sru/+packages?batch=200&memo=0&start=0

  [Regression Potential]
   * Not immediately while it requires an rdepend rebuild to manifest.

  [Other Info]
   * Regular upstream maintenance releases are likely to happen every 1-2 months

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1803136/+subscriptions


From 1800566 at bugs.launchpad.net  Fri Dec 20 14:23:32 2019
From: 1800566 at bugs.launchpad.net (Thadeu Lima de Souza Cascardo)
Date: Fri, 20 Dec 2019 14:23:32 -0000
Subject: [Bug 1800566] Re: Make reset_devices parameter default for kdump and
 decouple kdump systemd service from the KDUMP_CMDLINE_APPEND
References: <154085493301.19676.9585082283877136471.malonedeb@gac.canonical.com>
Message-ID: <157685181508.5281.8948698931519076883.launchpad@gac.canonical.com>

** Changed in: makedumpfile (Ubuntu Disco)
       Status: Confirmed => Won't Fix

** Changed in: makedumpfile (Ubuntu Focal)
       Status: Confirmed => In Progress

** Changed in: makedumpfile (Ubuntu Eoan)
       Status: Confirmed => In Progress

** Changed in: makedumpfile (Ubuntu Bionic)
       Status: Confirmed => In Progress

** Changed in: makedumpfile (Ubuntu Xenial)
       Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1800566

Title:
  Make reset_devices parameter default for kdump and decouple kdump
  systemd service from the KDUMP_CMDLINE_APPEND

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Trusty:
  Won't Fix
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  Won't Fix
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]

  * Kdump does not configure by default the crash kernel to perform a
  device reset by default, by passing the "reset_devices" parameter.
  Also, the systemd service "kdump-tools-dump" is tightly-coupled with
  KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion.

  * Kernel has the "reset_devices" parameter that drivers can opt-in,
  and perform special activity in case this parameter is parsed from
  command-line. For example, in kdump kernels it hints the drivers that
  they are booting from a non-healthy condition and needs to issue some
  form of reset to the adapter, like clearing DMA mapping in their
  firmware for example. Users currently (kernel v5.2) are: aacraid,
  hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

  * The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only 
  reasonable case for removing it is to debug kdump itself.

  
  [Test Case]

  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'reset_devices' parameter:

  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz

  Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit
  =kdump-tools.service" to be removed.

  
  [Regression Potential]

  The regression potential is low, since it doesn't need any changes in
  makedumpfile code and we're only adding a parameter on the crash
  kernel command-line. The risks are related with bad behavior with the
  kernel when using "reset_devices", like if the driver has bugs in this
  path. It's considered safer to have the option (and this way prevent
  problems for booting a unhealthy kernel with potential stuck DMAs in
  the devices) than not having it.

  Regarding the other change, about the systemd service, it'll only
  affect users the are debugging kdump itself and it has no known
  regression potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions


From ddstreet at canonical.com  Fri Dec 20 15:51:33 2019
From: ddstreet at canonical.com (Dan Streetman)
Date: Fri, 20 Dec 2019 15:51:33 -0000
Subject: [Bug 1800566] Re: Make reset_devices parameter default for kdump and
 decouple kdump systemd service from the KDUMP_CMDLINE_APPEND
References: <154085493301.19676.9585082283877136471.malonedeb@gac.canonical.com>
Message-ID: <157685709459.5548.2838512563239976265.launchpad@gac.canonical.com>

** Changed in: makedumpfile (Ubuntu Disco)
       Status: Won't Fix => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1800566

Title:
  Make reset_devices parameter default for kdump and decouple kdump
  systemd service from the KDUMP_CMDLINE_APPEND

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Trusty:
  Won't Fix
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]

  * Kdump does not configure by default the crash kernel to perform a
  device reset by default, by passing the "reset_devices" parameter.
  Also, the systemd service "kdump-tools-dump" is tightly-coupled with
  KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion.

  * Kernel has the "reset_devices" parameter that drivers can opt-in,
  and perform special activity in case this parameter is parsed from
  command-line. For example, in kdump kernels it hints the drivers that
  they are booting from a non-healthy condition and needs to issue some
  form of reset to the adapter, like clearing DMA mapping in their
  firmware for example. Users currently (kernel v5.2) are: aacraid,
  hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

  * The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only 
  reasonable case for removing it is to debug kdump itself.

  
  [Test Case]

  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'reset_devices' parameter:

  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz

  Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit
  =kdump-tools.service" to be removed.

  
  [Regression Potential]

  The regression potential is low, since it doesn't need any changes in
  makedumpfile code and we're only adding a parameter on the crash
  kernel command-line. The risks are related with bad behavior with the
  kernel when using "reset_devices", like if the driver has bugs in this
  path. It's considered safer to have the option (and this way prevent
  problems for booting a unhealthy kernel with potential stuck DMAs in
  the devices) than not having it.

  Regarding the other change, about the systemd service, it'll only
  affect users the are debugging kdump itself and it has no known
  regression potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions


From 1800566 at bugs.launchpad.net  Fri Dec 20 18:02:37 2019
From: 1800566 at bugs.launchpad.net (Guilherme G. Piccoli)
Date: Fri, 20 Dec 2019 18:02:37 -0000
Subject: [Bug 1800566] Re: Make reset_devices parameter default for kdump
References: <154085493301.19676.9585082283877136471.malonedeb@gac.canonical.com>
Message-ID: <157686495732.3022.1529700559185111227.malone@soybean.canonical.com>

After some attempt to merge the work needed in LP #1816743 here, we
decided to split the bugs and only work the 'reset_devices' addition
here.

Cheers,


Guilherme

** Summary changed:

- Make reset_devices parameter default for kdump and decouple kdump systemd service from the KDUMP_CMDLINE_APPEND
+ Make reset_devices parameter default for kdump

** Description changed:

  [Impact]
  
  * Kdump does not configure by default the crash kernel to perform a
- device reset by default, by passing the "reset_devices" parameter. Also,
- the systemd service "kdump-tools-dump" is tightly-coupled with
- KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion.
+ device reset by default, by passing the "reset_devices" parameter.
  
  * Kernel has the "reset_devices" parameter that drivers can opt-in, and
  perform special activity in case this parameter is parsed from command-
  line. For example, in kdump kernels it hints the drivers that they are
  booting from a non-healthy condition and needs to issue some form of
  reset to the adapter, like clearing DMA mapping in their firmware for
- example. Users currently (kernel v5.2) are: aacraid, hpsa, ipr,
+ example. Users currently (kernel v5.5-rc2) are: aacraid, hpsa, ipr,
  megaraid_sas, mpt3sas, smartpqi, xenbus.
  
  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.
  
- * The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only 
- reasonable case for removing it is to debug kdump itself.
- 
- 
  [Test Case]
  
- 1) Deploy a Disco VM e.g. with uvt-kvm
+ 1) Deploy a Bionic VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'reset_devices' parameter:
  
  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz
- 
- Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit
- =kdump-tools.service" to be removed.
  
  
  [Regression Potential]
  
  The regression potential is low, since it doesn't need any changes in
  makedumpfile code and we're only adding a parameter on the crash kernel
  command-line. The risks are related with bad behavior with the kernel
  when using "reset_devices", like if the driver has bugs in this path.
  It's considered safer to have the option (and this way prevent problems
  for booting a unhealthy kernel with potential stuck DMAs in the devices)
  than not having it.
- 
- Regarding the other change, about the systemd service, it'll only affect
- users the are debugging kdump itself and it has no known regression
- potential.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1800566

Title:
  Make reset_devices parameter default for kdump

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Trusty:
  Won't Fix
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  In Progress
Status in makedumpfile source package in Focal:
  In Progress

Bug description:
  [Impact]

  * Kdump does not configure by default the crash kernel to perform a
  device reset by default, by passing the "reset_devices" parameter.

  * Kernel has the "reset_devices" parameter that drivers can opt-in,
  and perform special activity in case this parameter is parsed from
  command-line. For example, in kdump kernels it hints the drivers that
  they are booting from a non-healthy condition and needs to issue some
  form of reset to the adapter, like clearing DMA mapping in their
  firmware for example. Users currently (kernel v5.5-rc2) are: aacraid,
  hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

  [Test Case]

  1) Deploy a Bionic VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'reset_devices' parameter:

  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz

  
  [Regression Potential]

  The regression potential is low, since it doesn't need any changes in
  makedumpfile code and we're only adding a parameter on the crash
  kernel command-line. The risks are related with bad behavior with the
  kernel when using "reset_devices", like if the driver has bugs in this
  path. It's considered safer to have the option (and this way prevent
  problems for booting a unhealthy kernel with potential stuck DMAs in
  the devices) than not having it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions


From 1837886 at bugs.launchpad.net  Sat Dec 21 07:36:08 2019
From: 1837886 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 21 Dec 2019 07:36:08 -0000
Subject: [Bug 1837886] Re: kpatch 0.5.0-0ubuntu2 ADT test failure with linux
 5.3.0-0.1
References: <156405991404.18485.18350487893200706506.malonedeb@gac.canonical.com>
Message-ID: <157691376908.5798.9482019935062861996.launchpad@gac.canonical.com>

** Changed in: kpatch (Ubuntu Bionic)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1837886

Title:
  kpatch 0.5.0-0ubuntu2 ADT test failure with linux 5.3.0-0.1

Status in kpatch package in Ubuntu:
  New
Status in kpatch source package in Bionic:
  New

Bug description:
  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/k/kpatch/20190724_125410_41a25@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1837886/+subscriptions


From 1737126 at bugs.launchpad.net  Mon Dec 23 17:36:33 2019
From: 1737126 at bugs.launchpad.net (Dmitrii Shcherbakov)
Date: Mon, 23 Dec 2019 17:36:33 -0000
Subject: [Bug 1737126] Re: [sru][xenial-updates-backport] support dash "-" in
 a tag name for filters
References: <151272528648.2991.5194786224415114564.malonedeb@gac.canonical.com>
Message-ID: <157712259489.3022.250902025325038747.launchpad@soybean.canonical.com>

** Changed in: simplestreams
     Assignee: Dmitrii Shcherbakov (dmitriis) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1737126

Title:
  [sru][xenial-updates-backport] support dash "-" in a tag name for
  filters

Status in simplestreams:
  In Progress

Bug description:
  [Impact]

  Matching by fields that have a dash in their name fails ("bootloader-
  type" in this case).

  sstream-mirror --progress --max=1 --keyring=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg http://images.maas.io/ephemeral-v3/daily/ ~/mirror/images.maas.io/ephemeral-v3/daily/ 'bootloader-type=~(pxe|(^$))' 'arch=amd64' 'subarch~((ga-16.04)|(^$))' 'kflavor~((generic)|(^$))' 'content_id~((com.ubuntu.maas:daily:1:bootloader-download)|com.ubuntu.maas.daily:v3)'
  Traceback (most recent call last):
    File "/usr/bin/sstream-mirror", line 157, in <module>
      main()
    File "/usr/bin/sstream-mirror", line 112, in main
      filter_list = filters.get_filters(args.filters)
    File "/usr/lib/python3/dist-packages/simplestreams/filters.py", line 62, in get_filters
      flist.append(ItemFilter(f, noneval=noneval))
    File "/usr/lib/python3/dist-packages/simplestreams/filters.py", line 29, in __init__
      raise ValueError("Unable to parse expression %s" % content)
  ValueError: Unable to parse expression bootloader-type=~(pxe|(^$))

  [Test Case]

  This is both a test case and a reproducer on a Xenial machine:

  sstream-mirror --progress --max=1 --keyring=/usr/share/keyrings
  /ubuntu-cloudimage-keyring.gpg
  http://images.maas.io/ephemeral-v3/daily/
  ~/mirror/images.maas.io/ephemeral-v3/daily/ 'bootloader-
  type=~(pxe|(^$))' 'arch=amd64' 'subarch~((ga-16.04)|(^$))'
  'kflavor~((generic)|(^$))' 'content_id~((com.ubuntu.maas:daily:1
  :bootloader-download)|com.ubuntu.maas.daily:v3)'

  
  [Regression Potential] 

  None

  [Other Info]

  Need to backport this to be able to match tag names that contain
  dashes:

  http://bazaar.launchpad.net/~simplestreams-
  dev/simplestreams/trunk/revision/445

  commit 2df782018dda0b58f2296b981e6eef2cc08b9ab0
  Author: Lee Trager <lee.trager at canonical.com>
  Date:   Mon Oct 17 13:26:06 2016 -0700

      Allow filtered fields to contain a '-'

  diff --git a/simplestreams/filters.py b/simplestreams/filters.py
  index 5e93ce4..3818949 100644
  --- a/simplestreams/filters.py
  +++ b/simplestreams/filters.py
  @@ -22,7 +22,7 @@ import re

   class ItemFilter(object):
       def __init__(self, content, noneval=""):
  -        rparsefmt = r"(\w+)[ ]*([!]{0,1}[=~])[ ]*(.*)[ ]*$"
  +        rparsefmt = r"([\w|\-]+)[ ]*([!]{0,1}[=~])[ ]*(.*)[ ]*$"
           parsed = re.match(rparsefmt, content)

           if not parsed:

To manage notifications about this bug go to:
https://bugs.launchpad.net/simplestreams/+bug/1737126/+subscriptions


From steve.langasek at canonical.com  Tue Dec 24 03:35:23 2019
From: steve.langasek at canonical.com (Steve Langasek)
Date: Tue, 24 Dec 2019 03:35:23 -0000
Subject: [Bug 1810154] Re: ply_boot_client_process_incoming_replies: Assertion
 `request_node != NULL' failed
References: <154626378387.25575.13007639149234339603.malonedeb@chaenomeles.canonical.com>
Message-ID: <157715852342.2574.3491444507113543103.malone@soybean.canonical.com>

I've confirmed that after upgrade to plymouth from unstable, the
testcase passes (and zfs initramfs decryption works now in Ubuntu
19.10).

** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1810154

Title:
  ply_boot_client_process_incoming_replies: Assertion `request_node !=
  NULL' failed

Status in plymouth package in Ubuntu:
  Fix Released
Status in plymouth source package in Eoan:
  Fix Committed

Bug description:
  [SRU Justification]
  An Ubuntu-specific patch causes a crash in plymouth that does not occur upstream and breaks one of the standard use cases of the plymouth client, to prompt for passwords.  While the specific error does not affect password prompting for LUKS due to a different invocation of plymouth, it does break password prompting for ZFS encryption, leaving users at an initramfs prompt on boot.

  [Test case]
  1. Change to VT3 on your system (so that you are not under a graphical login session) and log in.
  2. As root, run: plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid --tty=/dev/tty8; chvt 8; plymouth --show-splash; plymouth ask-for-password --prompt "This is a password prompt" --command="/bin/cat"; plymouth quit; chvt 3
  3. Observe that you are immediately returned to VT3 without being shown a password prompt, and the error message "ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed" is printed on the console.
  4. Install the plymouth package from eoan-proposed.
  5. Repeat step 2.
  6. Observe that you are shown a password prompt.
  7. Type something into the field and hit enter.
  8. Observe that you are returned to VT3 and the text you typed in step 7 has been echoed to the screen, with no error messages.

  [Regression potential]
  This is an Ubuntu-specific bug due to missing handling of a new upstream message type in an Ubuntu-specific patch.  This fixes a crash and has minimal risk of regression.

  
  ubuntu cosmic
  plymouth 0.9.3-1ubuntu10
  initramfs-tools 0.131ubuntu15

  I'm trying to get a password prompt working in the initramfs via
  plymouth, but I get an assertion error.

  This is the sample command I'm running:
  plymouth --debug ask-for-password --command=/bin/cat --prompt "Type something"

  And this is the output I get:
  [./plymouth.c:463]                           on_password_request:Password request
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [./plymouth.c:430]                   on_password_request_execute:executing password request (command /bin/cat)
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  [ply-event-loop.c:759]               ply_event_loop_stop_watching_fd:stopping watching fd 6
  [ply-event-loop.c:775]               ply_event_loop_stop_watching_fd:removing destination for fd 6
  plymouth: ./ply-boot-client.c:272: ply_boot_client_process_incoming_replies: Assertion `request_node != NULL' failed.
  Aborted

  plymouth --ping returns 0. It doesn't matter which --command I try.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154/+subscriptions


From 1856574 at bugs.launchpad.net  Wed Dec 25 05:33:26 2019
From: 1856574 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 25 Dec 2019 05:33:26 -0000
Subject: [Bug 1856574] Re: removal of various autopilot packages
References: <157650561253.19251.3333137627024153118.malonedeb@wampee.canonical.com>
Message-ID: <157725200747.3160.13890038173642513463.launchpad@soybean.canonical.com>

** Changed in: python-fixtures (Ubuntu)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856574

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  Fix Committed
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions


From 1856574 at bugs.launchpad.net  Wed Dec 25 05:41:12 2019
From: 1856574 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 25 Dec 2019 05:41:12 -0000
Subject: [Bug 1856574] Re: removal of various autopilot packages
References: <157650561253.19251.3333137627024153118.malonedeb@wampee.canonical.com>
Message-ID: <157725247382.27216.4158337801008256397.launchpad@chaenomeles.canonical.com>

** Changed in: python-testtools (Ubuntu)
       Status: New => Fix Committed

** Changed in: python-fixtures (Ubuntu)
   Importance: Undecided => Medium

** Changed in: python-testtools (Ubuntu)
   Importance: Undecided => High

** Changed in: python-testtools (Ubuntu)
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856574

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  Fix Committed
Status in python-testtools package in Ubuntu:
  Fix Committed

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions


From ppolihron at gmail.com  Thu Dec 26 11:02:11 2019
From: ppolihron at gmail.com (APolihron)
Date: Thu, 26 Dec 2019 11:02:11 -0000
Subject: [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157735813119.5353.14222487026559467362.malone@gac.canonical.com>

The fix is only for the HDMI output? The same issue is with displayport
:(

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions


From ppolihron at gmail.com  Thu Dec 26 11:03:58 2019
From: ppolihron at gmail.com (APolihron)
Date: Thu, 26 Dec 2019 11:03:58 -0000
Subject: [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157735823896.15141.10442876868022901915.malone@wampee.canonical.com>

This fix will fix this issue also?
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1334329

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions


From 1857641 at bugs.launchpad.net  Thu Dec 26 22:45:48 2019
From: 1857641 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 26 Dec 2019 22:45:48 -0000
Subject: [Bug 1857641] [NEW] Sync mediawiki 1:1.31.6-1 (universe) from Debian
 unstable (main)
References: <157740034545.27324.1052360345713343137.malonedeb@chaenomeles.canonical.com>
Message-ID: <157740034947.3464.16515192574781237739.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Kunal Mehta (legoktm):

Please sync mediawiki 1:1.31.6-1 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * debian/tests/control: set allow-stderr; sudo on some architectures will
    report being unable to set RLIMIT_CORE in autopkgtests due to specifics
    of the testing infrastructure. The command otherwise succeeds (without
    setting the limits).

Patch was included in Debian version 1:1.31.6-1.

Changelog entries since current focal version 1:1.31.5-3ubuntu1:

mediawiki (1:1.31.6-1) unstable; urgency=medium

  * New upstream version 1.31.6, fixing CVE-2019-19709.
    * Drop Postgres patches merged upstream
  * Suppress a bunch of lintian warnings that are ignored on purpose
  * Sync d/upstream/signing-key.asc with upstream
  * autopkgtests: set allow-stderr for all tests that use sudo. Thanks
    to Mathieu Trudel-Lapierre for reporting and fixing in Ubuntu.
    (Closes: #946665)

 -- Kunal Mehta <legoktm at debian.org>  Thu, 19 Dec 2019 13:20:56 -0800

** Affects: mediawiki (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync mediawiki 1:1.31.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1857641
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1857641 at bugs.launchpad.net  Sat Dec 28 08:32:38 2019
From: 1857641 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 28 Dec 2019 08:32:38 -0000
Subject: [Bug 1857641] Re: Sync mediawiki 1:1.31.6-1 (universe) from Debian
 unstable (main)
References: <157740034545.27324.1052360345713343137.malonedeb@chaenomeles.canonical.com>
Message-ID: <157752195911.5922.17214521004295601099.launchpad@gac.canonical.com>

** Changed in: mediawiki (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1857641

Title:
  Sync mediawiki 1:1.31.6-1 (universe) from Debian unstable (main)

Status in mediawiki package in Ubuntu:
  New

Bug description:
  Please sync mediawiki 1:1.31.6-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * debian/tests/control: set allow-stderr; sudo on some architectures will
      report being unable to set RLIMIT_CORE in autopkgtests due to specifics
      of the testing infrastructure. The command otherwise succeeds (without
      setting the limits).

  Patch was included in Debian version 1:1.31.6-1.

  Changelog entries since current focal version 1:1.31.5-3ubuntu1:

  mediawiki (1:1.31.6-1) unstable; urgency=medium

    * New upstream version 1.31.6, fixing CVE-2019-19709.
      * Drop Postgres patches merged upstream
    * Suppress a bunch of lintian warnings that are ignored on purpose
    * Sync d/upstream/signing-key.asc with upstream
    * autopkgtests: set allow-stderr for all tests that use sudo. Thanks
      to Mathieu Trudel-Lapierre for reporting and fixing in Ubuntu.
      (Closes: #946665)

   -- Kunal Mehta <legoktm at debian.org>  Thu, 19 Dec 2019 13:20:56 -0800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediawiki/+bug/1857641/+subscriptions


From 1847570 at bugs.launchpad.net  Sat Dec 28 11:22:23 2019
From: 1847570 at bugs.launchpad.net (Efthimios Chaskaris)
Date: Sat, 28 Dec 2019 11:22:23 -0000
Subject: [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157753214396.3421.15710477827122304665.malone@soybean.canonical.com>

Release 'eoan-proposed' for 'pulseaudio' was not found

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions


From mgerdzhev at gmail.com  Sun Dec 29 09:08:18 2019
From: mgerdzhev at gmail.com (Martin Gerdzhev)
Date: Sun, 29 Dec 2019 09:08:18 -0000
Subject: [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157761049868.2981.11796288895681245973.malone@soybean.canonical.com>

I have 2 displayport monitors that have no speakers and this is
happening all the time. It also happens when the resolution changes or
the monitor scaling is changed.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions


From 1857819 at bugs.launchpad.net  Sun Dec 29 15:44:45 2019
From: 1857819 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 29 Dec 2019 15:44:45 -0000
Subject: [Bug 1857819] [NEW] Sync ocrmypdf 9.1.0+dfsg-1 (universe) from Debian
 unstable (main)
References: <157763428262.14604.12073260710446931807.malonedeb@wampee.canonical.com>
Message-ID: <157763428594.5393.1362427738475457442.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Amr Ibrahim (amribrahim1987):

Please sync ocrmypdf 9.1.0+dfsg-1 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Pull the 9.0.5 changes for Python 3.8 compatibility.
Python 3.8 compatibility is in 9.1.0.

Changelog entries since current focal version 9.0.3+dfsg-1ubuntu1:

ocrmypdf (9.1.0+dfsg-1) unstable; urgency=medium

  * New upstream release (Closes: #944534).
    - Tighten build-dep on python3-pikepdf to require 1.7.0.

 -- Sean Whitton <spwhitton at spwhitton.name>  Tue, 12 Nov 2019 10:00:24
-0700

** Affects: ocrmypdf (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync ocrmypdf 9.1.0+dfsg-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1857819
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From daniel.van.vugt at canonical.com  Mon Dec 30 02:03:44 2019
From: daniel.van.vugt at canonical.com (Daniel van Vugt)
Date: Mon, 30 Dec 2019 02:03:44 -0000
Subject: [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157767142459.27324.11044839369892661858.malone@chaenomeles.canonical.com>

Hmm, upstream have now written a proper fix destined for PulseAudio 14:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/225

Maybe we should change to that.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions


From 1847570 at bugs.launchpad.net  Mon Dec 30 07:36:01 2019
From: 1847570 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 30 Dec 2019 07:36:01 -0000
Subject: [Bug 1847570] [NEW] PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157769136213.6040.14422182909708031167.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Daniel van Vugt (vanvugt):

[Impact]

On my freshly installed eoan system I have two output devices:
- HDMI/DisplayPort 2 - GK208 ...
- Line Out - Family 17h ...

When I login into the system pulseaudio always select the "wrong"
one (HDMI) and I need to go to gnome-settings/Sound/Output Device
and switch to "line out". This applies to every login/logout not
just reboots.

[Test Case]

0. Plug in a monitor that supports HDMI audio (one that appears in your
Settings>Sound)

1. Log out and in again.

Verify the default audio device in Settings is still speakers or
headphones. Not the monitor's HDMI audio device.

[Regression Potential]

Low. The fix proposed just reverts to the same code used in PulseAudio
12 and earlier. It has also been released and verified on focal already.

[Workaround]

Comment out:

load-module module-switch-on-port-available
load-module module-switch-on-connect

from /etc/pulse/default.pa

** Affects: pulseaudio
     Importance: Unknown
         Status: New

** Affects: pulseaudio (Ubuntu)
     Importance: Medium
     Assignee: Daniel van Vugt (vanvugt)
         Status: Fix Released

** Affects: pulseaudio (Ubuntu Eoan)
     Importance: Medium
     Assignee: Daniel van Vugt (vanvugt)
         Status: Fix Committed

** Affects: pulseaudio (Ubuntu Focal)
     Importance: Medium
     Assignee: Daniel van Vugt (vanvugt)
         Status: Fix Released


** Tags: eoan focal regression-release
-- 
PulseAudio automatically switches to HDMI sound output on login
https://bugs.launchpad.net/bugs/1847570
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From daniel.van.vugt at canonical.com  Mon Dec 30 07:37:56 2019
From: daniel.van.vugt at canonical.com (Daniel van Vugt)
Date: Mon, 30 Dec 2019 07:37:56 -0000
Subject: [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157769147692.27659.11672827003638417335.malone@chaenomeles.canonical.com>

It appears the upstream fix in master (PulseAudio 14) does not apply and
can't work in PulseAudio 13 so we will stick with the revert in
PulseAudio 13. The patch in comment #34 is still awaiting
sponsorship/publishing.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions


From 1856690 at bugs.launchpad.net  Mon Dec 30 12:08:31 2019
From: 1856690 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 30 Dec 2019 12:08:31 -0000
Subject: [Bug 1856690] [NEW] [SRU] Segmentation fault after close polkit window
References: <157658444068.27926.14426067731765433805.malonedeb@chaenomeles.canonical.com>
Message-ID: <157770771175.2981.13522740672583474037.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by handsome_feng (feng-kylin):

[Impact]

Segmentation fault after close polkit window in UbuntuKylin 19.10. This
cause the user can't authenticate after close the polkit window.

[Test Case]

1. Open ubuntu-kylin-software-center(or other software which need privilege)
2. Choose an app to install by click the install button under the app icon.
3. Close the authentication dialog.
4. Choose an app to install again.

expect:
The authentication dialog appeared and can install the app after enter the password.

actual:
Nothing happened.

[Regression Potential]

1. This patch references what others(such as polkit-kde-agent-1) have
done

2. This patch is well test in my PPA: https://launchpad.net/~feng-
kylin/+archive/ubuntu/1910test for a while.

** Affects: ukui-biometric-auth (Ubuntu)
     Importance: High
         Status: Fix Released

-- 
[SRU] Segmentation fault after close polkit window
https://bugs.launchpad.net/bugs/1856690
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From jianfengli at ubuntukylin.com  Mon Dec 30 12:08:49 2019
From: jianfengli at ubuntukylin.com (handsome_feng)
Date: Mon, 30 Dec 2019 12:08:49 -0000
Subject: [Bug 1856690] Re: [SRU] Segmentation fault after close polkit window
References: <157658444068.27926.14426067731765433805.malonedeb@chaenomeles.canonical.com>
Message-ID: <157770772949.27812.3195873958760617686.malone@chaenomeles.canonical.com>

** Attachment added: "buildlog_ubuntu-eoan-amd64.ukui-biometric-auth_1.0.3-2ubuntu0.1_BUILDING.txt.gz"
   https://bugs.launchpad.net/ubuntu/+source/ukui-biometric-auth/+bug/1856690/+attachment/5316506/+files/buildlog_ubuntu-eoan-amd64.ukui-biometric-auth_1.0.3-2ubuntu0.1_BUILDING.txt.gz

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856690

Title:
  [SRU] Segmentation fault after close polkit window

Status in ukui-biometric-auth package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Segmentation fault after close polkit window in UbuntuKylin 19.10.
  This cause the user can't authenticate after close the polkit window.

  [Test Case]

  1. Open ubuntu-kylin-software-center(or other software which need privilege)
  2. Choose an app to install by click the install button under the app icon.
  3. Close the authentication dialog.
  4. Choose an app to install again.

  expect:
  The authentication dialog appeared and can install the app after enter the password.

  actual:
  Nothing happened.

  [Regression Potential]

  1. This patch references what others(such as polkit-kde-agent-1) have
  done

  2. This patch is well test in my PPA: https://launchpad.net/~feng-
  kylin/+archive/ubuntu/1910test for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ukui-biometric-auth/+bug/1856690/+subscriptions


From jianfengli at ubuntukylin.com  Mon Dec 30 12:09:29 2019
From: jianfengli at ubuntukylin.com (handsome_feng)
Date: Mon, 30 Dec 2019 12:09:29 -0000
Subject: [Bug 1856690] Re: [SRU] Segmentation fault after close polkit window
References: <157658444068.27926.14426067731765433805.malonedeb@chaenomeles.canonical.com>
Message-ID: <157770776953.27812.2216901524975791099.malone@chaenomeles.canonical.com>

** Patch added: "ukui-biometric-auth_1.0.3-2ubuntu0.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/ukui-biometric-auth/+bug/1856690/+attachment/5316507/+files/ukui-biometric-auth_1.0.3-2ubuntu0.1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856690

Title:
  [SRU] Segmentation fault after close polkit window

Status in ukui-biometric-auth package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Segmentation fault after close polkit window in UbuntuKylin 19.10.
  This cause the user can't authenticate after close the polkit window.

  [Test Case]

  1. Open ubuntu-kylin-software-center(or other software which need privilege)
  2. Choose an app to install by click the install button under the app icon.
  3. Close the authentication dialog.
  4. Choose an app to install again.

  expect:
  The authentication dialog appeared and can install the app after enter the password.

  actual:
  Nothing happened.

  [Regression Potential]

  1. This patch references what others(such as polkit-kde-agent-1) have
  done

  2. This patch is well test in my PPA: https://launchpad.net/~feng-
  kylin/+archive/ubuntu/1910test for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ukui-biometric-auth/+bug/1856690/+subscriptions


From jianfengli at ubuntukylin.com  Mon Dec 30 12:17:05 2019
From: jianfengli at ubuntukylin.com (handsome_feng)
Date: Mon, 30 Dec 2019 12:17:05 -0000
Subject: [Bug 1856690] Re: [SRU] Segmentation fault after close polkit window
References: <157658444068.27926.14426067731765433805.malonedeb@chaenomeles.canonical.com>
Message-ID: <157770822643.5239.16897885192486002921.launchpad@gac.canonical.com>

** Also affects: ukui-biometric-auth (Ubuntu Eoan)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856690

Title:
  [SRU] Segmentation fault after close polkit window

Status in ukui-biometric-auth package in Ubuntu:
  Fix Released
Status in ukui-biometric-auth source package in Eoan:
  New

Bug description:
  [Impact]

  Segmentation fault after close polkit window in UbuntuKylin 19.10.
  This cause the user can't authenticate after close the polkit window.

  [Test Case]

  1. Open ubuntu-kylin-software-center(or other software which need privilege)
  2. Choose an app to install by click the install button under the app icon.
  3. Close the authentication dialog.
  4. Choose an app to install again.

  expect:
  The authentication dialog appeared and can install the app after enter the password.

  actual:
  Nothing happened.

  [Regression Potential]

  1. This patch references what others(such as polkit-kde-agent-1) have
  done

  2. This patch is well test in my PPA: https://launchpad.net/~feng-
  kylin/+archive/ubuntu/1910test for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ukui-biometric-auth/+bug/1856690/+subscriptions


From 1857819 at bugs.launchpad.net  Tue Dec 31 09:57:27 2019
From: 1857819 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 31 Dec 2019 09:57:27 -0000
Subject: [Bug 1857819] Re: Sync ocrmypdf 9.1.0+dfsg-1 (universe) from Debian
 unstable (main)
References: <157763428262.14604.12073260710446931807.malonedeb@wampee.canonical.com>
Message-ID: <157778624927.27526.5190405792884893669.launchpad@chaenomeles.canonical.com>

** Changed in: ocrmypdf (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1857819

Title:
  Sync ocrmypdf 9.1.0+dfsg-1 (universe) from Debian unstable (main)

Status in ocrmypdf package in Ubuntu:
  New

Bug description:
  Please sync ocrmypdf 9.1.0+dfsg-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Pull the 9.0.5 changes for Python 3.8 compatibility.
  Python 3.8 compatibility is in 9.1.0.

  Changelog entries since current focal version 9.0.3+dfsg-1ubuntu1:

  ocrmypdf (9.1.0+dfsg-1) unstable; urgency=medium

    * New upstream release (Closes: #944534).
      - Tighten build-dep on python3-pikepdf to require 1.7.0.

   -- Sean Whitton <spwhitton at spwhitton.name>  Tue, 12 Nov 2019 10:00:24
  -0700

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ocrmypdf/+bug/1857819/+subscriptions


From 1856690 at bugs.launchpad.net  Tue Dec 31 10:07:19 2019
From: 1856690 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 31 Dec 2019 10:07:19 -0000
Subject: [Bug 1856690] Re: [SRU] Segmentation fault after close polkit window
References: <157658444068.27926.14426067731765433805.malonedeb@chaenomeles.canonical.com>
Message-ID: <157778684147.27216.13065280426067463716.launchpad@chaenomeles.canonical.com>

** Changed in: ukui-biometric-auth (Ubuntu Eoan)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856690

Title:
  [SRU] Segmentation fault after close polkit window

Status in ukui-biometric-auth package in Ubuntu:
  Fix Released
Status in ukui-biometric-auth source package in Eoan:
  New

Bug description:
  [Impact]

  Segmentation fault after close polkit window in UbuntuKylin 19.10.
  This cause the user can't authenticate after close the polkit window.

  [Test Case]

  1. Open ubuntu-kylin-software-center(or other software which need privilege)
  2. Choose an app to install by click the install button under the app icon.
  3. Close the authentication dialog.
  4. Choose an app to install again.

  expect:
  The authentication dialog appeared and can install the app after enter the password.

  actual:
  Nothing happened.

  [Regression Potential]

  1. This patch references what others(such as polkit-kde-agent-1) have
  done

  2. This patch is well test in my PPA: https://launchpad.net/~feng-
  kylin/+archive/ubuntu/1910test for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ukui-biometric-auth/+bug/1856690/+subscriptions


From 1847570 at bugs.launchpad.net  Tue Dec 31 10:04:05 2019
From: 1847570 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 31 Dec 2019 10:04:05 -0000
Subject: [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound
 output on login
References: <157069050661.1321.12599075161737098722.malonedeb@chaenomeles.canonical.com>
Message-ID: <157778664669.27659.15347977250823694831.launchpad@chaenomeles.canonical.com>

** Changed in: pulseaudio (Ubuntu Eoan)
       Status: Fix Committed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Triaged
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions


