From 1918855 at bugs.launchpad.net  Mon Aug  2 02:12:03 2021
From: 1918855 at bugs.launchpad.net (Daniel van Vugt)
Date: Mon, 02 Aug 2021 02:12:03 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162787032351.6233.1694552620287873945.malone@soybean.canonical.com>

I've tried to give this bug a more unique title to distinguish it from
the other SIGABRTs:

  https://bugs.launchpad.net/ubuntu/+source/xorg-
server?field.searchtext=SIGABRT

Also note the stack trace in the Bug Description is not unique. It
should probably be deleted. Only stack traces with debug symbols are
useful with Xorg.

** Summary changed:

- Xorg xserver got signal 6 to abort
+ Xorg crashed with SIGABRT when under memory pressure

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1902820 at bugs.launchpad.net  Mon Aug  2 02:39:29 2021
From: 1902820 at bugs.launchpad.net (Bin Li)
Date: Mon, 02 Aug 2021 02:39:29 -0000
Subject: [Bug 1902820] Re: [MIR] oem-sutton.newell-canyon-meta
References: <160446515007.313.3017689582058793507.malonedeb@chaenomeles.canonical.com>
Message-ID: <162787196947.17862.16179036569421154601.malone@chaenomeles.canonical.com>

Attach oem-sutton.newell-canyon-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Patch removed: "oem-sutton.newell-canyon-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1902820/+attachment/5514856/+files/oem-sutton.newell-canyon-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-canyon-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1902820/+attachment/5515170/+files/oem-sutton.newell-canyon-meta_20.04~ubuntu1.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/1902820

Title:
  [MIR] oem-sutton.newell-canyon-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-canyon-meta for focal:
      git clone -b newell.canyon-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkCentre M75s/t Gen 2.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkCentre M75s/t Gen 2.
  oem-sutton.newell-canyon-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202010-28340
  https://ubuntu.com/certified/202010-28342

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1902820/+subscriptions



From 1893616 at bugs.launchpad.net  Mon Aug  2 02:37:59 2021
From: 1893616 at bugs.launchpad.net (Bin Li)
Date: Mon, 02 Aug 2021 02:37:59 -0000
Subject: [Bug 1893616] Re: [MIR] oem-sutton.simon-barbara-meta
References: <159885993002.21231.11327398475551015259.malonedeb@chaenomeles.canonical.com>
Message-ID: <162787188036.13034.15151872287812317314.malone@soybean.canonical.com>

Attach oem-sutton.simon-barbara-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Patch removed: "oem-sutton.simon-barbara-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1893616/+attachment/5514857/+files/oem-sutton.simon-barbara-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.simon-barbara-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1893616/+attachment/5515169/+files/oem-sutton.simon-barbara-meta_20.04~ubuntu1.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/1893616

Title:
  [MIR] oem-sutton.simon-barbara-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-barbara-meta for focal:
      git clone -b simon.barbara-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkStation P330.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkStation P330.
  oem-sutton.simon-barbara-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202008-28190

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893616/+subscriptions



From 1919451 at bugs.launchpad.net  Mon Aug  2 07:30:34 2021
From: 1919451 at bugs.launchpad.net (Frank Heimes)
Date: Mon, 02 Aug 2021 07:30:34 -0000
Subject: [Bug 1919451] Re: Update (python-)zhmcclient to latest release
References: <161598044626.18813.3480195737308253543.malonedeb@soybean.canonical.com>
Message-ID: <162788943562.18232.1480879984433235948.launchpad@gac.canonical.com>

** Description changed:

  [Impact]
  
  In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM LinuxONE
  III (or newer) machines/LPARs from within a MAAS controller, the
  python3-zhmcclient libraray (>= v0.29) is needed, to provide all the
  functions required for controlling the HMC.
  
  [Test Plan]
   * setup a MAAS controller inside a LPAR
   * use that controller to deploy a new Ubuntu Server instance in an additional LPAR
   * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR)
   * Power-cycle the LPAR instance
   * Power-cycle the KVM instance
-  * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
+  * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
  https://github.com/zhmcclient/python-zhmcclient/tree/master/examples
  
  Also get confirmation from the MAAS team that things are working as
  expected.
  
  [Where problems could occur]
  
  This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller.
  This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either.
+ 
+ Reviewing the changes/commits starting from 0.28 to 0.31 (68 + 37 + 27 +
+ 15 commits) let me think that these are largely unintrusive, just a few
+ new features were added (like DPM Capacity Groups), the docs, examples
+ and lots of meta updated, error and exception handling refined
+ <important>, and last but not least several important bugs fixed (for
+ installation, .find for objects <again important>, certificates, missing
+ argument in method) - some of them were identified during the
+ development of DPM/LPAR support in MAAS earlier this year (for example
+ LP#1916475).
+ 
+ Therefore, and because the zhmcclient is not wide-spread yet (since MAAS
+ v3.0 is the first version that can make use of it and was just made
+ available on June the 22nd), it's for accessing and managing Z systems
+ only via the HMC API, which not many organizations allow (in general -
+ for security reasons) and because v0.31 was the version that was already
+ used for development _nd final product testing (these days as a git
+ clone), makes me rating the regression risk as low.
  
  [Other Info]
  * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z
  * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04
  * The new package dependencies are fulfilled in Focal:
    - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main)
    - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main)
  
  === Original description ===
  
  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions work,
  like especially storage group support.
  
  The latest is package is v0.27 on hirsute and v0.22 on focal.
  
  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731
  
  Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was created at all.
  
  The updated package is especially needed for focal, since focal is the
  recommended base distro for MAAS DPM/LPAR, hence this would require a
  special SRU (for this package version bump).

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

Title:
  Update (python-)zhmcclient to latest release

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zhmcclient package in Ubuntu:
  Fix Released
Status in zhmcclient source package in Focal:
  Incomplete
Status in zhmcclient source package in Hirsute:
  New

Bug description:
  [Impact]

  In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM
  LinuxONE III (or newer) machines/LPARs from within a MAAS controller,
  the python3-zhmcclient libraray (>= v0.29) is needed, to provide all
  the functions required for controlling the HMC.

  [Test Plan]
   * setup a MAAS controller inside a LPAR
   * use that controller to deploy a new Ubuntu Server instance in an additional LPAR
   * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR)
   * Power-cycle the LPAR instance
   * Power-cycle the KVM instance
   * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
  https://github.com/zhmcclient/python-zhmcclient/tree/master/examples

  Also get confirmation from the MAAS team that things are working as
  expected.

  [Where problems could occur]

  This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller.
  This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either.

  Reviewing the changes/commits starting from 0.28 to 0.31 (68 + 37 + 27
  + 15 commits) let me think that these are largely unintrusive, just a
  few new features were added (like DPM Capacity Groups), the docs,
  examples and lots of meta updated, error and exception handling
  refined <important>, and last but not least several important bugs
  fixed (for installation, .find for objects <again important>,
  certificates, missing argument in method) - some of them were
  identified during the development of DPM/LPAR support in MAAS earlier
  this year (for example LP#1916475).

  Therefore, and because the zhmcclient is not wide-spread yet (since
  MAAS v3.0 is the first version that can make use of it and was just
  made available on June the 22nd), it's for accessing and managing Z
  systems only via the HMC API, which not many organizations allow (in
  general - for security reasons) and because v0.31 was the version that
  was already used for development _nd final product testing (these days
  as a git clone), makes me rating the regression risk as low.

  [Other Info]
  * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z
  * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04
  * The new package dependencies are fulfilled in Focal:
    - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main)
    - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main)

  === Original description ===

  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions
  work, like especially storage group support.

  The latest is package is v0.27 on hirsute and v0.22 on focal.

  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731

  Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was created at all.

  The updated package is especially needed for focal, since focal is the
  recommended base distro for MAAS DPM/LPAR, hence this would require a
  special SRU (for this package version bump).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions



From 1919451 at bugs.launchpad.net  Mon Aug  2 09:51:53 2021
From: 1919451 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Mon, 02 Aug 2021 09:51:53 -0000
Subject: [Bug 1919451] Re: Update (python-)zhmcclient to latest release
References: <161598044626.18813.3480195737308253543.malonedeb@soybean.canonical.com>
Message-ID: <162789791358.10439.10585098825847656004.malone@chaenomeles.canonical.com>

Thank you Robie for your thorough review and detailed comments &
references.

Thank you Frank for improving upon the original test plan, your
volunteering to help with the verification on real hardware and for your
review and comments regarding the changes.

I also went through the changelog (https://github.com/zhmcclient/python-
zhmcclient/blob/9270ac306586b235751d432cf4a7bd4cfac84c0d/docs/changes.rst)
since 0.22 (i.e. Focal+) that lists a few "incompatible changes" that we
need to be aware of and watch out for:

0.24.0
* Operations that resulted in HTTP status 403, reason 1 ("The user under which the API request was authenticated does not have the required authority to perform the requested action.") so far raised ServerAuthError. However, that exception does not represent that situation properly, because the login user is actually properly authenticated. The handling of this case was changed to now raise HTTPError instead of ServerAuthError. This change is only incompatible to users of the zhmcclient API who have code handling this exception specifically.
=> Tiny API change in the error handling.

0.28.0
* Removed the installed scripts cpcdata and cpcinfo and added them as cpcdata.py and cpcinfo.py to the examples folder.
=> Moving of (example) scripts to a different folder, but they are still available.

0.31.0
* Method 'NotificationReceiver.notifications()' now raises JMS errors returned by the HMC as a new exception 'NotificationJMSError'. JSON parse errors are now raised as a new exception 'NotificationParseError'. Both new exceptions are based on a new base exception 'NotificationError'. (issue #770)
=> Extension of error handling API.

* By default, the zhmcclient now verifies the HMC certificate using the CA certificates in the Python 'certifi' package. This can be controlled with a new 'verify_cert' init parameter to the 'zhmcclient.Session' class. (issue #779)
=> Checking of HMC certificates by default, that can easily be disabled using the 'verify_cert' parameter.

* The 'properties' attribute of the resource classes (e.g. 'Partition') now is an immutable 'DictView' object in order to enforce the stated rule that that callers must not modify the properties dictionary. If your code used to make such modifications nevertheless, it will now get a 'TypeError' or 'AttributeError' exception, dependent on the nature of the modification.
=> This change was reverted in debian/patches/0001-Revert-Changed-properties-attribute-to-be-immutable.patch for compatibility reasons (i.e. missing python immutable-views dependency).

Summary:
- 2 tiny changes in the error handling API
- 1 change of example script installation location
- 1 changed default, that can be controlled via 'verify_cert' parameter
- 1 reverted change that does not affect our users

As Frank stated, the primary user of this package is MAAS v3.0, that was
developed and tested with this newer version in mind already. Apart from
that the use case of zhmc-client is very small with few (if any at all)
external users. Therefore we do not expect to break anybody by
introducing those changes.

I've uploaded the version bump to Hirsute as well, albeit we expect very
little (if any) usage outside the LTS releases. It is included in
Impish/devel already.

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

Title:
  Update (python-)zhmcclient to latest release

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zhmcclient package in Ubuntu:
  Fix Released
Status in zhmcclient source package in Focal:
  Incomplete
Status in zhmcclient source package in Hirsute:
  New

Bug description:
  [Impact]

  In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM
  LinuxONE III (or newer) machines/LPARs from within a MAAS controller,
  the python3-zhmcclient libraray (>= v0.29) is needed, to provide all
  the functions required for controlling the HMC.

  [Test Plan]
   * setup a MAAS controller inside a LPAR
   * use that controller to deploy a new Ubuntu Server instance in an additional LPAR
   * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR)
   * Power-cycle the LPAR instance
   * Power-cycle the KVM instance
   * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
  https://github.com/zhmcclient/python-zhmcclient/tree/master/examples

  Also get confirmation from the MAAS team that things are working as
  expected.

  [Where problems could occur]

  This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller.
  This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either.

  Reviewing the changes/commits starting from 0.28 to 0.31 (68 + 37 + 27
  + 15 commits) let me think that these are largely unintrusive, just a
  few new features were added (like DPM Capacity Groups), the docs,
  examples and lots of meta updated, error and exception handling
  refined <important>, and last but not least several important bugs
  fixed (for installation, .find for objects <again important>,
  certificates, missing argument in method) - some of them were
  identified during the development of DPM/LPAR support in MAAS earlier
  this year (for example LP#1916475).

  Therefore, and because the zhmcclient is not wide-spread yet (since
  MAAS v3.0 is the first version that can make use of it and was just
  made available on June the 22nd), it's for accessing and managing Z
  systems only via the HMC API, which not many organizations allow (in
  general - for security reasons) and because v0.31 was the version that
  was already used for development _nd final product testing (these days
  as a git clone), makes me rating the regression risk as low.

  [Other Info]
  * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z
  * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04
  * The new package dependencies are fulfilled in Focal:
    - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main)
    - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main)

  === Original description ===

  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions
  work, like especially storage group support.

  The latest is package is v0.27 on hirsute and v0.22 on focal.

  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731

  Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was created at all.

  The updated package is especially needed for focal, since focal is the
  recommended base distro for MAAS DPM/LPAR, hence this would require a
  special SRU (for this package version bump).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions



From 1876620 at bugs.launchpad.net  Mon Aug  2 12:30:10 2021
From: 1876620 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Mon, 02 Aug 2021 12:30:10 -0000
Subject: [Bug 1876620] Re: Enable riscv64 build
References: <158853719561.13785.17729435717986557479.malonedeb@gac.canonical.com>
Message-ID: <162790741065.16632.12553450533734231854.malone@chaenomeles.canonical.com>

To enable RISC-V you need GRUB 2.06 plus this series:

[PATCH v2 0/7] Add LoadFile2 and riscv Linux loader
https://lists.gnu.org/archive/html/grub-devel/2021-06/msg00006.html

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

Title:
  Enable riscv64 build

Status in grub2 package in Ubuntu:
  New

Bug description:
  RISC-V EFI support is not yet in the Linux kernel (ca. 5.8:
  https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader
  support needs to happen with the kernel
  (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html),
  GRUB2 already has RISC-V EFI support.  It can't currently boot
  anything, but it is a valid UEFI application and displays a pretty
  menu.

  Please see the attached debdiff.  Of note:

  * grub2 requires efibootmgr and efivar.  I've filed Debian bugs to
  enable riscv64 for them (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=959499 respectively), but if this is actioned
  before those end up happening, it's a simple Architecture: update on
  each.

  * riscv-default-platform.patch: Upstreamed, allows `grub-install` to
  work without --platform.

  * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer"
  failure.

  * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv
  support; not sure if this should be integrated into ubuntu-
  linuxefi.patch.

  * Tested on qemu-system-riscv64 focal.

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



From 1876620 at bugs.launchpad.net  Mon Aug  2 12:40:24 2021
From: 1876620 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Mon, 02 Aug 2021 12:40:24 -0000
Subject: [Bug 1876620] Re: Enable riscv64 build
References: <158853719561.13785.17729435717986557479.malonedeb@gac.canonical.com>
Message-ID: <162790802467.21957.16811795151459643286.launchpad@gac.canonical.com>

** Tags removed: patch
** Tags added: riscv64

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

Title:
  Enable riscv64 build

Status in grub2 package in Ubuntu:
  New

Bug description:
  RISC-V EFI support is not yet in the Linux kernel (ca. 5.8:
  https://lkml.org/lkml/2020/4/20/1800), and while GRUB2 EFI Loader
  support needs to happen with the kernel
  (https://lists.gnu.org/archive/html/grub-devel/2020-04/msg00203.html),
  GRUB2 already has RISC-V EFI support.  It can't currently boot
  anything, but it is a valid UEFI application and displays a pretty
  menu.

  Please see the attached debdiff.  Of note:

  * grub2 requires efibootmgr and efivar.  I've filed Debian bugs to
  enable riscv64 for them (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=959498 and https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=959499 respectively), but if this is actioned
  before those end up happening, it's a simple Architecture: update on
  each.

  * riscv-default-platform.patch: Upstreamed, allows `grub-install` to
  work without --platform.

  * riscv-relocation-offset.patch: Upstreamed, fixes "unaligned pointer"
  failure.

  * riscv-ubuntu-linuxefi.patch: Patches ubuntu-linuxefi.patch for riscv
  support; not sure if this should be integrated into ubuntu-
  linuxefi.patch.

  * Tested on qemu-system-riscv64 focal.

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



From 1934209 at bugs.launchpad.net  Mon Aug  2 13:27:47 2021
From: 1934209 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 02 Aug 2021 13:27:47 -0000
Subject: [Bug 1934209] Re: Dell dock USB4 module need fwupd 1.5.11
References: <162510466629.25996.15967004560380142578.malonedeb@gac.canonical.com>
Message-ID: <162791086922.14853.14075589113052786679.malone@ackee.canonical.com>

This bug was fixed in the package fwupd - 1.5.11-0ubuntu1~21.04.1

---------------
fwupd (1.5.11-0ubuntu1~21.04.1) hirsute; urgency=medium

  * New upstream version (1.5.11) to support Dell dock USB4 module.
    (LP: #1934209)
  * Drop all patches upstream.
  * Sync updated files from contrib/debian/ to debian/.

 -- Yuan-Chen Cheng <yc.cheng at canonical.com>  Thu, 01 Jul 2021 01:06:11
+0000

** Changed in: fwupd (Ubuntu Hirsute)
       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/1934209

Title:
  Dell dock USB4 module need fwupd 1.5.11

Status in OEM Priority Project:
  Fix Committed
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Fix Committed
Status in fwupd-signed source package in Focal:
  Fix Committed
Status in fwupd source package in Hirsute:
  Fix Released
Status in fwupd-signed source package in Hirsute:
  Fix Committed
Status in fwupd source package in Impish:
  Fix Released
Status in fwupd-signed source package in Impish:
  Fix Released

Bug description:
  need focal/fwupd 1.5.11 to support this

  Ref: https://github.com/fwupd/fwupd/releases/tag/1.5.11

  Note: this version shall work well with shim with sbat.
  Note: for focal, we also need to upgrade jcat to make it work.

  [Impact]

   * We need to support Dell USB4 Dock and based on the fwupd design,
     need to upgrade the version to support it.

   * This new version will also enable certain vendors to upgrade
     intel-microcode by fwupd. Some security updates of intel-microcode
     does introduce regresssion because it's not tested across enough
     CPU family. Vendors can do more tests give they have access to
     those machines and have access to those new microcodes with
     security patches.

   * Will follow the new policy to do this SRU exception.
     https://wiki.ubuntu.com/firmware-updates

  [Test Plan]

   * Full standard verification test listed in
     https://wiki.ubuntu.com/firmware-updates

   * Install a sbat enable shim, turned on secure boot and make sure
     the new fwupd firmware upgrade efi still work fine.

   * Will also invite the component vendor to test the new supported
     docking when the new fwupd exists in the proposed channel.
     They already started to use the one in my ppa on focal given
     LTS release is the HWE project target.

  [Where problems could occur]

   * If it passed the verification procedure in the policy, I believe
     it shall already cover most cases.

  [Other Info]

   * This suppose to fix several bugs. OEM team will test
     those along the way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934209/+subscriptions



From 1934209 at bugs.launchpad.net  Mon Aug  2 13:27:51 2021
From: 1934209 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 02 Aug 2021 13:27:51 -0000
Subject: [Bug 1934209] Update Released
References: <162510466629.25996.15967004560380142578.malonedeb@gac.canonical.com>
Message-ID: <162791087184.1786.13714219395399786978.malone@gac.canonical.com>

The verification of the Stable Release Update for fwupd 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/1934209

Title:
  Dell dock USB4 module need fwupd 1.5.11

Status in OEM Priority Project:
  Fix Committed
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Fix Committed
Status in fwupd-signed source package in Focal:
  Fix Committed
Status in fwupd source package in Hirsute:
  Fix Released
Status in fwupd-signed source package in Hirsute:
  Fix Committed
Status in fwupd source package in Impish:
  Fix Released
Status in fwupd-signed source package in Impish:
  Fix Released

Bug description:
  need focal/fwupd 1.5.11 to support this

  Ref: https://github.com/fwupd/fwupd/releases/tag/1.5.11

  Note: this version shall work well with shim with sbat.
  Note: for focal, we also need to upgrade jcat to make it work.

  [Impact]

   * We need to support Dell USB4 Dock and based on the fwupd design,
     need to upgrade the version to support it.

   * This new version will also enable certain vendors to upgrade
     intel-microcode by fwupd. Some security updates of intel-microcode
     does introduce regresssion because it's not tested across enough
     CPU family. Vendors can do more tests give they have access to
     those machines and have access to those new microcodes with
     security patches.

   * Will follow the new policy to do this SRU exception.
     https://wiki.ubuntu.com/firmware-updates

  [Test Plan]

   * Full standard verification test listed in
     https://wiki.ubuntu.com/firmware-updates

   * Install a sbat enable shim, turned on secure boot and make sure
     the new fwupd firmware upgrade efi still work fine.

   * Will also invite the component vendor to test the new supported
     docking when the new fwupd exists in the proposed channel.
     They already started to use the one in my ppa on focal given
     LTS release is the HWE project target.

  [Where problems could occur]

   * If it passed the verification procedure in the policy, I believe
     it shall already cover most cases.

  [Other Info]

   * This suppose to fix several bugs. OEM team will test
     those along the way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934209/+subscriptions



From 1934209 at bugs.launchpad.net  Mon Aug  2 13:36:28 2021
From: 1934209 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 02 Aug 2021 13:36:28 -0000
Subject: [Bug 1934209] Re: Dell dock USB4 module need fwupd 1.5.11
References: <162510466629.25996.15967004560380142578.malonedeb@gac.canonical.com>
Message-ID: <162791139107.14854.12108046916270292985.malone@ackee.canonical.com>

This bug was fixed in the package fwupd-signed - 1.27.1ubuntu5

---------------
fwupd-signed (1.27.1ubuntu5) focal; urgency=medium

  * Build depend on fwupd version 1.5.11-0ubuntu1~20.04.2, take #2 (LP:
#1934209)

fwupd-signed (1.27.1ubuntu4) focal; urgency=medium

  * Build depend on fwupd version 1.5.11-0ubuntu1~20.04.2 (LP: #1934209)

fwupd-signed (1.27.1ubuntu3) focal; urgency=medium

  * Build depend on fwupd version 1.5.11-0ubuntu1~20.04.1 (LP: #1934209)

 -- Julian Andres Klode <juliank at ubuntu.com>  Mon, 26 Jul 2021 09:50:19
+0200

** Changed in: fwupd-signed (Ubuntu Focal)
       Status: Fix Committed => Fix Released

** Changed in: fwupd (Ubuntu Focal)
       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/1934209

Title:
  Dell dock USB4 module need fwupd 1.5.11

Status in OEM Priority Project:
  Fix Committed
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Fix Released
Status in fwupd-signed source package in Focal:
  Fix Released
Status in fwupd source package in Hirsute:
  Fix Released
Status in fwupd-signed source package in Hirsute:
  Fix Committed
Status in fwupd source package in Impish:
  Fix Released
Status in fwupd-signed source package in Impish:
  Fix Released

Bug description:
  need focal/fwupd 1.5.11 to support this

  Ref: https://github.com/fwupd/fwupd/releases/tag/1.5.11

  Note: this version shall work well with shim with sbat.
  Note: for focal, we also need to upgrade jcat to make it work.

  [Impact]

   * We need to support Dell USB4 Dock and based on the fwupd design,
     need to upgrade the version to support it.

   * This new version will also enable certain vendors to upgrade
     intel-microcode by fwupd. Some security updates of intel-microcode
     does introduce regresssion because it's not tested across enough
     CPU family. Vendors can do more tests give they have access to
     those machines and have access to those new microcodes with
     security patches.

   * Will follow the new policy to do this SRU exception.
     https://wiki.ubuntu.com/firmware-updates

  [Test Plan]

   * Full standard verification test listed in
     https://wiki.ubuntu.com/firmware-updates

   * Install a sbat enable shim, turned on secure boot and make sure
     the new fwupd firmware upgrade efi still work fine.

   * Will also invite the component vendor to test the new supported
     docking when the new fwupd exists in the proposed channel.
     They already started to use the one in my ppa on focal given
     LTS release is the HWE project target.

  [Where problems could occur]

   * If it passed the verification procedure in the policy, I believe
     it shall already cover most cases.

  [Other Info]

   * This suppose to fix several bugs. OEM team will test
     those along the way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934209/+subscriptions



From 1934209 at bugs.launchpad.net  Mon Aug  2 13:40:57 2021
From: 1934209 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 02 Aug 2021 13:40:57 -0000
Subject: [Bug 1934209] Re: Dell dock USB4 module need fwupd 1.5.11
References: <162510466629.25996.15967004560380142578.malonedeb@gac.canonical.com>
Message-ID: <162791166160.14854.14332706019438987555.malone@ackee.canonical.com>

This bug was fixed in the package fwupd - 1.5.11-0ubuntu1~20.04.2

---------------
fwupd (1.5.11-0ubuntu1~20.04.2) focal; urgency=medium

  * force to use libjcat >= 0.1.3, or signature verification will
failed.

fwupd (1.5.11-0ubuntu1~20.04.1) focal; urgency=medium

  * New upstream version (1.5.11) to support Dell dock USB4 module.
    (LP: #1934209)
  * Drop all patches upstream.
  * Downgrade libgusb from 0.3.5 to 0.3.4 which used in focal after
    checking through all commits between.

fwupd (1.5.8-0ubuntu1) hirsute; urgency=medium

  * New upstream version (1.5.8)
  * Backport a patch to fix SBAT (LP: #1921539)
  * Drop all other patches, upstream.

fwupd (1.5.7-3) unstable; urgency=medium

  * Backport a patch to fix regression in fwupdtool activate
  * Backport a patch to fix activatable devices getting stuck in an update loop
  * Rebuild to pick up new signing keys.

fwupd (1.5.7-2) unstable; urgency=medium

  * Backport a patch to fix FTBFS on armhf for SBAT

fwupd (1.5.7-1) unstable; urgency=medium

  * New upstream version (1.5.7)
    - Fixes issues with SBAT on UEFI.
  * Fixes dependencies for -dev packages:
    Closes: #980691, #980684

fwupd (1.5.6-1) unstable; urgency=medium

  [ Steve McIntyre ]
  * Fix up Uploaders for the -signed packages - remove Jared, add Matthias

  [ Mario Limonciello ]
  * New upstream version (1.5.6)
  * drop all upstream patches

fwupd (1.5.5-2) unstable; urgency=medium

  * fwupd.postinst: Adjust to read /etc/os-release instead of `/etc/lsb-
release`

fwupd (1.5.5-1) unstable; urgency=medium

  * New upstream version (1.5.5)
  * trivial: debian: migrate uefi->uefi_capsule in uefi.conf
  * trivial: debian: fix modules-load.d directory
  * trivial: debian: add dbus to recommends (Closes: #980049)
  * Backport 2 patches for continual "Unknown" message on new connections
  * trivial: debian: read /etc/lsb-release instead of dpkg-dev (Closes: #977860, #977861, #970783)

fwupd (1.5.3-2) unstable; urgency=medium

  * trivial: debian: only install fwupd-msr.conf if needed

fwupd (1.5.3-1) unstable; urgency=medium

  * New upstream version (1.5.3)
  * Drop all patches (upstream)
  * Follow defaults for nvme and redfish plugins (don't need efivar now)
  * debian/control:
    - Drop libsoup build dependency
    - Add libcurl build dependency
    - Add systemd build dependency
  * Migrate debian/fwupd.preinst content to debian/fwupd.maintscript

fwupd (1.5.1-5) unstable; urgency=medium

  * Backport patch to fix ppc64el autopkgtest failure

fwupd (1.5.1-4) unstable; urgency=medium

  * trivial: debian: disable downloading from LVFS in autopkgtest

fwupd (1.5.1-3) unstable; urgency=medium

  * Add breaks for fwupdate 12-7 (Closes: #960688)
  * trivial: debian: add git to fwupdate-tests dependencies

fwupd (1.5.1-2) unstable; urgency=medium

  [ Mario Limonciello ]
  * Backport a patch to indicate if packages are supported or not
  * backport a patch to fix autopkgtests on ppc64el
  * trivial: debian: don't hardcode paths in libexec
  * trivial: debian: disable msr plugin on all !x86

  [ Jessica Clarke ]
  * debian: Check DEB_HOST_ARCH_CPU not DEB_HOST_ARCH for MSR plugin
  * debian: Prefer Makefile substitution over shell substitution
  * debian: Use if/else rather than overriding default values
  * debian: Drop pointless dh_shlibdeps override
  * debian: Check for valgrind in Makefile not shell and don't hard-code path
  * debian: Fix dangerous lack of set -e
  * debian: Fix another instance of unusual ifeq syntax
  * debian: Build up CONFARGS list rather than individual variables
  * debian: Fix another dangerous missing set -e
  * debian: Use uniform spacing around semicolons
  * debian: Avoid looking like a set -e is missing
  * debian: Remove unnecessary ./ use
  * debian: Add quotes around glob

fwupd (1.5.1-1) unstable; urgency=medium

  * New upstream version (1.5.1)
  * Drop backported patches

fwupd (1.4.6-2) unstable; urgency=medium

  * Add udisks2 to recommends
  * Backport a patch to fix a crash when udisks2 is missing (Closes: #970054)
  * Disable flashrom for ia64

fwupd (1.4.6-1) unstable; urgency=medium

  * New upstream version (1.4.6)

fwupd (1.4.5-1) unstable; urgency=medium

  * New upstream version (1.4.5)
  * Drop flashrom patch, now upstream
  * Regenerate control file
    - Refresh dependencies for 1.4.x
    - Drop Jared as uploader

fwupd (1.3.11-2) unstable; urgency=medium

  * Stop generating debian/control automatically at build time
  * Add build-dep on libflashrom-dev

 -- Yuan-Chen Cheng <yc.cheng at canonical.com>  Fri, 23 Jul 2021 15:14:53
+0800

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

Title:
  Dell dock USB4 module need fwupd 1.5.11

Status in OEM Priority Project:
  Fix Committed
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Fix Released
Status in fwupd-signed source package in Focal:
  Fix Released
Status in fwupd source package in Hirsute:
  Fix Released
Status in fwupd-signed source package in Hirsute:
  Fix Committed
Status in fwupd source package in Impish:
  Fix Released
Status in fwupd-signed source package in Impish:
  Fix Released

Bug description:
  need focal/fwupd 1.5.11 to support this

  Ref: https://github.com/fwupd/fwupd/releases/tag/1.5.11

  Note: this version shall work well with shim with sbat.
  Note: for focal, we also need to upgrade jcat to make it work.

  [Impact]

   * We need to support Dell USB4 Dock and based on the fwupd design,
     need to upgrade the version to support it.

   * This new version will also enable certain vendors to upgrade
     intel-microcode by fwupd. Some security updates of intel-microcode
     does introduce regresssion because it's not tested across enough
     CPU family. Vendors can do more tests give they have access to
     those machines and have access to those new microcodes with
     security patches.

   * Will follow the new policy to do this SRU exception.
     https://wiki.ubuntu.com/firmware-updates

  [Test Plan]

   * Full standard verification test listed in
     https://wiki.ubuntu.com/firmware-updates

   * Install a sbat enable shim, turned on secure boot and make sure
     the new fwupd firmware upgrade efi still work fine.

   * Will also invite the component vendor to test the new supported
     docking when the new fwupd exists in the proposed channel.
     They already started to use the one in my ppa on focal given
     LTS release is the HWE project target.

  [Where problems could occur]

   * If it passed the verification procedure in the policy, I believe
     it shall already cover most cases.

  [Other Info]

   * This suppose to fix several bugs. OEM team will test
     those along the way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934209/+subscriptions



From 1938707 at bugs.launchpad.net  Mon Aug  2 15:53:10 2021
From: 1938707 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 02 Aug 2021 15:53:10 -0000
Subject: [Bug 1938707] [NEW] Sync sshguard 2.3.1-2 (universe) from Debian
 unstable (main)
References: <162791958678.2824.4847316839802775770.malonedeb@soybean.canonical.com>
Message-ID: <162791959071.9269.13298854977508779069.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Hans Joachim Desserud (hjd):

Please sync sshguard 2.3.1-2 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Drop Ubuntu delta and use nftables
  * Drop Ubuntu delta and use nftables
  * Drop Ubuntu delta and use nftables
  * Fix path to iptables binaries in the .service unit. LP: #1884848
  * Revert to use iptables which is default in Ubuntu:
    - Revert "Use nft instead iptables"
    - Revert "Change firewall backend to nftables"
    - Revert "Remove iptables from Depends"
  * Revert to use iptables which is default in Ubuntu:
    - Revert "Use nft instead iptables"
    - Revert "Change firewall backend to nftables"
    - Revert "Remove iptables from Depends"


Delta is effectively empty, newer version can be synced.

Changelog entries since current impish version 2.3.1-1ubuntu3:

sshguard (2.3.1-2) unstable; urgency=medium

  * Fix config file. (Closes: #928525)

 -- Julián Moreno Patiño <julian at debian.org>  Mon, 26 Jul 2021 22:18:43
-0500

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

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


From 1938259 at bugs.launchpad.net  Tue Aug  3 03:09:53 2021
From: 1938259 at bugs.launchpad.net (Yao Wei)
Date: Tue, 03 Aug 2021 03:09:53 -0000
Subject: [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell
 models
References: <162745556987.5514.108453593921646683.malonedeb@wampee.canonical.com>
Message-ID: <162796019342.29165.18197709343208425430.malone@chaenomeles.canonical.com>

When will we upload the changes to -proposed?

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  In Progress

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel 5.13, or kernel with this patch backported:
      https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 04:30:54 2021
From: 1938747 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 04:30:54 -0000
Subject: [Bug 1938747] [NEW] [SRU] can't adjust output volume through
 volume-slider after chaning output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162796505455.17590.8129926414551554559.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Hui Wang (hui.wang):

This bug is for tracking purpose.

** Affects: gnome-control-center (Ubuntu)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: In Progress

** Affects: gnome-control-center (Ubuntu Focal)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: In Progress

** Affects: gnome-control-center (Ubuntu Hirsute)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: In Progress

** Affects: gnome-control-center (Ubuntu Impish)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: In Progress

-- 
[SRU] can't adjust output volume through volume-slider after chaning output-device
https://bugs.launchpad.net/bugs/1938747
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1938747 at bugs.launchpad.net  Tue Aug  3 04:29:43 2021
From: 1938747 at bugs.launchpad.net (Hui Wang)
Date: Tue, 03 Aug 2021 04:29:43 -0000
Subject: [Bug 1938747] [NEW] [SRU] can't adjust output volume through
 volume-slider after changing output-device
Message-ID: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>

Public bug reported:

This bug is for tracking purpose.

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

** Affects: gnome-control-center (Ubuntu)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: In Progress

** Affects: gnome-control-center (Ubuntu Focal)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: In Progress

** Affects: gnome-control-center (Ubuntu Hirsute)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: In Progress

** Affects: gnome-control-center (Ubuntu Impish)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: In Progress


** Tags: oem-priority originate-from-1935594 sutton

** Also affects: gnome-control-center (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: gnome-control-center (Ubuntu Impish)
   Importance: Undecided
     Assignee: Hui Wang (hui.wang)
       Status: New

** Also affects: gnome-control-center (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Changed in: gnome-control-center (Ubuntu Focal)
       Status: New => In Progress

** Changed in: gnome-control-center (Ubuntu Hirsute)
       Status: New => In Progress

** Changed in: gnome-control-center (Ubuntu Impish)
       Status: New => In Progress

** Changed in: gnome-control-center (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: gnome-control-center (Ubuntu Hirsute)
   Importance: Undecided => High

** Changed in: gnome-control-center (Ubuntu Impish)
   Importance: Undecided => High

** Changed in: gnome-control-center (Ubuntu Focal)
     Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: gnome-control-center (Ubuntu Hirsute)
     Assignee: (unassigned) => Hui Wang (hui.wang)

** Tags added: oem-priority originate-from-1935594 sutton

** Summary changed:

- [SRU] can't adjust output volume through volume-slider after chaning output-device
+ [SRU] can't adjust output volume through volume-slider after changing output-device

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

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  In Progress

Bug description:
  This bug is for tracking purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1910952 at bugs.launchpad.net  Tue Aug  3 04:44:51 2021
From: 1910952 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 04:44:51 -0000
Subject: [Bug 1910952] Re: [MIR] oem-sutton.newell-adrion-meta
References: <161034470694.22048.6669612133363727884.malonedeb@wampee.canonical.com>
Message-ID: <162796589169.19492.4569290266953934083.malone@gac.canonical.com>

Attach oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-adrion-meta for focal:
      git clone -b newell.adrion-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for ThinkPad L13 Yoga Gen 2.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkPad L13 Yoga Gen 2.
  oem-sutton.newell-adrion-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202011-28408

** Patch removed: "oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1910952/+attachment/5501840/+files/oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1910952/+attachment/5515449/+files/oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.6

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

Title:
  [MIR] oem-sutton.newell-adrion-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-adrion-meta for focal:
      git clone -b newell.adrion-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkPad L13 Yoga Gen 2.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkPad L13 Yoga Gen 2.
  oem-sutton.newell-adrion-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28408

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1910952/+subscriptions



From 1930564 at bugs.launchpad.net  Tue Aug  3 04:48:09 2021
From: 1930564 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 04:48:09 -0000
Subject: [Bug 1930564] Re: [MIR] oem-sutton.newell-adrian-meta
References: <162262690796.29117.14096678191505230951.malonedeb@chaenomeles.canonical.com>
Message-ID: <162796608971.20831.4767234570205868187.malone@soybean.canonical.com>

Attach oem-sutton.newell-adrian-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-adrian-meta for focal:
      git clone -b newell.adrian-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for ThinkPad X1 Titanium Gen 1.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkPad X1 Titanium Gen 1.
  oem-sutton.newell-adrian-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202104-28989

** Patch removed: "oem-sutton.newell-adrian-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1930564/+attachment/5501853/+files/oem-sutton.newell-adrian-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-adrian-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1930564/+attachment/5515450/+files/oem-sutton.newell-adrian-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.6

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

Title:
  [MIR] oem-sutton.newell-adrian-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-adrian-meta for focal:
      git clone -b newell.adrian-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkPad X1 Titanium Gen 1.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkPad X1 Titanium Gen 1.
  oem-sutton.newell-adrian-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202104-28989

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1930564/+subscriptions



From 1924727 at bugs.launchpad.net  Tue Aug  3 04:53:29 2021
From: 1924727 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 04:53:29 -0000
Subject: [Bug 1924727] Re: [MIR] oem-sutton.newell-aenedleah-meta
References: <161856666138.16050.17574210822109530422.malonedeb@chaenomeles.canonical.com>
Message-ID: <162796640938.7323.4512730592481101689.malone@wampee.canonical.com>

Attach oem-sutton.newell-aenedleah-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-aenedleah-meta for focal:
      git clone -b newell.aenedleah-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-aenedleah-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202104-28987

** Patch removed: "oem-sutton.newell-aenedleah-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924727/+attachment/5501846/+files/oem-sutton.newell-aenedleah-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-aenedleah-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924727/+attachment/5515451/+files/oem-sutton.newell-aenedleah-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.6

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

Title:
  [MIR] oem-sutton.newell-aenedleah-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-aenedleah-meta for focal:
      git clone -b newell.aenedleah-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-aenedleah-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202104-28987

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924727/+subscriptions



From 1908865 at bugs.launchpad.net  Tue Aug  3 04:56:11 2021
From: 1908865 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 04:56:11 -0000
Subject: [Bug 1908865] Re: [MIR] oem-sutton.newell-carin-meta
References: <160853132747.28956.13462929633048402940.malonedeb@gac.canonical.com>
Message-ID: <162796657156.21895.10534874717929100794.malone@gac.canonical.com>

Attach oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff by oem-scripts
1.6.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carin-meta for focal:
      git clone -b newell.carin-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for ThinkCentre M60e.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkCentre M60e.
  oem-sutton.newell-carin-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202010-28307

** Patch removed: "oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1908865/+attachment/5501839/+files/oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1908865/+attachment/5515452/+files/oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.6

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

Title:
  [MIR] oem-sutton.newell-carin-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carin-meta for focal:
      git clone -b newell.carin-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkCentre M60e.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkCentre M60e.
  oem-sutton.newell-carin-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202010-28307

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1908865/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 05:12:12 2021
From: 1938747 at bugs.launchpad.net (Daniel van Vugt)
Date: Tue, 03 Aug 2021 05:12:12 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162796753319.24957.18281637273943025990.launchpad@gac.canonical.com>

** Tags added: fixed-in-41 fixed-upstream focal hirsute impish

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

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  In Progress

Bug description:
  This bug is for tracking purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1903847 at bugs.launchpad.net  Tue Aug  3 05:56:15 2021
From: 1903847 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 05:56:15 -0000
Subject: [Bug 1903847] Re: [MIR] oem-sutton.newell-carl-meta
References: <160509617480.9250.1663754645132012577.malonedeb@wampee.canonical.com>
Message-ID: <162797017542.3017.11021819049470617667.malone@soybean.canonical.com>

Attach oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff by oem-scripts
1.6.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carl-meta for focal:
      git clone -b newell.carl-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for Lenovo E41-50.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Lenovo E41-50.
  oem-sutton.newell-carl-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202011-28353

** Patch removed: "oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1903847/+attachment/5501838/+files/oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1903847/+attachment/5515454/+files/oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.6

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

Title:
  [MIR] oem-sutton.newell-carl-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carl-meta for focal:
      git clone -b newell.carl-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for Lenovo E41-50.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Lenovo E41-50.
  oem-sutton.newell-carl-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28353

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1903847/+subscriptions



From 1924734 at bugs.launchpad.net  Tue Aug  3 06:06:03 2021
From: 1924734 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 06:06:03 -0000
Subject: [Bug 1924734] [NEW] [MIR] oem-sutton.newell-carrie-meta
References: <161856673427.8978.10610118458597399917.malonedeb@gac.canonical.com>
Message-ID: <162797076415.23690.7675148625776195161.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Bin Li (binli):

[Background]

Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

[Impact]

 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
 2. The background and impact of the situation for this change, and it's impact.

[Testing]

 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

[Regression Potential]

Most potential regressions will live in the package set that will be
installed via dependency of this package, which live in OEM archive
(outside of Ubuntu) and control by OEM team. OEM team and other
corresponding team need take responsibility of those dependency
installed.

[When switching kernel flavour] Check that the new kernel flavour works
on the target platform.

[Availability]
This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
The source code of the oem-sutton.newell-carrie-meta for focal:
    git clone -b newell.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

[Rationale]
We want to improve the hardware support for some Lenovo platforms.

[Security]
No CVE/known security issue.

[Quality assurance]
I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
oem-sutton.newell-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

[Dependencies]
It only depends on ubuntu-oem-keyring.

[Standards compliance]
This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

[Maintenance]
Canonical OEM Enablement Team will take care of the maintenance.

[Background information]
Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
verify this MIR against the reference package in the archive.

** Affects: oem-priority
     Importance: Critical
     Assignee: Bin Li (binli)
         Status: Fix Committed

** Affects: ubuntu
     Importance: Undecided
         Status: Confirmed


** Tags: oem-meta-packages oem-priority oem-scripts-0.95
-- 
[MIR] oem-sutton.newell-carrie-meta
https://bugs.launchpad.net/bugs/1924734
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1909735 at bugs.launchpad.net  Tue Aug  3 06:04:25 2021
From: 1909735 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 06:04:25 -0000
Subject: [Bug 1909735] Re: [MIR] oem-sutton.newell-carleton-meta
References: <160939963683.3719.10357195190688241035.malonedeb@wampee.canonical.com>
Message-ID: <162797066542.1987.10777595706787854020.malone@gac.canonical.com>

Attach oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carleton-meta for focal:
      git clone -b newell.carleton-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for Lenovo V50a-22IMB.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Lenovo V50a-22IMB.
  oem-sutton.newell-carleton-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202011-28414

** Patch removed: "oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1909735/+attachment/5501829/+files/oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1909735/+attachment/5515455/+files/oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.6

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

Title:
  [MIR] oem-sutton.newell-carleton-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carleton-meta for focal:
      git clone -b newell.carleton-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for Lenovo V50a-22IMB.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Lenovo V50a-22IMB.
  oem-sutton.newell-carleton-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28414

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1909735/+subscriptions



From 1924734 at bugs.launchpad.net  Tue Aug  3 06:07:01 2021
From: 1924734 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 06:07:01 -0000
Subject: [Bug 1924734] Re: [MIR] oem-sutton.newell-carrie-meta
References: <161856673427.8978.10610118458597399917.malonedeb@gac.canonical.com>
Message-ID: <162797082158.2350.15095548156910386409.malone@gac.canonical.com>

Attach oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carrie-meta for focal:
      git clone -b newell.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

** Changed in: oem-priority
       Status: In Progress => Fix Committed

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

** Patch removed: "oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924734/+attachment/5501851/+files/oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924734/+attachment/5515456/+files/oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.6

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

Title:
  [MIR] oem-sutton.newell-carrie-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carrie-meta for focal:
      git clone -b newell.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924734/+subscriptions



From 1903847 at bugs.launchpad.net  Tue Aug  3 06:12:27 2021
From: 1903847 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 06:12:27 -0000
Subject: [Bug 1903847] Re: [MIR] oem-sutton.newell-carl-meta
References: <160509617480.9250.1663754645132012577.malonedeb@wampee.canonical.com>
Message-ID: <162797114763.23570.5047650299138348148.malone@wampee.canonical.com>

Attach oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff by oem-scripts
1.6.

** Patch removed: "oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1903847/+attachment/5515454/+files/oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1903847/+attachment/5515457/+files/oem-sutton.newell-carl-meta_20.04~ubuntu1.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/1903847

Title:
  [MIR] oem-sutton.newell-carl-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carl-meta for focal:
      git clone -b newell.carl-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for Lenovo E41-50.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Lenovo E41-50.
  oem-sutton.newell-carl-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28353

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1903847/+subscriptions



From 1932449 at bugs.launchpad.net  Tue Aug  3 06:24:24 2021
From: 1932449 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 06:24:24 -0000
Subject: [Bug 1932449] [NEW] [MIR] oem-sutton.simon-cabernet-meta
References: <162400365573.14232.5023731108567257724.malonedeb@wampee.canonical.com>
Message-ID: <162797186494.8844.1048046614951447554.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Bin Li (binli):

[Background]

Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

[Impact]

 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
 2. The background and impact of the situation for this change, and it's impact.

[Testing]

 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

[Regression Potential]

Most potential regressions will live in the package set that will be
installed via dependency of this package, which live in OEM archive
(outside of Ubuntu) and control by OEM team. OEM team and other
corresponding team need take responsibility of those dependency
installed.

[When switching kernel flavour] Check that the new kernel flavour works
on the target platform.

[Availability]
This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
The source code of the oem-sutton.simon-cabernet-meta for focal:
    git clone -b simon.cabernet-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

[Rationale]
We want to improve the hardware support for some Lenovo platforms.

[Security]
No CVE/known security issue.

[Quality assurance]
I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
oem-sutton.simon-cabernet-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

[Dependencies]
It only depends on ubuntu-oem-keyring.

[Standards compliance]
This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

[Maintenance]
Canonical OEM Enablement Team will take care of the maintenance.

[Background information]
Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
verify this MIR against the reference package in the archive.

https://ubuntu.com/certified/202104-28958

** Affects: oem-priority
     Importance: Critical
     Assignee: OEM Taipei Jenkins Role Account (oem-taipei-bot)
         Status: Fix Committed

** Affects: ubuntu
     Importance: Undecided
         Status: Confirmed


** Tags: oem-meta-packages oem-priority oem-scripts-0.98
-- 
[MIR] oem-sutton.simon-cabernet-meta
https://bugs.launchpad.net/bugs/1932449
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1909735 at bugs.launchpad.net  Tue Aug  3 06:19:31 2021
From: 1909735 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 06:19:31 -0000
Subject: [Bug 1909735] Re: [MIR] oem-sutton.newell-carleton-meta
References: <160939963683.3719.10357195190688241035.malonedeb@wampee.canonical.com>
Message-ID: <162797157169.3922.12399751526920108631.malone@chaenomeles.canonical.com>

Attach oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Patch removed: "oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1909735/+attachment/5515455/+files/oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1909735/+attachment/5515469/+files/oem-sutton.newell-carleton-meta_20.04~ubuntu1.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/1909735

Title:
  [MIR] oem-sutton.newell-carleton-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carleton-meta for focal:
      git clone -b newell.carleton-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for Lenovo V50a-22IMB.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Lenovo V50a-22IMB.
  oem-sutton.newell-carleton-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28414

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1909735/+subscriptions



From 1932449 at bugs.launchpad.net  Tue Aug  3 06:25:24 2021
From: 1932449 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 06:25:24 -0000
Subject: [Bug 1932449] Re: [MIR] oem-sutton.simon-cabernet-meta
References: <162400365573.14232.5023731108567257724.malonedeb@wampee.canonical.com>
Message-ID: <162797192497.10530.6661874287769826419.malone@soybean.canonical.com>

Attach oem-sutton.simon-cabernet-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Summary changed:

- [DRAFT][MIR] oem-sutton.simon-cabernet-meta
+ [MIR] oem-sutton.simon-cabernet-meta

** Description changed:

- [DRAFT][Availability]
+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
+ [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-cabernet-meta for focal:
      git clone -b simon.cabernet-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-cabernet-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202104-28958

** Changed in: oem-priority
       Status: Confirmed => Fix Committed

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

** Patch added: "oem-sutton.simon-cabernet-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1932449/+attachment/5515471/+files/oem-sutton.simon-cabernet-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.98
** Tags added: oem-scripts-1.6 ubuntu-certified

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

Title:
  [MIR] oem-sutton.simon-cabernet-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-cabernet-meta for focal:
      git clone -b simon.cabernet-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-cabernet-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202104-28958

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932449/+subscriptions



From 1923285 at bugs.launchpad.net  Tue Aug  3 06:22:41 2021
From: 1923285 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 06:22:41 -0000
Subject: [Bug 1923285] Re: [MIR] oem-sutton.simon-aenescumb-meta
References: <161802287931.31619.2239149582843054786.malonedeb@gac.canonical.com>
Message-ID: <162797176141.8055.10327509079165159953.malone@gac.canonical.com>

Attach oem-sutton.simon-aenescumb-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-aenescumb-meta for focal:
      git clone -b simon.aenescumb-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-aenescumb-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202103-28877
+ https://ubuntu.com/certified/202103-28879

** Patch removed: "oem-sutton.simon-aenescumb-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1923285/+attachment/5501843/+files/oem-sutton.simon-aenescumb-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.simon-aenescumb-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1923285/+attachment/5515470/+files/oem-sutton.simon-aenescumb-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.6

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

Title:
  [MIR] oem-sutton.simon-aenescumb-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-aenescumb-meta for focal:
      git clone -b simon.aenescumb-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-aenescumb-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202103-28877
  https://ubuntu.com/certified/202103-28879

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923285/+subscriptions



From 1926011 at bugs.launchpad.net  Tue Aug  3 06:55:21 2021
From: 1926011 at bugs.launchpad.net (Yuan-Chen Cheng)
Date: Tue, 03 Aug 2021 06:55:21 -0000
Subject: [Bug 1926011] Re: groovy / focal fwupd sbat support
References: <161926541642.4259.13732134536264544535.malonedeb@gac.canonical.com>
Message-ID: <162797372349.783.16012795595129126768.launchpad@wampee.canonical.com>

** Changed in: oem-priority
       Status: In Progress => 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/1926011

Title:
  groovy / focal fwupd sbat support

Status in OEM Priority Project:
  Fix Released
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Won't Fix
Status in fwupd-signed source package in Focal:
  Won't Fix
Status in fwupd source package in Groovy:
  Fix Released
Status in fwupd-signed source package in Groovy:
  Fix Released

Bug description:
  this is a follow-up bug for

  https://bugs.launchpad.net/oem-priority/+bug/1921539/comments/23

  [Impact]
  Future releases of shim will require that EFI binaries that are chainloaded include an SBAT region. fwupd in bionic does not currently contain this region.

  [Test Case]
  Verify that a shim that checks for sbat region can boot the fwupd with sbat region.

  [Regression Potential]
  This is moving to a new stable release in each of the series which is in bug fix only mode. The sbat region is the only "feature" that has been backported to this series in over a year.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926011/+subscriptions



From 1924734 at bugs.launchpad.net  Tue Aug  3 07:00:21 2021
From: 1924734 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 07:00:21 -0000
Subject: [Bug 1924734] Re: [MIR] oem-sutton.newell-carrie-meta
References: <161856673427.8978.10610118458597399917.malonedeb@gac.canonical.com>
Message-ID: <162797402175.16366.10000392484976703248.malone@gac.canonical.com>

Attach oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Patch removed: "oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924734/+attachment/5515456/+files/oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carrie-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924734/+attachment/5515472/+files/oem-sutton.newell-carrie-meta_20.04~ubuntu1.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/1924734

Title:
  [MIR] oem-sutton.newell-carrie-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carrie-meta for focal:
      git clone -b newell.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924734/+subscriptions



From 1933167 at bugs.launchpad.net  Tue Aug  3 07:08:30 2021
From: 1933167 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 07:08:30 -0000
Subject: [Bug 1933167] [NEW] [MIR] oem-sutton.simon-carrie-meta
References: <162432116259.2630.7892035131697104379.malonedeb@gac.canonical.com>
Message-ID: <162797451087.15261.12955337551994242796.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Bin Li (binli):

[Background]

Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

[Impact]

 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
 2. The background and impact of the situation for this change, and it's impact.

[Testing]

 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

[Regression Potential]

Most potential regressions will live in the package set that will be
installed via dependency of this package, which live in OEM archive
(outside of Ubuntu) and control by OEM team. OEM team and other
corresponding team need take responsibility of those dependency
installed.

[When switching kernel flavour] Check that the new kernel flavour works
on the target platform.

[Availability]
This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
The source code of the oem-sutton.simon-carrie-meta for focal:
    git clone -b simon.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

[Rationale]
We want to improve the hardware support for some Lenovo platforms.

[Security]
No CVE/known security issue.

[Quality assurance]
I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
oem-sutton.simon-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

[Dependencies]
It only depends on ubuntu-oem-keyring.

[Standards compliance]
This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

[Maintenance]
Canonical OEM Enablement Team will take care of the maintenance.

[Background information]
Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
verify this MIR against the reference package in the archive.

https://ubuntu.com/certified/202105-29058
https://ubuntu.com/certified/202105-29059

** Affects: oem-priority
     Importance: Critical
     Assignee: OEM Taipei Jenkins Role Account (oem-taipei-bot)
         Status: Fix Committed

** Affects: ubuntu
     Importance: Undecided
         Status: Confirmed


** Tags: oem-meta-packages oem-priority oem-scripts-0.98
-- 
[MIR] oem-sutton.simon-carrie-meta
https://bugs.launchpad.net/bugs/1933167
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1933167 at bugs.launchpad.net  Tue Aug  3 07:09:27 2021
From: 1933167 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 07:09:27 -0000
Subject: [Bug 1933167] Re: [MIR] oem-sutton.simon-carrie-meta
References: <162432116259.2630.7892035131697104379.malonedeb@gac.canonical.com>
Message-ID: <162797456765.20365.17576869793707481094.malone@soybean.canonical.com>

Attach oem-sutton.simon-carrie-meta_20.04~ubuntu1.debdiff by oem-scripts
1.6.

** Summary changed:

- [DRAFT][MIR] oem-sutton.simon-carrie-meta
+ [MIR] oem-sutton.simon-carrie-meta

** Description changed:

- [DRAFT][Availability]
+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
+ [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-carrie-meta for focal:
      git clone -b simon.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202105-29058
+ https://ubuntu.com/certified/202105-29059

** Changed in: oem-priority
       Status: Confirmed => Fix Committed

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

** Patch added: "oem-sutton.simon-carrie-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1933167/+attachment/5515473/+files/oem-sutton.simon-carrie-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.98
** Tags added: oem-scripts-1.6 ubuntu-certified

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

Title:
  [MIR] oem-sutton.simon-carrie-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-carrie-meta for focal:
      git clone -b simon.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202105-29058
  https://ubuntu.com/certified/202105-29059

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933167/+subscriptions



From 1932561 at bugs.launchpad.net  Tue Aug  3 08:10:15 2021
From: 1932561 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 08:10:15 -0000
Subject: [Bug 1932561] [NEW] [MIR] oem-somerville-sanbernardino-meta
References: <162402733063.10319.11571738544764792944.malonedeb@soybean.canonical.com>
Message-ID: <162797821685.19622.889961466476238943.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Andy Chi (andch):

[Background]

Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

[Impact]

 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
 2. The background and impact of the situation for this change, and it's impact.

[Testing]

 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

[Regression Potential]

Most potential regressions will live in the package set that will be
installed via dependency of this package, which live in OEM archive
(outside of Ubuntu) and control by OEM team. OEM team and other
corresponding team need take responsibility of those dependency
installed.

[When switching kernel flavour] Check that the new kernel flavour works
on the target platform.

[Availability]
This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
The source code of the oem-somerville-sanbernardino-meta for focal:
    git clone -b sanbernardino-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta

[Rationale]
We want to improve the hardware support for some Dell platforms.

[Security]
No CVE/known security issue.

[Quality assurance]
I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms.
oem-somerville-sanbernardino-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

[Dependencies]
It only depends on ubuntu-oem-keyring.

[Standards compliance]
This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

[Maintenance]
Canonical OEM Enablement Team will take care of the maintenance.

[Background information]
Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
verify this MIR against the reference package in the archive.

https://ubuntu.com/certified/201711-25935
https://ubuntu.com/certified/201712-26047

** Affects: oem-priority
     Importance: Critical
     Assignee: OEM Taipei Jenkins Role Account (oem-taipei-bot)
         Status: Fix Committed

** Affects: ubuntu
     Importance: Undecided
         Status: Confirmed


** Tags: oem-meta-packages oem-priority oem-scripts-0.98
-- 
[MIR] oem-somerville-sanbernardino-meta
https://bugs.launchpad.net/bugs/1932561
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1918855 at bugs.launchpad.net  Tue Aug  3 08:09:57 2021
From: 1918855 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 08:09:57 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162797820130.14854.16363360022775057853.malone@ackee.canonical.com>

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2

---------------
mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
    radeonsi caused by a bad backport. (LP: #1934783)

mesa (21.0.3-0ubuntu0.1) hirsute; urgency=medium

  * New upstream release. (LP: #1925434)
    - drisw-move-zink-down.diff dropped, upstream
  * Migrate to llvm-12. (LP: #1932311)
  * iris-avoid-abort-if-enomem.diff: Don't abort when out of memory.
    (LP: #1918855)

 -- Timo Aaltonen <tjaalton at debian.org>  Mon, 19 Jul 2021 22:26:12 +0300

** Changed in: mesa (Ubuntu Hirsute)
       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/1918855

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1918855 at bugs.launchpad.net  Tue Aug  3 08:10:32 2021
From: 1918855 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Tue, 03 Aug 2021 08:10:32 -0000
Subject: [Bug 1918855] Update Released
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162797823299.28633.9565948271205816799.malone@chaenomeles.canonical.com>

The verification of the Stable Release Update for mesa 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/1918855

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1932561 at bugs.launchpad.net  Tue Aug  3 08:11:56 2021
From: 1932561 at bugs.launchpad.net (Andy Chi)
Date: Tue, 03 Aug 2021 08:11:56 -0000
Subject: [Bug 1932561] Re: [MIR] oem-somerville-sanbernardino-meta
References: <162402733063.10319.11571738544764792944.malonedeb@soybean.canonical.com>
Message-ID: <162797831634.1981.8981052522519951610.malone@soybean.canonical.com>

Attach oem-somerville-sanbernardino-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Summary changed:

- [DRAFT][MIR] oem-somerville-sanbernardino-meta
+ [MIR] oem-somerville-sanbernardino-meta

** Description changed:

- [DRAFT][Availability]
+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
+ [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-somerville-sanbernardino-meta for focal:
      git clone -b sanbernardino-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Dell platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms.
  oem-somerville-sanbernardino-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/201711-25935
+ https://ubuntu.com/certified/201712-26047

** Changed in: oem-priority
       Status: Confirmed => Fix Committed

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

** Patch added: "oem-somerville-sanbernardino-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1932561/+attachment/5515518/+files/oem-somerville-sanbernardino-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.98
** Tags added: oem-scripts-1.6 ubuntu-certified

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

Title:
  [MIR] oem-somerville-sanbernardino-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-somerville-sanbernardino-meta for focal:
      git clone -b sanbernardino-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta

  [Rationale]
  We want to improve the hardware support for some Dell platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms.
  oem-somerville-sanbernardino-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/201711-25935
  https://ubuntu.com/certified/201712-26047

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932561/+subscriptions



From 1918855 at bugs.launchpad.net  Tue Aug  3 08:13:22 2021
From: 1918855 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 08:13:22 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162797840654.14853.13381221637994378334.malone@ackee.canonical.com>

This bug was fixed in the package mesa - 21.0.3-0ubuntu0.2~20.04.1

---------------
mesa (21.0.3-0ubuntu0.2~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1925320)
  * control, rules: Use gcc10 on ppc64el to fix the build.

mesa (21.0.3-0ubuntu0.2) hirsute; urgency=medium

  * amd-add-missing-line-from-backport.diff: Fix a regression with
    radeonsi caused by a bad backport. (LP: #1934783)

 -- Timo Aaltonen <tjaalton at debian.org>  Tue, 25 May 2021 09:51:53 +0300

** Changed in: mesa (Ubuntu Focal)
       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/1918855

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 08:59:12 2021
From: 1938747 at bugs.launchpad.net (Hui Wang)
Date: Tue, 03 Aug 2021 08:59:12 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162798115229.9084.1490553641922908219.malone@chaenomeles.canonical.com>

This is the debdiff for impish.

thx.


** Patch added: "gnome-control-center_40.0-1ubuntu3.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1938747/+attachment/5515521/+files/gnome-control-center_40.0-1ubuntu3.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/1938747

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  In Progress

Bug description:
  This bug is for tracking purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 08:59:48 2021
From: 1938747 at bugs.launchpad.net (Hui Wang)
Date: Tue, 03 Aug 2021 08:59:48 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162798118836.8536.11899779206601761224.malone@chaenomeles.canonical.com>

This is the debdiff for hirsute.

thx.


** Patch added: "gnome-control-center_3.38.5-1ubuntu2.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1938747/+attachment/5515522/+files/gnome-control-center_3.38.5-1ubuntu2.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/1938747

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  In Progress

Bug description:
  This bug is for tracking purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 09:00:24 2021
From: 1938747 at bugs.launchpad.net (Hui Wang)
Date: Tue, 03 Aug 2021 09:00:24 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162798122505.10621.15735536055142737223.malone@gac.canonical.com>

This is the debdiff for focal.

thx.


** Patch added: "gnome-control-center_3.36.5-0ubuntu3.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1938747/+attachment/5515523/+files/gnome-control-center_3.36.5-0ubuntu3.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/1938747

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  In Progress

Bug description:
  This bug is for tracking purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 09:16:33 2021
From: 1938747 at bugs.launchpad.net (Hui Wang)
Date: Tue, 03 Aug 2021 09:16:33 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162798219471.18253.17365196685530348473.launchpad@gac.canonical.com>

** Description changed:

- This bug is for tracking purpose.
+ [Impact]
+ On the machine with the legacy HDA audio driver, suppose the current output device is Speaker, users plug a HDMI monitor and select the HDMI audio as the current output device in the g-c-c, after that the output volume can't be adjusted through the volume-slider in the g-c-c. The UI of the volume-slider could be changed, but the output volume doesn't change.
+ 
+ [Fix]
+ Backport 1 upstream commit 0f18a662be6ee0d225249d1ad003dfef69294449. The root cause of this issue is the stream is not got when changing the output-device, the patch adds the getting stream in the update_sink callback, this could fix this bug.
+ 
+ [Test]
+ run the patches g-c-c, plug a hdmi monitor, select the HDMI audio from g-c-c, then change the output volume via volume-slider, play music, the sound could be changed with the adjustment with the volume-slider.
+ 
+ [Where problems will occur]
+ This patch brings the change to the output and input volume adjustment in the cc-sound-panel, this could make the output/input volume changing not work anymore, for example, the internal speaker or internal mic work well, after plugging a headset, the output device changes to headphone, the intput device changes to Mic, then the volume adjustment doesn't work on headphone and Mic anymore. But this possibility is very low since I tested the patch on different Lenovo and Dell machines, no regression found so far.

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

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  In Progress

Bug description:
  [Impact]
  On the machine with the legacy HDA audio driver, suppose the current output device is Speaker, users plug a HDMI monitor and select the HDMI audio as the current output device in the g-c-c, after that the output volume can't be adjusted through the volume-slider in the g-c-c. The UI of the volume-slider could be changed, but the output volume doesn't change.

  [Fix]
  Backport 1 upstream commit 0f18a662be6ee0d225249d1ad003dfef69294449. The root cause of this issue is the stream is not got when changing the output-device, the patch adds the getting stream in the update_sink callback, this could fix this bug.

  [Test]
  run the patches g-c-c, plug a hdmi monitor, select the HDMI audio from g-c-c, then change the output volume via volume-slider, play music, the sound could be changed with the adjustment with the volume-slider.

  [Where problems will occur]
  This patch brings the change to the output and input volume adjustment in the cc-sound-panel, this could make the output/input volume changing not work anymore, for example, the internal speaker or internal mic work well, after plugging a headset, the output device changes to headphone, the intput device changes to Mic, then the volume adjustment doesn't work on headphone and Mic anymore. But this possibility is very low since I tested the patch on different Lenovo and Dell machines, no regression found so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1909735 at bugs.launchpad.net  Tue Aug  3 09:20:12 2021
From: 1909735 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 09:20:12 -0000
Subject: [Bug 1909735] Re: [MIR] oem-sutton.newell-carleton-meta
References: <160939963683.3719.10357195190688241035.malonedeb@wampee.canonical.com>
Message-ID: <162798241313.16134.4250463393251421303.malone@gac.canonical.com>

Attach oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Patch removed: "oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1909735/+attachment/5515469/+files/oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carleton-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1909735/+attachment/5515532/+files/oem-sutton.newell-carleton-meta_20.04~ubuntu1.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/1909735

Title:
  [MIR] oem-sutton.newell-carleton-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carleton-meta for focal:
      git clone -b newell.carleton-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for Lenovo V50a-22IMB.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Lenovo V50a-22IMB.
  oem-sutton.newell-carleton-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28414

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1909735/+subscriptions



From 1910952 at bugs.launchpad.net  Tue Aug  3 09:24:07 2021
From: 1910952 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 09:24:07 -0000
Subject: [Bug 1910952] Re: [MIR] oem-sutton.newell-adrion-meta
References: <161034470694.22048.6669612133363727884.malonedeb@wampee.canonical.com>
Message-ID: <162798264746.6982.18260362947889188398.malone@wampee.canonical.com>

Attach oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.6.

** Patch removed: "oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1910952/+attachment/5515449/+files/oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-adrion-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1910952/+attachment/5515534/+files/oem-sutton.newell-adrion-meta_20.04~ubuntu1.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/1910952

Title:
  [MIR] oem-sutton.newell-adrion-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-adrion-meta for focal:
      git clone -b newell.adrion-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkPad L13 Yoga Gen 2.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkPad L13 Yoga Gen 2.
  oem-sutton.newell-adrion-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28408

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1910952/+subscriptions



From 1908865 at bugs.launchpad.net  Tue Aug  3 09:21:53 2021
From: 1908865 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 09:21:53 -0000
Subject: [Bug 1908865] Re: [MIR] oem-sutton.newell-carin-meta
References: <160853132747.28956.13462929633048402940.malonedeb@gac.canonical.com>
Message-ID: <162798251332.14605.6538675604642245567.malone@chaenomeles.canonical.com>

Attach oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff by oem-scripts
1.6.

** Patch removed: "oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1908865/+attachment/5515452/+files/oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carin-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1908865/+attachment/5515533/+files/oem-sutton.newell-carin-meta_20.04~ubuntu1.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/1908865

Title:
  [MIR] oem-sutton.newell-carin-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carin-meta for focal:
      git clone -b newell.carin-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkCentre M60e.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkCentre M60e.
  oem-sutton.newell-carin-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202010-28307

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1908865/+subscriptions



From 1903847 at bugs.launchpad.net  Tue Aug  3 09:27:11 2021
From: 1903847 at bugs.launchpad.net (Bin Li)
Date: Tue, 03 Aug 2021 09:27:11 -0000
Subject: [Bug 1903847] Re: [MIR] oem-sutton.newell-carl-meta
References: <160509617480.9250.1663754645132012577.malonedeb@wampee.canonical.com>
Message-ID: <162798283152.5695.7361230830149259568.malone@wampee.canonical.com>

Attach oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff by oem-scripts
1.6.

** Patch removed: "oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1903847/+attachment/5515457/+files/oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carl-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1903847/+attachment/5515535/+files/oem-sutton.newell-carl-meta_20.04~ubuntu1.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/1903847

Title:
  [MIR] oem-sutton.newell-carl-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carl-meta for focal:
      git clone -b newell.carl-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for Lenovo E41-50.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on Lenovo E41-50.
  oem-sutton.newell-carl-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28353

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1903847/+subscriptions



From 1932561 at bugs.launchpad.net  Tue Aug  3 10:24:27 2021
From: 1932561 at bugs.launchpad.net (Shih-Yuan Lee)
Date: Tue, 03 Aug 2021 10:24:27 -0000
Subject: [Bug 1932561] Re: [MIR] oem-somerville-sanbernardino-meta
References: <162402733063.10319.11571738544764792944.malonedeb@soybean.canonical.com>
Message-ID: <162798626837.29932.10271215134404251179.launchpad@chaenomeles.canonical.com>

** Changed in: oem-priority
     Assignee: OEM Taipei Jenkins Role Account (oem-taipei-bot) => Andy Chi (andch)

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

Title:
  [MIR] oem-somerville-sanbernardino-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-somerville-sanbernardino-meta for focal:
      git clone -b sanbernardino-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta

  [Rationale]
  We want to improve the hardware support for some Dell platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms.
  oem-somerville-sanbernardino-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/201711-25935
  https://ubuntu.com/certified/201712-26047

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932561/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 10:59:04 2021
From: 1938747 at bugs.launchpad.net (Gunnar Hjalmarsson)
Date: Tue, 03 Aug 2021 10:59:04 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162798834455.8612.16219859072640183505.malone@chaenomeles.canonical.com>

Sponsored impish to start with, since I had another thing pending in the
VCS.

@Hui Wang: When proposing changes to packages which have a VCS, it's
generally preferable to submit merge requests.

https://salsa.debian.org/gnome-team/gnome-control-
center/-/tree/ubuntu/master

** Changed in: gnome-control-center (Ubuntu Impish)
       Status: In Progress => 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/1938747

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  On the machine with the legacy HDA audio driver, suppose the current output device is Speaker, users plug a HDMI monitor and select the HDMI audio as the current output device in the g-c-c, after that the output volume can't be adjusted through the volume-slider in the g-c-c. The UI of the volume-slider could be changed, but the output volume doesn't change.

  [Fix]
  Backport 1 upstream commit 0f18a662be6ee0d225249d1ad003dfef69294449. The root cause of this issue is the stream is not got when changing the output-device, the patch adds the getting stream in the update_sink callback, this could fix this bug.

  [Test]
  run the patches g-c-c, plug a hdmi monitor, select the HDMI audio from g-c-c, then change the output volume via volume-slider, play music, the sound could be changed with the adjustment with the volume-slider.

  [Where problems will occur]
  This patch brings the change to the output and input volume adjustment in the cc-sound-panel, this could make the output/input volume changing not work anymore, for example, the internal speaker or internal mic work well, after plugging a headset, the output device changes to headphone, the intput device changes to Mic, then the volume adjustment doesn't work on headphone and Mic anymore. But this possibility is very low since I tested the patch on different Lenovo and Dell machines, no regression found so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1937988 at bugs.launchpad.net  Tue Aug  3 12:29:18 2021
From: 1937988 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 12:29:18 -0000
Subject: [Bug 1937988] [NEW] The image is distorted while use iGPU rendering
 and output via AMD GPU
References: <162727716374.10692.8871227137698749656.malonedeb@chaenomeles.canonical.com>
Message-ID: <162799375926.4396.14002799880243702138.launchpad@soybean.canonical.com>

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

[Steps to reproduce]
1. Connect a monitor on the AMD GPU.
2. Power on the system and boot into OS.
3. Run below command to launch glxgear
Cmd> DRI_PRIME=1 glxgears -info

[Expected result]
The image is not distrorted while running the glxgears

[Actual result]
The image is distrorted while running the glxgears

---

Here is the upstream bug for tracking this issue.
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

** Affects: oem-priority
     Importance: Critical
     Assignee: Shengyao Xue (xueshengyao)
         Status: In Progress

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

** Affects: mesa (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: mesa (Ubuntu Hirsute)
     Importance: Undecided
         Status: New


** Tags: fossa-edge-staging oem-priority originate-from-1904984 originate-from-1917700 originate-from-1931050 patch somerville sutton
-- 
The image is distorted while use iGPU rendering and output via AMD GPU
https://bugs.launchpad.net/bugs/1937988
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1937988 at bugs.launchpad.net  Tue Aug  3 12:29:19 2021
From: 1937988 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Tue, 03 Aug 2021 12:29:19 -0000
Subject: [Bug 1937988] Re: The image is distorted while use iGPU rendering and
 output via AMD GPU
References: <162727716374.10692.8871227137698749656.malonedeb@chaenomeles.canonical.com>
Message-ID: <162799375983.32207.12680122284885221524.malone@gac.canonical.com>

The attachment "mesa_20.2.6-0ubuntu0.20.04.1to2.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/1937988

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 14:00:09 2021
From: 1938747 at bugs.launchpad.net (Gunnar Hjalmarsson)
Date: Tue, 03 Aug 2021 14:00:09 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162799920940.10883.16728126722668824300.malone@wampee.canonical.com>

I have sponsored also hirsute and focal now, and they are waiting in
respective queue for review by the SRU team.

@Hui Wang: Good if you unsubscribe ubuntu-sponsors.

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

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  On the machine with the legacy HDA audio driver, suppose the current output device is Speaker, users plug a HDMI monitor and select the HDMI audio as the current output device in the g-c-c, after that the output volume can't be adjusted through the volume-slider in the g-c-c. The UI of the volume-slider could be changed, but the output volume doesn't change.

  [Fix]
  Backport 1 upstream commit 0f18a662be6ee0d225249d1ad003dfef69294449. The root cause of this issue is the stream is not got when changing the output-device, the patch adds the getting stream in the update_sink callback, this could fix this bug.

  [Test]
  run the patches g-c-c, plug a hdmi monitor, select the HDMI audio from g-c-c, then change the output volume via volume-slider, play music, the sound could be changed with the adjustment with the volume-slider.

  [Where problems will occur]
  This patch brings the change to the output and input volume adjustment in the cc-sound-panel, this could make the output/input volume changing not work anymore, for example, the internal speaker or internal mic work well, after plugging a headset, the output device changes to headphone, the intput device changes to Mic, then the volume adjustment doesn't work on headphone and Mic anymore. But this possibility is very low since I tested the patch on different Lenovo and Dell machines, no regression found so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1938747 at bugs.launchpad.net  Tue Aug  3 14:06:58 2021
From: 1938747 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 03 Aug 2021 14:06:58 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162799962108.14852.251390275537713870.malone@ackee.canonical.com>

This bug was fixed in the package gnome-control-center - 1:40.0-1ubuntu3

---------------
gnome-control-center (1:40.0-1ubuntu3) impish; urgency=medium

  [ Gunnar Hjalmarsson ]
  * Adapts-the-region-capplet-and-the-language-chooser-in-the.patch:
    - Revert the "Fix locales updates" commit
    - Drop update_region() call with NULL argument
  * d/p/u/Fix-volume-adjustment-failure-on-volume-slider.patch:
    - Added patch headers

  [ Hui Wang ]
  * d/p/u/Fix-volume-adjustment-failure-on-volume-slider.patch:
    - Can't adjust the output volume via volume-slider after changing
      the current output-device. (LP: #1938747)

 -- Gunnar Hjalmarsson <gunnarhj at ubuntu.com>  Tue, 03 Aug 2021 12:46:03
+0200

** Changed in: gnome-control-center (Ubuntu Impish)
       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/1938747

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  Fix Released

Bug description:
  [Impact]
  On the machine with the legacy HDA audio driver, suppose the current output device is Speaker, users plug a HDMI monitor and select the HDMI audio as the current output device in the g-c-c, after that the output volume can't be adjusted through the volume-slider in the g-c-c. The UI of the volume-slider could be changed, but the output volume doesn't change.

  [Fix]
  Backport 1 upstream commit 0f18a662be6ee0d225249d1ad003dfef69294449. The root cause of this issue is the stream is not got when changing the output-device, the patch adds the getting stream in the update_sink callback, this could fix this bug.

  [Test]
  run the patches g-c-c, plug a hdmi monitor, select the HDMI audio from g-c-c, then change the output volume via volume-slider, play music, the sound could be changed with the adjustment with the volume-slider.

  [Where problems will occur]
  This patch brings the change to the output and input volume adjustment in the cc-sound-panel, this could make the output/input volume changing not work anymore, for example, the internal speaker or internal mic work well, after plugging a headset, the output device changes to headphone, the intput device changes to Mic, then the volume adjustment doesn't work on headphone and Mic anymore. But this possibility is very low since I tested the patch on different Lenovo and Dell machines, no regression found so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1937988 at bugs.launchpad.net  Tue Aug  3 18:04:04 2021
From: 1937988 at bugs.launchpad.net (Shengyao Xue)
Date: Tue, 03 Aug 2021 18:04:04 -0000
Subject: [Bug 1937988] Re: The image is distorted while use iGPU rendering and
 output via AMD GPU
References: <162727716374.10692.8871227137698749656.malonedeb@chaenomeles.canonical.com>
Message-ID: <162801384413.19787.13439850017826956948.malone@gac.canonical.com>

@Timo, Thanks for help, I rebased to 21.0.3, on Focal and Hirsute.

This is the debdiff for Focal, thanks.

** Patch added: "mesa_21.0.3-0ubuntu0.2~20.04.1.dsc-to-mesa_21.0.3-0ubuntu0.3~20.04.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1937988/+attachment/5515606/+files/mesa_21.0.3-0ubuntu0.2~20.04.1.dsc-to-mesa_21.0.3-0ubuntu0.3~20.04.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/1937988

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions



From 1937988 at bugs.launchpad.net  Tue Aug  3 18:05:20 2021
From: 1937988 at bugs.launchpad.net (Shengyao Xue)
Date: Tue, 03 Aug 2021 18:05:20 -0000
Subject: [Bug 1937988] Re: The image is distorted while use iGPU rendering and
 output via AMD GPU
References: <162727716374.10692.8871227137698749656.malonedeb@chaenomeles.canonical.com>
Message-ID: <162801392083.26104.13110397579703000436.malone@soybean.canonical.com>

And this is the debdiff for Hirsute, thanks.

** Patch added: "mesa_21.0.3-0ubuntu0.2.dsc-to-mesa_21.0.3-0ubuntu0.3.dsc.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1937988/+attachment/5515607/+files/mesa_21.0.3-0ubuntu0.2.dsc-to-mesa_21.0.3-0ubuntu0.3.dsc.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/1937988

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Steps to reproduce]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgear
  Cmd> DRI_PRIME=1 glxgears -info

  [Expected result]
  The image is not distrorted while running the glxgears

  [Actual result]
  The image is distrorted while running the glxgears

  ---

  Here is the upstream bug for tracking this issue.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions



From 1917010 at bugs.launchpad.net  Tue Aug  3 19:19:36 2021
From: 1917010 at bugs.launchpad.net (Brian Murray)
Date: Tue, 03 Aug 2021 19:19:36 -0000
Subject: [Bug 1917010] Re: Hard to detect double-clicks on the HiDPI
 touchscreen system
References: <161432736111.14076.13599931823212336376.malonedeb@chaenomeles.canonical.com>
Message-ID: <162801837704.13118.8088668546972944695.malone@soybean.canonical.com>

Hello jeremyszu, or anyone else affected,

Accepted gnome-shell-extension-desktop-icons into hirsute-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/20.04.0+git20200908-5ubuntu0.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, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: gnome-shell-extension-desktop-icons (Ubuntu Hirsute)
       Status: In Progress => Fix Committed

** Tags removed: verification-failed-hirsute
** Tags added: verification-needed-hirsute

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags removed: verification-failed-focal
** Tags added: verification-needed-focal

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

Title:
  Hard to detect double-clicks on the HiDPI touchscreen system

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Fix Committed
Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Impish:
  Fix Committed
Status in gnome-shell-extension-desktop-icons-ng source package in Impish:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  Double tap desktop icons on a touchscreen barely works.

  [Fix]
  Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped.

  [Test]
  Roughly double tap the desktop icon and nothing happens.
  After applying the fix, double tap can 100% open the app or directory.
  [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed.
  [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed.

  [Where problems could occur]
  If the new code throws any exception, clicking can also be affected.

  == Original Bug Report ==
  Double-clicks touchscreen on HiDPI system, sometime it will not be detected.
  Here is a related patch on upstream
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+subscriptions



From 1917010 at bugs.launchpad.net  Tue Aug  3 19:21:01 2021
From: 1917010 at bugs.launchpad.net (Brian Murray)
Date: Tue, 03 Aug 2021 19:21:01 -0000
Subject: [Bug 1917010] Please test proposed package
References: <161432736111.14076.13599931823212336376.malonedeb@chaenomeles.canonical.com>
Message-ID: <162801846205.23031.3563367426951993534.malone@wampee.canonical.com>

Hello jeremyszu, or anyone else affected,

Accepted gnome-shell-extension-desktop-icons into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/20.04.0-3~ubuntu20.04.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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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/1917010

Title:
  Hard to detect double-clicks on the HiDPI touchscreen system

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Fix Committed
Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Impish:
  Fix Committed
Status in gnome-shell-extension-desktop-icons-ng source package in Impish:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  Double tap desktop icons on a touchscreen barely works.

  [Fix]
  Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped.

  [Test]
  Roughly double tap the desktop icon and nothing happens.
  After applying the fix, double tap can 100% open the app or directory.
  [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed.
  [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed.

  [Where problems could occur]
  If the new code throws any exception, clicking can also be affected.

  == Original Bug Report ==
  Double-clicks touchscreen on HiDPI system, sometime it will not be detected.
  Here is a related patch on upstream
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+subscriptions



From 1934518 at bugs.launchpad.net  Tue Aug  3 20:55:10 2021
From: 1934518 at bugs.launchpad.net (Heather Lemon)
Date: Tue, 03 Aug 2021 20:55:10 -0000
Subject: [Bug 1934518] Re:  improper invalidation of authorization sessions 
References: <162523373063.25728.9542415532730002380.malonedeb@wampee.canonical.com>
Message-ID: <162802411087.27223.8312065333674013391.launchpad@gac.canonical.com>

** Patch removed: "CVE-2019-2386-bionic-20210702.debdiff"
   https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1934518/+attachment/5508664/+files/CVE-2019-2386-bionic-20210702.debdiff

** Patch removed: "CVE-2019-2386-bionic-20210706.debdiff"
   https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1934518/+attachment/5509448/+files/CVE-2019-2386-bionic-20210706.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/1934518

Title:
   improper invalidation of authorization sessions

Status in mongodb source package in Trusty:
  Confirmed
Status in mongodb source package in Bionic:
  Confirmed
Status in mongodb source package in Focal:
  Confirmed

Bug description:
  CVE: https://ubuntu.com/security/CVE-2019-2386

  After user deletion in MongoDB Server the improper invalidation of
  authorization sessions allows an authenticated user’s session to
  persist and become conflated with new accounts, if those accounts
  reuse the names of deleted ones. This issue affects: MongoDB Inc.
  MongoDB Server v4.0 versions prior to 4.0.9; v3.6 versions prior to
  3.6.13; v3.4 versions prior to 3.4.22.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/mongodb/+bug/1934518/+subscriptions



From 1933520 at bugs.launchpad.net  Tue Aug  3 20:54:59 2021
From: 1933520 at bugs.launchpad.net (Heather Lemon)
Date: Tue, 03 Aug 2021 20:54:59 -0000
Subject: [Bug 1933520] Re: message decompressor to incorrectly allocate memory
References: <162455012060.17952.5873516193423039097.malonedeb@gac.canonical.com>
Message-ID: <162802410025.3800.15691017238927042174.launchpad@soybean.canonical.com>

** Patch removed: "CVE-2019-20925-bionic-20210706.debdiff"
   https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+attachment/5509447/+files/CVE-2019-20925-bionic-20210706.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/1933520

Title:
  message decompressor to incorrectly allocate memory

Status in mongodb source package in Bionic:
  Confirmed
Status in mongodb source package in Focal:
  Confirmed

Bug description:
  CVE 2019-20925: https://ubuntu.com/security/CVE-2019-20925

  An unauthenticated client can trigger denial of service by issuing
  specially crafted wire protocol messages, which cause the message
  decompressor to incorrectly allocate memory. This issue affects:
  MongoDB Inc. MongoDB Server v4.2 versions prior to 4.2.1; v4.0
  versions prior to 4.0.13; v3.6 versions prior to 3.6.15; v3.4 versions
  prior to 3.4.24.

  commit:
  https://github.com/mongodb/mongo/commit/c1a956e084d39e6da75cd347e63d0064ed9151a8

  Affected versions
  Ubuntu 18.04 LTS (Bionic Beaver)
  Ubuntu 20.04 LTS (Focal Fossa)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+subscriptions



From 1933520 at bugs.launchpad.net  Tue Aug  3 21:34:33 2021
From: 1933520 at bugs.launchpad.net (Heather Lemon)
Date: Tue, 03 Aug 2021 21:34:33 -0000
Subject: [Bug 1933520] Re: message decompressor to incorrectly allocate memory
References: <162455012060.17952.5873516193423039097.malonedeb@gac.canonical.com>
Message-ID: <162802647349.25959.3874228443046303255.malone@wampee.canonical.com>

redo debdiff for pulling from 3.4 not 3.6 
https://github.com/mongodb/mongo/commit/c1a956e084d39e6da75cd347e63d0064ed9151a8

** Patch added: "CVE-2019-20925-bionic-1933520-20210803-decompressor.debdiff"
   https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+attachment/5515614/+files/CVE-2019-20925-bionic-1933520-20210803-decompressor.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/1933520

Title:
  message decompressor to incorrectly allocate memory

Status in mongodb source package in Bionic:
  Confirmed
Status in mongodb source package in Focal:
  Confirmed

Bug description:
  CVE 2019-20925: https://ubuntu.com/security/CVE-2019-20925

  An unauthenticated client can trigger denial of service by issuing
  specially crafted wire protocol messages, which cause the message
  decompressor to incorrectly allocate memory. This issue affects:
  MongoDB Inc. MongoDB Server v4.2 versions prior to 4.2.1; v4.0
  versions prior to 4.0.13; v3.6 versions prior to 3.6.15; v3.4 versions
  prior to 3.4.24.

  commit:
  https://github.com/mongodb/mongo/commit/c1a956e084d39e6da75cd347e63d0064ed9151a8

  Affected versions
  Ubuntu 18.04 LTS (Bionic Beaver)
  Ubuntu 20.04 LTS (Focal Fossa)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+subscriptions



From 1933520 at bugs.launchpad.net  Tue Aug  3 23:05:00 2021
From: 1933520 at bugs.launchpad.net (Heather Lemon)
Date: Tue, 03 Aug 2021 23:05:00 -0000
Subject: [Bug 1933520] Re: message decompressor to incorrectly allocate memory
References: <162455012060.17952.5873516193423039097.malonedeb@gac.canonical.com>
Message-ID: <162803190065.26773.2420464433960945153.malone@chaenomeles.canonical.com>

rename patch to CVE-2019-20925-SERVER

** Patch removed: "CVE-2019-20925-bionic-1933520-20210803-decompressor.debdiff"
   https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+attachment/5515614/+files/CVE-2019-20925-bionic-1933520-20210803-decompressor.debdiff

** Patch added: "CVE-2019-20925-bionic-1933520-20210803-decompressor.debdiff"
   https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+attachment/5515616/+files/CVE-2019-20925-bionic-1933520-20210803-decompressor.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/1933520

Title:
  message decompressor to incorrectly allocate memory

Status in mongodb source package in Bionic:
  Confirmed
Status in mongodb source package in Focal:
  Confirmed

Bug description:
  CVE 2019-20925: https://ubuntu.com/security/CVE-2019-20925

  An unauthenticated client can trigger denial of service by issuing
  specially crafted wire protocol messages, which cause the message
  decompressor to incorrectly allocate memory. This issue affects:
  MongoDB Inc. MongoDB Server v4.2 versions prior to 4.2.1; v4.0
  versions prior to 4.0.13; v3.6 versions prior to 3.6.15; v3.4 versions
  prior to 3.4.24.

  commit:
  https://github.com/mongodb/mongo/commit/c1a956e084d39e6da75cd347e63d0064ed9151a8

  Affected versions
  Ubuntu 18.04 LTS (Bionic Beaver)
  Ubuntu 20.04 LTS (Focal Fossa)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+subscriptions



From 1934518 at bugs.launchpad.net  Tue Aug  3 23:14:50 2021
From: 1934518 at bugs.launchpad.net (Heather Lemon)
Date: Tue, 03 Aug 2021 23:14:50 -0000
Subject: [Bug 1934518] Re:  improper invalidation of authorization sessions 
References: <162523373063.25728.9542415532730002380.malonedeb@wampee.canonical.com>
Message-ID: <162803249018.27048.8401556835090778916.malone@gac.canonical.com>

I am getting a build failure after integrating the changes from v3.4 
https://github.com/mongodb/mongo/commit/64d8e9e1b12d16b54d6a592bae8110226c491b4e

Checking for mongoc_get_major_version() in C library mongoc-1.0... no
*** Run 'pip2 install --user regex' to speed up error code checking
DUPLICATE IDS: 40437
  src/mongo/bson/bsonelement.h:624:17:uassert(40437
  src/mongo/bson/bsonelement.h:655:17:uassert(40437
next id to use: 40679
debian/rules:45: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1
make[1]: Leaving directory '/root/userid-validate-CVE-2019-2386/mongodb-3.6.3'
debian/rules:74: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
debuild: fatal error at line 1152:
dpkg-buildpackage -rfakeroot -us -uc -ui -S -i failed

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

Title:
   improper invalidation of authorization sessions

Status in mongodb source package in Trusty:
  Confirmed
Status in mongodb source package in Bionic:
  Confirmed
Status in mongodb source package in Focal:
  Confirmed

Bug description:
  CVE: https://ubuntu.com/security/CVE-2019-2386

  After user deletion in MongoDB Server the improper invalidation of
  authorization sessions allows an authenticated user’s session to
  persist and become conflated with new accounts, if those accounts
  reuse the names of deleted ones. This issue affects: MongoDB Inc.
  MongoDB Server v4.0 versions prior to 4.0.9; v3.6 versions prior to
  3.6.13; v3.4 versions prior to 3.4.22.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/mongodb/+bug/1934518/+subscriptions



From 1938747 at bugs.launchpad.net  Wed Aug  4 01:37:05 2021
From: 1938747 at bugs.launchpad.net (Hui Wang)
Date: Wed, 04 Aug 2021 01:37:05 -0000
Subject: [Bug 1938747] Re: [SRU] can't adjust output volume through
 volume-slider after changing output-device
References: <162796498319.3519.6613983265788106615.malonedeb@wampee.canonical.com>
Message-ID: <162804102586.27011.902135962317046140.malone@gac.canonical.com>

Thanks Gunnar, unsubscribe ubuntu-sponsors 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/1938747

Title:
  [SRU] can't adjust output volume through volume-slider after changing
  output-device

Status in HWE Next:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  In Progress
Status in gnome-control-center source package in Hirsute:
  In Progress
Status in gnome-control-center source package in Impish:
  Fix Released

Bug description:
  [Impact]
  On the machine with the legacy HDA audio driver, suppose the current output device is Speaker, users plug a HDMI monitor and select the HDMI audio as the current output device in the g-c-c, after that the output volume can't be adjusted through the volume-slider in the g-c-c. The UI of the volume-slider could be changed, but the output volume doesn't change.

  [Fix]
  Backport 1 upstream commit 0f18a662be6ee0d225249d1ad003dfef69294449. The root cause of this issue is the stream is not got when changing the output-device, the patch adds the getting stream in the update_sink callback, this could fix this bug.

  [Test]
  run the patches g-c-c, plug a hdmi monitor, select the HDMI audio from g-c-c, then change the output volume via volume-slider, play music, the sound could be changed with the adjustment with the volume-slider.

  [Where problems will occur]
  This patch brings the change to the output and input volume adjustment in the cc-sound-panel, this could make the output/input volume changing not work anymore, for example, the internal speaker or internal mic work well, after plugging a headset, the output device changes to headphone, the intput device changes to Mic, then the volume adjustment doesn't work on headphone and Mic anymore. But this possibility is very low since I tested the patch on different Lenovo and Dell machines, no regression found so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1938747/+subscriptions



From 1919451 at bugs.launchpad.net  Wed Aug  4 08:08:54 2021
From: 1919451 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Wed, 04 Aug 2021 08:08:54 -0000
Subject: [Bug 1919451] Re: Update (python-)zhmcclient to latest release
References: <161598044626.18813.3480195737308253543.malonedeb@soybean.canonical.com>
Message-ID: <162806453581.20394.11316608694649366459.launchpad@chaenomeles.canonical.com>

** Changed in: zhmcclient (Ubuntu Focal)
       Status: Incomplete => In Progress

** Changed in: zhmcclient (Ubuntu Hirsute)
       Status: New => 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/1919451

Title:
  Update (python-)zhmcclient to latest release

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zhmcclient package in Ubuntu:
  Fix Released
Status in zhmcclient source package in Focal:
  In Progress
Status in zhmcclient source package in Hirsute:
  In Progress

Bug description:
  [Impact]

  In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM
  LinuxONE III (or newer) machines/LPARs from within a MAAS controller,
  the python3-zhmcclient libraray (>= v0.29) is needed, to provide all
  the functions required for controlling the HMC.

  [Test Plan]
   * setup a MAAS controller inside a LPAR
   * use that controller to deploy a new Ubuntu Server instance in an additional LPAR
   * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR)
   * Power-cycle the LPAR instance
   * Power-cycle the KVM instance
   * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
  https://github.com/zhmcclient/python-zhmcclient/tree/master/examples

  Also get confirmation from the MAAS team that things are working as
  expected.

  [Where problems could occur]

  This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller.
  This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either.

  Reviewing the changes/commits starting from 0.28 to 0.31 (68 + 37 + 27
  + 15 commits) let me think that these are largely unintrusive, just a
  few new features were added (like DPM Capacity Groups), the docs,
  examples and lots of meta updated, error and exception handling
  refined <important>, and last but not least several important bugs
  fixed (for installation, .find for objects <again important>,
  certificates, missing argument in method) - some of them were
  identified during the development of DPM/LPAR support in MAAS earlier
  this year (for example LP#1916475).

  Therefore, and because the zhmcclient is not wide-spread yet (since
  MAAS v3.0 is the first version that can make use of it and was just
  made available on June the 22nd), it's for accessing and managing Z
  systems only via the HMC API, which not many organizations allow (in
  general - for security reasons) and because v0.31 was the version that
  was already used for development _nd final product testing (these days
  as a git clone), makes me rating the regression risk as low.

  [Other Info]
  * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z
  * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04
  * The new package dependencies are fulfilled in Focal:
    - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main)
    - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main)

  === Original description ===

  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions
  work, like especially storage group support.

  The latest is package is v0.27 on hirsute and v0.22 on focal.

  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731

  Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was created at all.

  The updated package is especially needed for focal, since focal is the
  recommended base distro for MAAS DPM/LPAR, hence this would require a
  special SRU (for this package version bump).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions



From 1934209 at bugs.launchpad.net  Wed Aug  4 14:10:25 2021
From: 1934209 at bugs.launchpad.net (Yuan-Chen Cheng)
Date: Wed, 04 Aug 2021 14:10:25 -0000
Subject: [Bug 1934209] Re: Dell dock USB4 module need fwupd 1.5.11
References: <162510466629.25996.15967004560380142578.malonedeb@gac.canonical.com>
Message-ID: <162808622674.6406.6739700934715915020.launchpad@gac.canonical.com>

** Changed in: fwupd-signed (Ubuntu Hirsute)
       Status: Fix Committed => Fix Released

** Changed in: oem-priority
       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/1934209

Title:
  Dell dock USB4 module need fwupd 1.5.11

Status in OEM Priority Project:
  Fix Released
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Focal:
  Fix Released
Status in fwupd-signed source package in Focal:
  Fix Released
Status in fwupd source package in Hirsute:
  Fix Released
Status in fwupd-signed source package in Hirsute:
  Fix Released
Status in fwupd source package in Impish:
  Fix Released
Status in fwupd-signed source package in Impish:
  Fix Released

Bug description:
  need focal/fwupd 1.5.11 to support this

  Ref: https://github.com/fwupd/fwupd/releases/tag/1.5.11

  Note: this version shall work well with shim with sbat.
  Note: for focal, we also need to upgrade jcat to make it work.

  [Impact]

   * We need to support Dell USB4 Dock and based on the fwupd design,
     need to upgrade the version to support it.

   * This new version will also enable certain vendors to upgrade
     intel-microcode by fwupd. Some security updates of intel-microcode
     does introduce regresssion because it's not tested across enough
     CPU family. Vendors can do more tests give they have access to
     those machines and have access to those new microcodes with
     security patches.

   * Will follow the new policy to do this SRU exception.
     https://wiki.ubuntu.com/firmware-updates

  [Test Plan]

   * Full standard verification test listed in
     https://wiki.ubuntu.com/firmware-updates

   * Install a sbat enable shim, turned on secure boot and make sure
     the new fwupd firmware upgrade efi still work fine.

   * Will also invite the component vendor to test the new supported
     docking when the new fwupd exists in the proposed channel.
     They already started to use the one in my ppa on focal given
     LTS release is the HWE project target.

  [Where problems could occur]

   * If it passed the verification procedure in the policy, I believe
     it shall already cover most cases.

  [Other Info]

   * This suppose to fix several bugs. OEM team will test
     those along the way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934209/+subscriptions



From 1938946 at bugs.launchpad.net  Wed Aug  4 19:06:14 2021
From: 1938946 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 04 Aug 2021 19:06:14 -0000
Subject: [Bug 1938946] [NEW] Sync python-a38 0.1.3-2 (universe) from Debian
 unstable (main)
References: <162810397121.11975.16550884511435703023.malonedeb@wampee.canonical.com>
Message-ID: <162810397473.20144.12937787264517895420.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Hans Joachim Desserud (hjd):

Please sync python-a38 0.1.3-2 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * tests/test_p7m.py:
    - tests/data/test.txt.p7m has expired and this test fails,
      so just skip it. Upstream has not been updated in 2 years
      so it's unlikely this cert will be updated by upstream.


Patch to skip test has now been included in the Debian package.

Changelog entries since current impish version 0.1.3-1ubuntu1:

python-a38 (0.1.3-2) unstable; urgency=medium

  * Skip tests that fail because of an expired certificate. (Closes:
#991648)

 -- Elena Grandi <valhalla at debian.org>  Fri, 30 Jul 2021 12:01:58 +0200

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

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


From 1782984 at bugs.launchpad.net  Thu Aug  5 07:24:03 2021
From: 1782984 at bugs.launchpad.net (Timo Aaltonen)
Date: Thu, 05 Aug 2021 07:24:03 -0000
Subject: [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed
 with multiple applications
References: <153226365365.23524.716838067617811954.malonedeb@soybean.canonical.com>
Message-ID: <162814824485.4290.12392855511064345741.launchpad@gac.canonical.com>

** Changed in: libx11 (Ubuntu Focal)
       Status: Confirmed => In Progress

** Changed in: libx11 (Ubuntu Bionic)
       Status: Confirmed => In Progress

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  In Progress
Status in libx11 source package in Focal:
  In Progress
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  STEPS TO REPRODUCE
  ==================
  The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation.

  EXPECTED RESULTS
  ================
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==============
  All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =================
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  ============
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  ================
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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



From 1909733 at bugs.launchpad.net  Thu Aug  5 07:36:22 2021
From: 1909733 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 07:36:22 -0000
Subject: [Bug 1909733] Re: [MIR] oem-sutton.newell-adkins-meta
References: <160939901989.28737.4740305652778216756.malonedeb@gac.canonical.com>
Message-ID: <162814898209.8065.17688887741542285664.malone@soybean.canonical.com>

Hello Bin, or anyone else affected,

Accepted oem-sutton.newell-adkins-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.newell-adkins-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.newell-adkins-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.newell-adkins-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.newell-adkins-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-sutton.newell-adkins-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.newell-adkins-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.newell-adkins-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.newell-adkins-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-adkins-meta for focal:
      git clone -b newell.adkins-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkPad X1 Nano Gen 1.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkPad X1 Nano Gen 1.
  oem-sutton.newell-adkins-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202012-28574

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1909733/+subscriptions



From 1893616 at bugs.launchpad.net  Thu Aug  5 07:45:13 2021
From: 1893616 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 07:45:13 -0000
Subject: [Bug 1893616] Re: [MIR] oem-sutton.simon-barbara-meta
References: <159885993002.21231.11327398475551015259.malonedeb@chaenomeles.canonical.com>
Message-ID: <162814951336.5985.9426964018256203700.malone@gac.canonical.com>

Hello Bin, or anyone else affected,

Accepted oem-sutton.simon-barbara-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.simon-barbara-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.simon-barbara-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.simon-barbara-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.simon-barbara-meta (Ubuntu Focal)
       Status: New => In Progress

** Changed in: oem-sutton.simon-barbara-meta (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Changed in: oem-sutton.simon-barbara-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.simon-barbara-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.simon-barbara-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.simon-barbara-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-barbara-meta for focal:
      git clone -b simon.barbara-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkStation P330.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkStation P330.
  oem-sutton.simon-barbara-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202008-28190

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893616/+subscriptions



From 1902820 at bugs.launchpad.net  Thu Aug  5 07:50:41 2021
From: 1902820 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 07:50:41 -0000
Subject: [Bug 1902820] Re: [MIR] oem-sutton.newell-canyon-meta
References: <160446515007.313.3017689582058793507.malonedeb@chaenomeles.canonical.com>
Message-ID: <162814984192.10317.1032329552924714432.malone@soybean.canonical.com>

Hello Bin, or anyone else affected,

Accepted oem-sutton.newell-canyon-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.newell-canyon-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.newell-canyon-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.newell-canyon-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.newell-canyon-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-sutton.newell-canyon-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.newell-canyon-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.newell-canyon-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.newell-canyon-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-canyon-meta for focal:
      git clone -b newell.canyon-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkCentre M75s/t Gen 2.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkCentre M75s/t Gen 2.
  oem-sutton.newell-canyon-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202010-28340
  https://ubuntu.com/certified/202010-28342

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1902820/+subscriptions



From 1924727 at bugs.launchpad.net  Thu Aug  5 08:02:17 2021
From: 1924727 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 08:02:17 -0000
Subject: [Bug 1924727] Re: [MIR] oem-sutton.newell-aenedleah-meta
References: <161856666138.16050.17574210822109530422.malonedeb@chaenomeles.canonical.com>
Message-ID: <162815053747.21686.7902760183219949956.malone@chaenomeles.canonical.com>

Hello OEM, or anyone else affected,

Accepted oem-sutton.newell-aenedleah-meta into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.newell-aenedleah-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.newell-canyon-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.newell-canyon-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.newell-canyon-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-sutton.newell-canyon-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.newell-aenedleah-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.newell-canyon-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.newell-canyon-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-aenedleah-meta for focal:
      git clone -b newell.aenedleah-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-aenedleah-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202104-28987

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924727/+subscriptions



From 1930564 at bugs.launchpad.net  Thu Aug  5 08:14:20 2021
From: 1930564 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 08:14:20 -0000
Subject: [Bug 1930564] Re: [MIR] oem-sutton.newell-adrian-meta
References: <162262690796.29117.14096678191505230951.malonedeb@chaenomeles.canonical.com>
Message-ID: <162815126056.23445.2458994887750428661.malone@chaenomeles.canonical.com>

Hello Bin, or anyone else affected,

Accepted oem-sutton.newell-adrian-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.newell-adrian-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.newell-adrian-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.newell-adrian-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.newell-adrian-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-sutton.newell-adrian-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.newell-adrian-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.newell-adrian-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.newell-adrian-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-adrian-meta for focal:
      git clone -b newell.adrian-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkPad X1 Titanium Gen 1.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkPad X1 Titanium Gen 1.
  oem-sutton.newell-adrian-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202104-28989

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1930564/+subscriptions



From 1910952 at bugs.launchpad.net  Thu Aug  5 10:59:15 2021
From: 1910952 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 10:59:15 -0000
Subject: [Bug 1910952] Re: [MIR] oem-sutton.newell-adrion-meta
References: <161034470694.22048.6669612133363727884.malonedeb@wampee.canonical.com>
Message-ID: <162816115542.17873.16407953181256877452.malone@gac.canonical.com>

Hello Bin, or anyone else affected,

Accepted oem-sutton.newell-adrion-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.newell-adrion-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.newell-adrion-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.newell-adrion-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.newell-adrion-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-sutton.newell-adrion-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.newell-adrion-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.newell-adrion-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.newell-adrion-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-adrion-meta for focal:
      git clone -b newell.adrion-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkPad L13 Yoga Gen 2.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkPad L13 Yoga Gen 2.
  oem-sutton.newell-adrion-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202011-28408

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1910952/+subscriptions



From 1908865 at bugs.launchpad.net  Thu Aug  5 11:07:31 2021
From: 1908865 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 11:07:31 -0000
Subject: [Bug 1908865] Re: [MIR] oem-sutton.newell-carin-meta
References: <160853132747.28956.13462929633048402940.malonedeb@gac.canonical.com>
Message-ID: <162816165115.25329.17197433689322636239.malone@soybean.canonical.com>

Hello Bin, or anyone else affected,

Accepted oem-sutton.newell-carin-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.newell-carin-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.newell-carin-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.newell-carin-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.newell-carin-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-sutton.newell-carin-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.newell-carin-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.newell-carin-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.newell-carin-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carin-meta for focal:
      git clone -b newell.carin-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for ThinkCentre M60e.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on ThinkCentre M60e.
  oem-sutton.newell-carin-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202010-28307

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1908865/+subscriptions



From 1789177 at bugs.launchpad.net  Thu Aug  5 14:08:32 2021
From: 1789177 at bugs.launchpad.net (OpenStack Infra)
Date: Thu, 05 Aug 2021 14:08:32 -0000
Subject: [Bug 1789177] Change abandoned on oslo.messaging (stable/rocky)
References: <153535779443.12123.15995792084021935855.malonedeb@chaenomeles.canonical.com>
Message-ID: <162817251291.2191.2338325918386790128.malone@soybean.canonical.com>

Change abandoned by "Hervé Beraud <herveberaud.pro at gmail.com>" on branch: stable/rocky
Review: https://review.opendev.org/c/openstack/oslo.messaging/+/749194
Reason: rocky is now unmaintained

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

Title:
  RabbitMQ fails to synchronize exchanges under high load (Note for
  ubuntu: stein, rocky, queens(bionic) changes only fix compatibility
  with fully patched releases)

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Fix Released
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 oslo.messaging:
  Fix Released
Status in python-oslo.messaging package in Ubuntu:
  Fix Released
Status in python-oslo.messaging source package in Xenial:
  Invalid
Status in python-oslo.messaging source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  If there are many exchanges and queues, after failing over, rabbitmq-
  server shows us error that exchanges are cannot be found.

  Affected
   Bionic (Queens)
  Not affected
   Focal

  [Test Case]

  1. deploy simple rabbitmq cluster
  - https://pastebin.ubuntu.com/p/MR76VbMwY5/
  2. juju ssh neutron-gateway/0
  - for i in {1..1000}; do systemd restart neutron-metering-agent; sleep 2; done
  3. it would be better if we can add more exchanges, queues, bindings
  - rabbitmq-plugins enable rabbitmq_management
  - rabbitmqctl add_user test password
  - rabbitmqctl set_user_tags test administrator
  - rabbitmqctl set_permissions -p openstack test ".*" ".*" ".*"
  - https://pastebin.ubuntu.com/p/brw7rSXD7q/ ( save this as create.sh) [1]
  - for i in {1..2000}; do ./create.sh test_$i; done

  4. restart rabbitmq-server service or shutdown machine and turn on several times.
  5. you can see the exchange not found error

  [1] create.sh (pasting here because pastebins don't last forever)
  #!/bin/bash

  rabbitmqadmin declare exchange -V openstack name=$1 type=direct -u test -p password
  rabbitmqadmin declare queue -V openstack name=$1 durable=false -u test -p password 'arguments={"x-expires":1800000}'
  rabbitmqadmin -V openstack declare binding source=$1 destination_type="queue" destination=$1 routing_key="" -u test -p password

  [Where problems could occur]
  1. every service which uses oslo.messaging need to be restarted.
  2. Message transferring could be an issue

  [Others]

  Possible Workaround

  1. for exchange not found issue,
  - create exchange, queue, binding for problematic name in log
  - then restart rabbitmq-server one by one

  2. for queue crashed and failed to restart
  - delete specific queue in log

  
  // original description

  Input:
   - OpenStack Pike cluster with ~500 nodes
   - DVR enabled in neutron
   - Lots of messages

  Scenario: failover of one rabbit node in a cluster

  Issue: after failed rabbit node gets back online some rpc communications appear broken
  Logs from rabbit:

  =ERROR REPORT==== 10-Aug-2018::17:24:37 ===
  Channel error on connection <0.14839.1> (10.200.0.24:55834 -> 10.200.0.31:5672, vhost: '/openstack', user: 'openstack'), channel 1:
  operation basic.publish caused a channel exception not_found: no exchange 'reply_5675d7991b4a4fb7af5d239f4decb19f' in vhost '/openstack'

  Investigation:
  After rabbit node gets back online it gets many new connections immediately and fails to synchronize exchanges for some reason (number of exchanges in that cluster was ~1600), on that node it stays low and not increasing.

  Workaround: let the recovered node synchronize all exchanges - forbid
  new connections with iptables rules for some time after failed node
  gets online (30 sec)

  Proposal: do not create new exchanges (use default) for all direct
  messages - this also fixes the issue.

  Is there a good reason for creating new exchanges for direct messages?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions



From 1789177 at bugs.launchpad.net  Thu Aug  5 14:20:10 2021
From: 1789177 at bugs.launchpad.net (OpenStack Infra)
Date: Thu, 05 Aug 2021 14:20:10 -0000
Subject: [Bug 1789177] Change abandoned on oslo.messaging (stable/pike)
References: <153535779443.12123.15995792084021935855.malonedeb@chaenomeles.canonical.com>
Message-ID: <162817321015.32386.13052949570841736701.malone@gac.canonical.com>

Change abandoned by "Hervé Beraud <herveberaud.pro at gmail.com>" on branch: stable/pike
Review: https://review.opendev.org/c/openstack/oslo.messaging/+/728396
Reason: stable/pike is no longer maintained (https://releases.openstack.org/). Thanks for your understanding

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

Title:
  RabbitMQ fails to synchronize exchanges under high load (Note for
  ubuntu: stein, rocky, queens(bionic) changes only fix compatibility
  with fully patched releases)

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Fix Released
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 oslo.messaging:
  Fix Released
Status in python-oslo.messaging package in Ubuntu:
  Fix Released
Status in python-oslo.messaging source package in Xenial:
  Invalid
Status in python-oslo.messaging source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  If there are many exchanges and queues, after failing over, rabbitmq-
  server shows us error that exchanges are cannot be found.

  Affected
   Bionic (Queens)
  Not affected
   Focal

  [Test Case]

  1. deploy simple rabbitmq cluster
  - https://pastebin.ubuntu.com/p/MR76VbMwY5/
  2. juju ssh neutron-gateway/0
  - for i in {1..1000}; do systemd restart neutron-metering-agent; sleep 2; done
  3. it would be better if we can add more exchanges, queues, bindings
  - rabbitmq-plugins enable rabbitmq_management
  - rabbitmqctl add_user test password
  - rabbitmqctl set_user_tags test administrator
  - rabbitmqctl set_permissions -p openstack test ".*" ".*" ".*"
  - https://pastebin.ubuntu.com/p/brw7rSXD7q/ ( save this as create.sh) [1]
  - for i in {1..2000}; do ./create.sh test_$i; done

  4. restart rabbitmq-server service or shutdown machine and turn on several times.
  5. you can see the exchange not found error

  [1] create.sh (pasting here because pastebins don't last forever)
  #!/bin/bash

  rabbitmqadmin declare exchange -V openstack name=$1 type=direct -u test -p password
  rabbitmqadmin declare queue -V openstack name=$1 durable=false -u test -p password 'arguments={"x-expires":1800000}'
  rabbitmqadmin -V openstack declare binding source=$1 destination_type="queue" destination=$1 routing_key="" -u test -p password

  [Where problems could occur]
  1. every service which uses oslo.messaging need to be restarted.
  2. Message transferring could be an issue

  [Others]

  Possible Workaround

  1. for exchange not found issue,
  - create exchange, queue, binding for problematic name in log
  - then restart rabbitmq-server one by one

  2. for queue crashed and failed to restart
  - delete specific queue in log

  
  // original description

  Input:
   - OpenStack Pike cluster with ~500 nodes
   - DVR enabled in neutron
   - Lots of messages

  Scenario: failover of one rabbit node in a cluster

  Issue: after failed rabbit node gets back online some rpc communications appear broken
  Logs from rabbit:

  =ERROR REPORT==== 10-Aug-2018::17:24:37 ===
  Channel error on connection <0.14839.1> (10.200.0.24:55834 -> 10.200.0.31:5672, vhost: '/openstack', user: 'openstack'), channel 1:
  operation basic.publish caused a channel exception not_found: no exchange 'reply_5675d7991b4a4fb7af5d239f4decb19f' in vhost '/openstack'

  Investigation:
  After rabbit node gets back online it gets many new connections immediately and fails to synchronize exchanges for some reason (number of exchanges in that cluster was ~1600), on that node it stays low and not increasing.

  Workaround: let the recovered node synchronize all exchanges - forbid
  new connections with iptables rules for some time after failed node
  gets online (30 sec)

  Proposal: do not create new exchanges (use default) for all direct
  messages - this also fixes the issue.

  Is there a good reason for creating new exchanges for direct messages?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions



From 1789177 at bugs.launchpad.net  Thu Aug  5 14:26:47 2021
From: 1789177 at bugs.launchpad.net (OpenStack Infra)
Date: Thu, 05 Aug 2021 14:26:47 -0000
Subject: [Bug 1789177] Change abandoned on oslo.messaging (stable/queens)
References: <153535779443.12123.15995792084021935855.malonedeb@chaenomeles.canonical.com>
Message-ID: <162817360709.12178.8195528809778961070.malone@chaenomeles.canonical.com>

Change abandoned by "Hervé Beraud <herveberaud.pro at gmail.com>" on branch: stable/queens
Review: https://review.opendev.org/c/openstack/oslo.messaging/+/749196
Reason: Queens is no longer maintained (https://releases.openstack.org/).

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

Title:
  RabbitMQ fails to synchronize exchanges under high load (Note for
  ubuntu: stein, rocky, queens(bionic) changes only fix compatibility
  with fully patched releases)

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Fix Released
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 oslo.messaging:
  Fix Released
Status in python-oslo.messaging package in Ubuntu:
  Fix Released
Status in python-oslo.messaging source package in Xenial:
  Invalid
Status in python-oslo.messaging source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  If there are many exchanges and queues, after failing over, rabbitmq-
  server shows us error that exchanges are cannot be found.

  Affected
   Bionic (Queens)
  Not affected
   Focal

  [Test Case]

  1. deploy simple rabbitmq cluster
  - https://pastebin.ubuntu.com/p/MR76VbMwY5/
  2. juju ssh neutron-gateway/0
  - for i in {1..1000}; do systemd restart neutron-metering-agent; sleep 2; done
  3. it would be better if we can add more exchanges, queues, bindings
  - rabbitmq-plugins enable rabbitmq_management
  - rabbitmqctl add_user test password
  - rabbitmqctl set_user_tags test administrator
  - rabbitmqctl set_permissions -p openstack test ".*" ".*" ".*"
  - https://pastebin.ubuntu.com/p/brw7rSXD7q/ ( save this as create.sh) [1]
  - for i in {1..2000}; do ./create.sh test_$i; done

  4. restart rabbitmq-server service or shutdown machine and turn on several times.
  5. you can see the exchange not found error

  [1] create.sh (pasting here because pastebins don't last forever)
  #!/bin/bash

  rabbitmqadmin declare exchange -V openstack name=$1 type=direct -u test -p password
  rabbitmqadmin declare queue -V openstack name=$1 durable=false -u test -p password 'arguments={"x-expires":1800000}'
  rabbitmqadmin -V openstack declare binding source=$1 destination_type="queue" destination=$1 routing_key="" -u test -p password

  [Where problems could occur]
  1. every service which uses oslo.messaging need to be restarted.
  2. Message transferring could be an issue

  [Others]

  Possible Workaround

  1. for exchange not found issue,
  - create exchange, queue, binding for problematic name in log
  - then restart rabbitmq-server one by one

  2. for queue crashed and failed to restart
  - delete specific queue in log

  
  // original description

  Input:
   - OpenStack Pike cluster with ~500 nodes
   - DVR enabled in neutron
   - Lots of messages

  Scenario: failover of one rabbit node in a cluster

  Issue: after failed rabbit node gets back online some rpc communications appear broken
  Logs from rabbit:

  =ERROR REPORT==== 10-Aug-2018::17:24:37 ===
  Channel error on connection <0.14839.1> (10.200.0.24:55834 -> 10.200.0.31:5672, vhost: '/openstack', user: 'openstack'), channel 1:
  operation basic.publish caused a channel exception not_found: no exchange 'reply_5675d7991b4a4fb7af5d239f4decb19f' in vhost '/openstack'

  Investigation:
  After rabbit node gets back online it gets many new connections immediately and fails to synchronize exchanges for some reason (number of exchanges in that cluster was ~1600), on that node it stays low and not increasing.

  Workaround: let the recovered node synchronize all exchanges - forbid
  new connections with iptables rules for some time after failed node
  gets online (30 sec)

  Proposal: do not create new exchanges (use default) for all direct
  messages - this also fixes the issue.

  Is there a good reason for creating new exchanges for direct messages?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1789177/+subscriptions



From 1923285 at bugs.launchpad.net  Thu Aug  5 14:37:49 2021
From: 1923285 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 14:37:49 -0000
Subject: [Bug 1923285] Re: [MIR] oem-sutton.simon-aenescumb-meta
References: <161802287931.31619.2239149582843054786.malonedeb@gac.canonical.com>
Message-ID: <162817427003.9290.11057231415489704682.malone@soybean.canonical.com>

Hello OEM, or anyone else affected,

Accepted oem-sutton.simon-aenescumb-meta into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.simon-aenescumb-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.simon-aenescumb-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.simon-aenescumb-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.simon-aenescumb-meta (Ubuntu)
       Status: New => Won't Fix

** Changed in: oem-sutton.simon-aenescumb-meta (Ubuntu Focal)
       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/1923285

Title:
  [MIR] oem-sutton.simon-aenescumb-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.simon-aenescumb-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.simon-aenescumb-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-aenescumb-meta for focal:
      git clone -b simon.aenescumb-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-aenescumb-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202103-28877
  https://ubuntu.com/certified/202103-28879

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923285/+subscriptions



From 1932449 at bugs.launchpad.net  Thu Aug  5 15:44:11 2021
From: 1932449 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 15:44:11 -0000
Subject: [Bug 1932449] Re: [MIR] oem-sutton.simon-cabernet-meta
References: <162400365573.14232.5023731108567257724.malonedeb@wampee.canonical.com>
Message-ID: <162817825163.28690.1908433176016910280.malone@soybean.canonical.com>

Hello OEM, or anyone else affected,

Accepted oem-sutton.simon-cabernet-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.simon-cabernet-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.simon-cabernet-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.simon-cabernet-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.simon-cabernet-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-sutton.simon-cabernet-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.simon-cabernet-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.simon-cabernet-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.simon-cabernet-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-cabernet-meta for focal:
      git clone -b simon.cabernet-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-cabernet-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202104-28958

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932449/+subscriptions



From 1932561 at bugs.launchpad.net  Thu Aug  5 16:03:14 2021
From: 1932561 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 16:03:14 -0000
Subject: [Bug 1932561] Re: [MIR] oem-somerville-sanbernardino-meta
References: <162402733063.10319.11571738544764792944.malonedeb@soybean.canonical.com>
Message-ID: <162817939482.30525.16549037987659968841.malone@soybean.canonical.com>

Hello OEM, or anyone else affected,

Accepted oem-somerville-sanbernardino-meta into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/oem-somerville-sanbernardino-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-somerville-sanbernardino-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-somerville-sanbernardino-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-somerville-sanbernardino-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-somerville-sanbernardino-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-somerville-sanbernardino-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-somerville-sanbernardino-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-somerville-sanbernardino-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-somerville-sanbernardino-meta for focal:
      git clone -b sanbernardino-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta

  [Rationale]
  We want to improve the hardware support for some Dell platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms.
  oem-somerville-sanbernardino-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/201711-25935
  https://ubuntu.com/certified/201712-26047

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932561/+subscriptions



From 1864613 at bugs.launchpad.net  Thu Aug  5 23:02:16 2021
From: 1864613 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 23:02:16 -0000
Subject: [Bug 1864613] Re: xfwm4 very, very slow - leaking something?
References: <158261619123.14595.16226605885522077599.malonedeb@soybean.canonical.com>
Message-ID: <162820453649.2490.6276088476622115632.malone@chaenomeles.canonical.com>

I see this upload is present in the SRU queue for quite a while. As
Robie disagreed with accepting it as is, this is currently blocked until
further action is performed and our hands are tied. Is this still being
worked on? What is the status?

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

Title:
  xfwm4 very, very slow - leaking something?

Status in Xfwm4:
  Unknown
Status in xfwm4 package in Ubuntu:
  Fix Released
Status in xfwm4 source package in Focal:
  In Progress
Status in xfwm4 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * There is an error leak in the Xfwm4 compositor, causing the system
  to run slowly after some uptime.

  [Test Plan]

   * Enable the Xfwm4 compositor if it is not already. Settings Manager
  > Window Manager Tweaks > Compositor > Toggle on "Enable Display
  Compositing".

   * Use the desktop for some time. Reportedly, zooming in and out
  repeatedly can speed up the process. To zoom, hold Alt, and scroll up
  and down.

   * The system should start performing poorly after some time, with
  xfwm4 consuming much of the CPU resources.

   * Once fixed, the system should be much more performant after
  performing these tasks.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  After some uptime, xfwm4 is VERY slow at something, to the point that
  it's consuming 100% of CPU on a Xeon system and making the system
  entirely unusable. I don't know who is leaking what, but somebody is
  clearly leaking something.

  I don't have debug symbols, so this is the best I can get:

  Thread 1 (Thread 0x7f7b9d98af00 (LWP 27599)):
  #0  0x00007f7b9f1e8b7f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #1  0x00007f7b9f1e8be2 in gdk_x11_display_error_trap_push () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #2  0x0000555c9582c771 in ?? ()
  #3  0x00007f7b9ee75248 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x00007f7b9ee7471e in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x00007f7b9ee74ad0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #6  0x00007f7b9ee74dc3 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x00007f7b9f4d2c2d in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #8  0x0000555c958222ce in ?? ()
  #9  0x00007f7b9e7861e3 in __libc_start_main (main=0x555c95821b50, argc=6, argv=0x7fffbeb91c18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffbeb91c08) at ../csu/libc-start.c:308
  #10 0x0000555c9582249e in ?? ()

  or

  Thread 1 (Thread 0x7f7b9d98af00 (LWP 27599)):
  #0  0x00007f7b9f1e8b83 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #1  0x00007f7b9f1e8be2 in gdk_x11_display_error_trap_push () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #2  0x0000555c9582e33a in ?? ()
  #3  0x0000555c95834f1b in ?? ()
  #4  0x0000555c958337d0 in ?? ()
  #5  0x00007f7b9f1f0f4f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #6  0x00007f7b9f1f133a in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #7  0x00007f7b9f1b9094 in gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #8  0x00007f7b9f1f0fe6 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  #9  0x00007f7b9ee7484d in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x00007f7b9ee74ad0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x00007f7b9ee74dc3 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x00007f7b9f4d2c2d in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  #13 0x0000555c958222ce in ?? ()
  #14 0x00007f7b9e7861e3 in __libc_start_main (main=0x555c95821b50, argc=6, argv=0x7fffbeb91c18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffbeb91c08) at ../csu/libc-start.c:308
  #15 0x0000555c9582249e in ?? ()

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xfwm4 4.14.0-1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb 24 23:18:34 2020
  InstallationDate: Installed on 2019-01-21 (399 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
  SourcePackage: xfwm4
  UpgradeStatus: Upgraded to eoan on 2019-11-10 (106 days ago)

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



From 1919451 at bugs.launchpad.net  Thu Aug  5 23:15:54 2021
From: 1919451 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 23:15:54 -0000
Subject: [Bug 1919451] Re: Update (python-)zhmcclient to latest release
References: <161598044626.18813.3480195737308253543.malonedeb@soybean.canonical.com>
Message-ID: <162820535421.6208.11205682301422117544.malone@chaenomeles.canonical.com>

Thank you Robie, Lukas and Frank for working on this SRU. I think with
proper analysis performed in #12 and additional context in #11, I am
happy to get this accepted for both hirsute and focal. Please be sure to
perform proper verification.

** Changed in: zhmcclient (Ubuntu Hirsute)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  Update (python-)zhmcclient to latest release

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zhmcclient package in Ubuntu:
  Fix Released
Status in zhmcclient source package in Focal:
  Fix Committed
Status in zhmcclient source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM
  LinuxONE III (or newer) machines/LPARs from within a MAAS controller,
  the python3-zhmcclient libraray (>= v0.29) is needed, to provide all
  the functions required for controlling the HMC.

  [Test Plan]
   * setup a MAAS controller inside a LPAR
   * use that controller to deploy a new Ubuntu Server instance in an additional LPAR
   * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR)
   * Power-cycle the LPAR instance
   * Power-cycle the KVM instance
   * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
  https://github.com/zhmcclient/python-zhmcclient/tree/master/examples

  Also get confirmation from the MAAS team that things are working as
  expected.

  [Where problems could occur]

  This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller.
  This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either.

  Reviewing the changes/commits starting from 0.28 to 0.31 (68 + 37 + 27
  + 15 commits) let me think that these are largely unintrusive, just a
  few new features were added (like DPM Capacity Groups), the docs,
  examples and lots of meta updated, error and exception handling
  refined <important>, and last but not least several important bugs
  fixed (for installation, .find for objects <again important>,
  certificates, missing argument in method) - some of them were
  identified during the development of DPM/LPAR support in MAAS earlier
  this year (for example LP#1916475).

  Therefore, and because the zhmcclient is not wide-spread yet (since
  MAAS v3.0 is the first version that can make use of it and was just
  made available on June the 22nd), it's for accessing and managing Z
  systems only via the HMC API, which not many organizations allow (in
  general - for security reasons) and because v0.31 was the version that
  was already used for development _nd final product testing (these days
  as a git clone), makes me rating the regression risk as low.

  [Other Info]
  * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z
  * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04
  * The new package dependencies are fulfilled in Focal:
    - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main)
    - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main)

  === Original description ===

  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions
  work, like especially storage group support.

  The latest is package is v0.27 on hirsute and v0.22 on focal.

  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731

  Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was created at all.

  The updated package is especially needed for focal, since focal is the
  recommended base distro for MAAS DPM/LPAR, hence this would require a
  special SRU (for this package version bump).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions



From 1919451 at bugs.launchpad.net  Thu Aug  5 23:16:23 2021
From: 1919451 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 23:16:23 -0000
Subject: [Bug 1919451] Please test proposed package
References: <161598044626.18813.3480195737308253543.malonedeb@soybean.canonical.com>
Message-ID: <162820538333.4640.13100140301526220891.malone@chaenomeles.canonical.com>

Hello Frank, or anyone else affected,

Accepted zhmcclient into hirsute-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/zhmcclient/0.31.0-0ubuntu3~21.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, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: zhmcclient (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Update (python-)zhmcclient to latest release

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zhmcclient package in Ubuntu:
  Fix Released
Status in zhmcclient source package in Focal:
  Fix Committed
Status in zhmcclient source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM
  LinuxONE III (or newer) machines/LPARs from within a MAAS controller,
  the python3-zhmcclient libraray (>= v0.29) is needed, to provide all
  the functions required for controlling the HMC.

  [Test Plan]
   * setup a MAAS controller inside a LPAR
   * use that controller to deploy a new Ubuntu Server instance in an additional LPAR
   * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR)
   * Power-cycle the LPAR instance
   * Power-cycle the KVM instance
   * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
  https://github.com/zhmcclient/python-zhmcclient/tree/master/examples

  Also get confirmation from the MAAS team that things are working as
  expected.

  [Where problems could occur]

  This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller.
  This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either.

  Reviewing the changes/commits starting from 0.28 to 0.31 (68 + 37 + 27
  + 15 commits) let me think that these are largely unintrusive, just a
  few new features were added (like DPM Capacity Groups), the docs,
  examples and lots of meta updated, error and exception handling
  refined <important>, and last but not least several important bugs
  fixed (for installation, .find for objects <again important>,
  certificates, missing argument in method) - some of them were
  identified during the development of DPM/LPAR support in MAAS earlier
  this year (for example LP#1916475).

  Therefore, and because the zhmcclient is not wide-spread yet (since
  MAAS v3.0 is the first version that can make use of it and was just
  made available on June the 22nd), it's for accessing and managing Z
  systems only via the HMC API, which not many organizations allow (in
  general - for security reasons) and because v0.31 was the version that
  was already used for development _nd final product testing (these days
  as a git clone), makes me rating the regression risk as low.

  [Other Info]
  * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z
  * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04
  * The new package dependencies are fulfilled in Focal:
    - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main)
    - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main)

  === Original description ===

  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions
  work, like especially storage group support.

  The latest is package is v0.27 on hirsute and v0.22 on focal.

  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731

  Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was created at all.

  The updated package is especially needed for focal, since focal is the
  recommended base distro for MAAS DPM/LPAR, hence this would require a
  special SRU (for this package version bump).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions



From 1919451 at bugs.launchpad.net  Thu Aug  5 23:19:03 2021
From: 1919451 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Thu, 05 Aug 2021 23:19:03 -0000
Subject: [Bug 1919451] Please test proposed package
References: <161598044626.18813.3480195737308253543.malonedeb@soybean.canonical.com>
Message-ID: <162820554380.30545.18147895419892661169.malone@soybean.canonical.com>

Hello Frank, or anyone else affected,

Accepted zhmcclient into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/zhmcclient/0.31.0-0ubuntu3~20.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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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/1919451

Title:
  Update (python-)zhmcclient to latest release

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zhmcclient package in Ubuntu:
  Fix Released
Status in zhmcclient source package in Focal:
  Fix Committed
Status in zhmcclient source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM
  LinuxONE III (or newer) machines/LPARs from within a MAAS controller,
  the python3-zhmcclient libraray (>= v0.29) is needed, to provide all
  the functions required for controlling the HMC.

  [Test Plan]
   * setup a MAAS controller inside a LPAR
   * use that controller to deploy a new Ubuntu Server instance in an additional LPAR
   * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR)
   * Power-cycle the LPAR instance
   * Power-cycle the KVM instance
   * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
  https://github.com/zhmcclient/python-zhmcclient/tree/master/examples

  Also get confirmation from the MAAS team that things are working as
  expected.

  [Where problems could occur]

  This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller.
  This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either.

  Reviewing the changes/commits starting from 0.28 to 0.31 (68 + 37 + 27
  + 15 commits) let me think that these are largely unintrusive, just a
  few new features were added (like DPM Capacity Groups), the docs,
  examples and lots of meta updated, error and exception handling
  refined <important>, and last but not least several important bugs
  fixed (for installation, .find for objects <again important>,
  certificates, missing argument in method) - some of them were
  identified during the development of DPM/LPAR support in MAAS earlier
  this year (for example LP#1916475).

  Therefore, and because the zhmcclient is not wide-spread yet (since
  MAAS v3.0 is the first version that can make use of it and was just
  made available on June the 22nd), it's for accessing and managing Z
  systems only via the HMC API, which not many organizations allow (in
  general - for security reasons) and because v0.31 was the version that
  was already used for development _nd final product testing (these days
  as a git clone), makes me rating the regression risk as low.

  [Other Info]
  * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z
  * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04
  * The new package dependencies are fulfilled in Focal:
    - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main)
    - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main)

  === Original description ===

  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions
  work, like especially storage group support.

  The latest is package is v0.27 on hirsute and v0.22 on focal.

  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731

  Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was created at all.

  The updated package is especially needed for focal, since focal is the
  recommended base distro for MAAS DPM/LPAR, hence this would require a
  special SRU (for this package version bump).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions



From 1937988 at bugs.launchpad.net  Fri Aug  6 06:54:03 2021
From: 1937988 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 06 Aug 2021 06:54:03 -0000
Subject: [Bug 1937988] Re: The image is distorted while use iGPU rendering and
 output via AMD GPU
References: <162727716374.10692.8871227137698749656.malonedeb@chaenomeles.canonical.com>
Message-ID: <162823284404.32112.9256950979619644612.launchpad@chaenomeles.canonical.com>

** Description changed:

- [Steps to reproduce]
+ [Impact]
+ Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes.
+ 
+ [Fix]
+ Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total.
+ 
+ [Test case]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
- 3. Run below command to launch glxgear
+ 3. Run below command to launch glxgears
  Cmd> DRI_PRIME=1 glxgears -info
  
- [Expected result]
- The image is not distrorted while running the glxgears
+ * Expected result
+ The image is not distorted while running the glxgears
  
- [Actual result]
- The image is distrorted while running the glxgears
+ * Actual result
+ The image is distorted while running the glxgears
+ 
+ [Where things might go wrong]
+ This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms.
+ 
  
  ---
  
  Here is the upstream bug for tracking this issue.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Impact]
  Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes.

  [Fix]
  Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total.

  [Test case]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgears
  Cmd> DRI_PRIME=1 glxgears -info

  * Expected result
  The image is not distorted while running the glxgears

  * Actual result
  The image is distorted while running the glxgears

  [Where things might go wrong]
  This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms.

  
  ---

  Here is the upstream bug for tracking this issue.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions



From 1933092 at bugs.launchpad.net  Fri Aug  6 12:38:05 2021
From: 1933092 at bugs.launchpad.net (Bernard Cafarelli)
Date: Fri, 06 Aug 2021 12:38:05 -0000
Subject: [Bug 1933092] Re: snat arp entry missing in qrouter namespace
References: <162427405969.6393.15410591280056043295.malonedeb@soybean.canonical.com>
Message-ID: <162825348675.14838.7423749188214864371.launchpad@chaenomeles.canonical.com>

** Tags added: neutron-proactive-backport-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/1933092

Title:
  snat arp entry missing in qrouter namespace

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive ussuri series:
  Fix Released
Status in Ubuntu Cloud Archive victoria series:
  New
Status in Ubuntu Cloud Archive wallaby series:
  New
Status in Ubuntu Cloud Archive xena series:
  New
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Focal:
  Fix Released
Status in neutron source package in Groovy:
  New
Status in neutron source package in Hirsute:
  New
Status in neutron source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Load Balancers deployed on the cloud are unreachable

  [Test Case]
  1. Deploy openstack with atleast 4 compute nodes with networking features DVR SNAT+L3HA
  2. Execute the script test_snat_arp_entry.sh
  3. The script loops for 20 times creating network, router and connecting router to external, internal network and checking if ARP entries are populated properly on qrouter namespaces
  4. The script stops if arp entries are missing.
  5. If the script runs for 20 loops, then there are no issues.

  [Regression Potential]
  The issue only happens a few times when a router is created, external gateway set and internal subnet attached to router in quick succession. In other cases, the arp entry of snat is already added.
  The fix just adds extra logic to add arp entry retrieving snat information from the router. In working cases, this extra logic will execute commands to add arp entry twice which should not cause further issues.

  [Original Bug Report]
  In one of the cloud environment, the FIP attached to the Octavia Loadbalancer VIP is not reachable. After analysis, we found the ARP entry for SNAT IP is missing in the qrouter namespace where Amphora VM is running. And so the return packets are not forwarded from qrouter to snat on active l3-agent node.

  Version:
  Ubuntu Ussuri packages (16.3.2 point release)
  DVR+SNAT+L3HA enabled

  Expectation is to have PERMANENT arp entry for snat ip on qrouter namespace on all compute nodes
  192.168.33.238 dev qr-4ee692e0-7a lladdr fa:16:3e:25:6a:73 used 38/38/38 probes 0 PERMANENT

  How to reproduce:

  Attaching a script to simulate the problem (without octavia) with following steps
  1. network/subnet/router is created, network attached to router
  2. verify if qrouter on all compute nodes has arp entries related to snat ip
  3. if arp entries exists, delete network/subnet/router
  4. Repeat steps 1,2,3 until missing arp entry is observed.

  I am able to reproduce missing arp entry sometimes in 3rd loop and
  sometimes in 6th loop.

  Observed arp entries for snat ip is updated at the following places
  [1] [2] but get_snat_interfaces() and get_ports_by_subnet() are not
  updated with snat ip in non-working cases.

  [1] https://opendev.org/openstack/neutron/src/commit/dfd04115b059c2263cdd8ac44ccc2ec47614bcc3/neutron/agent/l3/dvr_local_router.py#L570
  [2] https://opendev.org/openstack/neutron/src/commit/dfd04115b059c2263cdd8ac44ccc2ec47614bcc3/neutron/agent/l3/dvr_local_router.py#L317

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1933092/+subscriptions



From 1938946 at bugs.launchpad.net  Fri Aug  6 21:13:26 2021
From: 1938946 at bugs.launchpad.net (Logan Rosen)
Date: Fri, 06 Aug 2021 21:13:26 -0000
Subject: [Bug 1938946] Re: Sync python-a38 0.1.3-2 (universe) from Debian
 unstable (main)
References: <162810397121.11975.16550884511435703023.malonedeb@wampee.canonical.com>
Message-ID: <162828440674.395.9540231103066527773.malone@wampee.canonical.com>

This bug was fixed in the package python-a38 - 0.1.3-2
Sponsored for Hans Joachim Desserud (hjd)

---------------
python-a38 (0.1.3-2) unstable; urgency=medium

  * Skip tests that fail because of an expired certificate. (Closes:
#991648)

 -- Elena Grandi <valhalla at debian.org>  Fri, 30 Jul 2021 12:01:58 +0200

** Changed in: python-a38 (Ubuntu)
     Assignee: (unassigned) => Logan Rosen (logan)

** Changed in: python-a38 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: python-a38 (Ubuntu)
       Status: New => In Progress

** Changed in: python-a38 (Ubuntu)
       Status: In Progress => 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/1938946

Title:
  Sync python-a38 0.1.3-2 (universe) from Debian unstable (main)

Status in python-a38 package in Ubuntu:
  Fix Released

Bug description:
  Please sync python-a38 0.1.3-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * tests/test_p7m.py:
      - tests/data/test.txt.p7m has expired and this test fails,
        so just skip it. Upstream has not been updated in 2 years
        so it's unlikely this cert will be updated by upstream.

  
  Patch to skip test has now been included in the Debian package.

  Changelog entries since current impish version 0.1.3-1ubuntu1:

  python-a38 (0.1.3-2) unstable; urgency=medium

    * Skip tests that fail because of an expired certificate. (Closes:
  #991648)

   -- Elena Grandi <valhalla at debian.org>  Fri, 30 Jul 2021 12:01:58
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-a38/+bug/1938946/+subscriptions



From 1931987 at bugs.launchpad.net  Mon Aug  9 08:56:41 2021
From: 1931987 at bugs.launchpad.net (Alfonso Sanchez-Beato)
Date: Mon, 09 Aug 2021 08:56:41 -0000
Subject: [Bug 1931987] Re: [SRU] Creating FIT images is not supported
References: <162374651866.11595.13047179558275551809.malonedeb@soybean.canonical.com>
Message-ID: <162849940185.29142.2234656324421648480.malone@chaenomeles.canonical.com>

I have verified in focal. Installation generated FIT images on my Kria
system, and reboot was successful. I cannot verify on hirsute though as
I do not have a Kria image for that Ubuntu version.

$ apt policy flash-kernel
flash-kernel:
  Installed: 3.103ubuntu1~20.04.3
  Candidate: 3.103ubuntu1~20.04.3
  Version table:
 *** 3.103ubuntu1~20.04.3 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages
        100 /var/lib/dpkg/status
     3.103ubuntu1~20.04.2 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages
     3.98ubuntu12 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages


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

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

Title:
  [SRU] Creating FIT images is not supported

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

Bug description:
  [Impact]

  flash-kernel does currently not support creating FIT images. There are
  some platforms where this is preferred, for instance for the Kria SOM
  platform.

  This have been just fixed in flash-kernel 3.104ubuntu4 in impish (dev)
  (LP: #1931278), and we would like this ported back to hirsute/focal to
  support Kria SOM platform in focal.

  [Test Plan]

  For testing, a Kria SOM device is needed. By install flash-kernel with
  the fix, a file in path /boot/firmware/image.fit will be created, and
  the system should be able to boot.

  [Where problems could occur]

  The change adds new functionality which should not interfere with the
  previous one. However, there is some small potential for a regression
  happening. If that is the case, some hardware platforms that use
  flash-kernel might not be able to update the bootloader or will break
  it, making the system unable to boot.

  [Other Info]

  See LP: #1931278

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



From 1937988 at bugs.launchpad.net  Mon Aug  9 09:07:13 2021
From: 1937988 at bugs.launchpad.net (Timo Aaltonen)
Date: Mon, 09 Aug 2021 09:07:13 -0000
Subject: [Bug 1937988] Re: The image is distorted while use iGPU rendering and
 output via AMD GPU
References: <162727716374.10692.8871227137698749656.malonedeb@chaenomeles.canonical.com>
Message-ID: <162850003365.28979.12305248835211903217.malone@wampee.canonical.com>

impish-proposed has 21.2.0-1

** Changed in: mesa (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/1937988

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  [Impact]
  Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes.

  [Fix]
  Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total.

  [Test case]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgears
  Cmd> DRI_PRIME=1 glxgears -info

  * Expected result
  The image is not distorted while running the glxgears

  * Actual result
  The image is distorted while running the glxgears

  [Where things might go wrong]
  This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms.

  
  ---

  Here is the upstream bug for tracking this issue.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions



From 1939293 at bugs.launchpad.net  Mon Aug  9 12:29:35 2021
From: 1939293 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 09 Aug 2021 12:29:35 -0000
Subject: [Bug 1939293] [NEW] unable to load externals: undefined symbol
 "__pow_finite" and similar
References: <162851026232.8975.14546106013945743585.malonedeb@wampee.canonical.com>
Message-ID: <162851217617.17339.2691554854324169856.launchpad@wampee.canonical.com>

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

[Impact]

Pd-0.50.2-3 (as shipped with focal) is unable to load the external
objects (plugins) shipped in the "puredata-extra" package (which is
built from the same source package as "puredata" itself) due to a
problem with some symbols that should be provided by libm.

The missing symbols are `__exp_finite`, `__log_finite`, `__logf_finite` and `__pow_finite`.
The affected externals are:
- bonk~
- choice
- fiddle~
- sigmund~

The problem appears to come from a change in the symbols when upgrading
from glibc-2.30 to glibc-2.31 (e.g. see
https://sourceware.org/pipermail/libc-alpha/2020-May/113773.html)

A simple rebuild of the package seems to fix the problem.

To trigger a rebuild I've added a debdiff that bumps the version number
to "0.50.2-3build1~ubuntu20.04.1" (i hope this is the correct version
scheme for such an upload).


[Test Plan]

A quick way to check whether the objects can be loaded is by running
this script (after installing the "puredata-extra" package):

~~~
find /usr/lib/puredata/extra/*/ -name "*-help.pd" -exec pd -nrt -nogui -send "pd quit" {} ";"
~~~

I've attached the output of such a (failing) test run (note the lines
starting with "error:")


[Where problems could occur]
The rebuild apparently fixes the problem, although a more correct fix would probably be to add "-lm" to the linker-flags when building the plugins.
(This is what upstream did for the Pd-0.51 release).
In order to keep the impact of my patch minimal, i have chosen to just trigger a rebuild.


ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: puredata-extra 0.50.2-3
ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
Uname: Linux 5.4.0-80-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Aug  9 11:23:35 2021
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: puredata
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal patch uec-images
-- 
unable to load externals: undefined symbol "__pow_finite" and similar
https://bugs.launchpad.net/bugs/1939293
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939293 at bugs.launchpad.net  Mon Aug  9 12:29:36 2021
From: 1939293 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Mon, 09 Aug 2021 12:29:36 -0000
Subject: [Bug 1939293] Re: unable to load externals: undefined symbol
 "__pow_finite" and similar
References: <162851026232.8975.14546106013945743585.malonedeb@wampee.canonical.com>
Message-ID: <162851217661.17339.17251023084398285222.malone@wampee.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.]

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

Title:
  unable to load externals: undefined symbol "__pow_finite" and similar

Status in puredata package in Ubuntu:
  New

Bug description:
  [Impact]

  Pd-0.50.2-3 (as shipped with focal) is unable to load the external
  objects (plugins) shipped in the "puredata-extra" package (which is
  built from the same source package as "puredata" itself) due to a
  problem with some symbols that should be provided by libm.

  The missing symbols are `__exp_finite`, `__log_finite`, `__logf_finite` and `__pow_finite`.
  The affected externals are:
  - bonk~
  - choice
  - fiddle~
  - sigmund~

  The problem appears to come from a change in the symbols when
  upgrading from glibc-2.30 to glibc-2.31 (e.g. see
  https://sourceware.org/pipermail/libc-alpha/2020-May/113773.html)

  A simple rebuild of the package seems to fix the problem.

  To trigger a rebuild I've added a debdiff that bumps the version
  number to "0.50.2-3build1~ubuntu20.04.1" (i hope this is the correct
  version scheme for such an upload).


  [Test Plan]

  A quick way to check whether the objects can be loaded is by running
  this script (after installing the "puredata-extra" package):

  ~~~
  find /usr/lib/puredata/extra/*/ -name "*-help.pd" -exec pd -nrt -nogui -send "pd quit" {} ";"
  ~~~

  I've attached the output of such a (failing) test run (note the lines
  starting with "error:")


  [Where problems could occur]

  The rebuild apparently fixes the problem, although a more correct fix would probably be to add "-lm" to the linker-flags when building the plugins.
  (This is what upstream did for the Pd-0.51 release).
  In order to keep the impact of my patch minimal, i have chosen to just trigger a rebuild.


  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: puredata-extra 0.50.2-3
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug  9 11:23:35 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: puredata
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 1939293 at bugs.launchpad.net  Mon Aug  9 12:30:02 2021
From: 1939293 at bugs.launchpad.net (IOhannes m zmoelnig)
Date: Mon, 09 Aug 2021 12:30:02 -0000
Subject: [Bug 1939293] Re: unable to load externals: undefined symbol
 "__pow_finite" and similar
References: <162851026232.8975.14546106013945743585.malonedeb@wampee.canonical.com>
Message-ID: <162851220266.25977.15848239167030416349.launchpad@soybean.canonical.com>

** Description changed:

  [Impact]
  
  Pd-0.50.2-3 (as shipped with focal) is unable to load the external
  objects (plugins) shipped in the "puredata-extra" package (which is
  built from the same source package as "puredata" itself) due to a
  problem with some symbols that should be provided by libm.
  
  The missing symbols are `__exp_finite`, `__log_finite`, `__logf_finite` and `__pow_finite`.
  The affected externals are:
  - bonk~
  - choice
  - fiddle~
  - sigmund~
  
  The problem appears to come from a change in the symbols when upgrading
  from glibc-2.30 to glibc-2.31 (e.g. see
  https://sourceware.org/pipermail/libc-alpha/2020-May/113773.html)
  
  A simple rebuild of the package seems to fix the problem.
  
  To trigger a rebuild I've added a debdiff that bumps the version number
  to "0.50.2-3build1~ubuntu20.04.1" (i hope this is the correct version
  scheme for such an upload).
  
  
  [Test Plan]
  
  A quick way to check whether the objects can be loaded is by running
  this script (after installing the "puredata-extra" package):
  
  ~~~
  find /usr/lib/puredata/extra/*/ -name "*-help.pd" -exec pd -nrt -nogui -send "pd quit" {} ";"
  ~~~
  
  I've attached the output of such a (failing) test run (note the lines
  starting with "error:")
  
  
  [Where problems could occur]
+ 
  The rebuild apparently fixes the problem, although a more correct fix would probably be to add "-lm" to the linker-flags when building the plugins.
  (This is what upstream did for the Pd-0.51 release).
  In order to keep the impact of my patch minimal, i have chosen to just trigger a rebuild.
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: puredata-extra 0.50.2-3
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug  9 11:23:35 2021
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: puredata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  unable to load externals: undefined symbol "__pow_finite" and similar

Status in puredata package in Ubuntu:
  New

Bug description:
  [Impact]

  Pd-0.50.2-3 (as shipped with focal) is unable to load the external
  objects (plugins) shipped in the "puredata-extra" package (which is
  built from the same source package as "puredata" itself) due to a
  problem with some symbols that should be provided by libm.

  The missing symbols are `__exp_finite`, `__log_finite`, `__logf_finite` and `__pow_finite`.
  The affected externals are:
  - bonk~
  - choice
  - fiddle~
  - sigmund~

  The problem appears to come from a change in the symbols when
  upgrading from glibc-2.30 to glibc-2.31 (e.g. see
  https://sourceware.org/pipermail/libc-alpha/2020-May/113773.html)

  A simple rebuild of the package seems to fix the problem.

  To trigger a rebuild I've added a debdiff that bumps the version
  number to "0.50.2-3build1~ubuntu20.04.1" (i hope this is the correct
  version scheme for such an upload).


  [Test Plan]

  A quick way to check whether the objects can be loaded is by running
  this script (after installing the "puredata-extra" package):

  ~~~
  find /usr/lib/puredata/extra/*/ -name "*-help.pd" -exec pd -nrt -nogui -send "pd quit" {} ";"
  ~~~

  I've attached the output of such a (failing) test run (note the lines
  starting with "error:")


  [Where problems could occur]

  The rebuild apparently fixes the problem, although a more correct fix would probably be to add "-lm" to the linker-flags when building the plugins.
  (This is what upstream did for the Pd-0.51 release).
  In order to keep the impact of my patch minimal, i have chosen to just trigger a rebuild.


  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: puredata-extra 0.50.2-3
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug  9 11:23:35 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: puredata
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 1939293 at bugs.launchpad.net  Mon Aug  9 12:44:09 2021
From: 1939293 at bugs.launchpad.net (IOhannes m zmoelnig)
Date: Mon, 09 Aug 2021 12:44:09 -0000
Subject: [Bug 1939293] Re: unable to load externals: undefined symbol
 "__pow_finite" and similar
References: <162851026232.8975.14546106013945743585.malonedeb@wampee.canonical.com>
Message-ID: <162851304960.22075.9603437551445402349.malone@wampee.canonical.com>

sidenote: this bug seems to *only* affect `focal`.
Hirsute comes with Pd-0.51, which explicitely links against "-lm" (and has apparently been rebuild against newer glibc).

In any case when i run the test script from above on a fresh `Impish`
installation, there are no more errors and everything looks good:

~~~sh
$ find /usr/lib/puredata/extra/*/ -name "*-help.pd" -exec pd -nrt -nogui -send "pd quit" {} ";"
bonk version 1.5
fiddle version 1.1 TEST4
sigmund~ version 0.07
pd~ version 0.54
pique 0.1 for PD version 23
sigmund~ version 0.07
pd~ version 0.54
$
~~~

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

Title:
  unable to load externals: undefined symbol "__pow_finite" and similar

Status in puredata package in Ubuntu:
  Fix Released
Status in puredata source package in Focal:
  In Progress

Bug description:
  [Impact]

  Pd-0.50.2-3 (as shipped with focal) is unable to load the external
  objects (plugins) shipped in the "puredata-extra" package (which is
  built from the same source package as "puredata" itself) due to a
  problem with some symbols that should be provided by libm.

  The missing symbols are `__exp_finite`, `__log_finite`, `__logf_finite` and `__pow_finite`.
  The affected externals are:
  - bonk~
  - choice
  - fiddle~
  - sigmund~

  The problem appears to come from a change in the symbols when
  upgrading from glibc-2.30 to glibc-2.31 (e.g. see
  https://sourceware.org/pipermail/libc-alpha/2020-May/113773.html)

  A simple rebuild of the package seems to fix the problem.

  To trigger a rebuild I've added a debdiff that bumps the version
  number to "0.50.2-3build1~ubuntu20.04.1" (i hope this is the correct
  version scheme for such an upload).


  [Test Plan]

  A quick way to check whether the objects can be loaded is by running
  this script (after installing the "puredata-extra" package):

  ~~~
  find /usr/lib/puredata/extra/*/ -name "*-help.pd" -exec pd -nrt -nogui -send "pd quit" {} ";"
  ~~~

  I've attached the output of such a (failing) test run (note the lines
  starting with "error:")


  [Where problems could occur]

  The rebuild apparently fixes the problem, although a more correct fix would probably be to add "-lm" to the linker-flags when building the plugins.
  (This is what upstream did for the Pd-0.51 release).
  In order to keep the impact of my patch minimal, i have chosen to just trigger a rebuild.


  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: puredata-extra 0.50.2-3
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug  9 11:23:35 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: puredata
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 1939293 at bugs.launchpad.net  Mon Aug  9 12:49:39 2021
From: 1939293 at bugs.launchpad.net (Robie Basak)
Date: Mon, 09 Aug 2021 12:49:39 -0000
Subject: [Bug 1939293] Re: unable to load externals: undefined symbol
 "__pow_finite" and similar
References: <162851026232.8975.14546106013945743585.malonedeb@wampee.canonical.com>
Message-ID: <162851337946.21971.336977151158732198.malone@wampee.canonical.com>

Sponsored. Thanks!

Now awaiting SRU review (from someone other than me).

** Also affects: puredata (Ubuntu Focal)
   Importance: Undecided
       Status: New

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

** Changed in: puredata (Ubuntu Focal)
       Status: New => 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/1939293

Title:
  unable to load externals: undefined symbol "__pow_finite" and similar

Status in puredata package in Ubuntu:
  Fix Released
Status in puredata source package in Focal:
  In Progress

Bug description:
  [Impact]

  Pd-0.50.2-3 (as shipped with focal) is unable to load the external
  objects (plugins) shipped in the "puredata-extra" package (which is
  built from the same source package as "puredata" itself) due to a
  problem with some symbols that should be provided by libm.

  The missing symbols are `__exp_finite`, `__log_finite`, `__logf_finite` and `__pow_finite`.
  The affected externals are:
  - bonk~
  - choice
  - fiddle~
  - sigmund~

  The problem appears to come from a change in the symbols when
  upgrading from glibc-2.30 to glibc-2.31 (e.g. see
  https://sourceware.org/pipermail/libc-alpha/2020-May/113773.html)

  A simple rebuild of the package seems to fix the problem.

  To trigger a rebuild I've added a debdiff that bumps the version
  number to "0.50.2-3build1~ubuntu20.04.1" (i hope this is the correct
  version scheme for such an upload).


  [Test Plan]

  A quick way to check whether the objects can be loaded is by running
  this script (after installing the "puredata-extra" package):

  ~~~
  find /usr/lib/puredata/extra/*/ -name "*-help.pd" -exec pd -nrt -nogui -send "pd quit" {} ";"
  ~~~

  I've attached the output of such a (failing) test run (note the lines
  starting with "error:")


  [Where problems could occur]

  The rebuild apparently fixes the problem, although a more correct fix would probably be to add "-lm" to the linker-flags when building the plugins.
  (This is what upstream did for the Pd-0.51 release).
  In order to keep the impact of my patch minimal, i have chosen to just trigger a rebuild.


  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: puredata-extra 0.50.2-3
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug  9 11:23:35 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: puredata
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 1937988 at bugs.launchpad.net  Mon Aug  9 14:06:11 2021
From: 1937988 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 09 Aug 2021 14:06:11 -0000
Subject: [Bug 1937988] Re: The image is distorted while use iGPU rendering and
 output via AMD GPU
References: <162727716374.10692.8871227137698749656.malonedeb@chaenomeles.canonical.com>
Message-ID: <162851797131.18860.8763187099818162065.malone@soybean.canonical.com>

Hello jeremyszu, or anyone else affected,

Accepted mesa into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.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, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: mesa (Ubuntu Hirsute)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes.

  [Fix]
  Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total.

  [Test case]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgears
  Cmd> DRI_PRIME=1 glxgears -info

  * Expected result
  The image is not distorted while running the glxgears

  * Actual result
  The image is distorted while running the glxgears

  [Where things might go wrong]
  This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms.

  
  ---

  Here is the upstream bug for tracking this issue.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions



From 1937988 at bugs.launchpad.net  Mon Aug  9 14:14:48 2021
From: 1937988 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 09 Aug 2021 14:14:48 -0000
Subject: [Bug 1937988] Re: The image is distorted while use iGPU rendering and
 output via AMD GPU
References: <162727716374.10692.8871227137698749656.malonedeb@chaenomeles.canonical.com>
Message-ID: <162851848811.10881.3200402254804599380.malone@wampee.canonical.com>

Hello jeremyszu, or anyone else affected,

Accepted mesa into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: mesa (Ubuntu Focal)
       Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes.

  [Fix]
  Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total.

  [Test case]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgears
  Cmd> DRI_PRIME=1 glxgears -info

  * Expected result
  The image is not distorted while running the glxgears

  * Actual result
  The image is distorted while running the glxgears

  [Where things might go wrong]
  This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms.

  
  ---

  Here is the upstream bug for tracking this issue.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions



From 1933167 at bugs.launchpad.net  Tue Aug 10 05:27:21 2021
From: 1933167 at bugs.launchpad.net (Shih-Yuan Lee)
Date: Tue, 10 Aug 2021 05:27:21 -0000
Subject: [Bug 1933167] Re: [MIR] oem-sutton.simon-carrie-meta
References: <162432116259.2630.7892035131697104379.malonedeb@gac.canonical.com>
Message-ID: <162857324264.24338.13746963380764871138.launchpad@wampee.canonical.com>

** Description changed:

  [Background]
  
  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
  
  [Impact]
  
-  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
-  2. The background and impact of the situation for this change, and it's impact.
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
  
  [Testing]
  
-  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
-  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
-  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
  
  [Regression Potential]
  
  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.
  
  [When switching kernel flavour] Check that the new kernel flavour works
  on the target platform.
  
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-carrie-meta for focal:
-     git clone -b simon.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
+     git clone -b simon.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
  
- https://ubuntu.com/certified/202105-29058
  https://ubuntu.com/certified/202105-29059

** Changed in: oem-priority
     Assignee: OEM Taipei Jenkins Role Account (oem-taipei-bot) => Bin Li (binli)

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

Title:
  [MIR] oem-sutton.simon-carrie-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-carrie-meta for focal:
      git clone -b simon.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202105-29059

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933167/+subscriptions



From 1924729 at bugs.launchpad.net  Tue Aug 10 10:52:04 2021
From: 1924729 at bugs.launchpad.net (Bin Li)
Date: Tue, 10 Aug 2021 10:52:04 -0000
Subject: [Bug 1924729] Re: [MIR] oem-sutton.newell-carlisle-meta
References: <161856669114.19086.9474159012667293872.malonedeb@wampee.canonical.com>
Message-ID: <162859272458.22068.15217721987619685385.malone@gac.canonical.com>

Attach oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.7.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carlisle-meta for focal:
      git clone -b newell.carlisle-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carlisle-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202102-28732

** Patch removed: "oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924729/+attachment/5501847/+files/oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924729/+attachment/5517064/+files/oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.7

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

Title:
  [MIR] oem-sutton.newell-carlisle-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carlisle-meta for focal:
      git clone -b newell.carlisle-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carlisle-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202102-28732

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924729/+subscriptions



From 1915819 at bugs.launchpad.net  Tue Aug 10 10:50:47 2021
From: 1915819 at bugs.launchpad.net (Graham Inggs)
Date: Tue, 10 Aug 2021 10:50:47 -0000
Subject: [Bug 1915819] Re: 'NoneType' object has no attribute 'encode' in
 requestReceived() when multipart body doesn't include content-disposition
References: <161348008246.20935.12756494153193548026.malonedeb@wampee.canonical.com>
Message-ID: <162859264759.16606.18008439399127582524.launchpad@soybean.canonical.com>

** Bug watch added: Debian Bug tracker #982923
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982923

** Also affects: twisted (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982923
   Importance: Unknown
       Status: Unknown

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

Title:
  'NoneType' object has no attribute 'encode' in requestReceived() when
  multipart body doesn't include content-disposition

Status in twisted package in Ubuntu:
  Fix Released
Status in twisted source package in Focal:
  Fix Released
Status in twisted source package in Groovy:
  Fix Released
Status in twisted source package in Hirsute:
  Fix Released
Status in twisted package in Debian:
  Unknown

Bug description:
  [impact]

  python-twisted errors out with "'NoneType' object has no attribute
  'encode' in requestReceived()" when it tries to parse a multipart mime
  message and python3.7+ is used. This happens because before commit
  cc3fa20 in cpython, cgi.parse_multipart ignored parts without a name
  defined in "content-disposition" (or parts without headers for that
  matter) but after 3.7+ the return of the function can now contain
  NoneType keys, which fail to encode.

  [scope]

  Even though this bug affects all python3-twisted releases, I'll
  backport the fix just to Focal, Groovy and Hirsute. Bionic and Xenial
  do not have Python 3.7 as the default interpreter (required to trigger
  the issue), and the delta in python3-twisted might be to big to
  backport as the current packages do not contemplate _PY37PLUS at all.

  Fixed upstream with commit 310496249, available since 21.2.0rc1

  [test case]

  1. Save the following code as webserver.py

  from twisted.application.internet import TCPServer
  from twisted.application.service import Application
  from twisted.web.resource import Resource
  from twisted.web.server import Site

  class Foo(Resource):
      def render_POST(self, request):
          newdata = request.content.getvalue()
          print(newdata)
          return ''

  root = Resource()
  root.putChild("foo", Foo())
  application = Application("cgi.parse_multipart test")
  TCPServer(8080, Site(root)).setServiceParent(application)

  2. Save the following code as client.py (python3-httplib2 is required)

  #!/usr/bin/env python
  import httplib2

  def http_request(url, method, body=None, headers=None, insecure=False):
      """Issue an http request."""
      http = httplib2.Http(disable_ssl_certificate_validation=insecure)
      if isinstance(url, bytes):
          url = url.decode("ascii")
      return http.request(url, method, body=body, headers=headers)

  url = "http://localhost:8080"
  method = "POST"
  headers = {'Content-Type': 'multipart/form-data; boundary="8825899812428059282"'}
  emptyh = '--8825899812428059282\n\n--8825899812428059282--'

  print("== BODY: " + emptyh + "\n")
  response, content = http_request(url, method, emptyh, headers)

  3. Run the server with "twistd3 -y webserver.py"
  4. Run the client
  5. twistd will fail to encode the key and will drop this traceback in the log file (twistd.log)

  2021-02-16T13:41:39+0100 [_GenericHTTPChannelProtocol,7,127.0.0.1] Unhandled Error
          Traceback (most recent call last):
            File "/usr/lib/python3/dist-packages/twisted/python/log.py", line 103, in callWithLogger
              return callWithContext({"system": lp}, func, *args, **kw)
            File "/usr/lib/python3/dist-packages/twisted/python/log.py", line 86, in callWithContext
              return context.call({ILogContext: newCtx}, func, *args, **kw)
            File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 122, in callWithContext
              return self.currentContext().callWithContext(ctx, func, *args, **kw)
            File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 85, in callWithContext
              return func(*args,**kw)
          --- <exception caught here> ---
            File "/usr/lib/python3/dist-packages/twisted/internet/posixbase.py", line 614, in _doReadOrWrite
              why = selectable.doRead()
            File "/usr/lib/python3/dist-packages/twisted/internet/tcp.py", line 243, in doRead
              return self._dataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/internet/tcp.py", line 249, in _dataReceived
              rval = self.protocol.dataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2952, in dataReceived
              return self._channel.dataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2245, in dataReceived
              return basic.LineReceiver.dataReceived(self, data)
            File "/usr/lib/python3/dist-packages/twisted/protocols/basic.py", line 579, in dataReceived
              why = self.rawDataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2252, in rawDataReceived
              self._transferDecoder.dataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 1699, in dataReceived
              finishCallback(data[contentLength:])
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2115, in _finishRequestBody
              self.allContentReceived()
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2224, in allContentReceived
              req.requestReceived(command, path, version)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 898, in requestReceived
              self.args.update({
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 899, in <dictcomp>
              x.encode('iso-8859-1'): \
          builtins.AttributeError: 'NoneType' object has no attribute 'encode'

  [regression potential]

  This affects the returned dictionaries with non-str keys, which were
  discarded in python3.6 or earlier before they reached twisted, so
  patching this will make its behavior consistent.

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



From 1924729 at bugs.launchpad.net  Tue Aug 10 10:57:21 2021
From: 1924729 at bugs.launchpad.net (Bin Li)
Date: Tue, 10 Aug 2021 10:57:21 -0000
Subject: [Bug 1924729] Re: [MIR] oem-sutton.newell-carlisle-meta
References: <161856669114.19086.9474159012667293872.malonedeb@wampee.canonical.com>
Message-ID: <162859304115.6949.9477854844841658178.malone@wampee.canonical.com>

Attach oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.7.

** Patch removed: "oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924729/+attachment/5517064/+files/oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carlisle-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924729/+attachment/5517065/+files/oem-sutton.newell-carlisle-meta_20.04~ubuntu1.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/1924729

Title:
  [MIR] oem-sutton.newell-carlisle-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carlisle-meta for focal:
      git clone -b newell.carlisle-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carlisle-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202102-28732

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924729/+subscriptions



From 1924730 at bugs.launchpad.net  Tue Aug 10 11:07:02 2021
From: 1924730 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 10 Aug 2021 11:07:02 -0000
Subject: [Bug 1924730] [NEW] [MIR] oem-sutton.newell-carnell-meta
References: <161856670162.16097.363547585646369873.malonedeb@chaenomeles.canonical.com>
Message-ID: <162859362250.7429.13697407309333963283.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Bin Li (binli):

[Background]

Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

[Impact]

 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
 2. The background and impact of the situation for this change, and it's impact.

[Testing]

 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

[Regression Potential]

Most potential regressions will live in the package set that will be
installed via dependency of this package, which live in OEM archive
(outside of Ubuntu) and control by OEM team. OEM team and other
corresponding team need take responsibility of those dependency
installed.

[When switching kernel flavour] Check that the new kernel flavour works
on the target platform.

[Availability]
This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
The source code of the oem-sutton.newell-carnell-meta for focal:
    git clone -b newell.carnell-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

[Rationale]
We want to improve the hardware support for some Lenovo platforms.

[Security]
No CVE/known security issue.

[Quality assurance]
I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
oem-sutton.newell-carnell-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

[Dependencies]
It only depends on ubuntu-oem-keyring.

[Standards compliance]
This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

[Maintenance]
Canonical OEM Enablement Team will take care of the maintenance.

[Background information]
Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
verify this MIR against the reference package in the archive.

** Affects: oem-priority
     Importance: Critical
     Assignee: Bin Li (binli)
         Status: Fix Committed

** Affects: ubuntu
     Importance: Undecided
         Status: Confirmed


** Tags: oem-meta-packages oem-priority oem-scripts-0.95
-- 
[MIR] oem-sutton.newell-carnell-meta
https://bugs.launchpad.net/bugs/1924730
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1924730 at bugs.launchpad.net  Tue Aug 10 11:08:22 2021
From: 1924730 at bugs.launchpad.net (Bin Li)
Date: Tue, 10 Aug 2021 11:08:22 -0000
Subject: [Bug 1924730] Re: [MIR] oem-sutton.newell-carnell-meta
References: <161856670162.16097.363547585646369873.malonedeb@chaenomeles.canonical.com>
Message-ID: <162859370277.21997.15580768816562850818.malone@soybean.canonical.com>

Attach oem-sutton.newell-carnell-meta_20.04~ubuntu1.debdiff by oem-
scripts 1.7.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carnell-meta for focal:
      git clone -b newell.carnell-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carnell-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

** Changed in: oem-priority
       Status: In Progress => Fix Committed

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

** Patch removed: "oem-sutton.newell-carnell-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924730/+attachment/5501848/+files/oem-sutton.newell-carnell-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carnell-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924730/+attachment/5517067/+files/oem-sutton.newell-carnell-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.7

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

Title:
  [MIR] oem-sutton.newell-carnell-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carnell-meta for focal:
      git clone -b newell.carnell-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carnell-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924730/+subscriptions



From 1924732 at bugs.launchpad.net  Tue Aug 10 11:15:23 2021
From: 1924732 at bugs.launchpad.net (Bin Li)
Date: Tue, 10 Aug 2021 11:15:23 -0000
Subject: [Bug 1924732] Re: [MIR] oem-sutton.newell-carol-meta
References: <161856671257.18939.10183742418606767560.malonedeb@wampee.canonical.com>
Message-ID: <162859412317.25768.5764093760589912235.malone@soybean.canonical.com>

Attach oem-sutton.newell-carol-meta_20.04~ubuntu1.debdiff by oem-scripts
1.7.

** Description changed:

+ [Background]
+ 
+ Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
+ https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.
+ 
+ [Impact]
+ 
+  1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
+  2. The background and impact of the situation for this change, and it's impact.
+ 
+ [Testing]
+ 
+  1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
+  2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
+  3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.
+ 
+ [Regression Potential]
+ 
+ Most potential regressions will live in the package set that will be
+ installed via dependency of this package, which live in OEM archive
+ (outside of Ubuntu) and control by OEM team. OEM team and other
+ corresponding team need take responsibility of those dependency
+ installed.
+ 
+ [When switching kernel flavour] Check that the new kernel flavour works
+ on the target platform.
+ 
  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carol-meta for focal:
      git clone -b newell.carol-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta
  
  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.
  
  [Security]
  No CVE/known security issue.
  
  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carol-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.
  
  [Dependencies]
  It only depends on ubuntu-oem-keyring.
  
  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.
  
  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.
  
  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.
  
  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.
+ 
+ https://ubuntu.com/certified/202102-28714

** Patch removed: "oem-sutton.newell-carol-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924732/+attachment/5501849/+files/oem-sutton.newell-carol-meta_20.04~ubuntu1.debdiff

** Patch added: "oem-sutton.newell-carol-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1924732/+attachment/5517068/+files/oem-sutton.newell-carol-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.95
** Tags added: oem-scripts-1.7

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

Title:
  [MIR] oem-sutton.newell-carol-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.newell-carol-meta for focal:
      git clone -b newell.carol-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.newell-carol-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202102-28714

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924732/+subscriptions



From 1932010 at bugs.launchpad.net  Tue Aug 10 11:59:29 2021
From: 1932010 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 10 Aug 2021 11:59:29 -0000
Subject: [Bug 1932010] [NEW] [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162859676977.3860.10339241188103397979.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Use SIMD instructions to accelerate the zlib CRC32 implementation.
Business value: Performance improvement in database area

The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
https://github.com/zlib-ng/zlib-ng/pull/912

The patch for zlib will be based on that.

** Affects: ubuntu-z-systems
     Importance: High
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: Triaged

** Affects: zlib (Ubuntu)
     Importance: Undecided
     Assignee: Simon Chopin (schopin)
         Status: In Progress


** Tags: architecture-s39064 bugnameltc-192731 fr-1445 severity-high targetmilestone-inin2110
-- 
[21.10 FEAT] zlib CRC32 optimization for s390x
https://bugs.launchpad.net/bugs/1932010
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1932010 at bugs.launchpad.net  Tue Aug 10 12:00:49 2021
From: 1932010 at bugs.launchpad.net (Simon Chopin)
Date: Tue, 10 Aug 2021 12:00:49 -0000
Subject: [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162859685003.2019.4714903252861751004.malone@soybean.canonical.com>

You'll find a built version of the package in my PPA :
https://launchpad.net/~schopin/+archive/ubuntu/test-
ppa/+sourcepub/12641334/+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/1932010

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  Triaged
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1932010 at bugs.launchpad.net  Tue Aug 10 13:11:20 2021
From: 1932010 at bugs.launchpad.net (Frank Heimes)
Date: Tue, 10 Aug 2021 13:11:20 -0000
Subject: [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162860108113.6175.1846422231381543585.launchpad@chaenomeles.canonical.com>

** Changed in: ubuntu-z-systems
       Status: Triaged => 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/1932010

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1939411 at bugs.launchpad.net  Tue Aug 10 13:40:37 2021
From: 1939411 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 10 Aug 2021 13:40:37 -0000
Subject: [Bug 1939411] [NEW] Sync lksctp-tools 1.0.19+dfsg-1 (main) from
 Debian unstable (main)
References: <162860283240.28271.16707864960405310619.malonedeb@soybean.canonical.com>
Message-ID: <162860283781.459.5720189167540914664.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Please sync lksctp-tools 1.0.19+dfsg-1 (main) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Use symver attribute for symbol versioning, fixing the lto build,
    patch taken from Fedora.

This patch has been merged upstream for the 1.0.19 release, and is thus
unnecessary.

Changelog entries since current impish version 1.0.18+dfsg-1ubuntu1:

lksctp-tools (1.0.19+dfsg-1) unstable; urgency=medium

  [ Ondřej Nový ]
  * d/copyright: Use https protocol in Format field
  * d/control: Removing redundant Priority field in binary package
  * d/changelog: Remove trailing whitespaces

  [ Michael Biebl ]
  * New upstream version 1.0.19+dfsg
  * Drop patches, all merged upstream
  * Update symbols file for libsctp1
  * Switch to debhelper-compat and bump compat level to 13
  * Bump Standards-Version to 4.5.1

 -- Michael Biebl <biebl at debian.org>  Sat, 15 May 2021 15:55:00 +0200

** Affects: lksctp-tools (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync lksctp-tools 1.0.19+dfsg-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1939411
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939411 at bugs.launchpad.net  Tue Aug 10 14:06:19 2021
From: 1939411 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 10 Aug 2021 14:06:19 -0000
Subject: [Bug 1939411] Re: Sync lksctp-tools 1.0.19+dfsg-1 (main) from Debian
 unstable (main)
References: <162860283240.28271.16707864960405310619.malonedeb@soybean.canonical.com>
Message-ID: <162860437951.16807.3658744608853191538.malone@wampee.canonical.com>

This bug was fixed in the package lksctp-tools - 1.0.19+dfsg-1
Sponsored for Simon Chopin (schopin)

---------------
lksctp-tools (1.0.19+dfsg-1) unstable; urgency=medium

  [ Ondřej Nový ]
  * d/copyright: Use https protocol in Format field
  * d/control: Removing redundant Priority field in binary package
  * d/changelog: Remove trailing whitespaces

  [ Michael Biebl ]
  * New upstream version 1.0.19+dfsg
  * Drop patches, all merged upstream
  * Update symbols file for libsctp1
  * Switch to debhelper-compat and bump compat level to 13
  * Bump Standards-Version to 4.5.1

 -- Michael Biebl <biebl at debian.org>  Sat, 15 May 2021 15:55:00 +0200

** Changed in: lksctp-tools (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/1939411

Title:
  Sync lksctp-tools 1.0.19+dfsg-1 (main) from Debian unstable (main)

Status in lksctp-tools package in Ubuntu:
  Fix Released

Bug description:
  Please sync lksctp-tools 1.0.19+dfsg-1 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Use symver attribute for symbol versioning, fixing the lto build,
      patch taken from Fedora.

  This patch has been merged upstream for the 1.0.19 release, and is thus
  unnecessary.

  Changelog entries since current impish version 1.0.18+dfsg-1ubuntu1:

  lksctp-tools (1.0.19+dfsg-1) unstable; urgency=medium

    [ Ondřej Nový ]
    * d/copyright: Use https protocol in Format field
    * d/control: Removing redundant Priority field in binary package
    * d/changelog: Remove trailing whitespaces

    [ Michael Biebl ]
    * New upstream version 1.0.19+dfsg
    * Drop patches, all merged upstream
    * Update symbols file for libsctp1
    * Switch to debhelper-compat and bump compat level to 13
    * Bump Standards-Version to 4.5.1

   -- Michael Biebl <biebl at debian.org>  Sat, 15 May 2021 15:55:00 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lksctp-tools/+bug/1939411/+subscriptions



From 1813003 at bugs.launchpad.net  Tue Aug 10 16:51:33 2021
From: 1813003 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 10 Aug 2021 16:51:33 -0000
Subject: [Bug 1813003] [NEW] Invalid free while running docker build
References: <154824444386.1905.3790103681743097182.malonedeb@wampee.canonical.com>
Message-ID: <162861429408.26068.1770951229846182429.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Athos Ribeiro (athos-ribeiro):

[Impact]

The bug results in an error being printed on the user screen when
running docker builds.

While the error will not cause the build to fail, the bug does prevent
users to login on servers with no X11 installed.

[Test Plan]

- Install docker.io and golang-docker-credential-helpers
- Run a simple docker build
- Verify that the error occurs
- Install the proposed fix
- Run a simple docker build
- Verify the error is no longer present

- alternatively, try to run "docker login" and provide a correct
username and password. By the end of the login process, an error will
occur and the login will not succeed.

```
apt-get update
apt-get install -y docker.io golang-docker-credential-helpers
mkdir /tmp/dummy-docker-build
cd /tmp/dummy-docker-build
cat <<EOF > Dockerfile
FROM ubuntu:focal
LABEL hello=label
EOF
docker build -t golang-docker-credential-helpers:test
# Verify the error is triggered.
# update the package and try the build again with
# docker build -t golang-docker-credential-helpers:test
# from this directory
```

[Where problems could occur]

While the patch being applied is a simple, straightforward change,
performing a rebuild of this package in bionic may pull newer versions
of build dependencies which may cause unpredictable behavior in a stable
package.

[Other Info]
 
This fix is already present upstream, in Debian, and in all following Ubuntu series.

[Original message]

Description of the problem:
Running docker build generates a warning that an invalid free was performed.

Steps to reproduce:
sudo apt-get install docker-compose
sudo docker build -f Dockerfile.build https://github.com/docker-library/hello-world.git

Expected results:
Docker container to be built without errors

Actual results:
An error is produced while the container is being built:

free(): invalid pointer
SIGABRT: abort
PC=0x7f7027c42e97 m=0 sigcode=18446744073709551610
signal arrived during cgo execution

goroutine 1 [syscall, locked to thread]:
runtime.cgocall(0x4afd50, 0xc420073cc0, 0xc420073ce8)
 /usr/lib/go-1.8/src/runtime/cgocall.go:131 +0xe2 fp=0xc420073c90 sp=0xc420073c50
github.com/docker/docker-credential-helpers/secretservice._Cfunc_free(0x12c4da0)
 github.com/docker/docker-credential-helpers/secretservice/_obj/_cgo_gotypes.go:111 +0x41 fp=0xc420073cc0 sp=0xc420073c90
github.com/docker/docker-credential-helpers/secretservice.Secretservice.List.func5(0x12c4da0)
 /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:96 +0x60 fp=0xc420073cf8 sp=0xc420073cc0
github.com/docker/docker-credential-helpers/secretservice.Secretservice.List(0x0, 0x756060, 0xc420014370)
 /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:97 +0x217 fp=0xc420073da0 sp=0xc420073cf8
github.com/docker/docker-credential-helpers/secretservice.(*Secretservice).List(0x77e548, 0xc420073e88, 0x410022, 0xc4200142d0)
 <autogenerated>:4 +0x46 fp=0xc420073de0 sp=0xc420073da0
github.com/docker/docker-credential-helpers/credentials.List(0x756ba0, 0x77e548, 0x7560e0, 0xc42000e018, 0x0, 0x10)
 /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:145 +0x3e fp=0xc420073e68 sp=0xc420073de0
github.com/docker/docker-credential-helpers/credentials.HandleCommand(0x756ba0, 0x77e548, 0x7fff8fa9e879, 0x4, 0x7560a0, 0xc42000e010, 0x7560e0, 0xc42000e018, 0x40e398, 0x4d35c0)
 /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:60 +0x16d fp=0xc420073ed8 sp=0xc420073e68
github.com/docker/docker-credential-helpers/credentials.Serve(0x756ba0, 0x77e548)
 /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:41 +0x1cb fp=0xc420073f58 sp=0xc420073ed8
main.main()
 /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/secretservice/cmd/main_linux.go:9 +0x4f fp=0xc420073f88 sp=0xc420073f58
runtime.main()
 /usr/lib/go-1.8/src/runtime/proc.go:185 +0x20a fp=0xc420073fe0 sp=0xc420073f88
runtime.goexit()
 /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420073fe8 sp=0xc420073fe0

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
 /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1

rax    0x0
rbx    0x7fff8fa9e310
rcx    0x7f7027c42e97
rdx    0x0
rdi    0x2
rsi    0x7fff8fa9e0a0
rbp    0x7fff8fa9e410
rsp    0x7fff8fa9e0a0
r8     0x0
r9     0x7fff8fa9e0a0
r10    0x8
r11    0x246
r12    0x7fff8fa9e310
r13    0x1000
r14    0x0
r15    0x30
rip    0x7f7027c42e97
rflags 0x246
cs     0x33
fs     0x0
gs     0x0

How reproducible is the problem?
Happens every time.

Version information:
Ubuntu 18.04.1 LTS
docker.io 18.06.1-0ubuntu1~18.04.1
docker-compose 1.17.1-2
golang-docker-credential-helpers 0.5.0-2

Additional information:
It looks like there's a patch which will fix this issue in the docker-credential-helpers project (see the https://github.com/docker/docker-credential-helpers/commit/73e5f5dbfea31ee3b81111ebbf189785fa69731c commit) but it only landed on master on the 19th July 2018 and the last "release" was v0.6.1. The patch looks fairly self contained though so looks like a ready candidate for backporting (and given how widespread this issue is this is the course of action I would recommend).

There are also a lot of issues elsewhere on the web describing this issue:
https://github.com/moby/moby/issues/34048 ("Error in `docker-credential-secretservice': free(): invalid pointer: 0x00000000011b3150" which reports that you need to install gnome-keyring)
https://github.com/docker/for-linux/issues/185 ("Docker-engine on Debian should have `accountsservice` and `gnome-keyring` as dependencies")
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884596 ("Please make golang-docker-credential-helpers depend on gnome-keyring")
https://github.com/docker/docker-credential-helpers/issues/103 ("strange errors on docker build " where someone says they have both gnome-keyring and accountsservice installed but they still see a problem. https://github.com/docker/docker-credential-helpers/issues/104 and https://github.com/docker/docker-credential-helpers/issues/23 appear to be duplicates).
https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1792824 ("Please remove golang-docker-credential-helpers dependency from the Ubuntu docker-compose package" got the reply "Please don't ask us (Ubuntu) - go and ask Debian")
https://github.com/moby/moby/issues/37916 ("Error on build: double free or corruption (out) SIGABRT: abort PC=0x7f7464f01e97 m=0 sigcode=18446744073709551610 signal arrived during cgo execution", seems to be the same as the problem described in https://github.com/docker/docker-credential-helpers/issues/103 ).

** Affects: golang-github-docker-docker-credential-helpers (Ubuntu)
     Importance: Undecided
         Status: Confirmed

** Affects: golang-github-docker-docker-credential-helpers (Ubuntu Bionic)
     Importance: Undecided
     Assignee: Athos Ribeiro (athos-ribeiro)
         Status: Confirmed


** Tags: bionic
-- 
Invalid free while running docker build
https://bugs.launchpad.net/bugs/1813003
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1813003 at bugs.launchpad.net  Tue Aug 10 18:56:02 2021
From: 1813003 at bugs.launchpad.net (Sergio Durigan Junior)
Date: Tue, 10 Aug 2021 18:56:02 -0000
Subject: [Bug 1813003] Re: Invalid free while running docker build
References: <154824444386.1905.3790103681743097182.malonedeb@wampee.canonical.com>
Message-ID: <162862176301.25377.2752057146926179069.malone@chaenomeles.canonical.com>

Thanks for the patch and for working on this bug, Athos.

A few comments:

- Since this is an SRU, the version will be a bit different than in a
normal upload to a development version.  In this particular case, the
version should be:

  0.5.0-2ubuntu0.1

- The "Origin:" DEP-3 header should contain the direct link to the
commit.  It should also specify if this patch is a backport or if it was
applied cleanly from upstream.  For example:

  Origin: upstream, https://link.to.commit

or

  Origin: backport, https://link.to.commit

Other than that, the patch LGTM.

The SRU template also LGTM, but there's a small nit in the Test Case
section: the "docker build" command expects the directory where the
build will happen as an argument, so I think the command should be:

   docker build -t golang-docker-credential-helpers:test .

Other than that, I followed the reproduction steps and verified that (1)
the error is indeed hapening, and (2) it is fixed by this patch.

Let me know when you update the patch and I can upload it.  Thanks.

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

Title:
  Invalid free while running docker build

Status in golang-github-docker-docker-credential-helpers package in Ubuntu:
  Confirmed
Status in golang-github-docker-docker-credential-helpers source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  The bug results in an error being printed on the user screen when
  running docker builds.

  While the error will not cause the build to fail, the bug does prevent
  users to login on servers with no X11 installed.

  [Test Plan]

  - Install docker.io and golang-docker-credential-helpers
  - Run a simple docker build
  - Verify that the error occurs
  - Install the proposed fix
  - Run a simple docker build
  - Verify the error is no longer present

  - alternatively, try to run "docker login" and provide a correct
  username and password. By the end of the login process, an error will
  occur and the login will not succeed.

  ```
  apt-get update
  apt-get install -y docker.io golang-docker-credential-helpers
  mkdir /tmp/dummy-docker-build
  cd /tmp/dummy-docker-build
  cat <<EOF > Dockerfile
  FROM ubuntu:focal
  LABEL hello=label
  EOF
  docker build -t golang-docker-credential-helpers:test
  # Verify the error is triggered.
  # update the package and try the build again with
  # docker build -t golang-docker-credential-helpers:test
  # from this directory
  ```

  [Where problems could occur]

  While the patch being applied is a simple, straightforward change,
  performing a rebuild of this package in bionic may pull newer versions
  of build dependencies which may cause unpredictable behavior in a
  stable package.

  [Other Info]
   
  This fix is already present upstream, in Debian, and in all following Ubuntu series.

  [Original message]

  Description of the problem:
  Running docker build generates a warning that an invalid free was performed.

  Steps to reproduce:
  sudo apt-get install docker-compose
  sudo docker build -f Dockerfile.build https://github.com/docker-library/hello-world.git

  Expected results:
  Docker container to be built without errors

  Actual results:
  An error is produced while the container is being built:

  free(): invalid pointer
  SIGABRT: abort
  PC=0x7f7027c42e97 m=0 sigcode=18446744073709551610
  signal arrived during cgo execution

  goroutine 1 [syscall, locked to thread]:
  runtime.cgocall(0x4afd50, 0xc420073cc0, 0xc420073ce8)
   /usr/lib/go-1.8/src/runtime/cgocall.go:131 +0xe2 fp=0xc420073c90 sp=0xc420073c50
  github.com/docker/docker-credential-helpers/secretservice._Cfunc_free(0x12c4da0)
   github.com/docker/docker-credential-helpers/secretservice/_obj/_cgo_gotypes.go:111 +0x41 fp=0xc420073cc0 sp=0xc420073c90
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List.func5(0x12c4da0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:96 +0x60 fp=0xc420073cf8 sp=0xc420073cc0
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List(0x0, 0x756060, 0xc420014370)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:97 +0x217 fp=0xc420073da0 sp=0xc420073cf8
  github.com/docker/docker-credential-helpers/secretservice.(*Secretservice).List(0x77e548, 0xc420073e88, 0x410022, 0xc4200142d0)
   <autogenerated>:4 +0x46 fp=0xc420073de0 sp=0xc420073da0
  github.com/docker/docker-credential-helpers/credentials.List(0x756ba0, 0x77e548, 0x7560e0, 0xc42000e018, 0x0, 0x10)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:145 +0x3e fp=0xc420073e68 sp=0xc420073de0
  github.com/docker/docker-credential-helpers/credentials.HandleCommand(0x756ba0, 0x77e548, 0x7fff8fa9e879, 0x4, 0x7560a0, 0xc42000e010, 0x7560e0, 0xc42000e018, 0x40e398, 0x4d35c0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:60 +0x16d fp=0xc420073ed8 sp=0xc420073e68
  github.com/docker/docker-credential-helpers/credentials.Serve(0x756ba0, 0x77e548)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:41 +0x1cb fp=0xc420073f58 sp=0xc420073ed8
  main.main()
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/secretservice/cmd/main_linux.go:9 +0x4f fp=0xc420073f88 sp=0xc420073f58
  runtime.main()
   /usr/lib/go-1.8/src/runtime/proc.go:185 +0x20a fp=0xc420073fe0 sp=0xc420073f88
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420073fe8 sp=0xc420073fe0

  goroutine 17 [syscall, locked to thread]:
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1

  rax    0x0
  rbx    0x7fff8fa9e310
  rcx    0x7f7027c42e97
  rdx    0x0
  rdi    0x2
  rsi    0x7fff8fa9e0a0
  rbp    0x7fff8fa9e410
  rsp    0x7fff8fa9e0a0
  r8     0x0
  r9     0x7fff8fa9e0a0
  r10    0x8
  r11    0x246
  r12    0x7fff8fa9e310
  r13    0x1000
  r14    0x0
  r15    0x30
  rip    0x7f7027c42e97
  rflags 0x246
  cs     0x33
  fs     0x0
  gs     0x0

  How reproducible is the problem?
  Happens every time.

  Version information:
  Ubuntu 18.04.1 LTS
  docker.io 18.06.1-0ubuntu1~18.04.1
  docker-compose 1.17.1-2
  golang-docker-credential-helpers 0.5.0-2

  Additional information:
  It looks like there's a patch which will fix this issue in the docker-credential-helpers project (see the https://github.com/docker/docker-credential-helpers/commit/73e5f5dbfea31ee3b81111ebbf189785fa69731c commit) but it only landed on master on the 19th July 2018 and the last "release" was v0.6.1. The patch looks fairly self contained though so looks like a ready candidate for backporting (and given how widespread this issue is this is the course of action I would recommend).

  There are also a lot of issues elsewhere on the web describing this issue:
  https://github.com/moby/moby/issues/34048 ("Error in `docker-credential-secretservice': free(): invalid pointer: 0x00000000011b3150" which reports that you need to install gnome-keyring)
  https://github.com/docker/for-linux/issues/185 ("Docker-engine on Debian should have `accountsservice` and `gnome-keyring` as dependencies")
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884596 ("Please make golang-docker-credential-helpers depend on gnome-keyring")
  https://github.com/docker/docker-credential-helpers/issues/103 ("strange errors on docker build " where someone says they have both gnome-keyring and accountsservice installed but they still see a problem. https://github.com/docker/docker-credential-helpers/issues/104 and https://github.com/docker/docker-credential-helpers/issues/23 appear to be duplicates).
  https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1792824 ("Please remove golang-docker-credential-helpers dependency from the Ubuntu docker-compose package" got the reply "Please don't ask us (Ubuntu) - go and ask Debian")
  https://github.com/moby/moby/issues/37916 ("Error on build: double free or corruption (out) SIGABRT: abort PC=0x7f7464f01e97 m=0 sigcode=18446744073709551610 signal arrived during cgo execution", seems to be the same as the problem described in https://github.com/docker/docker-credential-helpers/issues/103 ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-docker-credential-helpers/+bug/1813003/+subscriptions



From 1813003 at bugs.launchpad.net  Tue Aug 10 20:40:13 2021
From: 1813003 at bugs.launchpad.net (Athos Ribeiro)
Date: Tue, 10 Aug 2021 20:40:13 -0000
Subject: [Bug 1813003] Re: Invalid free while running docker build
References: <154824444386.1905.3790103681743097182.malonedeb@wampee.canonical.com>
Message-ID: <162862801319.4176.6761402396127659386.malone@gac.canonical.com>

Thanks for the review, Sergio.

I addressed your comments and pushed the proposed fix to the following
PPA:

https://launchpad.net/~athos-ribeiro/+archive/ubuntu/lp-1813003-docker-
credential-helpers/+packages


** Patch added: "1-0.5.0-2ubuntu0.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-docker-credential-helpers/+bug/1813003/+attachment/5517153/+files/1-0.5.0-2ubuntu0.1.debdiff

** Description changed:

  [Impact]
  
  The bug results in an error being printed on the user screen when
  running docker builds.
  
  While the error will not cause the build to fail, the bug does prevent
  users to login on servers with no X11 installed.
  
  [Test Plan]
  
  - Install docker.io and golang-docker-credential-helpers
  - Run a simple docker build
  - Verify that the error occurs
  - Install the proposed fix
  - Run a simple docker build
  - Verify the error is no longer present
  
  - alternatively, try to run "docker login" and provide a correct
  username and password. By the end of the login process, an error will
  occur and the login will not succeed.
  
  ```
  apt-get update
  apt-get install -y docker.io golang-docker-credential-helpers
  mkdir /tmp/dummy-docker-build
  cd /tmp/dummy-docker-build
  cat <<EOF > Dockerfile
  FROM ubuntu:focal
  LABEL hello=label
  EOF
- docker build -t golang-docker-credential-helpers:test
+ docker build -t golang-docker-credential-helpers:test .
  # Verify the error is triggered.
  # update the package and try the build again with
  # docker build -t golang-docker-credential-helpers:test
  # from this directory
  ```
  
  [Where problems could occur]
  
  While the patch being applied is a simple, straightforward change,
  performing a rebuild of this package in bionic may pull newer versions
  of build dependencies which may cause unpredictable behavior in a stable
  package.
  
  [Other Info]
-  
- This fix is already present upstream, in Debian, and in all following Ubuntu series.
+ 
+ This fix is already present upstream, in Debian, and in all following
+ Ubuntu series.
  
  [Original message]
  
  Description of the problem:
  Running docker build generates a warning that an invalid free was performed.
  
  Steps to reproduce:
  sudo apt-get install docker-compose
  sudo docker build -f Dockerfile.build https://github.com/docker-library/hello-world.git
  
  Expected results:
  Docker container to be built without errors
  
  Actual results:
  An error is produced while the container is being built:
  
  free(): invalid pointer
  SIGABRT: abort
  PC=0x7f7027c42e97 m=0 sigcode=18446744073709551610
  signal arrived during cgo execution
  
  goroutine 1 [syscall, locked to thread]:
  runtime.cgocall(0x4afd50, 0xc420073cc0, 0xc420073ce8)
   /usr/lib/go-1.8/src/runtime/cgocall.go:131 +0xe2 fp=0xc420073c90 sp=0xc420073c50
  github.com/docker/docker-credential-helpers/secretservice._Cfunc_free(0x12c4da0)
   github.com/docker/docker-credential-helpers/secretservice/_obj/_cgo_gotypes.go:111 +0x41 fp=0xc420073cc0 sp=0xc420073c90
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List.func5(0x12c4da0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:96 +0x60 fp=0xc420073cf8 sp=0xc420073cc0
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List(0x0, 0x756060, 0xc420014370)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:97 +0x217 fp=0xc420073da0 sp=0xc420073cf8
  github.com/docker/docker-credential-helpers/secretservice.(*Secretservice).List(0x77e548, 0xc420073e88, 0x410022, 0xc4200142d0)
   <autogenerated>:4 +0x46 fp=0xc420073de0 sp=0xc420073da0
  github.com/docker/docker-credential-helpers/credentials.List(0x756ba0, 0x77e548, 0x7560e0, 0xc42000e018, 0x0, 0x10)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:145 +0x3e fp=0xc420073e68 sp=0xc420073de0
  github.com/docker/docker-credential-helpers/credentials.HandleCommand(0x756ba0, 0x77e548, 0x7fff8fa9e879, 0x4, 0x7560a0, 0xc42000e010, 0x7560e0, 0xc42000e018, 0x40e398, 0x4d35c0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:60 +0x16d fp=0xc420073ed8 sp=0xc420073e68
  github.com/docker/docker-credential-helpers/credentials.Serve(0x756ba0, 0x77e548)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:41 +0x1cb fp=0xc420073f58 sp=0xc420073ed8
  main.main()
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/secretservice/cmd/main_linux.go:9 +0x4f fp=0xc420073f88 sp=0xc420073f58
  runtime.main()
   /usr/lib/go-1.8/src/runtime/proc.go:185 +0x20a fp=0xc420073fe0 sp=0xc420073f88
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420073fe8 sp=0xc420073fe0
  
  goroutine 17 [syscall, locked to thread]:
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1
  
  rax    0x0
  rbx    0x7fff8fa9e310
  rcx    0x7f7027c42e97
  rdx    0x0
  rdi    0x2
  rsi    0x7fff8fa9e0a0
  rbp    0x7fff8fa9e410
  rsp    0x7fff8fa9e0a0
  r8     0x0
  r9     0x7fff8fa9e0a0
  r10    0x8
  r11    0x246
  r12    0x7fff8fa9e310
  r13    0x1000
  r14    0x0
  r15    0x30
  rip    0x7f7027c42e97
  rflags 0x246
  cs     0x33
  fs     0x0
  gs     0x0
  
  How reproducible is the problem?
  Happens every time.
  
  Version information:
  Ubuntu 18.04.1 LTS
  docker.io 18.06.1-0ubuntu1~18.04.1
  docker-compose 1.17.1-2
  golang-docker-credential-helpers 0.5.0-2
  
  Additional information:
  It looks like there's a patch which will fix this issue in the docker-credential-helpers project (see the https://github.com/docker/docker-credential-helpers/commit/73e5f5dbfea31ee3b81111ebbf189785fa69731c commit) but it only landed on master on the 19th July 2018 and the last "release" was v0.6.1. The patch looks fairly self contained though so looks like a ready candidate for backporting (and given how widespread this issue is this is the course of action I would recommend).
  
  There are also a lot of issues elsewhere on the web describing this issue:
  https://github.com/moby/moby/issues/34048 ("Error in `docker-credential-secretservice': free(): invalid pointer: 0x00000000011b3150" which reports that you need to install gnome-keyring)
  https://github.com/docker/for-linux/issues/185 ("Docker-engine on Debian should have `accountsservice` and `gnome-keyring` as dependencies")
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884596 ("Please make golang-docker-credential-helpers depend on gnome-keyring")
  https://github.com/docker/docker-credential-helpers/issues/103 ("strange errors on docker build " where someone says they have both gnome-keyring and accountsservice installed but they still see a problem. https://github.com/docker/docker-credential-helpers/issues/104 and https://github.com/docker/docker-credential-helpers/issues/23 appear to be duplicates).
  https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1792824 ("Please remove golang-docker-credential-helpers dependency from the Ubuntu docker-compose package" got the reply "Please don't ask us (Ubuntu) - go and ask Debian")
  https://github.com/moby/moby/issues/37916 ("Error on build: double free or corruption (out) SIGABRT: abort PC=0x7f7464f01e97 m=0 sigcode=18446744073709551610 signal arrived during cgo execution", seems to be the same as the problem described in https://github.com/docker/docker-credential-helpers/issues/103 ).

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

Title:
  Invalid free while running docker build

Status in golang-github-docker-docker-credential-helpers package in Ubuntu:
  Confirmed
Status in golang-github-docker-docker-credential-helpers source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  The bug results in an error being printed on the user screen when
  running docker builds.

  While the error will not cause the build to fail, the bug does prevent
  users to login on servers with no X11 installed.

  [Test Plan]

  - Install docker.io and golang-docker-credential-helpers
  - Run a simple docker build
  - Verify that the error occurs
  - Install the proposed fix
  - Run a simple docker build
  - Verify the error is no longer present

  - alternatively, try to run "docker login" and provide a correct
  username and password. By the end of the login process, an error will
  occur and the login will not succeed.

  ```
  apt-get update
  apt-get install -y docker.io golang-docker-credential-helpers
  mkdir /tmp/dummy-docker-build
  cd /tmp/dummy-docker-build
  cat <<EOF > Dockerfile
  FROM ubuntu:focal
  LABEL hello=label
  EOF
  docker build -t golang-docker-credential-helpers:test .
  # Verify the error is triggered.
  # update the package and try the build again with
  # docker build -t golang-docker-credential-helpers:test
  # from this directory
  ```

  [Where problems could occur]

  While the patch being applied is a simple, straightforward change,
  performing a rebuild of this package in bionic may pull newer versions
  of build dependencies which may cause unpredictable behavior in a
  stable package.

  [Other Info]

  This fix is already present upstream, in Debian, and in all following
  Ubuntu series.

  [Original message]

  Description of the problem:
  Running docker build generates a warning that an invalid free was performed.

  Steps to reproduce:
  sudo apt-get install docker-compose
  sudo docker build -f Dockerfile.build https://github.com/docker-library/hello-world.git

  Expected results:
  Docker container to be built without errors

  Actual results:
  An error is produced while the container is being built:

  free(): invalid pointer
  SIGABRT: abort
  PC=0x7f7027c42e97 m=0 sigcode=18446744073709551610
  signal arrived during cgo execution

  goroutine 1 [syscall, locked to thread]:
  runtime.cgocall(0x4afd50, 0xc420073cc0, 0xc420073ce8)
   /usr/lib/go-1.8/src/runtime/cgocall.go:131 +0xe2 fp=0xc420073c90 sp=0xc420073c50
  github.com/docker/docker-credential-helpers/secretservice._Cfunc_free(0x12c4da0)
   github.com/docker/docker-credential-helpers/secretservice/_obj/_cgo_gotypes.go:111 +0x41 fp=0xc420073cc0 sp=0xc420073c90
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List.func5(0x12c4da0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:96 +0x60 fp=0xc420073cf8 sp=0xc420073cc0
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List(0x0, 0x756060, 0xc420014370)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:97 +0x217 fp=0xc420073da0 sp=0xc420073cf8
  github.com/docker/docker-credential-helpers/secretservice.(*Secretservice).List(0x77e548, 0xc420073e88, 0x410022, 0xc4200142d0)
   <autogenerated>:4 +0x46 fp=0xc420073de0 sp=0xc420073da0
  github.com/docker/docker-credential-helpers/credentials.List(0x756ba0, 0x77e548, 0x7560e0, 0xc42000e018, 0x0, 0x10)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:145 +0x3e fp=0xc420073e68 sp=0xc420073de0
  github.com/docker/docker-credential-helpers/credentials.HandleCommand(0x756ba0, 0x77e548, 0x7fff8fa9e879, 0x4, 0x7560a0, 0xc42000e010, 0x7560e0, 0xc42000e018, 0x40e398, 0x4d35c0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:60 +0x16d fp=0xc420073ed8 sp=0xc420073e68
  github.com/docker/docker-credential-helpers/credentials.Serve(0x756ba0, 0x77e548)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:41 +0x1cb fp=0xc420073f58 sp=0xc420073ed8
  main.main()
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/secretservice/cmd/main_linux.go:9 +0x4f fp=0xc420073f88 sp=0xc420073f58
  runtime.main()
   /usr/lib/go-1.8/src/runtime/proc.go:185 +0x20a fp=0xc420073fe0 sp=0xc420073f88
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420073fe8 sp=0xc420073fe0

  goroutine 17 [syscall, locked to thread]:
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1

  rax    0x0
  rbx    0x7fff8fa9e310
  rcx    0x7f7027c42e97
  rdx    0x0
  rdi    0x2
  rsi    0x7fff8fa9e0a0
  rbp    0x7fff8fa9e410
  rsp    0x7fff8fa9e0a0
  r8     0x0
  r9     0x7fff8fa9e0a0
  r10    0x8
  r11    0x246
  r12    0x7fff8fa9e310
  r13    0x1000
  r14    0x0
  r15    0x30
  rip    0x7f7027c42e97
  rflags 0x246
  cs     0x33
  fs     0x0
  gs     0x0

  How reproducible is the problem?
  Happens every time.

  Version information:
  Ubuntu 18.04.1 LTS
  docker.io 18.06.1-0ubuntu1~18.04.1
  docker-compose 1.17.1-2
  golang-docker-credential-helpers 0.5.0-2

  Additional information:
  It looks like there's a patch which will fix this issue in the docker-credential-helpers project (see the https://github.com/docker/docker-credential-helpers/commit/73e5f5dbfea31ee3b81111ebbf189785fa69731c commit) but it only landed on master on the 19th July 2018 and the last "release" was v0.6.1. The patch looks fairly self contained though so looks like a ready candidate for backporting (and given how widespread this issue is this is the course of action I would recommend).

  There are also a lot of issues elsewhere on the web describing this issue:
  https://github.com/moby/moby/issues/34048 ("Error in `docker-credential-secretservice': free(): invalid pointer: 0x00000000011b3150" which reports that you need to install gnome-keyring)
  https://github.com/docker/for-linux/issues/185 ("Docker-engine on Debian should have `accountsservice` and `gnome-keyring` as dependencies")
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884596 ("Please make golang-docker-credential-helpers depend on gnome-keyring")
  https://github.com/docker/docker-credential-helpers/issues/103 ("strange errors on docker build " where someone says they have both gnome-keyring and accountsservice installed but they still see a problem. https://github.com/docker/docker-credential-helpers/issues/104 and https://github.com/docker/docker-credential-helpers/issues/23 appear to be duplicates).
  https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1792824 ("Please remove golang-docker-credential-helpers dependency from the Ubuntu docker-compose package" got the reply "Please don't ask us (Ubuntu) - go and ask Debian")
  https://github.com/moby/moby/issues/37916 ("Error on build: double free or corruption (out) SIGABRT: abort PC=0x7f7464f01e97 m=0 sigcode=18446744073709551610 signal arrived during cgo execution", seems to be the same as the problem described in https://github.com/docker/docker-credential-helpers/issues/103 ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-docker-credential-helpers/+bug/1813003/+subscriptions



From 1813003 at bugs.launchpad.net  Tue Aug 10 21:13:31 2021
From: 1813003 at bugs.launchpad.net (Sergio Durigan Junior)
Date: Tue, 10 Aug 2021 21:13:31 -0000
Subject: [Bug 1813003] Re: Invalid free while running docker build
References: <154824444386.1905.3790103681743097182.malonedeb@wampee.canonical.com>
Message-ID: <162863001149.26807.11886919685668897365.malone@chaenomeles.canonical.com>

Thanks for addressing the comments, Athos.

Uploaded:

$ dput golang-github-docker-docker-credential-helpers_0.5.0-2ubuntu0.1_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /home/sergio/work/golang-github-docker-docker-credential-helpers/golang-github-docker-docker-credential-helpers_0.5.0-2ubuntu0.1_source.changes: Valid signature from 106DA1C8C3CBBF14
Checking signature on .dsc
gpg: /home/sergio/work/golang-github-docker-docker-credential-helpers/golang-github-docker-docker-credential-helpers_0.5.0-2ubuntu0.1.dsc: Valid signature from 106DA1C8C3CBBF14
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading golang-github-docker-docker-credential-helpers_0.5.0-2ubuntu0.1.dsc: done.
  Uploading golang-github-docker-docker-credential-helpers_0.5.0-2ubuntu0.1.debian.tar.xz: done.
  Uploading golang-github-docker-docker-credential-helpers_0.5.0-2ubuntu0.1_source.buildinfo: done.
  Uploading golang-github-docker-docker-credential-helpers_0.5.0-2ubuntu0.1_source.changes: done.
Successfully uploaded packages.

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

Title:
  Invalid free while running docker build

Status in golang-github-docker-docker-credential-helpers package in Ubuntu:
  Confirmed
Status in golang-github-docker-docker-credential-helpers source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  The bug results in an error being printed on the user screen when
  running docker builds.

  While the error will not cause the build to fail, the bug does prevent
  users to login on servers with no X11 installed.

  [Test Plan]

  - Install docker.io and golang-docker-credential-helpers
  - Run a simple docker build
  - Verify that the error occurs
  - Install the proposed fix
  - Run a simple docker build
  - Verify the error is no longer present

  - alternatively, try to run "docker login" and provide a correct
  username and password. By the end of the login process, an error will
  occur and the login will not succeed.

  ```
  apt-get update
  apt-get install -y docker.io golang-docker-credential-helpers
  mkdir /tmp/dummy-docker-build
  cd /tmp/dummy-docker-build
  cat <<EOF > Dockerfile
  FROM ubuntu:focal
  LABEL hello=label
  EOF
  docker build -t golang-docker-credential-helpers:test .
  # Verify the error is triggered.
  # update the package and try the build again with
  # docker build -t golang-docker-credential-helpers:test
  # from this directory
  ```

  [Where problems could occur]

  While the patch being applied is a simple, straightforward change,
  performing a rebuild of this package in bionic may pull newer versions
  of build dependencies which may cause unpredictable behavior in a
  stable package.

  [Other Info]

  This fix is already present upstream, in Debian, and in all following
  Ubuntu series.

  [Original message]

  Description of the problem:
  Running docker build generates a warning that an invalid free was performed.

  Steps to reproduce:
  sudo apt-get install docker-compose
  sudo docker build -f Dockerfile.build https://github.com/docker-library/hello-world.git

  Expected results:
  Docker container to be built without errors

  Actual results:
  An error is produced while the container is being built:

  free(): invalid pointer
  SIGABRT: abort
  PC=0x7f7027c42e97 m=0 sigcode=18446744073709551610
  signal arrived during cgo execution

  goroutine 1 [syscall, locked to thread]:
  runtime.cgocall(0x4afd50, 0xc420073cc0, 0xc420073ce8)
   /usr/lib/go-1.8/src/runtime/cgocall.go:131 +0xe2 fp=0xc420073c90 sp=0xc420073c50
  github.com/docker/docker-credential-helpers/secretservice._Cfunc_free(0x12c4da0)
   github.com/docker/docker-credential-helpers/secretservice/_obj/_cgo_gotypes.go:111 +0x41 fp=0xc420073cc0 sp=0xc420073c90
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List.func5(0x12c4da0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:96 +0x60 fp=0xc420073cf8 sp=0xc420073cc0
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List(0x0, 0x756060, 0xc420014370)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:97 +0x217 fp=0xc420073da0 sp=0xc420073cf8
  github.com/docker/docker-credential-helpers/secretservice.(*Secretservice).List(0x77e548, 0xc420073e88, 0x410022, 0xc4200142d0)
   <autogenerated>:4 +0x46 fp=0xc420073de0 sp=0xc420073da0
  github.com/docker/docker-credential-helpers/credentials.List(0x756ba0, 0x77e548, 0x7560e0, 0xc42000e018, 0x0, 0x10)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:145 +0x3e fp=0xc420073e68 sp=0xc420073de0
  github.com/docker/docker-credential-helpers/credentials.HandleCommand(0x756ba0, 0x77e548, 0x7fff8fa9e879, 0x4, 0x7560a0, 0xc42000e010, 0x7560e0, 0xc42000e018, 0x40e398, 0x4d35c0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:60 +0x16d fp=0xc420073ed8 sp=0xc420073e68
  github.com/docker/docker-credential-helpers/credentials.Serve(0x756ba0, 0x77e548)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:41 +0x1cb fp=0xc420073f58 sp=0xc420073ed8
  main.main()
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/secretservice/cmd/main_linux.go:9 +0x4f fp=0xc420073f88 sp=0xc420073f58
  runtime.main()
   /usr/lib/go-1.8/src/runtime/proc.go:185 +0x20a fp=0xc420073fe0 sp=0xc420073f88
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420073fe8 sp=0xc420073fe0

  goroutine 17 [syscall, locked to thread]:
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1

  rax    0x0
  rbx    0x7fff8fa9e310
  rcx    0x7f7027c42e97
  rdx    0x0
  rdi    0x2
  rsi    0x7fff8fa9e0a0
  rbp    0x7fff8fa9e410
  rsp    0x7fff8fa9e0a0
  r8     0x0
  r9     0x7fff8fa9e0a0
  r10    0x8
  r11    0x246
  r12    0x7fff8fa9e310
  r13    0x1000
  r14    0x0
  r15    0x30
  rip    0x7f7027c42e97
  rflags 0x246
  cs     0x33
  fs     0x0
  gs     0x0

  How reproducible is the problem?
  Happens every time.

  Version information:
  Ubuntu 18.04.1 LTS
  docker.io 18.06.1-0ubuntu1~18.04.1
  docker-compose 1.17.1-2
  golang-docker-credential-helpers 0.5.0-2

  Additional information:
  It looks like there's a patch which will fix this issue in the docker-credential-helpers project (see the https://github.com/docker/docker-credential-helpers/commit/73e5f5dbfea31ee3b81111ebbf189785fa69731c commit) but it only landed on master on the 19th July 2018 and the last "release" was v0.6.1. The patch looks fairly self contained though so looks like a ready candidate for backporting (and given how widespread this issue is this is the course of action I would recommend).

  There are also a lot of issues elsewhere on the web describing this issue:
  https://github.com/moby/moby/issues/34048 ("Error in `docker-credential-secretservice': free(): invalid pointer: 0x00000000011b3150" which reports that you need to install gnome-keyring)
  https://github.com/docker/for-linux/issues/185 ("Docker-engine on Debian should have `accountsservice` and `gnome-keyring` as dependencies")
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884596 ("Please make golang-docker-credential-helpers depend on gnome-keyring")
  https://github.com/docker/docker-credential-helpers/issues/103 ("strange errors on docker build " where someone says they have both gnome-keyring and accountsservice installed but they still see a problem. https://github.com/docker/docker-credential-helpers/issues/104 and https://github.com/docker/docker-credential-helpers/issues/23 appear to be duplicates).
  https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1792824 ("Please remove golang-docker-credential-helpers dependency from the Ubuntu docker-compose package" got the reply "Please don't ask us (Ubuntu) - go and ask Debian")
  https://github.com/moby/moby/issues/37916 ("Error on build: double free or corruption (out) SIGABRT: abort PC=0x7f7464f01e97 m=0 sigcode=18446744073709551610 signal arrived during cgo execution", seems to be the same as the problem described in https://github.com/docker/docker-credential-helpers/issues/103 ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-docker-credential-helpers/+bug/1813003/+subscriptions



From 1932010 at bugs.launchpad.net  Tue Aug 10 21:49:34 2021
From: 1932010 at bugs.launchpad.net (bugproxy)
Date: Tue, 10 Aug 2021 21:49:34 -0000
Subject: [Bug 1932010] Comment bridged from LTC Bugzilla
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162863217433.22261.8994458185841334738.malone@soybean.canonical.com>

------- Comment From iii at de.ibm.com 2021-08-10 17:45 EDT-------
*** Bug 193835 has been marked as a duplicate of this bug. ***

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

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1932010 at bugs.launchpad.net  Tue Aug 10 21:49:35 2021
From: 1932010 at bugs.launchpad.net (bugproxy)
Date: Tue, 10 Aug 2021 21:49:35 -0000
Subject: [Bug 1932010] patch
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162863217595.21414.12893785370609726811.malone@gac.canonical.com>

------- Comment on attachment From iii at de.ibm.com 2021-08-10 17:47 EDT-------


Argh, I haven't noticed this ticket and made a backport on my own a week ago. I'm attaching my patch here just for reference and will give yours a try tomorrow.

** Attachment added: "patch"
   https://bugs.launchpad.net/bugs/1932010/+attachment/5517176/+files/0001-s390x-vectorize-crc32.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/1932010

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1813003 at bugs.launchpad.net  Tue Aug 10 22:12:20 2021
From: 1813003 at bugs.launchpad.net (Athos Ribeiro)
Date: Tue, 10 Aug 2021 22:12:20 -0000
Subject: [Bug 1813003] Re: Invalid free while running docker build
References: <154824444386.1905.3790103681743097182.malonedeb@wampee.canonical.com>
Message-ID: <162863354040.9322.4577694503617918948.malone@wampee.canonical.com>

Thanks for the review and upload, Sergio!

** Changed in: golang-github-docker-docker-credential-helpers (Ubuntu Bionic)
       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/1813003

Title:
  Invalid free while running docker build

Status in golang-github-docker-docker-credential-helpers package in Ubuntu:
  Confirmed
Status in golang-github-docker-docker-credential-helpers source package in Bionic:
  In Progress

Bug description:
  [Impact]

  The bug results in an error being printed on the user screen when
  running docker builds.

  While the error will not cause the build to fail, the bug does prevent
  users to login on servers with no X11 installed.

  [Test Plan]

  - Install docker.io and golang-docker-credential-helpers
  - Run a simple docker build
  - Verify that the error occurs
  - Install the proposed fix
  - Run a simple docker build
  - Verify the error is no longer present

  - alternatively, try to run "docker login" and provide a correct
  username and password. By the end of the login process, an error will
  occur and the login will not succeed.

  ```
  apt-get update
  apt-get install -y docker.io golang-docker-credential-helpers
  mkdir /tmp/dummy-docker-build
  cd /tmp/dummy-docker-build
  cat <<EOF > Dockerfile
  FROM ubuntu:focal
  LABEL hello=label
  EOF
  docker build -t golang-docker-credential-helpers:test .
  # Verify the error is triggered.
  # update the package and try the build again with
  # docker build -t golang-docker-credential-helpers:test
  # from this directory
  ```

  [Where problems could occur]

  While the patch being applied is a simple, straightforward change,
  performing a rebuild of this package in bionic may pull newer versions
  of build dependencies which may cause unpredictable behavior in a
  stable package.

  [Other Info]

  This fix is already present upstream, in Debian, and in all following
  Ubuntu series.

  [Original message]

  Description of the problem:
  Running docker build generates a warning that an invalid free was performed.

  Steps to reproduce:
  sudo apt-get install docker-compose
  sudo docker build -f Dockerfile.build https://github.com/docker-library/hello-world.git

  Expected results:
  Docker container to be built without errors

  Actual results:
  An error is produced while the container is being built:

  free(): invalid pointer
  SIGABRT: abort
  PC=0x7f7027c42e97 m=0 sigcode=18446744073709551610
  signal arrived during cgo execution

  goroutine 1 [syscall, locked to thread]:
  runtime.cgocall(0x4afd50, 0xc420073cc0, 0xc420073ce8)
   /usr/lib/go-1.8/src/runtime/cgocall.go:131 +0xe2 fp=0xc420073c90 sp=0xc420073c50
  github.com/docker/docker-credential-helpers/secretservice._Cfunc_free(0x12c4da0)
   github.com/docker/docker-credential-helpers/secretservice/_obj/_cgo_gotypes.go:111 +0x41 fp=0xc420073cc0 sp=0xc420073c90
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List.func5(0x12c4da0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:96 +0x60 fp=0xc420073cf8 sp=0xc420073cc0
  github.com/docker/docker-credential-helpers/secretservice.Secretservice.List(0x0, 0x756060, 0xc420014370)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:97 +0x217 fp=0xc420073da0 sp=0xc420073cf8
  github.com/docker/docker-credential-helpers/secretservice.(*Secretservice).List(0x77e548, 0xc420073e88, 0x410022, 0xc4200142d0)
   <autogenerated>:4 +0x46 fp=0xc420073de0 sp=0xc420073da0
  github.com/docker/docker-credential-helpers/credentials.List(0x756ba0, 0x77e548, 0x7560e0, 0xc42000e018, 0x0, 0x10)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:145 +0x3e fp=0xc420073e68 sp=0xc420073de0
  github.com/docker/docker-credential-helpers/credentials.HandleCommand(0x756ba0, 0x77e548, 0x7fff8fa9e879, 0x4, 0x7560a0, 0xc42000e010, 0x7560e0, 0xc42000e018, 0x40e398, 0x4d35c0)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:60 +0x16d fp=0xc420073ed8 sp=0xc420073e68
  github.com/docker/docker-credential-helpers/credentials.Serve(0x756ba0, 0x77e548)
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:41 +0x1cb fp=0xc420073f58 sp=0xc420073ed8
  main.main()
   /build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/secretservice/cmd/main_linux.go:9 +0x4f fp=0xc420073f88 sp=0xc420073f58
  runtime.main()
   /usr/lib/go-1.8/src/runtime/proc.go:185 +0x20a fp=0xc420073fe0 sp=0xc420073f88
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc420073fe8 sp=0xc420073fe0

  goroutine 17 [syscall, locked to thread]:
  runtime.goexit()
   /usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1

  rax    0x0
  rbx    0x7fff8fa9e310
  rcx    0x7f7027c42e97
  rdx    0x0
  rdi    0x2
  rsi    0x7fff8fa9e0a0
  rbp    0x7fff8fa9e410
  rsp    0x7fff8fa9e0a0
  r8     0x0
  r9     0x7fff8fa9e0a0
  r10    0x8
  r11    0x246
  r12    0x7fff8fa9e310
  r13    0x1000
  r14    0x0
  r15    0x30
  rip    0x7f7027c42e97
  rflags 0x246
  cs     0x33
  fs     0x0
  gs     0x0

  How reproducible is the problem?
  Happens every time.

  Version information:
  Ubuntu 18.04.1 LTS
  docker.io 18.06.1-0ubuntu1~18.04.1
  docker-compose 1.17.1-2
  golang-docker-credential-helpers 0.5.0-2

  Additional information:
  It looks like there's a patch which will fix this issue in the docker-credential-helpers project (see the https://github.com/docker/docker-credential-helpers/commit/73e5f5dbfea31ee3b81111ebbf189785fa69731c commit) but it only landed on master on the 19th July 2018 and the last "release" was v0.6.1. The patch looks fairly self contained though so looks like a ready candidate for backporting (and given how widespread this issue is this is the course of action I would recommend).

  There are also a lot of issues elsewhere on the web describing this issue:
  https://github.com/moby/moby/issues/34048 ("Error in `docker-credential-secretservice': free(): invalid pointer: 0x00000000011b3150" which reports that you need to install gnome-keyring)
  https://github.com/docker/for-linux/issues/185 ("Docker-engine on Debian should have `accountsservice` and `gnome-keyring` as dependencies")
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884596 ("Please make golang-docker-credential-helpers depend on gnome-keyring")
  https://github.com/docker/docker-credential-helpers/issues/103 ("strange errors on docker build " where someone says they have both gnome-keyring and accountsservice installed but they still see a problem. https://github.com/docker/docker-credential-helpers/issues/104 and https://github.com/docker/docker-credential-helpers/issues/23 appear to be duplicates).
  https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/1792824 ("Please remove golang-docker-credential-helpers dependency from the Ubuntu docker-compose package" got the reply "Please don't ask us (Ubuntu) - go and ask Debian")
  https://github.com/moby/moby/issues/37916 ("Error on build: double free or corruption (out) SIGABRT: abort PC=0x7f7464f01e97 m=0 sigcode=18446744073709551610 signal arrived during cgo execution", seems to be the same as the problem described in https://github.com/docker/docker-credential-helpers/issues/103 ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-docker-credential-helpers/+bug/1813003/+subscriptions



From 1932010 at bugs.launchpad.net  Tue Aug 10 23:34:49 2021
From: 1932010 at bugs.launchpad.net (Michael Hudson-Doyle)
Date: Tue, 10 Aug 2021 23:34:49 -0000
Subject: [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162863848932.22695.15677918944683624383.malone@chaenomeles.canonical.com>

At a very quick glance, Simon's patch looks a bit closer to the pull
request than the one in comment #4, so if you could test that soon that
would be good.

Simon, aside from debian/patches/lp1932010-ibm-z-add-vectorized-
crc32-implementation.patch which I'm not sure I'm competent to review
beyond seeing how it compares to the pull request, your patch looks
mostly fine but it seems you've duplicated the definition of CONFIGURE_*
in debian/rules? You probably don't want to do 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/1932010

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1932010 at bugs.launchpad.net  Wed Aug 11 07:45:17 2021
From: 1932010 at bugs.launchpad.net (Simon Chopin)
Date: Wed, 11 Aug 2021 07:45:17 -0000
Subject: [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162866791734.16153.12612366381938709427.malone@gac.canonical.com>

Indeed, nice catch! The _32 and _64 variants weren't used anymore,
either.

Updated debdiff attached, and a ~ppa2 version has been uploaded to my
PPA.


** Patch added: "zlib.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1932010/+attachment/5517264/+files/zlib.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/1932010

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1916509 at bugs.launchpad.net  Wed Aug 11 10:02:58 2021
From: 1916509 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 11 Aug 2021 10:02:58 -0000
Subject: [Bug 1916509] [NEW] Update PAM and PAM modules
References: <161400999710.8901.6417089714210711266.malonedeb@gac.canonical.com>
Message-ID: <162867617836.24689.213636917519732256.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

I want to implement pam_faillock which replaces pam_tally2 but requires pam version >= 1.4.0
The ability to 'reliably' lock accounts after a certain number of failed attempts is a requirement of the NIST 800-171 controls implemented by many U.S. government agencies and contractors.

** Affects: pam (Ubuntu)
     Importance: Undecided
     Assignee: Simon Chopin (schopin)
         Status: In Progress


** Tags: libpam pam pam-modules
-- 
Update PAM and PAM modules
https://bugs.launchpad.net/bugs/1916509
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1916509 at bugs.launchpad.net  Wed Aug 11 10:02:26 2021
From: 1916509 at bugs.launchpad.net (Simon Chopin)
Date: Wed, 11 Aug 2021 10:02:26 -0000
Subject: [Bug 1916509] Re: Update PAM and PAM modules
References: <161400999710.8901.6417089714210711266.malonedeb@gac.canonical.com>
Message-ID: <162867614616.25120.14851831219201877038.malone@soybean.canonical.com>

Here's the diff from the Ubuntu branch, much more massive as it includes
the upstream diff...

** Patch added: "pam_from_ubuntu.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1916509/+attachment/5517278/+files/pam_from_ubuntu.debdiff

** Tags added: fr-1604

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

Title:
  Update PAM and PAM modules

Status in pam package in Ubuntu:
  In Progress

Bug description:
  I want to implement pam_faillock which replaces pam_tally2 but requires pam version >= 1.4.0
  The ability to 'reliably' lock accounts after a certain number of failed attempts is a requirement of the NIST 800-171 controls implemented by many U.S. government agencies and contractors.

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



From 1932010 at bugs.launchpad.net  Wed Aug 11 11:09:56 2021
From: 1932010 at bugs.launchpad.net (bugproxy)
Date: Wed, 11 Aug 2021 11:09:56 -0000
Subject: [Bug 1932010] Comment bridged from LTC Bugzilla
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162868019649.30311.7219318100905134980.malone@gac.canonical.com>

------- Comment From iii at de.ibm.com 2021-08-11 06:59 EDT-------
zlib1g_1.2.11.dfsg-2ubuntu7~ppa2_s390x.deb works fine, thanks!

# time -p env DFLTCC=0 python3 -c 'import gzip; gzip.decompress(gzip.compress(b"\x00" * 500000000, 1))'
real 2.59
user 2.23
sys 0.35

# dpkg -i zlib1g_1.2.11.dfsg-2ubuntu7~ppa2_s390x.deb

# time -p env DFLTCC=0 python3 -c 'import gzip; gzip.decompress(gzip.compress(b"\x00" * 500000000, 1))'
real 1.99
user 1.62
sys 0.36

However, I'm not quite sure why does

++#ifdef S390_CRC32_VX
++    if (getauxval(AT_HWCAP) & HWCAP_S390_VX)
++        return s390_crc32_vx;
++#endif

work. For me getauxval() causes a segfault when called from an ifunc,
that's why I have to use the s390-specific ifunc's hwcap parameter.

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

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1932010 at bugs.launchpad.net  Wed Aug 11 11:33:13 2021
From: 1932010 at bugs.launchpad.net (Simon Chopin)
Date: Wed, 11 Aug 2021 11:33:13 -0000
Subject: [Bug 1932010] Comment bridged from LTC Bugzilla
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
 <162868019649.30311.7219318100905134980.malone@gac.canonical.com>
Message-ID: <CAOOWow0664iD99xd-d+kfgdOY2k=fhwJhf_18SsEZsP72PL6MQ@mail.gmail.com>

> However, I'm not quite sure why does
>
> ++#ifdef S390_CRC32_VX
> ++    if (getauxval(AT_HWCAP) & HWCAP_S390_VX)
> ++        return s390_crc32_vx;
> ++#endif
>
> work. For me getauxval() causes a segfault when called from an ifunc,
> that's why I have to use the s390-specific ifunc's hwcap parameter.

Perhaps a bug in your compiler version?

In any case, I believe we can consider the current patch as working as
intended, despite this mystery.

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

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1939544 at bugs.launchpad.net  Wed Aug 11 11:44:58 2021
From: 1939544 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 11 Aug 2021 11:44:58 -0000
Subject: [Bug 1939544] [NEW] Merge the 1.1.1k version from Debian
References: <162867821570.21991.16915484794970250733.malonedeb@gac.canonical.com>
Message-ID: <162868229840.6872.695903905300482999.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Impish currently ships with a version based on the upstream 1.1.1j,
while Debian bullseye/sid has 1.1.1k. Let's merge!

** Affects: openssl (Ubuntu)
     Importance: Undecided
     Assignee: Simon Chopin (schopin)
         Status: In Progress


** Tags: fr-1605
-- 
Merge the 1.1.1k version from Debian
https://bugs.launchpad.net/bugs/1939544
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939544 at bugs.launchpad.net  Wed Aug 11 13:33:15 2021
From: 1939544 at bugs.launchpad.net (Simon Chopin)
Date: Wed, 11 Aug 2021 13:33:15 -0000
Subject: [Bug 1939544] Re: Merge the 1.1.1k version from Debian
References: <162867821570.21991.16915484794970250733.malonedeb@gac.canonical.com>
Message-ID: <162868879516.21159.9236676730999144019.malone@chaenomeles.canonical.com>

Removed previous patches, as there was a small issue with the changelog
(no bug number). Reattaching them now :)

** Patch removed: "openssl_diff_from_ubuntu.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1939544/+attachment/5517303/+files/openssl_diff_from_ubuntu.debdiff

** Patch removed: "openssl_diff_from_debian.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1939544/+attachment/5517304/+files/openssl_diff_from_debian.debdiff

** Patch added: "openssl_diff_from_ubuntu.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1939544/+attachment/5517310/+files/openssl_diff_from_ubuntu.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/1939544

Title:
  Merge the 1.1.1k version from Debian

Status in openssl package in Ubuntu:
  In Progress

Bug description:
  Impish currently ships with a version based on the upstream 1.1.1j,
  while Debian bullseye/sid has 1.1.1k. Let's merge!

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



From 1916509 at bugs.launchpad.net  Wed Aug 11 13:42:44 2021
From: 1916509 at bugs.launchpad.net (Simon Chopin)
Date: Wed, 11 Aug 2021 13:42:44 -0000
Subject: [Bug 1916509] Re: Update PAM and PAM modules
References: <161400999710.8901.6417089714210711266.malonedeb@gac.canonical.com>
Message-ID: <162868936454.16481.9854650381114596184.malone@soybean.canonical.com>

Deleting attachments as they're superseded by these new versions. First
the diff against Ubuntu, followed by the one against Debian for
reference.

** Patch removed: "pam_from_ubuntu.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1916509/+attachment/5517278/+files/pam_from_ubuntu.debdiff

** Patch removed: "pam_from_debian.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1916509/+attachment/5517277/+files/pam_from_debian.debdiff

** Patch added: "pam_from_ubuntu.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1916509/+attachment/5517312/+files/pam_from_ubuntu.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/1916509

Title:
  Update PAM and PAM modules

Status in pam package in Ubuntu:
  In Progress

Bug description:
  I want to implement pam_faillock which replaces pam_tally2 but requires pam version >= 1.4.0
  The ability to 'reliably' lock accounts after a certain number of failed attempts is a requirement of the NIST 800-171 controls implemented by many U.S. government agencies and contractors.

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



From 1916509 at bugs.launchpad.net  Wed Aug 11 13:43:06 2021
From: 1916509 at bugs.launchpad.net (Simon Chopin)
Date: Wed, 11 Aug 2021 13:43:06 -0000
Subject: [Bug 1916509] Re: Update PAM and PAM modules
References: <161400999710.8901.6417089714210711266.malonedeb@gac.canonical.com>
Message-ID: <162868938698.5178.4102968064458629128.malone@gac.canonical.com>

** Patch added: "pam_from_debian.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1916509/+attachment/5517313/+files/pam_from_debian.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/1916509

Title:
  Update PAM and PAM modules

Status in pam package in Ubuntu:
  In Progress

Bug description:
  I want to implement pam_faillock which replaces pam_tally2 but requires pam version >= 1.4.0
  The ability to 'reliably' lock accounts after a certain number of failed attempts is a requirement of the NIST 800-171 controls implemented by many U.S. government agencies and contractors.

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



From 1932010 at bugs.launchpad.net  Wed Aug 11 14:39:56 2021
From: 1932010 at bugs.launchpad.net (bugproxy)
Date: Wed, 11 Aug 2021 14:39:56 -0000
Subject: [Bug 1932010] Comment bridged from LTC Bugzilla
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162869279682.7388.5996893916301346134.malone@wampee.canonical.com>

------- Comment From iii at de.ibm.com 2021-08-11 10:36 EDT-------
I think it rather has to do with glibc - ifunc are normally called quite early and therefore cannot use the dynamically resolved symbols, but maybe newer glibcs tolerate that. Unfortunately I couldn't find more information on this subject. The code seems to work, but just to be on the safe side I'd rather switch to the "old way" of doing things, that involves the hwcap argument:

https://bugzilla.linux.ibm.com/attachment.cgi?id=150618&action=diff#a/crc32.c_sec1
https://bugzilla.linux.ibm.com/attachment.cgi?id=150618&action=diff#a/crc32.c_sec3

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

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1939567 at bugs.launchpad.net  Wed Aug 11 15:06:46 2021
From: 1939567 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 11 Aug 2021 15:06:46 -0000
Subject: [Bug 1939567] [NEW] Merge 2.2.27-2 from Debian
References: <162868772832.28928.4696309983101623186.malonedeb@gac.canonical.com>
Message-ID: <162869440653.27833.5689252258937235276.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Hasn't been merged for a while, the changes from upstream are mostly
bugfixes.

** Affects: gnupg2 (Ubuntu)
     Importance: Undecided
     Assignee: Simon Chopin (schopin)
         Status: In Progress

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


From 1933167 at bugs.launchpad.net  Wed Aug 11 15:44:02 2021
From: 1933167 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Wed, 11 Aug 2021 15:44:02 -0000
Subject: [Bug 1933167] Re: [MIR] oem-sutton.simon-carrie-meta
References: <162432116259.2630.7892035131697104379.malonedeb@gac.canonical.com>
Message-ID: <162869664270.3076.17561436764206870549.malone@gac.canonical.com>

Hello OEM, or anyone else affected,

Accepted oem-sutton.simon-carrie-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.simon-carrie-
meta/20.04~ubuntu1 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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.

** Tags added: verification-needed verification-needed-focal

** Also affects: oem-sutton.simon-carrie-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oem-sutton.simon-carrie-meta (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: Ubuntu Focal
   Importance: Undecided
       Status: New

** Changed in: oem-sutton.simon-carrie-meta (Ubuntu Focal)
       Status: New => Fix Committed

** Changed in: oem-sutton.simon-carrie-meta (Ubuntu)
       Status: New => Won't Fix

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

Title:
  [MIR] oem-sutton.simon-carrie-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed
Status in oem-sutton.simon-carrie-meta package in Ubuntu:
  Won't Fix
Status in The Focal Fossa:
  New
Status in oem-sutton.simon-carrie-meta source package in Focal:
  Fix Committed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-sutton.simon-carrie-meta for focal:
      git clone -b simon.carrie-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta

  [Rationale]
  We want to improve the hardware support for some Lenovo platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms.
  oem-sutton.simon-carrie-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202105-29059

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933167/+subscriptions



From 1932010 at bugs.launchpad.net  Wed Aug 11 17:10:33 2021
From: 1932010 at bugs.launchpad.net (Simon Chopin)
Date: Wed, 11 Aug 2021 17:10:33 -0000
Subject: [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162870183319.25829.16663243838590709017.malone@gac.canonical.com>

I don't have access to your bugzilla, so I'm assuming you pointed to
your own patch and its crc32.c section where you pass hwcap by argument
and call it earlier in the stack? If so, I've implemented this approach
in this new debdiff, and the PPA has been updated as well :-).

Michael, if you're wondering why the s390_crc32_vx has migrated to
crc32.c, it's because the GLibc documentation mentions something about
ifunc only working properly if the deported functions are in the same
translation unit.

In the end, my version of the patch doesn't look that different to
Ilya's ;-)

** Patch added: "zlib.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1932010/+attachment/5517342/+files/zlib.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/1932010

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1932010 at bugs.launchpad.net  Wed Aug 11 18:50:03 2021
From: 1932010 at bugs.launchpad.net (bugproxy)
Date: Wed, 11 Aug 2021 18:50:03 -0000
Subject: [Bug 1932010] Comment bridged from LTC Bugzilla
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162870780403.3071.11342616091177971390.malone@chaenomeles.canonical.com>

------- Comment From iii at de.ibm.com 2021-08-11 14:45 EDT-------
Oh, sorry, I forgot that you can't use the IBM BZ links. I indeed had the following diffs in mind:

1.
#ifndef Z_IFUNC_ASM
local
#endif
-unsigned long (*(crc32_z_ifunc(void)))(unsigned long, const unsigned char FAR *, z_size_t)
+unsigned long (*(crc32_z_ifunc(
+#ifdef __s390__
+unsigned long hwcap
+#else
+void
+#endif
+)))(unsigned long, const unsigned char FAR *, z_size_t)
{
#if _ARCH_PWR8==1
#if defined(__BUILTIN_CPU_SUPPORTS__)

2.
#endif
#endif /* _ARCH_PWR8 */

+#ifdef HAVE_S390X_VX
+    if (hwcap & HWCAP_S390_VX)
+        return s390_crc32_vx;
+#endif
+
/* return a function pointer for optimized arches here */

3.
static unsigned long ZEXPORT (*crc32_func)(unsigned long, const unsigned char FAR *, z_size_t) = NULL;

if (!crc32_func)
-        crc32_func = crc32_z_ifunc();
+        crc32_func = crc32_z_ifunc(
+#ifdef __s390__
+            getauxval(AT_HWCAP)
+#endif
+        );
return (*crc32_func)(crc, buf, len);
}

I think the latest debdiff still misses the second one (the getauxval()
call is still there):

++#if defined(__s390__) && defined(S390_CRC32_VX)
++    if (getauxval(AT_HWCAP) & HWCAP_S390_VX)
++        return s390_crc32_vx;
++#endif

A couple nits:
- changelog: it's dfltcc, not dltss (yeah, the name is super weird :-))
- "/* Work around a probable bug in glibc when invoking getauxval in the ifunc */" - I don't think it's actually a bug, since https://sourceware.org/glibc/wiki/GNU_IFUNC says that:

When LD_BIND_NOW=1 or -Wl,z,now is in effect symbols must be immediately
resolved at startup. In cases where an external function call depends
needs to be made that may fail if such a call has not been initialized
yet (PLT-based relocation which is processed later). For example calling
strlen in an IFUNC resolver built with -Wl,z,now may lead to a segfault
because the PLT is not yet resolved. This may work on x86_64 where the
R_*_IRELATIVE relocations happen in DT_JMPREL after the DT_REL*
relocations, but that is no guarantee that it will work on AArch64,
PPC64, or other architectures that are slightly different. Such
fundamental limitations may be lifted at a future point.

What's surprising is rather that, given this paragraph, the code
nevertheless works and there doesn't seem to be an obvious glibc commit
that lifts this limitation.

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

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1932010 at bugs.launchpad.net  Thu Aug 12 03:46:14 2021
From: 1932010 at bugs.launchpad.net (Michael Hudson-Doyle)
Date: Thu, 12 Aug 2021 03:46:14 -0000
Subject: [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162873997437.31842.5775647791297517543.malone@gac.canonical.com>

I made the changes iii suggested and uploaded.

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

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1939695 at bugs.launchpad.net  Thu Aug 12 14:33:46 2021
From: 1939695 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 12 Aug 2021 14:33:46 -0000
Subject: [Bug 1939695] [NEW] Please merge lshw-02.18.85-0.7 (main) from Debian
 unstable (main)
References: <162877474044.1463.14072735482186585689.malonedeb@gac.canonical.com>
Message-ID: <162877882611.11451.10270562617389993877.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Matthieu Clemenceau (mclemenceau):

Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

At the time of filling this bug, the target debian unstable version is
02.18.85-0.7

Remaining changes on ubuntu are
 - Cherry pick two patches from upstream to fix JSON formatting
   - 2b1c730b493d647bbab4854713571458e82a81e7.patch                            
   - 15565229509455527de9ce7cbb9530e2b31d043b.patch 
 - Cherry pick patches for NMVe support
   - d/p/lp1826737-code-clean-up.patch                                         
   - d/p/lp1826737-implement-NVMe-scanning.patch                               
   - d/p/lp1826737-align-physical-ID-with-NVMe-namespace.patch                 
   - d/p/lp1826737-treat-NVMe-namespaces-like-disks.patch

** Affects: lshw
     Importance: Undecided
         Status: New

-- 
Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1939695
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939695 at bugs.launchpad.net  Thu Aug 12 14:34:24 2021
From: 1939695 at bugs.launchpad.net (Matthieu Clemenceau)
Date: Thu, 12 Aug 2021 14:34:24 -0000
Subject: [Bug 1939695] Re: Please merge lshw-02.18.85-0.7 (main) from Debian
 unstable (main)
References: <162877474044.1463.14072735482186585689.malonedeb@gac.canonical.com>
Message-ID: <162877886494.8218.15215560759985297136.malone@soybean.canonical.com>

debdiff and successful sbuild log have been attached the bug. waiting
for a sponsor 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/1939695

Title:
  Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

Status in lshw:
  New

Bug description:
  Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

  At the time of filling this bug, the target debian unstable version is
  02.18.85-0.7

  Remaining changes on ubuntu are
   - Cherry pick two patches from upstream to fix JSON formatting
     - 2b1c730b493d647bbab4854713571458e82a81e7.patch                            
     - 15565229509455527de9ce7cbb9530e2b31d043b.patch 
   - Cherry pick patches for NMVe support
     - d/p/lp1826737-code-clean-up.patch                                         
     - d/p/lp1826737-implement-NVMe-scanning.patch                               
     - d/p/lp1826737-align-physical-ID-with-NVMe-namespace.patch                 
     - d/p/lp1826737-treat-NVMe-namespaces-like-disks.patch

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



From 1932010 at bugs.launchpad.net  Thu Aug 12 15:49:49 2021
From: 1932010 at bugs.launchpad.net (bugproxy)
Date: Thu, 12 Aug 2021 15:49:49 -0000
Subject: [Bug 1932010] Comment bridged from LTC Bugzilla
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162878338964.8330.9438217339492861199.malone@gac.canonical.com>

------- Comment From iii at de.ibm.com 2021-08-12 11:39 EDT-------
Thanks, everything looks good now!

# time -p env DFLTCC=0 python3 -c 'import gzip; gzip.decompress(gzip.compress(b"\x00" * 500000000, 1))'
real 2.56
user 2.23
sys 0.33

# sha1sum zlib1g_1.2.11.dfsg-2ubuntu7_s390x.deb
56f20f19ee81e025b6ee26efb803f442aeb2819a  zlib1g_1.2.11.dfsg-2ubuntu7_s390x.deb
# dpkg -i zlib1g_1.2.11.dfsg-2ubuntu7_s390x.deb

# time -p env DFLTCC=0 python3 -c 'import gzip; gzip.decompress(gzip.compress(b"\x00" * 500000000, 1))'
real 1.95
user 1.62
sys 0.32

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

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1939728 at bugs.launchpad.net  Thu Aug 12 17:44:19 2021
From: 1939728 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 12 Aug 2021 17:44:19 -0000
Subject: [Bug 1939728] [NEW] Please merge icu 67.1-7 (main) from Debian
 unstable
References: <162878878900.24040.3750746540482533273.malonedeb@wampee.canonical.com>
Message-ID: <162879025949.32515.4455464326295051437.launchpad@gac.canonical.com>

You have been subscribed to a public bug by William Wilson (jawn-smith):

This requires a merge because there are changes in the Ubuntu version
not present in the Debian version.

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

-- 
Please merge icu 67.1-7 (main) from Debian unstable
https://bugs.launchpad.net/bugs/1939728
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939739 at bugs.launchpad.net  Thu Aug 12 19:27:40 2021
From: 1939739 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 12 Aug 2021 19:27:40 -0000
Subject: [Bug 1939739] [NEW] Please merge gnutls28 3.7.1-5 (main) from Debian
 unstable
References: <162879244949.8960.4950265841511856934.malonedeb@gac.canonical.com>
Message-ID: <162879646108.22852.12042939093952893039.launchpad@gac.canonical.com>

You have been subscribed to a public bug by William Wilson (jawn-smith):

This requires a merge because there are changes in the Ubuntu version
not present in the Debian version.

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

-- 
Please merge gnutls28 3.7.1-5 (main) from Debian unstable
https://bugs.launchpad.net/bugs/1939739
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939695 at bugs.launchpad.net  Thu Aug 12 20:23:04 2021
From: 1939695 at bugs.launchpad.net (Brian Murray)
Date: Thu, 12 Aug 2021 20:23:04 -0000
Subject: [Bug 1939695] Re: Please merge lshw-02.18.85-0.7 (main) from Debian
 unstable (main)
References: <162877474044.1463.14072735482186585689.malonedeb@gac.canonical.com>
Message-ID: <162879978603.29326.16741515858998697278.launchpad@chaenomeles.canonical.com>

** Project changed: lshw => lshw (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/1939695

Title:
  Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

Status in lshw package in Ubuntu:
  New

Bug description:
  Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

  At the time of filling this bug, the target debian unstable version is
  02.18.85-0.7

  Remaining changes on ubuntu are
   - Cherry pick two patches from upstream to fix JSON formatting
     - 2b1c730b493d647bbab4854713571458e82a81e7.patch                            
     - 15565229509455527de9ce7cbb9530e2b31d043b.patch 
   - Cherry pick patches for NMVe support
     - d/p/lp1826737-code-clean-up.patch                                         
     - d/p/lp1826737-implement-NVMe-scanning.patch                               
     - d/p/lp1826737-align-physical-ID-with-NVMe-namespace.patch                 
     - d/p/lp1826737-treat-NVMe-namespaces-like-disks.patch

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



From 1939750 at bugs.launchpad.net  Thu Aug 12 21:07:18 2021
From: 1939750 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 12 Aug 2021 21:07:18 -0000
Subject: [Bug 1939750] [NEW] Please merge 7.74.0-1.3
References: <162880205922.12278.17954833672225369383.malonedeb@gac.canonical.com>
Message-ID: <162880243907.8306.2355622990300641637.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Dan Bungert (dbungert):

Debian version 7.74.0-1.3 cherry-picks a fix for a command line API
breakage that would be unexpected in a minor version release.
Please help merge.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064
https://github.com/curl/curl/issues/6321

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

** Affects: debian
     Importance: Unknown
         Status: Unknown


** Tags: patch
-- 
Please merge 7.74.0-1.3
https://bugs.launchpad.net/bugs/1939750
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939751 at bugs.launchpad.net  Thu Aug 12 21:55:43 2021
From: 1939751 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 12 Aug 2021 21:55:43 -0000
Subject: [Bug 1939751] [NEW] openssh FTBFS with glibc >= 2.34
References: <162880212312.6537.6691163062217728505.malonedeb@chaenomeles.canonical.com>
Message-ID: <162880534409.27292.2139132050756467107.launchpad@gac.canonical.com>

You have been subscribed to a public bug by William Wilson (jawn-smith):

Due to an incompatible function prototype in openbsd-compat tests, this
package FTBFS with glibc >= 2.34. There is an upstream patch already in
place to address this.

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

** Affects: openssh (Debian)
     Importance: Unknown
         Status: Unknown

-- 
openssh FTBFS with glibc >= 2.34
https://bugs.launchpad.net/bugs/1939751
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1853301 at bugs.launchpad.net  Fri Aug 13 00:25:02 2021
From: 1853301 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 13 Aug 2021 00:25:02 -0000
Subject: [Bug 1853301] [NEW] [21.10 FEAT] SMC: Statistics Support - smc-tools
References: <157425839040.7124.1828263599040764648.malonedeb@gac.canonical.com>
Message-ID: <162881430254.542.5477920925156993609.launchpad@gac.canonical.com>

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

Add statistics for traffic run across RoCE (RDMA) and ISM devices. Most
like requires a new tool in smc-tools that queries the stats from the
smc module via netlink.

smc.tools part

** Affects: ubuntu-z-systems
     Importance: Medium
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: Triaged

** Affects: smc-tools (Ubuntu)
     Importance: Undecided
     Assignee: Matthieu Clemenceau (mclemenceau)
         Status: New


** Tags: architecture-s39064 bugnameltc-182543 fr-1552 patch severity-high targetmilestone-inin2110
-- 
[21.10 FEAT] SMC: Statistics Support - smc-tools
https://bugs.launchpad.net/bugs/1853301
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1853301 at bugs.launchpad.net  Fri Aug 13 00:25:02 2021
From: 1853301 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Fri, 13 Aug 2021 00:25:02 -0000
Subject: [Bug 1853301] Re: [21.10 FEAT] SMC: Statistics Support - smc-tools
References: <157425839040.7124.1828263599040764648.malonedeb@gac.canonical.com>
Message-ID: <162881430299.24094.7025328555535913593.malone@chaenomeles.canonical.com>

The attachment "smc-tools_1.5.0-0ubuntu2_1.6.0-0ubuntu1.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/1853301

Title:
  [21.10 FEAT] SMC: Statistics Support - smc-tools

Status in Ubuntu on IBM z Systems:
  Triaged
Status in smc-tools package in Ubuntu:
  New

Bug description:
  Add statistics for traffic run across RoCE (RDMA) and ISM devices.
  Most like requires a new tool in smc-tools that queries the stats from
  the smc module via netlink.

  smc.tools part

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853301/+subscriptions



From 1932555 at bugs.launchpad.net  Fri Aug 13 03:06:41 2021
From: 1932555 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 13 Aug 2021 03:06:41 -0000
Subject: [Bug 1932555] [NEW] [MIR] oem-somerville-bowen-meta
References: <162402726627.16821.4852855021194925587.malonedeb@gac.canonical.com>
Message-ID: <162882400135.23077.14956201803639005560.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Yao Wei (medicalwei):

[Background]

Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

[Impact]

 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
 2. The background and impact of the situation for this change, and it's impact.

[Testing]

 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

[Regression Potential]

Most potential regressions will live in the package set that will be
installed via dependency of this package, which live in OEM archive
(outside of Ubuntu) and control by OEM team. OEM team and other
corresponding team need take responsibility of those dependency
installed.

[When switching kernel flavour] Check that the new kernel flavour works
on the target platform.

[Availability]
This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
The source code of the oem-somerville-bowen-meta for focal:
    git clone -b bowen-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta

[Rationale]
We want to improve the hardware support for some Dell platforms.

[Security]
No CVE/known security issue.

[Quality assurance]
I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms.
oem-somerville-bowen-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

[Dependencies]
It only depends on ubuntu-oem-keyring.

[Standards compliance]
This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

[Maintenance]
Canonical OEM Enablement Team will take care of the maintenance.

[Background information]
Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
verify this MIR against the reference package in the archive.

https://ubuntu.com/certified/202001-27708
https://ubuntu.com/certified/202002-27718

** Affects: oem-priority
     Importance: Critical
     Assignee: OEM Taipei Jenkins Role Account (oem-taipei-bot)
         Status: Fix Committed

** Affects: ubuntu
     Importance: Undecided
         Status: Confirmed


** Tags: oem-meta-packages oem-priority oem-scripts-0.98
-- 
[MIR] oem-somerville-bowen-meta
https://bugs.launchpad.net/bugs/1932555
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1932555 at bugs.launchpad.net  Fri Aug 13 03:12:09 2021
From: 1932555 at bugs.launchpad.net (Yao Wei)
Date: Fri, 13 Aug 2021 03:12:09 -0000
Subject: [Bug 1932555] Re: [MIR] oem-somerville-bowen-meta
References: <162402726627.16821.4852855021194925587.malonedeb@gac.canonical.com>
Message-ID: <162882432949.29669.14402540279010525937.malone@wampee.canonical.com>

Attach oem-somerville-bowen-meta_20.04~ubuntu1.debdiff by oem-scripts
1.7.

** Patch added: "oem-somerville-bowen-meta_20.04~ubuntu1.debdiff"
   https://bugs.launchpad.net/bugs/1932555/+attachment/5517654/+files/oem-somerville-bowen-meta_20.04~ubuntu1.debdiff

** Tags removed: oem-scripts-0.98
** Tags added: oem-scripts-1.7 ubuntu-certified

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

Title:
  [MIR] oem-somerville-bowen-meta

Status in OEM Priority Project:
  Fix Committed
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-somerville-bowen-meta for focal:
      git clone -b bowen-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta

  [Rationale]
  We want to improve the hardware support for some Dell platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms.
  oem-somerville-bowen-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202001-27708
  https://ubuntu.com/certified/202002-27718

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932555/+subscriptions



From 1939739 at bugs.launchpad.net  Fri Aug 13 05:40:32 2021
From: 1939739 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:40:32 -0000
Subject: [Bug 1939739] Re: Please merge gnutls28 3.7.1-5 (main) from Debian
 unstable
References: <162879244949.8960.4950265841511856934.malonedeb@gac.canonical.com>
Message-ID: <162883323332.26263.6259614927474931900.launchpad@wampee.canonical.com>

** Changed in: gnutls28 (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/1939739

Title:
  Please merge gnutls28 3.7.1-5 (main) from Debian unstable

Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

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



From 1939728 at bugs.launchpad.net  Fri Aug 13 05:40:21 2021
From: 1939728 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:40:21 -0000
Subject: [Bug 1939728] Re: Please merge icu 67.1-7 (main) from Debian unstable
References: <162878878900.24040.3750746540482533273.malonedeb@wampee.canonical.com>
Message-ID: <162883322236.24066.8315803427074443365.launchpad@chaenomeles.canonical.com>

** Changed in: icu (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/1939728

Title:
  Please merge icu 67.1-7 (main) from Debian unstable

Status in icu package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

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



From 1938707 at bugs.launchpad.net  Fri Aug 13 05:38:01 2021
From: 1938707 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:38:01 -0000
Subject: [Bug 1938707] Re: Sync sshguard 2.3.1-2 (universe) from Debian
 unstable (main)
References: <162791958678.2824.4847316839802775770.malonedeb@soybean.canonical.com>
Message-ID: <162883308238.28415.14175978868553664599.launchpad@gac.canonical.com>

** Changed in: sshguard (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/1938707

Title:
  Sync sshguard 2.3.1-2 (universe) from Debian unstable (main)

Status in sshguard package in Ubuntu:
  New

Bug description:
  Please sync sshguard 2.3.1-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Drop Ubuntu delta and use nftables
    * Drop Ubuntu delta and use nftables
    * Drop Ubuntu delta and use nftables
    * Fix path to iptables binaries in the .service unit. LP: #1884848
    * Revert to use iptables which is default in Ubuntu:
      - Revert "Use nft instead iptables"
      - Revert "Change firewall backend to nftables"
      - Revert "Remove iptables from Depends"
    * Revert to use iptables which is default in Ubuntu:
      - Revert "Use nft instead iptables"
      - Revert "Change firewall backend to nftables"
      - Revert "Remove iptables from Depends"

  
  Delta is effectively empty, newer version can be synced.

  Changelog entries since current impish version 2.3.1-1ubuntu3:

  sshguard (2.3.1-2) unstable; urgency=medium

    * Fix config file. (Closes: #928525)

   -- Julián Moreno Patiño <julian at debian.org>  Mon, 26 Jul 2021
  22:18:43 -0500

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



From 1939695 at bugs.launchpad.net  Fri Aug 13 05:40:13 2021
From: 1939695 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:40:13 -0000
Subject: [Bug 1939695] Re: Please merge lshw-02.18.85-0.7 (main) from Debian
 unstable (main)
References: <162877474044.1463.14072735482186585689.malonedeb@gac.canonical.com>
Message-ID: <162883321417.21219.12492728261719970933.launchpad@chaenomeles.canonical.com>

** Changed in: lshw (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/1939695

Title:
  Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

Status in lshw package in Ubuntu:
  New

Bug description:
  Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

  At the time of filling this bug, the target debian unstable version is
  02.18.85-0.7

  Remaining changes on ubuntu are
   - Cherry pick two patches from upstream to fix JSON formatting
     - 2b1c730b493d647bbab4854713571458e82a81e7.patch                            
     - 15565229509455527de9ce7cbb9530e2b31d043b.patch 
   - Cherry pick patches for NMVe support
     - d/p/lp1826737-code-clean-up.patch                                         
     - d/p/lp1826737-implement-NVMe-scanning.patch                               
     - d/p/lp1826737-align-physical-ID-with-NVMe-namespace.patch                 
     - d/p/lp1826737-treat-NVMe-namespaces-like-disks.patch

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



From 1939567 at bugs.launchpad.net  Fri Aug 13 05:40:03 2021
From: 1939567 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:40:03 -0000
Subject: [Bug 1939567] Re: Merge 2.2.27-2 from Debian
References: <162868772832.28928.4696309983101623186.malonedeb@gac.canonical.com>
Message-ID: <162883320510.28105.2631693153887399689.launchpad@wampee.canonical.com>

** Changed in: gnupg2 (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/1939567

Title:
  Merge 2.2.27-2 from Debian

Status in gnupg2 package in Ubuntu:
  In Progress

Bug description:
  Hasn't been merged for a while, the changes from upstream are mostly
  bugfixes.

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



From 1939544 at bugs.launchpad.net  Fri Aug 13 05:39:23 2021
From: 1939544 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:39:23 -0000
Subject: [Bug 1939544] Re: Merge the 1.1.1k version from Debian
References: <162867821570.21991.16915484794970250733.malonedeb@gac.canonical.com>
Message-ID: <162883316379.28168.13737005003402565727.launchpad@gac.canonical.com>

** Changed in: openssl (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/1939544

Title:
  Merge the 1.1.1k version from Debian

Status in openssl package in Ubuntu:
  In Progress

Bug description:
  Impish currently ships with a version based on the upstream 1.1.1j,
  while Debian bullseye/sid has 1.1.1k. Let's merge!

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



From 1936664 at bugs.launchpad.net  Fri Aug 13 05:37:43 2021
From: 1936664 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:37:43 -0000
Subject: [Bug 1936664] Re: buildmode=c-shared not supported on linux/risc-v
References: <162644431906.27897.7005500802674012219.malonedeb@wampee.canonical.com>
Message-ID: <162883306457.23250.10796413707817891627.launchpad@soybean.canonical.com>

** Changed in: golang-1.16 (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/1936664

Title:
  buildmode=c-shared not supported on linux/risc-v

Status in golang-1.16 package in Ubuntu:
  New

Bug description:
  In order to build ubuntu-report and eventual desktop images for
  risc-v, golang needs to support buildmode=c-shared on linux/risc-v. We
  have submitted the change upstream, and will need to carry a delta
  until it lands in debian.

  See https://github.com/golang/go/issues/47100 for upstream work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.16/+bug/1936664/+subscriptions



From 1939751 at bugs.launchpad.net  Fri Aug 13 05:42:21 2021
From: 1939751 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:42:21 -0000
Subject: [Bug 1939751] Re: openssh FTBFS with glibc >= 2.34
References: <162880212312.6537.6691163062217728505.malonedeb@chaenomeles.canonical.com>
Message-ID: <162883334257.26309.13654607490994338904.launchpad@wampee.canonical.com>

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

** Tags added: ftbfs

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

Title:
  openssh FTBFS with glibc >= 2.34

Status in openssh package in Ubuntu:
  Confirmed
Status in openssh package in Debian:
  Unknown

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

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



From 1939750 at bugs.launchpad.net  Fri Aug 13 05:40:43 2021
From: 1939750 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:40:43 -0000
Subject: [Bug 1939750] Re: Please merge 7.74.0-1.3
References: <162880205922.12278.17954833672225369383.malonedeb@gac.canonical.com>
Message-ID: <162883324517.27724.17509476908346898942.launchpad@wampee.canonical.com>

** Changed in: curl (Ubuntu)
   Importance: Undecided => Wishlist

** Package changed: debian => curl (Debian)

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

Title:
  Please merge 7.74.0-1.3

Status in curl package in Ubuntu:
  Confirmed
Status in curl package in Debian:
  Unknown

Bug description:
  Debian version 7.74.0-1.3 cherry-picks a fix for a command line API
  breakage that would be unexpected in a minor version release.
  Please help merge.

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064
  https://github.com/curl/curl/issues/6321

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



From 1932010 at bugs.launchpad.net  Fri Aug 13 05:44:23 2021
From: 1932010 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:44:23 -0000
Subject: [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162883346450.23881.12830465894960611817.launchpad@soybean.canonical.com>

** Changed in: zlib (Ubuntu)
   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/1932010

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1853301 at bugs.launchpad.net  Fri Aug 13 05:43:35 2021
From: 1853301 at bugs.launchpad.net (Mathew Hodson)
Date: Fri, 13 Aug 2021 05:43:35 -0000
Subject: [Bug 1853301] Re: [21.10 FEAT] SMC: Statistics Support - smc-tools
References: <157425839040.7124.1828263599040764648.malonedeb@gac.canonical.com>
Message-ID: <162883341723.28412.7951271021245717841.launchpad@wampee.canonical.com>

** Changed in: smc-tools (Ubuntu)
   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/1853301

Title:
  [21.10 FEAT] SMC: Statistics Support - smc-tools

Status in Ubuntu on IBM z Systems:
  Triaged
Status in smc-tools package in Ubuntu:
  New

Bug description:
  Add statistics for traffic run across RoCE (RDMA) and ISM devices.
  Most like requires a new tool in smc-tools that queries the stats from
  the smc module via netlink.

  smc.tools part

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853301/+subscriptions



From 1921658 at bugs.launchpad.net  Fri Aug 13 06:15:35 2021
From: 1921658 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 13 Aug 2021 06:15:35 -0000
Subject: [Bug 1921658] [NEW] Can't compose kvm host with lvm storage on maas
 2.8.4 
References: <161697993430.18838.13362103946863867785.malonedeb@gac.canonical.com>
Message-ID: <162883533615.32150.11565479217622327365.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Seyeong Kim (seyeongkim):

I can't compose kvm host on maas 2.8.4 ( bionic)

I upgraded twisted and related component with pip but the symptom is the
same.

MaaS 2.9.x in Focal works fine.

in 2.8.x, pexpect virsh vol-path should return [2] but returns [3]

[2]
/dev/maas_data_vg/8d4e8b04-4031-4a1b-b5f2-a8306192db11
[3]
2021-03-17 20:43:34 stderr: [error] Message: 'this is the result...\n'
2021-03-17 20:43:34 stderr: [error] Arguments: ([' ', '<3ef-46ca-87c8-19171950592f --pool maas_guest_lvm_vg', "error: command 'attach-disk' doesn't support option --pool"],)

sometimes it fails in

    def get_volume_path(self, pool, volume):
        """Return the path to the file from `pool` and `volume`."""
        output = self.run(["vol-path", volume, "--pool", pool])
        return output.strip()

sometimes failes in

    def get_machine_xml(self, machine):
        # Check if we have a cached version of the XML.
        # This is a short-lived object, so we don't need to worry about
        # expiring objects in the cache.
        if machine in self.xml:
            return self.xml[machine]

        # Grab the XML from virsh if we don't have it already.
        output = self.run(["dumpxml", machine]).strip()
        if output.startswith("error:"):
            maaslog.error("%s: Failed to get XML for machine", machine)
            return None

        # Cache the XML, since we'll need it later to reconfigure the VM.
        self.xml[machine] = output
        return output

I assume that run function has issue.

Command line virsh vol-path and simple pepect python code works fine.


Any advice for this issue?

Thanks.

Reproducer is below.[1]

[1]

1) Create file to be used as loopback device

sudo dd if=/dev/zero of=lvm bs=16000 count=1M

2) sudo losetup /dev/loop39 lvm

3) sudo pvcreate /dev/loop39

4) sudo vgcreate maas_data_vg /dev/loop39

5) Save below xml:
<pool type='logical'>
<name>maas_guest_lvm_vg</name>
<source>
<name>maas_data_vg</name>
<format type='lvm2'/>
</source>
<target>
<path>/dev/maas_data_vg</path>
</target>
</pool>

6) virsh pool-create maas_guest_lvm_vg.xml

7) Add KVM host in MaaS

8) Attempt to compose a POD using storage pool maas_guest_lvm_vg

9) GUI will fail with:

Pod unable to compose machine: Unable to compose machine because: Failed
talking to pod: Start tag expected, '<' not found, line 1, column 1
(<string>, line 1)

** Affects: maas
     Importance: Medium
         Status: Triaged

** Affects: readline (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: readline (Ubuntu Bionic)
     Importance: Undecided
     Assignee: Seyeong Kim (seyeongkim)
         Status: In Progress


** Tags: sts
-- 
Can't compose kvm host with lvm storage on maas 2.8.4 
https://bugs.launchpad.net/bugs/1921658
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939409 at bugs.launchpad.net  Fri Aug 13 07:49:42 2021
From: 1939409 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 13 Aug 2021 07:49:42 -0000
Subject: [Bug 1939409] [NEW] merge e2fsprogs 1.46.3-1 from Debian: s390x fails
 in test f_baddotdir
References: <162860191203.23963.14834301011076203546.malonedeb@soybean.canonical.com>
Message-ID: <162884098264.17477.8005999262086158036.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Heinrich Schuchardt (xypron):

e2fsprogs 1.46.3-1ubuntu1 is in proposed.

Architecture s390x fail in test f_baddotdir. The test image was changed
with the new release.

Next step should be analyzing the error on a s390x virtual machine.

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


** Tags: fr-1602 s390x
-- 
merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir
https://bugs.launchpad.net/bugs/1939409
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939409 at bugs.launchpad.net  Fri Aug 13 07:52:12 2021
From: 1939409 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Fri, 13 Aug 2021 07:52:12 -0000
Subject: [Bug 1939409] Re: merge e2fsprogs 1.46.3-1 from Debian: s390x fails
 in test f_baddotdir
References: <162860191203.23963.14834301011076203546.malonedeb@soybean.canonical.com>
Message-ID: <162884113297.19230.598081372767717150.malone@chaenomeles.canonical.com>

e2fsprogs - 1.46.3-1ubuntu2 is available in ppa:xypron/merge-from-debian

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

Title:
  merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  e2fsprogs 1.46.3-1ubuntu1 is in proposed.

  Architecture s390x fail in test f_baddotdir. The test image was
  changed with the new release.

  Next step should be analyzing the error on a s390x virtual machine.

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



From 1939613 at bugs.launchpad.net  Fri Aug 13 12:28:48 2021
From: 1939613 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 13 Aug 2021 12:28:48 -0000
Subject: [Bug 1939613] [NEW] xrt package does not create  xilinx.icd
References: <162870820279.31010.18218099389662983300.malonedeb@soybean.canonical.com>
Message-ID: <162885772917.22290.1853258746016696216.launchpad@soybean.canonical.com>

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

As part of the installation, the XRT package should create the vendor-
specific /etc/OpenCL/vendor/xilinx.icd file.  The contents of the file
should be:

libxilinxopencl.so

This provides support for the Installable Client Driver (ICD) model as
described here: https://github.com/KhronosGroup/OpenCL-ICD-Loader

Applications can then be built using -lOpenCL instead of linking to the
xilinx-specific libxilinxopencl.so.


$ apt-cache policy xrt-embedded
xrt-embedded:
  Installed: 202020.2.8.726-0ubuntu2
  Candidate: 202020.2.8.726-0ubuntu7~20.04
  Version table:
     202020.2.8.726-0ubuntu7~20.04 500
        500 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe arm64 Packages
 *** 202020.2.8.726-0ubuntu2 100
        100 /var/lib/dpkg/status

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


** Tags: patch
-- 
xrt package does not create  xilinx.icd
https://bugs.launchpad.net/bugs/1939613
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939613 at bugs.launchpad.net  Fri Aug 13 12:28:49 2021
From: 1939613 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Fri, 13 Aug 2021 12:28:49 -0000
Subject: [Bug 1939613] Re: xrt package does not create  xilinx.icd
References: <162870820279.31010.18218099389662983300.malonedeb@soybean.canonical.com>
Message-ID: <162885772963.22165.15655524408826612600.malone@soybean.canonical.com>

The attachment "debdiff.patch" 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/1939613

Title:
  xrt package does not create  xilinx.icd

Status in xrt package in Ubuntu:
  New

Bug description:
  As part of the installation, the XRT package should create the vendor-
  specific /etc/OpenCL/vendor/xilinx.icd file.  The contents of the file
  should be:

  libxilinxopencl.so

  This provides support for the Installable Client Driver (ICD) model as
  described here: https://github.com/KhronosGroup/OpenCL-ICD-Loader

  Applications can then be built using -lOpenCL instead of linking to
  the xilinx-specific libxilinxopencl.so.

  
  $ apt-cache policy xrt-embedded
  xrt-embedded:
    Installed: 202020.2.8.726-0ubuntu2
    Candidate: 202020.2.8.726-0ubuntu7~20.04
    Version table:
       202020.2.8.726-0ubuntu7~20.04 500
          500 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe arm64 Packages
   *** 202020.2.8.726-0ubuntu2 100
          100 /var/lib/dpkg/status

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



From 1939613 at bugs.launchpad.net  Fri Aug 13 12:38:52 2021
From: 1939613 at bugs.launchpad.net (Alfonso Sanchez-Beato)
Date: Fri, 13 Aug 2021 12:38:52 -0000
Subject: [Bug 1939613] Re: xrt package does not create  xilinx.icd
References: <162870820279.31010.18218099389662983300.malonedeb@soybean.canonical.com>
Message-ID: <162885833378.22425.2632244833667633444.launchpad@soybean.canonical.com>

** Changed in: xrt (Ubuntu)
     Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)

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

Title:
  xrt package does not create  xilinx.icd

Status in xrt package in Ubuntu:
  New

Bug description:
  As part of the installation, the XRT package should create the vendor-
  specific /etc/OpenCL/vendor/xilinx.icd file.  The contents of the file
  should be:

  libxilinxopencl.so

  This provides support for the Installable Client Driver (ICD) model as
  described here: https://github.com/KhronosGroup/OpenCL-ICD-Loader

  Applications can then be built using -lOpenCL instead of linking to
  the xilinx-specific libxilinxopencl.so.

  
  $ apt-cache policy xrt-embedded
  xrt-embedded:
    Installed: 202020.2.8.726-0ubuntu2
    Candidate: 202020.2.8.726-0ubuntu7~20.04
    Version table:
       202020.2.8.726-0ubuntu7~20.04 500
          500 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe arm64 Packages
   *** 202020.2.8.726-0ubuntu2 100
          100 /var/lib/dpkg/status

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



From 1782984 at bugs.launchpad.net  Fri Aug 13 13:14:46 2021
From: 1782984 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 13 Aug 2021 13:14:46 -0000
Subject: [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed
 with multiple applications
References: <153226365365.23524.716838067617811954.malonedeb@soybean.canonical.com>
Message-ID: <162886048786.4279.3367888375755472840.launchpad@wampee.canonical.com>

** Description changed:

+ [Impact]
+ 
+ There is a race in libx11 causing applications to randomly abort. It's
+ not trivial to reproduce, but there are enough duplicates that this
+ deserves an SRU to bionic & focal.
+ 
+ [Fix]
+ 
+ Backport a commit from upstream:
+ 
+ From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
+ From: Frediano Ziglio <fziglio at redhat.com>
+ Date: Wed, 29 Jan 2020 09:06:54 +0000
+ Subject: [PATCH] Fix poll_for_response race condition
+ 
+ In poll_for_response is it possible that event replies are skipped
+ and a more up to date message reply is returned.
+ This will cause next poll_for_event call to fail aborting the program.
+ 
+ This was proved using some slow ssh tunnel or using some program
+ to slow down server replies (I used a combination of xtrace and strace).
+ 
+ How the race happens:
+ - program enters into poll_for_response;
+ - poll_for_event is called but the server didn't still send the reply;
+ - pending_requests is not NULL because we send a request (see call
+   to  append_pending_request in _XSend);
+ - xcb_poll_for_reply64 is called from poll_for_response;
+ - xcb_poll_for_reply64 will read from server, at this point
+   server reply with an event (say sequence N) and the reply to our
+   last request (say sequence N+1);
+ - xcb_poll_for_reply64 returns the reply for the request we asked;
+ - last_request_read is set to N+1 sequence in poll_for_response;
+ - poll_for_response returns the response to the request;
+ - poll_for_event is called (for instance from another poll_for_response);
+ - event with sequence N is retrieved;
+ - the N sequence is widen, however, as the "new" number computed from
+   last_request_read is less than N the number is widened to N + 2^32
+   (assuming last_request_read is still contained in 32 bit);
+ - poll_for_event enters the nested if statement as req is NULL;
+ - we compare the widen N (which now does not fit into 32 bit) with
+   request (which fits into 32 bit) hitting the throw_thread_fail_assert.
+ 
+ To avoid the race condition and to avoid the sequence to go back
+ I check again for new events after getting the response and
+ return this last event if present saving the reply to return it
+ later.
+ 
+ To test the race and the fix it's helpful to add a delay (I used a
+ "usleep(5000)") before calling xcb_poll_for_reply64.
+ 
+ Original patch written by Frediano Ziglio, see
+ https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34
+ 
+ Reworked primarily for readability by Peter Hutterer, see
+ https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53
+ 
+ Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
+ 
+ bionic needs another commit so that the real fix applies.
+ 
+ [Test case]
+ 
+ It's a race condition, the SRU sponsor (tjaalton) does not have a test
+ case for this, but the bug subscribers seem to.
+ 
+ 
+ [Where things could go wrong]
+ 
+ In theory there might be a case where a race still happens, but since
+ this has been upstream for a year now with no follow-up commits, it's
+ safe to assume that there are no regressions.
+ 
+ 
+ --
+ 
  STEPS TO REPRODUCE
  ==================
  The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation.
  
  EXPECTED RESULTS
  ================
  pcmanfm works without problem.
  
  ACTUAL RESULTS
  ==============
  All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log:
  
  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload
  
  (note the timestamp on the message will vary)
  
  AFFECTED VERSIONS
  =================
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1
  
  UPSTREAM BUG
  ============
  https://sourceforge.net/p/pcmanfm/bugs/1089/
  
  ADDITIONAL NOTES
  ================
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710
  
  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  In Progress
Status in libx11 source package in Focal:
  In Progress
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio <fziglio at redhat.com>
  Date: Wed, 29 Jan 2020 09:06:54 +0000
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
    to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
    server reply with an event (say sequence N) and the reply to our
    last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
    last_request_read is less than N the number is widened to N + 2^32
    (assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
    request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==================
  The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation.

  EXPECTED RESULTS
  ================
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==============
  All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =================
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  ============
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  ================
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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



From 1853301 at bugs.launchpad.net  Fri Aug 13 14:32:36 2021
From: 1853301 at bugs.launchpad.net (Graham Inggs)
Date: Fri, 13 Aug 2021 14:32:36 -0000
Subject: [Bug 1853301] Re: [21.10 FEAT] SMC: Statistics Support - smc-tools
References: <157425839040.7124.1828263599040764648.malonedeb@gac.canonical.com>
Message-ID: <162886515786.20459.4812092253531116354.launchpad@gac.canonical.com>

** Changed in: smc-tools (Ubuntu)
     Assignee: Matthieu Clemenceau (mclemenceau) => Graham Inggs (ginggs)

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

Title:
  [21.10 FEAT] SMC: Statistics Support - smc-tools

Status in Ubuntu on IBM z Systems:
  Triaged
Status in smc-tools package in Ubuntu:
  New

Bug description:
  Add statistics for traffic run across RoCE (RDMA) and ISM devices.
  Most like requires a new tool in smc-tools that queries the stats from
  the smc module via netlink.

  smc.tools part

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853301/+subscriptions



From 1939909 at bugs.launchpad.net  Fri Aug 13 16:36:42 2021
From: 1939909 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 13 Aug 2021 16:36:42 -0000
Subject: [Bug 1939909] [NEW] FTBFS against glibc 2.34
References: <162887225110.21018.1195284754935981627.malonedeb@wampee.canonical.com>
Message-ID: <162887260235.17149.18211872108551254930.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

The package m4 failed to build in a recent archive rebuild, see
https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#foundations-bugs .

The build failure can be traced to the glibc version used for the
rebuild, 2.34, as discussed there
https://lists.gnu.org/archive/html/bug-m4/2021-03/msg00000.html

** Affects: m4 (Ubuntu)
     Importance: Undecided
     Assignee: Simon Chopin (schopin)
         Status: In Progress

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


From 1939544 at bugs.launchpad.net  Fri Aug 13 17:36:53 2021
From: 1939544 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 13 Aug 2021 17:36:53 -0000
Subject: [Bug 1939544] Re: Merge the 1.1.1k version from Debian
References: <162867821570.21991.16915484794970250733.malonedeb@gac.canonical.com>
Message-ID: <162887621455.32099.1879465368071363112.launchpad@gac.canonical.com>

** Changed in: openssl (Ubuntu)
       Status: In Progress => 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/1939544

Title:
  Merge the 1.1.1k version from Debian

Status in openssl package in Ubuntu:
  Fix Committed

Bug description:
  Impish currently ships with a version based on the upstream 1.1.1j,
  while Debian bullseye/sid has 1.1.1k. Let's merge!

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



From 1939918 at bugs.launchpad.net  Sat Aug 14 00:24:14 2021
From: 1939918 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 14 Aug 2021 00:24:14 -0000
Subject: [Bug 1939918] [NEW] FTBFS against glibc 2.34
References: <162888353293.31443.7107257617651384274.malonedeb@wampee.canonical.com>
Message-ID: <162890065514.15385.2880869256316404814.launchpad@gac.canonical.com>

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

The package libnss-db failed to build in a recent archive rebuild, see
https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#foundations-bugs .

** Affects: libnss-db (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: fr-1583 patch
-- 
FTBFS against glibc 2.34
https://bugs.launchpad.net/bugs/1939918
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1939918 at bugs.launchpad.net  Sat Aug 14 00:24:15 2021
From: 1939918 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Sat, 14 Aug 2021 00:24:15 -0000
Subject: [Bug 1939918] Re: FTBFS against glibc 2.34
References: <162888353293.31443.7107257617651384274.malonedeb@wampee.canonical.com>
Message-ID: <162890065563.23558.2255053003501996932.malone@soybean.canonical.com>

The attachment "libnss-
db-1_2.2.3pre1-6build8.1.1_2.2.3pre1-6ubuntu1.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/1939918

Title:
  FTBFS against glibc 2.34

Status in libnss-db package in Ubuntu:
  New

Bug description:
  The package libnss-db failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-db/+bug/1939918/+subscriptions



From 1879923 at bugs.launchpad.net  Sun Aug 15 12:26:44 2021
From: 1879923 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 15 Aug 2021 12:26:44 -0000
Subject: [Bug 1879923] [NEW] Update Scan Data Over Internet fails
References: <159005701176.1272.4566518412318297427.malonedeb@chaenomeles.canonical.com>
Message-ID: <162903040462.10332.7417362661230972597.launchpad@chaenomeles.canonical.com>

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

Workaround from Tj; 3 commands (ignore word-wrapping by launchpad):

cd ~/.local/share/kaffeine
mv scanfile.dvb{,.$(awk 'C==1{print;exit}/^\[date\]/{C=1}' scanfile.dvb)}
wget https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/scantable.dvb -O scanfile.dvb

----


Running Kaffeine 2.0.18 on Ubuntu 20.04 LTS Plasma Desktop.  Update Scan Data Over Internet fails with message: Scan data update failed

I believe Kaffeine is looking for a file called scanfile.dvb or perhaps
scanfile.dvb.qz

https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/ shows a file
called scantable.dvb  (Different file name)

The wiki here (https://linuxtv.org/wiki/index.php/Dtv-scan-tables) says
that this file will be autocreated and eventually be located here:
https://autoconfig.kde.org/kaffeine/  The file i see at  this location
is currently called: scantable.dvb.qz

Perhaps this is just a file naming issue?

Thanks,

Iestyn Guest

** Affects: kaffeine
     Importance: Unknown
         Status: Unknown

** Affects: kaffeine (Ubuntu)
     Importance: Undecided
     Assignee: TJ (tj)
         Status: In Progress


** Tags: patch
-- 
Update Scan Data Over Internet fails
https://bugs.launchpad.net/bugs/1879923
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1879923 at bugs.launchpad.net  Sun Aug 15 12:26:44 2021
From: 1879923 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Sun, 15 Aug 2021 12:26:44 -0000
Subject: [Bug 1879923] Re: Update Scan Data Over Internet fails
References: <159005701176.1272.4566518412318297427.malonedeb@chaenomeles.canonical.com>
Message-ID: <162903040500.9928.21558665889811735.malone@gac.canonical.com>

The attachment "Update for focal 20.04" 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/1879923

Title:
  Update Scan Data Over Internet fails

Status in Kaffeine:
  Unknown
Status in kaffeine package in Ubuntu:
  In Progress

Bug description:
  Workaround from Tj; 3 commands (ignore word-wrapping by launchpad):

  cd ~/.local/share/kaffeine
  mv scanfile.dvb{,.$(awk 'C==1{print;exit}/^\[date\]/{C=1}' scanfile.dvb)}
  wget https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/scantable.dvb -O scanfile.dvb

  ----

  
  Running Kaffeine 2.0.18 on Ubuntu 20.04 LTS Plasma Desktop.  Update Scan Data Over Internet fails with message: Scan data update failed

  I believe Kaffeine is looking for a file called scanfile.dvb or
  perhaps scanfile.dvb.qz

  https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/ shows a file
  called scantable.dvb  (Different file name)

  The wiki here (https://linuxtv.org/wiki/index.php/Dtv-scan-tables)
  says that this file will be autocreated and eventually be located
  here: https://autoconfig.kde.org/kaffeine/  The file i see at  this
  location is currently called: scantable.dvb.qz

  Perhaps this is just a file naming issue?

  Thanks,

  Iestyn Guest

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



From 1875414 at bugs.launchpad.net  Sun Aug 15 20:31:29 2021
From: 1875414 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 15 Aug 2021 20:31:29 -0000
Subject: [Bug 1875414] [NEW] Wrong liquidsoap installation, libs are missed
References: <158799904147.26865.5895844944654784320.malonedeb@wampee.canonical.com>
Message-ID: <162905948932.14001.14165387703803034663.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Kyle Robbertze (krobbertze):

[Impact]

The package ships the pervasive libraries /usr/share/liquidsoap/libs,
while liquidsoap searches for them in /usr/share/liquidsoap/1.4.1/libs.
These libraries are used to implement much of the built-in modules used
within liquidsoap scripts. The fix here would fix scripts using these
pervasive libraries. The fix has been working in Debian unstable and
testing without issue.

[Test Plan]

Here is a short script to replicate it:
  #!/usr/bin/liquidsoap --check
  stream = playlist("")
  source = output.icecast(%mp3, host="localhost", port=8000, mount="listen.m3u", password="hackme")
  mksafe(source(mksafe(stream)))

Then ran the check against the liq file:
  liquidsoap --check ./radio.liq

This should terminate successfully. If the libs are not in the correct
position, this command will error out.

[Where problems could occur]

This patch creates a symlink, which could cause issues if the user has
used the workaround described below. Liquidsoap searches for the libs in
a subdirectory of /usr/share/liquidsoap that corresponds with the
version of the package, so for Ubuntu 20.04, this should be 1.4.1. An
incorrect symlink would result in no-change of the status-quo

-------------------------------
Original Bug report
-------------------------------

Could not use several script commands in liquidsoap, because liquidsoap
could not find several .liq - files.

Following

sudo mkdir /usr/share/liquidsoap/1.4.1
sudo ln -s /usr/share/liquidsoap/libs /usr/share/liquidsoap/1.4.1/

fixed it, like described here: https://github.com/radiorabe/centos-rpm-
liquidsoap/issues/3

** Affects: liquidsoap (Ubuntu)
     Importance: Undecided
         Status: Fix Released

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


From 1940036 at bugs.launchpad.net  Mon Aug 16 07:37:11 2021
From: 1940036 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 16 Aug 2021 07:37:11 -0000
Subject: [Bug 1940036] [NEW] Sync exuberant-ctags 1:5.9~svn20110310-15 (main)
 from Debian unstable (main)
References: <162909942680.4682.8995020702609541028.malonedeb@wampee.canonical.com>
Message-ID: <162909943180.11470.4413879092804910609.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Please sync exuberant-ctags 1:5.9~svn20110310-15 (main) from Debian
unstable (main)

Changelog entries since current impish version
1:5.9~svn20110310-14build1:

exuberant-ctags (1:5.9~svn20110310-15) unstable; urgency=medium

  [ Simon Chopin ]
  * d/p/use-conventional-unused-marker.patch: Fix FTBFS against glibc 2.34

 -- Colin Watson <cjwatson at debian.org>  Fri, 13 Aug 2021 17:12:44 +0100

** Affects: exuberant-ctags (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync exuberant-ctags 1:5.9~svn20110310-15 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1940036
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940036 at bugs.launchpad.net  Mon Aug 16 07:41:33 2021
From: 1940036 at bugs.launchpad.net (Graham Inggs)
Date: Mon, 16 Aug 2021 07:41:33 -0000
Subject: [Bug 1940036] Re: Sync exuberant-ctags 1:5.9~svn20110310-15 (main)
 from Debian unstable (main)
References: <162909942680.4682.8995020702609541028.malonedeb@wampee.canonical.com>
Message-ID: <162909969333.5351.10720483935223208713.malone@wampee.canonical.com>

This bug was fixed in the package exuberant-ctags - 1:5.9~svn20110310-15
Sponsored for Simon Chopin (schopin)

---------------
exuberant-ctags (1:5.9~svn20110310-15) unstable; urgency=medium

  [ Simon Chopin ]
  * d/p/use-conventional-unused-marker.patch: Fix FTBFS against glibc 2.34

 -- Colin Watson <cjwatson at debian.org>  Fri, 13 Aug 2021 17:12:44 +0100

** Changed in: exuberant-ctags (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/1940036

Title:
  Sync exuberant-ctags 1:5.9~svn20110310-15 (main) from Debian unstable
  (main)

Status in exuberant-ctags package in Ubuntu:
  Fix Released

Bug description:
  Please sync exuberant-ctags 1:5.9~svn20110310-15 (main) from Debian
  unstable (main)

  Changelog entries since current impish version
  1:5.9~svn20110310-14build1:

  exuberant-ctags (1:5.9~svn20110310-15) unstable; urgency=medium

    [ Simon Chopin ]
    * d/p/use-conventional-unused-marker.patch: Fix FTBFS against glibc 2.34

   -- Colin Watson <cjwatson at debian.org>  Fri, 13 Aug 2021 17:12:44
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exuberant-ctags/+bug/1940036/+subscriptions



From 1931987 at bugs.launchpad.net  Mon Aug 16 08:49:02 2021
From: 1931987 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 16 Aug 2021 08:49:02 -0000
Subject: [Bug 1931987] Re: [SRU] Creating FIT images is not supported
References: <162374651866.11595.13047179558275551809.malonedeb@soybean.canonical.com>
Message-ID: <162910374218.32507.796196256156237173.malone@chaenomeles.canonical.com>

I think the ageing we got on hirsute is enough of a verification on
hirsute.

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

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

Title:
  [SRU] Creating FIT images is not supported

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Focal:
  Fix Released
Status in flash-kernel source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  flash-kernel does currently not support creating FIT images. There are
  some platforms where this is preferred, for instance for the Kria SOM
  platform.

  This have been just fixed in flash-kernel 3.104ubuntu4 in impish (dev)
  (LP: #1931278), and we would like this ported back to hirsute/focal to
  support Kria SOM platform in focal.

  [Test Plan]

  For testing, a Kria SOM device is needed. By install flash-kernel with
  the fix, a file in path /boot/firmware/image.fit will be created, and
  the system should be able to boot.

  [Where problems could occur]

  The change adds new functionality which should not interfere with the
  previous one. However, there is some small potential for a regression
  happening. If that is the case, some hardware platforms that use
  flash-kernel might not be able to update the bootloader or will break
  it, making the system unable to boot.

  [Other Info]

  See LP: #1931278

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



From 1931987 at bugs.launchpad.net  Mon Aug 16 08:49:27 2021
From: 1931987 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 16 Aug 2021 08:49:27 -0000
Subject: [Bug 1931987] Update Released
References: <162374651866.11595.13047179558275551809.malonedeb@soybean.canonical.com>
Message-ID: <162910376800.2515.13181006321840788704.malone@chaenomeles.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/1931987

Title:
  [SRU] Creating FIT images is not supported

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Focal:
  Fix Released
Status in flash-kernel source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  flash-kernel does currently not support creating FIT images. There are
  some platforms where this is preferred, for instance for the Kria SOM
  platform.

  This have been just fixed in flash-kernel 3.104ubuntu4 in impish (dev)
  (LP: #1931278), and we would like this ported back to hirsute/focal to
  support Kria SOM platform in focal.

  [Test Plan]

  For testing, a Kria SOM device is needed. By install flash-kernel with
  the fix, a file in path /boot/firmware/image.fit will be created, and
  the system should be able to boot.

  [Where problems could occur]

  The change adds new functionality which should not interfere with the
  previous one. However, there is some small potential for a regression
  happening. If that is the case, some hardware platforms that use
  flash-kernel might not be able to update the bootloader or will break
  it, making the system unable to boot.

  [Other Info]

  See LP: #1931278

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



From 1931987 at bugs.launchpad.net  Mon Aug 16 08:49:56 2021
From: 1931987 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 16 Aug 2021 08:49:56 -0000
Subject: [Bug 1931987] Re: [SRU] Creating FIT images is not supported
References: <162374651866.11595.13047179558275551809.malonedeb@soybean.canonical.com>
Message-ID: <162910379850.13734.10309450137367553156.malone@ackee.canonical.com>

This bug was fixed in the package flash-kernel - 3.103ubuntu1~20.04.3

---------------
flash-kernel (3.103ubuntu1~20.04.3) focal; urgency=medium

  * Backport from 3.104ubuntu4 (LP: #1931987):
    * Add support for FIT images
      - Support for ITS files
      - New Boot-FIT-Path and Boot-ITS-File-Name DB fields
    * Add Xilinx Kria SOM and ZCU10{2,4,6} boards to the devices database

 -- Alfonso Sanchez-Beato (email Canonical) <alfonso.sanchez-
beato at canonical.com>  Fri, 30 Jul 2021 09:46:25 +0200

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

** Changed in: flash-kernel (Ubuntu Hirsute)
       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/1931987

Title:
  [SRU] Creating FIT images is not supported

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Focal:
  Fix Released
Status in flash-kernel source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  flash-kernel does currently not support creating FIT images. There are
  some platforms where this is preferred, for instance for the Kria SOM
  platform.

  This have been just fixed in flash-kernel 3.104ubuntu4 in impish (dev)
  (LP: #1931278), and we would like this ported back to hirsute/focal to
  support Kria SOM platform in focal.

  [Test Plan]

  For testing, a Kria SOM device is needed. By install flash-kernel with
  the fix, a file in path /boot/firmware/image.fit will be created, and
  the system should be able to boot.

  [Where problems could occur]

  The change adds new functionality which should not interfere with the
  previous one. However, there is some small potential for a regression
  happening. If that is the case, some hardware platforms that use
  flash-kernel might not be able to update the bootloader or will break
  it, making the system unable to boot.

  [Other Info]

  See LP: #1931278

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



From 1931987 at bugs.launchpad.net  Mon Aug 16 08:51:28 2021
From: 1931987 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 16 Aug 2021 08:51:28 -0000
Subject: [Bug 1931987] Re: [SRU] Creating FIT images is not supported
References: <162374651866.11595.13047179558275551809.malonedeb@soybean.canonical.com>
Message-ID: <162910389122.13739.9586881486307438536.malone@ackee.canonical.com>

This bug was fixed in the package flash-kernel - 3.104ubuntu4~21.04

---------------
flash-kernel (3.104ubuntu4~21.04) hirsute; urgency=medium

  * Backport from 3.104ubuntu4 (LP: #1931987)
    * Add support for FIT images
      - Support for ITS files
      - New Boot-FIT-Path and Boot-ITS-File-Name DB fields
    * Add Xilinx Kria SOM and ZCU10{2,4,6} boards to the devices database

 -- Alfonso Sanchez-Beato (email Canonical) <alfonso.sanchez-
beato at canonical.com>  Tue, 15 Jun 2021 10:51:59 +0200

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

Title:
  [SRU] Creating FIT images is not supported

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Focal:
  Fix Released
Status in flash-kernel source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  flash-kernel does currently not support creating FIT images. There are
  some platforms where this is preferred, for instance for the Kria SOM
  platform.

  This have been just fixed in flash-kernel 3.104ubuntu4 in impish (dev)
  (LP: #1931278), and we would like this ported back to hirsute/focal to
  support Kria SOM platform in focal.

  [Test Plan]

  For testing, a Kria SOM device is needed. By install flash-kernel with
  the fix, a file in path /boot/firmware/image.fit will be created, and
  the system should be able to boot.

  [Where problems could occur]

  The change adds new functionality which should not interfere with the
  previous one. However, there is some small potential for a regression
  happening. If that is the case, some hardware platforms that use
  flash-kernel might not be able to update the bootloader or will break
  it, making the system unable to boot.

  [Other Info]

  See LP: #1931278

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



From 1939409 at bugs.launchpad.net  Mon Aug 16 09:39:04 2021
From: 1939409 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Mon, 16 Aug 2021 09:39:04 -0000
Subject: [Bug 1939409] Re: merge e2fsprogs 1.46.3-1 from Debian: s390x fails
 in test f_baddotdir
References: <162860191203.23963.14834301011076203546.malonedeb@soybean.canonical.com>
Message-ID: <162910674512.9560.5443882031668564425.launchpad@soybean.canonical.com>

** Changed in: e2fsprogs (Ubuntu)
       Status: New => 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/1939409

Title:
  merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir

Status in e2fsprogs package in Ubuntu:
  In Progress

Bug description:
  e2fsprogs 1.46.3-1ubuntu1 is in proposed.

  Architecture s390x fail in test f_baddotdir. The test image was
  changed with the new release.

  Next step should be analyzing the error on a s390x virtual machine.

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



From 1939409 at bugs.launchpad.net  Mon Aug 16 09:55:33 2021
From: 1939409 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Mon, 16 Aug 2021 09:55:33 -0000
Subject: [Bug 1939409] Re: merge e2fsprogs 1.46.3-1 from Debian: s390x fails
 in test f_baddotdir
References: <162860191203.23963.14834301011076203546.malonedeb@soybean.canonical.com>
Message-ID: <162910773361.5014.8405893605114229566.malone@wampee.canonical.com>

Thank you for providing & integrating the patches. LGTM!

$ dput ubuntu ../e2fsprogs_1.46.3-1ubuntu2_source.changes
Checking signature on .changes
gpg: ../e2fsprogs_1.46.3-1ubuntu2_source.changes: Valid signature from 5889C17AB1C8D890
Checking signature on .dsc
gpg: ../e2fsprogs_1.46.3-1ubuntu2.dsc: Valid signature from 5889C17AB1C8D890
Uploading to ubuntu (via sftp to upload.ubuntu.com):
  Uploading e2fsprogs_1.46.3-1ubuntu2.dsc: done.
  Uploading e2fsprogs_1.46.3-1ubuntu2.debian.tar.xz: done.  
  Uploading e2fsprogs_1.46.3-1ubuntu2_source.buildinfo: done.
  Uploading e2fsprogs_1.46.3-1ubuntu2_source.changes: done.
Successfully uploaded packages.

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

Title:
  merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir

Status in e2fsprogs package in Ubuntu:
  In Progress

Bug description:
  e2fsprogs 1.46.3-1ubuntu1 is in proposed.

  Architecture s390x fail in test f_baddotdir. The test image was
  changed with the new release.

  Next step should be analyzing the error on a s390x virtual machine.

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



From 1939918 at bugs.launchpad.net  Mon Aug 16 13:15:39 2021
From: 1939918 at bugs.launchpad.net (Dan Bungert)
Date: Mon, 16 Aug 2021 13:15:39 -0000
Subject: [Bug 1939918] Re: FTBFS against glibc 2.34
References: <162888353293.31443.7107257617651384274.malonedeb@wampee.canonical.com>
Message-ID: <162911973980.24215.15054003793252101787.launchpad@gac.canonical.com>

** Tags removed: 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/1939918

Title:
  FTBFS against glibc 2.34

Status in libnss-db package in Ubuntu:
  New

Bug description:
  The package libnss-db failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-db/+bug/1939918/+subscriptions



From 1940123 at bugs.launchpad.net  Mon Aug 16 16:21:51 2021
From: 1940123 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 16 Aug 2021 16:21:51 -0000
Subject: [Bug 1940123] [NEW] Autopkgtest fail for 1.0.2.1~ds-1
References: <162913089482.4563.12588944250490121289.malonedeb@wampee.canonical.com>
Message-ID: <162913091122.16525.10827158141534721779.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

ALl tests fail, because of a missing dependency on git-mercurial.

Fixed in the Debian Salsa repository but the fix hasn't been uploaded to
Debian yet, so attached is a debdiff porting it as an Ubuntu diff, so
that we can get 1.0.2.1 in before the feature freeze.

** Affects: git-remote-hg (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Autopkgtest fail for 1.0.2.1~ds-1
https://bugs.launchpad.net/bugs/1940123
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1912168 at bugs.launchpad.net  Mon Aug 16 20:22:44 2021
From: 1912168 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 16 Aug 2021 20:22:44 -0000
Subject: [Bug 1912168] [NEW] please merge ppp 2.4.9 for 21.04 and then
 consider ipv6 default fix for SRU
References: <161095854683.30278.15024416028507416039.malonedeb@chaenomeles.canonical.com>
Message-ID: <162914536444.24655.7923552128485063247.launchpad@gac.canonical.com>

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

Hi,
due to this ML on devel-discuss [1] I realized that there is a new version that should be merged for Ubuntu 21.04 - and probably later [2] be considered/discussed for an SRU
That new version is in Debian now [3] and I think it would be great to get that merged/synced.

I guess ppp might be out-of-focus today, therefore per [4] I'm also
pinging the Desktop team hoping this will help to get a look at it.

[1]: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2021-January/018916.html
[2]: https://github.com/paulusmack/ppp/pull/145/commits/0678d3bf69116af58b00fbc64bd4185acb4d5c37
[3]: https://tracker.debian.org/news/1217613/ppp-249-11-migrated-to-testing/
[4]: http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html

** Affects: ppp (Ubuntu)
     Importance: Low
         Status: Triaged


** Tags: patch rls-hh-notfixing
-- 
please merge ppp 2.4.9 for 21.04 and then consider ipv6 default fix for SRU
https://bugs.launchpad.net/bugs/1912168
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940141 at bugs.launchpad.net  Mon Aug 16 20:23:15 2021
From: 1940141 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 16 Aug 2021 20:23:15 -0000
Subject: [Bug 1940141] [NEW] OpenSSL servers can send a non-empty
 status_request in a CertificateRequest
References: <162914012164.16193.1962205616306104875.malonedeb@soybean.canonical.com>
Message-ID: <162914539614.2861.1048299866944559967.launchpad@chaenomeles.canonical.com>

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

[Impact]

openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
CertificateRequest message to the client with a non-empty
status_request extension.

This issue was fixed in openssl-1.1.1d and is included in Focal
onward.

Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
Upstream patch review at https://github.com/openssl/openssl/pull/9780

[Test Plan]

The issue can be reproduced by building with `enable-ssl-trace`
and then running `s_server` like this:

```
openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5
```

And running `s_client` like this:

```
openssl s_client -status -trace -cert cert.pem -key key.pem
```

The output shows a `status_request` extension in the
`CertificateRequest` as follows:

Received Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 1591
  Inner Content Type = Handshake (22)
    CertificateRequest, Length=1570
      request_context (len=0):
      extensions, length = 1567
        extension_type=status_request(5), length=1521
          0000 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   ....0..........
          000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   0.....+.....0..
          001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   ....0...0......
          002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   0..1.0...U....G
...more lines omitted...

If the `status_request` extension is present in a
`CertificateRequest` then it must be empty according to RFC8446,
Sec. 4.4.2.1.

[Where problems could occur]

The patch disables the `status_request` extension inside a
`CertificateRequest`. Applications expecting the incorrect,
non-empty reply for the `status_request` extension will break
with this patch. As a non-empty reply is incorrect behavior

** Affects: openssl (Ubuntu)
     Importance: Undecided
     Assignee: Nicolas Bock (nicolasbock)
         Status: New

** Affects: openssl (Ubuntu Bionic)
     Importance: Undecided
     Assignee: Nicolas Bock (nicolasbock)
         Status: New


** Tags: patch
-- 
OpenSSL servers can send a non-empty status_request in a CertificateRequest
https://bugs.launchpad.net/bugs/1940141
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940141 at bugs.launchpad.net  Mon Aug 16 20:23:16 2021
From: 1940141 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Mon, 16 Aug 2021 20:23:16 -0000
Subject: [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request
 in a CertificateRequest
References: <162914012164.16193.1962205616306104875.malonedeb@soybean.canonical.com>
Message-ID: <162914539648.3578.8010731349280304872.malone@soybean.canonical.com>

The attachment "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/1940141

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
      CertificateRequest, Length=1570
        request_context (len=0):
        extensions, length = 1567
          extension_type=status_request(5), length=1521
            0000 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   ....0..........
            000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   0.....+.....0..
            001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   ....0...0......
            002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   0..1.0...U....G
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch. As a non-empty reply is incorrect behavior

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



From 1912168 at bugs.launchpad.net  Mon Aug 16 20:22:44 2021
From: 1912168 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Mon, 16 Aug 2021 20:22:44 -0000
Subject: [Bug 1912168] Re: please merge ppp 2.4.9 for 21.04 and then consider
 ipv6 default fix for SRU
References: <161095854683.30278.15024416028507416039.malonedeb@chaenomeles.canonical.com>
Message-ID: <162914536480.2189.9004969444485678228.malone@chaenomeles.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/1912168

Title:
  please merge ppp 2.4.9 for 21.04 and then consider ipv6 default fix
  for SRU

Status in ppp package in Ubuntu:
  Triaged

Bug description:
  Hi,
  due to this ML on devel-discuss [1] I realized that there is a new version that should be merged for Ubuntu 21.04 - and probably later [2] be considered/discussed for an SRU
  That new version is in Debian now [3] and I think it would be great to get that merged/synced.

  I guess ppp might be out-of-focus today, therefore per [4] I'm also
  pinging the Desktop team hoping this will help to get a look at it.

  [1]: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2021-January/018916.html
  [2]: https://github.com/paulusmack/ppp/pull/145/commits/0678d3bf69116af58b00fbc64bd4185acb4d5c37
  [3]: https://tracker.debian.org/news/1217613/ppp-249-11-migrated-to-testing/
  [4]: http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html

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



From 1940153 at bugs.launchpad.net  Mon Aug 16 22:01:21 2021
From: 1940153 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 16 Aug 2021 22:01:21 -0000
Subject: [Bug 1940153] [NEW] Sync intel-ipsec-mb 1.0-1 (universe) from Debian
 unstable (main)
References: <162915127626.12948.11573510597290358415.malonedeb@gac.canonical.com>
Message-ID: <162915128179.25268.1859860975440712131.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Colin Ian King (colin-king):

Please sync intel-ipsec-mb 1.0-1 (universe) from Debian unstable (main)

Changelog entries since current impish version 0.55-1:

intel-ipsec-mb (1.0-1) unstable; urgency=medium

  * Sync to latest 1.0 release
  * Rename libipsec-mb0 to libipsec-mb1
  * Remove debian/watch as the upstream project is not serving tarballs now
  * Add note about elf debug optimization being disabled in rules
  * Add back the Uploaders field in the control file

 -- Colin Ian King <colin.king at canonical.com>  Fri, 7 May 2021 09:11:47
+0100

** Affects: intel-ipsec-mb (Ubuntu)
     Importance: Wishlist
         Status: New

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


From 1930776 at bugs.launchpad.net  Mon Aug 16 23:16:50 2021
From: 1930776 at bugs.launchpad.net (Michael Hudson-Doyle)
Date: Mon, 16 Aug 2021 23:16:50 -0000
Subject: [Bug 1930776] Re: failing test with golang 1.16
References: <162276758670.7584.1197523821980443282.malonedeb@wampee.canonical.com>
Message-ID: <162915581055.6263.9622178912321571817.malone@chaenomeles.canonical.com>

sponsored

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

Title:
  failing test with golang 1.16

Status in golang-github-nicksnyder-go-i18n.v2 package in Ubuntu:
  Fix Committed
Status in golang-github-nicksnyder-go-i18n.v2 package in Debian:
  New

Bug description:
  Running tests with golang 1.16 results in the following test failure:

  === RUN   TestExecute/hello_{{
      template_test.go:57: expected err "template: :1: unexpected unclosed action in command"; got "template: :1: unclosed action"
  --- FAIL: TestExecute (0.00s)

  
  I have reported this upstream.
  https://github.com/nicksnyder/go-i18n/issues/259

  A fix is reasonably straightforward - one could just check that error
  is non-nil for example, instead of worrying about the exact error
  text.  Or one could check that "unclosed action" is part of the error
  substring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n.v2/+bug/1930776/+subscriptions



From 1930772 at bugs.launchpad.net  Mon Aug 16 23:18:41 2021
From: 1930772 at bugs.launchpad.net (Michael Hudson-Doyle)
Date: Mon, 16 Aug 2021 23:18:41 -0000
Subject: [Bug 1930772] Re: currently FTBFS due to TestTLSConfig
References: <162276556236.6736.8193428372429412761.malonedeb@wampee.canonical.com>
Message-ID: <162915592158.27946.7063408141446629748.malone@gac.canonical.com>

sponsored

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

Title:
  currently FTBFS due to TestTLSConfig

Status in golang-github-prometheus-common package in Ubuntu:
  Fix Committed
Status in golang-github-prometheus-common package in Debian:
  New

Bug description:
  golang-github-prometheus-common package currently FTBFS due to
  TestTLSConfig

  === RUN   TestTLSConfig
  http_config_test.go:519: Unexpected TLS Config result:

  [...]
  RootCAs:0xc00011d470
  [...]
           expected                                                                                                                    
  [...]
  RootCAs:0xc00011cf30
  [...]
  -- FAIL: TestTLSConfig (0.00s) 

  This is reported upstream at https://github.com/prometheus/common/issues/267
  This is also already fixed in commit 10e1378a4a94394e5671c529b7d87833c2b70d13

  This also appears to be related to go 1.16 - previous versions of go appear to                                                       not trigger the issue (or so I infer from the upstream bug report).                                                                  
                                                                                                                                       
  Filing the bug largely to track this as a known issue and mark it in the                                                             
  update-excuses report.  Should be resolved when a new version is uploaded, or                                                        
  the above fix could be cherry-picked if someone is so inclined.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-prometheus-common/+bug/1930772/+subscriptions



From 1936664 at bugs.launchpad.net  Tue Aug 17 08:49:47 2021
From: 1936664 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Tue, 17 Aug 2021 08:49:47 -0000
Subject: [Bug 1936664] Re: buildmode=c-shared not supported on linux/risc-v
References: <162644431906.27897.7005500802674012219.malonedeb@wampee.canonical.com>
Message-ID: <162919018801.30673.4463258819926160309.malone@soybean.canonical.com>

@mhodson:
Why did you set this to importance wishlist? Other packages cannot be built due to this deficiency. E.g. gnome-initial-setup.

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

Title:
  buildmode=c-shared not supported on linux/risc-v

Status in golang-1.16 package in Ubuntu:
  New

Bug description:
  In order to build ubuntu-report and eventual desktop images for
  risc-v, golang needs to support buildmode=c-shared on linux/risc-v. We
  have submitted the change upstream, and will need to carry a delta
  until it lands in debian.

  See https://github.com/golang/go/issues/47100 for upstream work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.16/+bug/1936664/+subscriptions



From 1932010 at bugs.launchpad.net  Tue Aug 17 09:10:41 2021
From: 1932010 at bugs.launchpad.net (Frank Heimes)
Date: Tue, 17 Aug 2021 09:10:41 -0000
Subject: [Bug 1932010] Re: [21.10 FEAT] zlib CRC32 optimization for s390x
References: <162375656462.17686.8090271452944134348.malonedeb@gac.canonical.com>
Message-ID: <162919144114.17133.3907263375134838363.malone@gac.canonical.com>

Since the updated package version arrived in impish-proposed:
 zlib | 1:1.2.11.dfsg-2ubuntu7   | impish-proposed | source
I'm updating the status to Fix Committed.

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

** Changed in: ubuntu-z-systems
       Status: In Progress => 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/1932010

Title:
  [21.10 FEAT] zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zlib package in Ubuntu:
  Fix Committed

Bug description:
  Use SIMD instructions to accelerate the zlib CRC32 implementation.
  Business value: Performance improvement in database area

  The zlib CRC32 optimization for IBM Z is currently being discussed for inclusion into zlib-ng:
  https://github.com/zlib-ng/zlib-ng/pull/912

  The patch for zlib will be based on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932010/+subscriptions



From 1930776 at bugs.launchpad.net  Tue Aug 17 09:11:34 2021
From: 1930776 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 17 Aug 2021 09:11:34 -0000
Subject: [Bug 1930776] Re: failing test with golang 1.16
References: <162276758670.7584.1197523821980443282.malonedeb@wampee.canonical.com>
Message-ID: <162919149638.19253.2460639682115214657.malone@ackee.canonical.com>

This bug was fixed in the package golang-github-nicksnyder-go-i18n.v2 -
2.1.1-2ubuntu1

---------------
golang-github-nicksnyder-go-i18n.v2 (2.1.1-2ubuntu1) impish; urgency=medium

  * Update test case to work with golang-1.16 and golang-1.15 (LP:
#1930776)

 -- William 'jawn-smith' Wilson <william.wilson at canonical.com>  Wed, 23
Jun 2021 14:50:37 +0000

** Changed in: golang-github-nicksnyder-go-i18n.v2 (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/1930776

Title:
  failing test with golang 1.16

Status in golang-github-nicksnyder-go-i18n.v2 package in Ubuntu:
  Fix Released
Status in golang-github-nicksnyder-go-i18n.v2 package in Debian:
  New

Bug description:
  Running tests with golang 1.16 results in the following test failure:

  === RUN   TestExecute/hello_{{
      template_test.go:57: expected err "template: :1: unexpected unclosed action in command"; got "template: :1: unclosed action"
  --- FAIL: TestExecute (0.00s)

  
  I have reported this upstream.
  https://github.com/nicksnyder/go-i18n/issues/259

  A fix is reasonably straightforward - one could just check that error
  is non-nil for example, instead of worrying about the exact error
  text.  Or one could check that "unclosed action" is part of the error
  substring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n.v2/+bug/1930776/+subscriptions



From 1930772 at bugs.launchpad.net  Tue Aug 17 09:11:28 2021
From: 1930772 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 17 Aug 2021 09:11:28 -0000
Subject: [Bug 1930772] Re: currently FTBFS due to TestTLSConfig
References: <162276556236.6736.8193428372429412761.malonedeb@wampee.canonical.com>
Message-ID: <162919149006.19263.14279102222728378829.malone@ackee.canonical.com>

This bug was fixed in the package golang-github-prometheus-common -
0.15.0-2ubuntu1

---------------
golang-github-prometheus-common (0.15.0-2ubuntu1) impish; urgency=medium

  * Cherry pick code from upstream to fix an issue with RootCA comparison. As
    of go 1.16 these RootCAs will never be equal, so we just compare the
    subjects instead of the entire value. (LP: #1930772)

 -- William 'jawn-smith' Wilson <william.wilson at canonical.com>  Wed, 23
Jun 2021 17:25:06 +0000

** Changed in: golang-github-prometheus-common (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/1930772

Title:
  currently FTBFS due to TestTLSConfig

Status in golang-github-prometheus-common package in Ubuntu:
  Fix Released
Status in golang-github-prometheus-common package in Debian:
  New

Bug description:
  golang-github-prometheus-common package currently FTBFS due to
  TestTLSConfig

  === RUN   TestTLSConfig
  http_config_test.go:519: Unexpected TLS Config result:

  [...]
  RootCAs:0xc00011d470
  [...]
           expected                                                                                                                    
  [...]
  RootCAs:0xc00011cf30
  [...]
  -- FAIL: TestTLSConfig (0.00s) 

  This is reported upstream at https://github.com/prometheus/common/issues/267
  This is also already fixed in commit 10e1378a4a94394e5671c529b7d87833c2b70d13

  This also appears to be related to go 1.16 - previous versions of go appear to                                                       not trigger the issue (or so I infer from the upstream bug report).                                                                  
                                                                                                                                       
  Filing the bug largely to track this as a known issue and mark it in the                                                             
  update-excuses report.  Should be resolved when a new version is uploaded, or                                                        
  the above fix could be cherry-picked if someone is so inclined.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-prometheus-common/+bug/1930772/+subscriptions



From 1875414 at bugs.launchpad.net  Tue Aug 17 10:48:01 2021
From: 1875414 at bugs.launchpad.net (Kyle Robbertze)
Date: Tue, 17 Aug 2021 10:48:01 -0000
Subject: [Bug 1875414] Re: Wrong liquidsoap installation, libs are missed
References: <158799904147.26865.5895844944654784320.malonedeb@wampee.canonical.com>
Message-ID: <162919728112.16377.3460049782602349821.malone@wampee.canonical.com>

Debdiff against 1.4.1-1build1

** Patch added: "debdiff.patch"
   https://bugs.launchpad.net/ubuntu/+source/liquidsoap/+bug/1875414/+attachment/5518500/+files/debdiff.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/1875414

Title:
  Wrong liquidsoap installation, libs are missed

Status in liquidsoap package in Ubuntu:
  Fix Released
Status in liquidsoap source package in Focal:
  New

Bug description:
  [Impact]

  The package ships the pervasive libraries /usr/share/liquidsoap/libs,
  while liquidsoap searches for them in
  /usr/share/liquidsoap/1.4.1/libs. These libraries are used to
  implement much of the built-in modules used within liquidsoap scripts.
  The fix here would fix scripts using these pervasive libraries. The
  fix has been working in Debian unstable and testing without issue.

  [Test Plan]

  Here is a short script to replicate it:
    #!/usr/bin/liquidsoap --check
    stream = playlist("")
    source = output.icecast(%mp3, host="localhost", port=8000, mount="listen.m3u", password="hackme")
    mksafe(source(mksafe(stream)))

  Then ran the check against the liq file:
    liquidsoap --check ./radio.liq

  This should terminate successfully. If the libs are not in the correct
  position, this command will error out.

  [Where problems could occur]

  This patch creates a symlink, which could cause issues if the user has
  used the workaround described below. Liquidsoap searches for the libs
  in a subdirectory of /usr/share/liquidsoap that corresponds with the
  version of the package, so for Ubuntu 20.04, this should be 1.4.1. An
  incorrect symlink would result in no-change of the status-quo

  -------------------------------
  Original Bug report
  -------------------------------

  Could not use several script commands in liquidsoap, because
  liquidsoap could not find several .liq - files.

  Following

  sudo mkdir /usr/share/liquidsoap/1.4.1
  sudo ln -s /usr/share/liquidsoap/libs /usr/share/liquidsoap/1.4.1/

  fixed it, like described here: https://github.com/radiorabe/centos-
  rpm-liquidsoap/issues/3

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



From 1939695 at bugs.launchpad.net  Tue Aug 17 15:00:12 2021
From: 1939695 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 17 Aug 2021 15:00:12 -0000
Subject: [Bug 1939695] Re: Please merge lshw-02.18.85-0.7 (main) from Debian
 unstable (main)
References: <162877474044.1463.14072735482186585689.malonedeb@gac.canonical.com>
Message-ID: <162921241331.18492.5412312263522793912.launchpad@chaenomeles.canonical.com>

** Changed in: lshw (Ubuntu)
       Status: New => 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/1939695

Title:
  Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

Status in lshw package in Ubuntu:
  In Progress

Bug description:
  Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)

  At the time of filling this bug, the target debian unstable version is
  02.18.85-0.7

  Remaining changes on ubuntu are
   - Cherry pick two patches from upstream to fix JSON formatting
     - 2b1c730b493d647bbab4854713571458e82a81e7.patch                            
     - 15565229509455527de9ce7cbb9530e2b31d043b.patch 
   - Cherry pick patches for NMVe support
     - d/p/lp1826737-code-clean-up.patch                                         
     - d/p/lp1826737-implement-NVMe-scanning.patch                               
     - d/p/lp1826737-align-physical-ID-with-NVMe-namespace.patch                 
     - d/p/lp1826737-treat-NVMe-namespaces-like-disks.patch

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



From 1940322 at bugs.launchpad.net  Tue Aug 17 20:24:11 2021
From: 1940322 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 17 Aug 2021 20:24:11 -0000
Subject: [Bug 1940322] [NEW] autopkgtest test_system_file_used_if_not_expired
 failing in impish
References: <162922784492.19949.3014232438045180282.malonedeb@chaenomeles.canonical.com>
Message-ID: <162923185129.31550.11938883005110932634.launchpad@wampee.canonical.com>

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

This autopkgtest is failing. It appears to be related to the weakened
"good_enough" expiration value set by a previous patch.

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


** Tags: patch
-- 
autopkgtest test_system_file_used_if_not_expired failing in impish
https://bugs.launchpad.net/bugs/1940322
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940322 at bugs.launchpad.net  Tue Aug 17 20:24:11 2021
From: 1940322 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Tue, 17 Aug 2021 20:24:11 -0000
Subject: [Bug 1940322] Re: autopkgtest test_system_file_used_if_not_expired
 failing in impish
References: <162922784492.19949.3014232438045180282.malonedeb@chaenomeles.canonical.com>
Message-ID: <162923185176.1739.1044472565776270762.malone@chaenomeles.canonical.com>

The attachment "lp1940322.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/1940322

Title:
  autopkgtest test_system_file_used_if_not_expired failing in impish

Status in astropy package in Ubuntu:
  New

Bug description:
  This autopkgtest is failing. It appears to be related to the weakened
  "good_enough" expiration value set by a previous patch.

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



From 1939544 at bugs.launchpad.net  Tue Aug 17 20:55:51 2021
From: 1939544 at bugs.launchpad.net (Brian Murray)
Date: Tue, 17 Aug 2021 20:55:51 -0000
Subject: [Bug 1939544] Re: Merge the 1.1.1k version from Debian
References: <162867821570.21991.16915484794970250733.malonedeb@gac.canonical.com>
Message-ID: <162923375232.16202.1173492680349904391.malone@soybean.canonical.com>

I'm unsubscribing the sponsors team given that this is in -proposed.

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

Title:
  Merge the 1.1.1k version from Debian

Status in openssl package in Ubuntu:
  Fix Committed

Bug description:
  Impish currently ships with a version based on the upstream 1.1.1j,
  while Debian bullseye/sid has 1.1.1k. Let's merge!

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



From 1938707 at bugs.launchpad.net  Tue Aug 17 21:03:37 2021
From: 1938707 at bugs.launchpad.net (Brian Murray)
Date: Tue, 17 Aug 2021 21:03:37 -0000
Subject: [Bug 1938707] Re: Sync sshguard 2.3.1-2 (universe) from Debian
 unstable (main)
References: <162791958678.2824.4847316839802775770.malonedeb@soybean.canonical.com>
Message-ID: <162923421757.29224.643643703024515742.malone@gac.canonical.com>

OK: sshguard_2.3.1-2.dsc                                                                                                                   
     -> Component: main Section: net                                                                                                        
 OK: sshguard_2.3.1.orig.tar.gz                                                                                                             
 OK: sshguard_2.3.1-2.debian.tar.xz                                                                                                         
                                                                                                                                            
Announcing to impish-changes at lists.ubuntu.com                                                                                               
                                                                                                                                            
Thank you for your contribution to Ubuntu.                                                                                                  
                                                       

** Changed in: sshguard (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/1938707

Title:
  Sync sshguard 2.3.1-2 (universe) from Debian unstable (main)

Status in sshguard package in Ubuntu:
  Fix Released

Bug description:
  Please sync sshguard 2.3.1-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Drop Ubuntu delta and use nftables
    * Drop Ubuntu delta and use nftables
    * Drop Ubuntu delta and use nftables
    * Fix path to iptables binaries in the .service unit. LP: #1884848
    * Revert to use iptables which is default in Ubuntu:
      - Revert "Use nft instead iptables"
      - Revert "Change firewall backend to nftables"
      - Revert "Remove iptables from Depends"
    * Revert to use iptables which is default in Ubuntu:
      - Revert "Use nft instead iptables"
      - Revert "Change firewall backend to nftables"
      - Revert "Remove iptables from Depends"

  
  Delta is effectively empty, newer version can be synced.

  Changelog entries since current impish version 2.3.1-1ubuntu3:

  sshguard (2.3.1-2) unstable; urgency=medium

    * Fix config file. (Closes: #928525)

   -- Julián Moreno Patiño <julian at debian.org>  Mon, 26 Jul 2021
  22:18:43 -0500

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



From 1940322 at bugs.launchpad.net  Wed Aug 18 00:01:04 2021
From: 1940322 at bugs.launchpad.net (William Wilson)
Date: Wed, 18 Aug 2021 00:01:04 -0000
Subject: [Bug 1940322] Re: autopkgtest test_system_file_used_if_not_expired
 failing in impish
References: <162922784492.19949.3014232438045180282.malonedeb@chaenomeles.canonical.com>
Message-ID: <162924486431.28764.5291167982213499168.malone@gac.canonical.com>

This patch adds the bug number to the changelog and includes an update-
maintainer

** Patch added: "Fixed changelog"
   https://bugs.launchpad.net/ubuntu/+source/astropy/+bug/1940322/+attachment/5518617/+files/lp1940322.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/1940322

Title:
  autopkgtest test_system_file_used_if_not_expired failing in impish

Status in astropy package in Ubuntu:
  New

Bug description:
  This autopkgtest is failing. It appears to be related to the weakened
  "good_enough" expiration value set by a previous patch.

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



From 1932555 at bugs.launchpad.net  Wed Aug 18 03:13:00 2021
From: 1932555 at bugs.launchpad.net (Yao Wei)
Date: Wed, 18 Aug 2021 03:13:00 -0000
Subject: [Bug 1932555] Re: [MIR] oem-somerville-bowen-meta
References: <162402726627.16821.4852855021194925587.malonedeb@gac.canonical.com>
Message-ID: <162925638086.17485.13778581455214061512.malone@wampee.canonical.com>

Change to In Progress for switching to HWE kernel

** Changed in: oem-priority
       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/1932555

Title:
  [MIR] oem-somerville-bowen-meta

Status in OEM Priority Project:
  In Progress
Status in Ubuntu:
  Confirmed

Bug description:
  [Background]

  Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and
  https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details.

  [Impact]

   1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive.
   2. The background and impact of the situation for this change, and it's impact.

  [Testing]

   1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware
   2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the  hardware
   3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly.

  [Regression Potential]

  Most potential regressions will live in the package set that will be
  installed via dependency of this package, which live in OEM archive
  (outside of Ubuntu) and control by OEM team. OEM team and other
  corresponding team need take responsibility of those dependency
  installed.

  [When switching kernel flavour] Check that the new kernel flavour
  works on the target platform.

  [Availability]
  This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet.
  The source code of the oem-somerville-bowen-meta for focal:
      git clone -b bowen-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta

  [Rationale]
  We want to improve the hardware support for some Dell platforms.

  [Security]
  No CVE/known security issue.

  [Quality assurance]
  I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms.
  oem-somerville-bowen-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive.

  [Dependencies]
  It only depends on ubuntu-oem-keyring.

  [Standards compliance]
  This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM.

  [Maintenance]
  Canonical OEM Enablement Team will take care of the maintenance.

  [Background information]
  Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details.

  Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to
  verify this MIR against the reference package in the archive.

  https://ubuntu.com/certified/202001-27708
  https://ubuntu.com/certified/202002-27718

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932555/+subscriptions



From 1940385 at bugs.launchpad.net  Wed Aug 18 07:15:21 2021
From: 1940385 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Aug 2021 07:15:21 -0000
Subject: [Bug 1940385] [NEW] Sync git-remote-hg 1.0.2.1~ds-2 (universe) from
 Debian unstable (main)
References: <162927091508.3993.18443319631792368039.malonedeb@chaenomeles.canonical.com>
Message-ID: <162927092223.522.11289739937148722635.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Please sync git-remote-hg 1.0.2.1~ds-2 (universe) from Debian unstable
(main)

Changelog entries since current impish version 1.0.2.1~ds-1:

git-remote-hg (1.0.2.1~ds-2) unstable; urgency=medium

  * QA upload.
  * Add missing mercurial-git test dependency (LP: #1940123)

 -- Paul Wise <pabs at debian.org>  Tue, 17 Aug 2021 20:36:22 +0800

** Affects: git-remote-hg (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync git-remote-hg 1.0.2.1~ds-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1940385
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940385 at bugs.launchpad.net  Wed Aug 18 07:28:32 2021
From: 1940385 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Wed, 18 Aug 2021 07:28:32 -0000
Subject: [Bug 1940385] Re: Sync git-remote-hg 1.0.2.1~ds-2 (universe) from
 Debian unstable (main)
References: <162927091508.3993.18443319631792368039.malonedeb@chaenomeles.canonical.com>
Message-ID: <162927171299.3993.12694612970051188245.malone@chaenomeles.canonical.com>

This bug was fixed in the package git-remote-hg - 1.0.2.1~ds-2
Sponsored for Simon Chopin (schopin)

---------------
git-remote-hg (1.0.2.1~ds-2) unstable; urgency=medium

  * QA upload.
  * Add missing mercurial-git test dependency (LP: #1940123)

 -- Paul Wise <pabs at debian.org>  Tue, 17 Aug 2021 20:36:22 +0800

** Changed in: git-remote-hg (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/1940385

Title:
  Sync git-remote-hg 1.0.2.1~ds-2 (universe) from Debian unstable (main)

Status in git-remote-hg package in Ubuntu:
  Fix Released

Bug description:
  Please sync git-remote-hg 1.0.2.1~ds-2 (universe) from Debian unstable
  (main)

  Changelog entries since current impish version 1.0.2.1~ds-1:

  git-remote-hg (1.0.2.1~ds-2) unstable; urgency=medium

    * QA upload.
    * Add missing mercurial-git test dependency (LP: #1940123)

   -- Paul Wise <pabs at debian.org>  Tue, 17 Aug 2021 20:36:22 +0800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git-remote-hg/+bug/1940385/+subscriptions



From 1940405 at bugs.launchpad.net  Wed Aug 18 09:39:57 2021
From: 1940405 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Aug 2021 09:39:57 -0000
Subject: [Bug 1940405] [NEW] Sync dh-python 4.20201102+nmu1 (universe) from
 Debian unstable (main)
References: <162927959062.21857.5988225423491374857.malonedeb@gac.canonical.com>
Message-ID: <162927959733.4199.2469834369448497007.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Please sync dh-python 4.20201102+nmu1 (universe) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Disable the nosetests autopkg test. Unmaintained.
  * Disable the nosetests autopkg test. Unmaintained.
  * Fix DocTest.
-> Those have been fixed by the NMU

  * Don't run test t301.

-> I don't really understand the rationale for disabling this test.
While the test case specifies a python version << 3.9 which wouldn't make
it fit for current versions of Ubuntu, I believe what is being tested is the
ability to specify the version bounds properly, which shouldn't be affected by
the default version on the system.

Changelog entries since current impish version 4.20201102ubuntu4:

dh-python (4.20201102+nmu1) unstable; urgency=medium

  * Non-maintainer upload
  * Don't fail tests just because the default python gets hardcoded
    (Closes: #975536)

 -- Paul Gevers <elbrus at debian.org>  Sat, 27 Feb 2021 19:51:37 +0100

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

-- 
Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1940405
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940410 at bugs.launchpad.net  Wed Aug 18 10:36:48 2021
From: 1940410 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Aug 2021 10:36:48 -0000
Subject: [Bug 1940410] [NEW] Merge 0.13.1-5 from Debian
References: <162928125091.28500.2282620664034061591.malonedeb@gac.canonical.com>
Message-ID: <162928300840.17471.12152048474742802039.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Merge the few changes from Debian to reduce the diff as much as
possible.

** Affects: quassel (Ubuntu)
     Importance: Undecided
         Status: In Progress

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


From 1940419 at bugs.launchpad.net  Wed Aug 18 11:03:42 2021
From: 1940419 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Aug 2021 11:03:42 -0000
Subject: [Bug 1940419] [NEW] Please merge debmirror 1:2.35 (universe) from
 Debian stable (main)
References: <162928407887.21124.14193465791850028404.malonedeb@chaenomeles.canonical.com>
Message-ID: <162928462320.25484.10269387938961697408.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Valters Jansons (sigv):

Upstream has released debmirror 1:2.35:

  [ Kees Cook ]
  * Remove temporary files created while verifying InRelease (closes:
    #961197).

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

-- 
Please merge debmirror 1:2.35 (universe) from Debian stable (main)
https://bugs.launchpad.net/bugs/1940419
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940423 at bugs.launchpad.net  Wed Aug 18 11:24:13 2021
From: 1940423 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Aug 2021 11:24:13 -0000
Subject: [Bug 1940423] [NEW] Sync racket 7.9+dfsg1-2 (universe) from Debian
 unstable (main)
References: <162928584819.2892.995416147893686789.malonedeb@soybean.canonical.com>
Message-ID: <162928585341.7537.768300565292008195.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Please sync racket 7.9+dfsg1-2 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Merge from Debian unstable.  Remaining changes:
    - Ensure building with -O2 to work around a misbuild on ppc64el which
    defaults to -O3.
    - Build with gcc-9 to work around failure to build on s390x

When uploading the 7.9+dfsg1-2 version to a PPA ( https://launchpad.net/~schopin/+archive/ubuntu/test-ppa/+sourcepub/12655139/+listing-archive-extra )
the build failures don't appear on the mentioned architectures. We can assume the problem have been either fixed upstream or in GCC 11.

Changelog entries since current impish version 7.8+dfsg1-1ubuntu1:

racket (7.9+dfsg1-2) unstable; urgency=medium

  * Bug fix: "CVE-2021-32773", thanks to Moritz Mühlenhoff (Closes:
    #991327). Backport commit aa2e814a02 from racket 8.2. See also
    https://github.com/racket/racket/issues/3923

 -- David Bremner <bremner at debian.org>  Sat, 24 Jul 2021 11:13:09 -0300

racket (7.9+dfsg1-1) unstable; urgency=medium

  * New upstream release
  * Adjust include path in racket-arch.c (thanks to Asumu Takikawa)

 -- David Bremner <bremner at debian.org>  Tue, 08 Dec 2020 20:47:19 -0400

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

-- 
Sync racket 7.9+dfsg1-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1940423
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940423 at bugs.launchpad.net  Wed Aug 18 12:02:55 2021
From: 1940423 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Wed, 18 Aug 2021 12:02:55 -0000
Subject: [Bug 1940423] Re: Sync racket 7.9+dfsg1-2 (universe) from Debian
 unstable (main)
References: <162928584819.2892.995416147893686789.malonedeb@soybean.canonical.com>
Message-ID: <162928817570.22311.18187795662840765906.malone@gac.canonical.com>

This bug was fixed in the package racket - 7.9+dfsg1-2
Sponsored for Simon Chopin (schopin)

---------------
racket (7.9+dfsg1-2) unstable; urgency=medium

  * Bug fix: "CVE-2021-32773", thanks to Moritz Mühlenhoff (Closes:
    #991327). Backport commit aa2e814a02 from racket 8.2. See also
    https://github.com/racket/racket/issues/3923

 -- David Bremner <bremner at debian.org>  Sat, 24 Jul 2021 11:13:09 -0300

racket (7.9+dfsg1-1) unstable; urgency=medium

  * New upstream release
  * Adjust include path in racket-arch.c (thanks to Asumu Takikawa)

 -- David Bremner <bremner at debian.org>  Tue, 08 Dec 2020 20:47:19 -0400

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

** Bug watch added: github.com/racket/racket/issues #3923
   https://github.com/racket/racket/issues/3923

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-32773

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

Title:
  Sync racket 7.9+dfsg1-2 (universe) from Debian unstable (main)

Status in racket package in Ubuntu:
  Fix Released

Bug description:
  Please sync racket 7.9+dfsg1-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Merge from Debian unstable.  Remaining changes:
      - Ensure building with -O2 to work around a misbuild on ppc64el which
      defaults to -O3.
      - Build with gcc-9 to work around failure to build on s390x

  When uploading the 7.9+dfsg1-2 version to a PPA ( https://launchpad.net/~schopin/+archive/ubuntu/test-ppa/+sourcepub/12655139/+listing-archive-extra )
  the build failures don't appear on the mentioned architectures. We can assume the problem have been either fixed upstream or in GCC 11.

  Changelog entries since current impish version 7.8+dfsg1-1ubuntu1:

  racket (7.9+dfsg1-2) unstable; urgency=medium

    * Bug fix: "CVE-2021-32773", thanks to Moritz Mühlenhoff (Closes:
      #991327). Backport commit aa2e814a02 from racket 8.2. See also
      https://github.com/racket/racket/issues/3923

   -- David Bremner <bremner at debian.org>  Sat, 24 Jul 2021 11:13:09
  -0300

  racket (7.9+dfsg1-1) unstable; urgency=medium

    * New upstream release
    * Adjust include path in racket-arch.c (thanks to Asumu Takikawa)

   -- David Bremner <bremner at debian.org>  Tue, 08 Dec 2020 20:47:19
  -0400

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



From 1940439 at bugs.launchpad.net  Wed Aug 18 16:24:05 2021
From: 1940439 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 18 Aug 2021 16:24:05 -0000
Subject: [Bug 1940439] [NEW] Merge 1.9.14-1 from Debian
References: <162929669753.24756.4219577710722269932.malonedeb@gac.canonical.com>
Message-ID: <162930384590.4783.12505369354763615450.launchpad@chaenomeles.canonical.com>

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

New upstream version with bugfixes.

** Affects: haveged (Ubuntu)
     Importance: Undecided
         Status: In Progress


** Tags: patch
-- 
Merge 1.9.14-1 from Debian
https://bugs.launchpad.net/bugs/1940439
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940439 at bugs.launchpad.net  Wed Aug 18 16:24:06 2021
From: 1940439 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Wed, 18 Aug 2021 16:24:06 -0000
Subject: [Bug 1940439] Re: Merge 1.9.14-1 from Debian
References: <162929669753.24756.4219577710722269932.malonedeb@gac.canonical.com>
Message-ID: <162930384630.5485.10714740628279860568.malone@chaenomeles.canonical.com>

The attachment "haveged.diff" 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/1940439

Title:
  Merge 1.9.14-1 from Debian

Status in haveged package in Ubuntu:
  In Progress

Bug description:
  New upstream version with bugfixes.

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



From 1939728 at bugs.launchpad.net  Wed Aug 18 17:30:17 2021
From: 1939728 at bugs.launchpad.net (Brian Murray)
Date: Wed, 18 Aug 2021 17:30:17 -0000
Subject: [Bug 1939728] Re: Please merge icu 67.1-7 (main) from Debian unstable
References: <162878878900.24040.3750746540482533273.malonedeb@wampee.canonical.com>
Message-ID: <162930781800.5464.8205355217103867654.malone@gac.canonical.com>

It looks like this got sponsored so I'm unsubscribing the sponsors team.

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

Title:
  Please merge icu 67.1-7 (main) from Debian unstable

Status in icu package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

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



From 1939739 at bugs.launchpad.net  Wed Aug 18 17:31:29 2021
From: 1939739 at bugs.launchpad.net (Brian Murray)
Date: Wed, 18 Aug 2021 17:31:29 -0000
Subject: [Bug 1939739] Re: Please merge gnutls28 3.7.1-5 (main) from Debian
 unstable
References: <162879244949.8960.4950265841511856934.malonedeb@gac.canonical.com>
Message-ID: <162930788929.20967.18388737493146693086.malone@chaenomeles.canonical.com>

This has been sponsored so I'm unsubscribing the sponsors team.

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

Title:
  Please merge gnutls28 3.7.1-5 (main) from Debian unstable

Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

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



From 1939750 at bugs.launchpad.net  Wed Aug 18 17:36:51 2021
From: 1939750 at bugs.launchpad.net (Brian Murray)
Date: Wed, 18 Aug 2021 17:36:51 -0000
Subject: [Bug 1939750] Re: Please merge 7.74.0-1.3
References: <162880205922.12278.17954833672225369383.malonedeb@gac.canonical.com>
Message-ID: <162930821116.6182.8562550712739845783.malone@gac.canonical.com>

I'll sponsor this today.

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

Title:
  Please merge 7.74.0-1.3

Status in curl package in Ubuntu:
  Confirmed
Status in curl package in Debian:
  Unknown

Bug description:
  Debian version 7.74.0-1.3 cherry-picks a fix for a command line API
  breakage that would be unexpected in a minor version release.
  Please help merge.

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064
  https://github.com/curl/curl/issues/6321

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



From 1940419 at bugs.launchpad.net  Wed Aug 18 20:06:19 2021
From: 1940419 at bugs.launchpad.net (Brian Murray)
Date: Wed, 18 Aug 2021 20:06:19 -0000
Subject: [Bug 1940419] Re: Please merge debmirror 1:2.35 (universe) from
 Debian stable (main)
References: <162928407887.21124.14193465791850028404.malonedeb@chaenomeles.canonical.com>
Message-ID: <162931717976.27324.11269814593506684660.malone@wampee.canonical.com>

I'll do this today.

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

Title:
  Please merge debmirror 1:2.35 (universe) from Debian stable (main)

Status in debmirror package in Ubuntu:
  Confirmed

Bug description:
  Upstream has released debmirror 1:2.35:

    [ Kees Cook ]
    * Remove temporary files created while verifying InRelease (closes:
      #961197).

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



From 1934829 at bugs.launchpad.net  Thu Aug 19 00:22:04 2021
From: 1934829 at bugs.launchpad.net (Athos Ribeiro)
Date: Thu, 19 Aug 2021 00:22:04 -0000
Subject: [Bug 1934829] Re: universal-ctags FTBFS  with glibc-2.33
References: <162561352934.24466.11087677901252740671.malonedeb@chaenomeles.canonical.com>
Message-ID: <162933252419.25033.4528708636790277268.malone@gac.canonical.com>

I addressed Sergio comments regarding the changelog.

Moreover, I did dig through the armhf failure and I realized the
newfstatat system call is not available there. It then falls back to
calling statx, which is not in the seccomp rules, leading to failure.

I rebuilt the package with an additional fix in the same PPA, at

https://launchpad.net/~athos-ribeiro/+archive/ubuntu/universal-ctags-
lp1934829-glibc233/+packages

I am attaching a new debdiff, with an additional patch to fix the armhf
build failure, which I forwarded upstream at
https://github.com/universal-ctags/ctags/pull/3125

** Patch added: "3-0+git20200824-1.1ubuntu1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/universal-ctags/+bug/1934829/+attachment/5518870/+files/3-0+git20200824-1.1ubuntu1.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/1934829

Title:
  universal-ctags FTBFS  with glibc-2.33

Status in universal-ctags package in Ubuntu:
  New
Status in universal-ctags package in Debian:
  New

Bug description:
  The latest sync from Debian FTBFS [1][2]. This is due to the newer
  version of glibc (2.33) available in impish and in hirsute.

  Since glibc in Debian unstable is at 2.31, the issue does not manifest
  itself there.

  Moreover, this has been fixed upstream [3] and should be included in
  Debian when the package gets updated after the current freeze.
  Therefore, I am attaching a patch to unblock Ubuntu's migration, which
  was not forwarded to Debian. The package builds fine in impish and
  works as expected.

  [1] https://launchpad.net/ubuntu/+source/universal-ctags/0+git20200824-1.1
  [2] https://launchpad.net/ubuntu/+source/universal-ctags/0+git20200824-1.1/+build/21478505
  [3] https://github.com/universal-ctags/ctags/pull/2990

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/universal-ctags/+bug/1934829/+subscriptions



From 1940153 at bugs.launchpad.net  Thu Aug 19 00:35:30 2021
From: 1940153 at bugs.launchpad.net (Brian Murray)
Date: Thu, 19 Aug 2021 00:35:30 -0000
Subject: [Bug 1940153] Re: Sync intel-ipsec-mb 1.0-1 (universe) from Debian
 unstable (main)
References: <162915127626.12948.11573510597290358415.malonedeb@gac.canonical.com>
Message-ID: <162933333099.18414.14835524030706396192.malone@wampee.canonical.com>

$ syncpackage -d unstable -r impish-proposed intel-ipsec-mb 
Source intel-ipsec-mb -> impish/Proposed: current version 0.55-1, new version 1.0-1
Downloading intel-ipsec-mb_1.0-1.dsc from deb.debian.org (0.002 MiB)
Download Error: Could not download http://ftpmaster.internal/ubuntu/pool/universe/i/intel-ipsec-mb/intel-ipsec-mb_0.55-1.dsc to /tmp/tmpyfvd
v923/intel-ipsec-mb_0.55-1.dsc
Downloading intel-ipsec-mb_0.55-1.dsc from archive.ubuntu.com (0.002 MiB)
Downloading changelog from launchpadlibrarian.net (0.004 MiB)                                                                              
New changes:                                                                                                                               
intel-ipsec-mb (1.0-1) unstable; urgency=medium

  * Sync to latest 1.0 release
  * Rename libipsec-mb0 to libipsec-mb1
  * Remove debian/watch as the upstream project is not serving tarballs now
  * Add note about elf debug optimization being disabled in rules
  * Add back the Uploaders field in the control file

 -- Colin Ian King <colin.king at canonical.com>  Fri, 7 May 2021 09:11:47 +0100
Sync this package [y|N]? y

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

Title:
  Sync intel-ipsec-mb 1.0-1 (universe) from Debian unstable (main)

Status in intel-ipsec-mb package in Ubuntu:
  New

Bug description:
  Please sync intel-ipsec-mb 1.0-1 (universe) from Debian unstable
  (main)

  Changelog entries since current impish version 0.55-1:

  intel-ipsec-mb (1.0-1) unstable; urgency=medium

    * Sync to latest 1.0 release
    * Rename libipsec-mb0 to libipsec-mb1
    * Remove debian/watch as the upstream project is not serving tarballs now
    * Add note about elf debug optimization being disabled in rules
    * Add back the Uploaders field in the control file

   -- Colin Ian King <colin.king at canonical.com>  Fri, 7 May 2021
  09:11:47 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-ipsec-mb/+bug/1940153/+subscriptions



From 1939567 at bugs.launchpad.net  Thu Aug 19 00:48:08 2021
From: 1939567 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 00:48:08 -0000
Subject: [Bug 1939567] Re: Merge gnupg2 2.2.27-2 from Debian
References: <162868772832.28928.4696309983101623186.malonedeb@gac.canonical.com>
Message-ID: <162933408881.15752.7876610962902476684.launchpad@chaenomeles.canonical.com>

** Summary changed:

- Merge 2.2.27-2 from Debian
+ Merge gnupg2 2.2.27-2 from Debian

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

Title:
  Merge gnupg2 2.2.27-2 from Debian

Status in gnupg2 package in Ubuntu:
  In Progress

Bug description:
  Hasn't been merged for a while, the changes from upstream are mostly
  bugfixes.

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



From 1937873 at bugs.launchpad.net  Thu Aug 19 00:45:32 2021
From: 1937873 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 00:45:32 -0000
Subject: [Bug 1937873] Re: overlay-root doesn't work by default
References: <162706816152.668.6098463639469078527.malonedeb@chaenomeles.canonical.com>
Message-ID: <162933393286.28159.6928567987136057568.launchpad@gac.canonical.com>

** Summary changed:

- overlay-root doesn't work bij default.
+ overlay-root doesn't work by default

** Changed in: dracut (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/1937873

Title:
  overlay-root doesn't work by default

Status in dracut package in Ubuntu:
  New

Bug description:
  By default the module 90overlay-root gets installed, but this module won't work in hostonly mode.
  In hostonly mode the required kernel module overlay is not installed.
  Using the command line option rootovl at boot will hang the system, because the dracut module will try to run but fail because of the missing kernel support.
  Other dracut modules fix this by setting hostonly='' before running instmods.

  Regards,

  Usarin Heininga

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



From 1939918 at bugs.launchpad.net  Thu Aug 19 00:54:58 2021
From: 1939918 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 00:54:58 -0000
Subject: [Bug 1939918] Re: FTBFS against glibc 2.34
References: <162888353293.31443.7107257617651384274.malonedeb@wampee.canonical.com>
Message-ID: <162933450046.22510.11622553930841123986.launchpad@wampee.canonical.com>

** Changed in: libnss-db (Ubuntu)
   Importance: Undecided => High

** Tags added: ftbfs

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

Title:
  FTBFS against glibc 2.34

Status in libnss-db package in Ubuntu:
  New

Bug description:
  The package libnss-db failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-db/+bug/1939918/+subscriptions



From 1939909 at bugs.launchpad.net  Thu Aug 19 00:54:37 2021
From: 1939909 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 00:54:37 -0000
Subject: [Bug 1939909] Re: FTBFS against glibc 2.34
References: <162887225110.21018.1195284754935981627.malonedeb@wampee.canonical.com>
Message-ID: <162933447906.22557.3799149217183704817.launchpad@wampee.canonical.com>

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

** Tags added: ftbfs

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

Title:
  FTBFS against glibc 2.34

Status in m4 package in Ubuntu:
  In Progress

Bug description:
  The package m4 failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The build failure can be traced to the glibc version used for the
  rebuild, 2.34, as discussed there
  https://lists.gnu.org/archive/html/bug-m4/2021-03/msg00000.html

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



From 1940439 at bugs.launchpad.net  Thu Aug 19 00:58:14 2021
From: 1940439 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 00:58:14 -0000
Subject: [Bug 1940439] Re: Merge 1.9.14-1 from Debian
References: <162929669753.24756.4219577710722269932.malonedeb@gac.canonical.com>
Message-ID: <162933469545.19541.9859979091530697605.launchpad@chaenomeles.canonical.com>

** Changed in: haveged (Ubuntu)
   Importance: Undecided => Wishlist

** Summary changed:

- Merge 1.9.14-1 from Debian
+ Merge quassel 1.9.14-1 from Debian

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

Title:
  Merge quassel 1.9.14-1 from Debian

Status in haveged package in Ubuntu:
  In Progress

Bug description:
  New upstream version with bugfixes.

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



From 1940410 at bugs.launchpad.net  Thu Aug 19 00:58:02 2021
From: 1940410 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 00:58:02 -0000
Subject: [Bug 1940410] Re: Merge 0.13.1-5 from Debian
References: <162928125091.28500.2282620664034061591.malonedeb@gac.canonical.com>
Message-ID: <162933468404.20844.12528179652688194294.launchpad@wampee.canonical.com>

** Changed in: quassel (Ubuntu)
   Importance: Undecided => Wishlist

** Summary changed:

- Merge 0.13.1-5 from Debian
+ Merge quassel 0.13.1-5 from Debian

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

Title:
  Merge quassel 0.13.1-5 from Debian

Status in quassel package in Ubuntu:
  In Progress

Bug description:
  Merge the few changes from Debian to reduce the diff as much as
  possible.

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



From 1940405 at bugs.launchpad.net  Thu Aug 19 00:59:09 2021
From: 1940405 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 00:59:09 -0000
Subject: [Bug 1940405] Re: Sync dh-python 4.20201102+nmu1 (universe) from
 Debian unstable (main)
References: <162927959062.21857.5988225423491374857.malonedeb@gac.canonical.com>
Message-ID: <162933475094.19213.10270884112501910861.launchpad@chaenomeles.canonical.com>

** Changed in: dh-python (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/1940405

Title:
  Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main)

Status in dh-python package in Ubuntu:
  New

Bug description:
  Please sync dh-python 4.20201102+nmu1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Disable the nosetests autopkg test. Unmaintained.
    * Disable the nosetests autopkg test. Unmaintained.
    * Fix DocTest.
  -> Those have been fixed by the NMU

    * Don't run test t301.

  -> I don't really understand the rationale for disabling this test.
  While the test case specifies a python version << 3.9 which wouldn't make
  it fit for current versions of Ubuntu, I believe what is being tested is the
  ability to specify the version bounds properly, which shouldn't be affected by
  the default version on the system.

  Changelog entries since current impish version 4.20201102ubuntu4:

  dh-python (4.20201102+nmu1) unstable; urgency=medium

    * Non-maintainer upload
    * Don't fail tests just because the default python gets hardcoded
      (Closes: #975536)

   -- Paul Gevers <elbrus at debian.org>  Sat, 27 Feb 2021 19:51:37 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1940405/+subscriptions



From 1912168 at bugs.launchpad.net  Thu Aug 19 00:57:48 2021
From: 1912168 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 00:57:48 -0000
Subject: [Bug 1912168] Re: Merge ppp 2.4.9
References: <161095854683.30278.15024416028507416039.malonedeb@chaenomeles.canonical.com>
Message-ID: <162933466848.19211.7045602316039631170.launchpad@chaenomeles.canonical.com>

** Summary changed:

- please merge ppp 2.4.9 for 21.04 and then consider ipv6 default fix for SRU
+ Merge ppp 2.4.9

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

Title:
  Merge ppp 2.4.9

Status in ppp package in Ubuntu:
  Triaged

Bug description:
  Hi,
  due to this ML on devel-discuss [1] I realized that there is a new version that should be merged for Ubuntu 21.04 - and probably later [2] be considered/discussed for an SRU
  That new version is in Debian now [3] and I think it would be great to get that merged/synced.

  I guess ppp might be out-of-focus today, therefore per [4] I'm also
  pinging the Desktop team hoping this will help to get a look at it.

  [1]: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2021-January/018916.html
  [2]: https://github.com/paulusmack/ppp/pull/145/commits/0678d3bf69116af58b00fbc64bd4185acb4d5c37
  [3]: https://tracker.debian.org/news/1217613/ppp-249-11-migrated-to-testing/
  [4]: http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html

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



From 1939613 at bugs.launchpad.net  Thu Aug 19 01:01:33 2021
From: 1939613 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 01:01:33 -0000
Subject: [Bug 1939613] Re: xrt package does not create  xilinx.icd
References: <162870820279.31010.18218099389662983300.malonedeb@soybean.canonical.com>
Message-ID: <162933489448.31689.15674263516383793494.launchpad@gac.canonical.com>

** Changed in: xrt (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/1939613

Title:
  xrt package does not create  xilinx.icd

Status in xrt package in Ubuntu:
  New

Bug description:
  As part of the installation, the XRT package should create the vendor-
  specific /etc/OpenCL/vendor/xilinx.icd file.  The contents of the file
  should be:

  libxilinxopencl.so

  This provides support for the Installable Client Driver (ICD) model as
  described here: https://github.com/KhronosGroup/OpenCL-ICD-Loader

  Applications can then be built using -lOpenCL instead of linking to
  the xilinx-specific libxilinxopencl.so.

  
  $ apt-cache policy xrt-embedded
  xrt-embedded:
    Installed: 202020.2.8.726-0ubuntu2
    Candidate: 202020.2.8.726-0ubuntu7~20.04
    Version table:
       202020.2.8.726-0ubuntu7~20.04 500
          500 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe arm64 Packages
   *** 202020.2.8.726-0ubuntu2 100
          100 /var/lib/dpkg/status

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



From 1940141 at bugs.launchpad.net  Thu Aug 19 01:07:55 2021
From: 1940141 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 01:07:55 -0000
Subject: [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request
 in a CertificateRequest
References: <162914012164.16193.1962205616306104875.malonedeb@soybean.canonical.com>
Message-ID: <162933527650.483.11412842811318487545.launchpad@soybean.canonical.com>

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

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

** Changed in: openssl (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/1940141

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
      CertificateRequest, Length=1570
        request_context (len=0):
        extensions, length = 1567
          extension_type=status_request(5), length=1521
            0000 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   ....0..........
            000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   0.....+.....0..
            001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   ....0...0......
            002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   0..1.0...U....G
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch. As a non-empty reply is incorrect behavior

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



From 1921658 at bugs.launchpad.net  Thu Aug 19 01:09:12 2021
From: 1921658 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 19 Aug 2021 01:09:12 -0000
Subject: [Bug 1921658] Re: Can't compose kvm host with lvm storage on maas
 2.8.4 
References: <161697993430.18838.13362103946863867785.malonedeb@gac.canonical.com>
Message-ID: <162933535406.1497.3494644263636926154.launchpad@soybean.canonical.com>

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

** Changed in: readline (Ubuntu Bionic)
   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/1921658

Title:
  Can't compose kvm host with lvm storage on maas 2.8.4

Status in MAAS:
  Triaged
Status in readline package in Ubuntu:
  Fix Released
Status in readline source package in Bionic:
  In Progress

Bug description:
  I can't compose kvm host on maas 2.8.4 ( bionic)

  I upgraded twisted and related component with pip but the symptom is
  the same.

  MaaS 2.9.x in Focal works fine.

  in 2.8.x, pexpect virsh vol-path should return [2] but returns [3]

  [2]
  /dev/maas_data_vg/8d4e8b04-4031-4a1b-b5f2-a8306192db11
  [3]
  2021-03-17 20:43:34 stderr: [error] Message: 'this is the result...\n'
  2021-03-17 20:43:34 stderr: [error] Arguments: ([' ', '<3ef-46ca-87c8-19171950592f --pool maas_guest_lvm_vg', "error: command 'attach-disk' doesn't support option --pool"],)

  sometimes it fails in

      def get_volume_path(self, pool, volume):
          """Return the path to the file from `pool` and `volume`."""
          output = self.run(["vol-path", volume, "--pool", pool])
          return output.strip()

  sometimes failes in

      def get_machine_xml(self, machine):
          # Check if we have a cached version of the XML.
          # This is a short-lived object, so we don't need to worry about
          # expiring objects in the cache.
          if machine in self.xml:
              return self.xml[machine]

          # Grab the XML from virsh if we don't have it already.
          output = self.run(["dumpxml", machine]).strip()
          if output.startswith("error:"):
              maaslog.error("%s: Failed to get XML for machine", machine)
              return None

          # Cache the XML, since we'll need it later to reconfigure the VM.
          self.xml[machine] = output
          return output

  I assume that run function has issue.

  Command line virsh vol-path and simple pepect python code works fine.

  
  Any advice for this issue?

  Thanks.

  Reproducer is below.[1]

  [1]

  1) Create file to be used as loopback device

  sudo dd if=/dev/zero of=lvm bs=16000 count=1M

  2) sudo losetup /dev/loop39 lvm

  3) sudo pvcreate /dev/loop39

  4) sudo vgcreate maas_data_vg /dev/loop39

  5) Save below xml:
  <pool type='logical'>
  <name>maas_guest_lvm_vg</name>
  <source>
  <name>maas_data_vg</name>
  <format type='lvm2'/>
  </source>
  <target>
  <path>/dev/maas_data_vg</path>
  </target>
  </pool>

  6) virsh pool-create maas_guest_lvm_vg.xml

  7) Add KVM host in MaaS

  8) Attempt to compose a POD using storage pool maas_guest_lvm_vg

  9) GUI will fail with:

  Pod unable to compose machine: Unable to compose machine because:
  Failed talking to pod: Start tag expected, '<' not found, line 1,
  column 1 (<string>, line 1)

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



From 1934829 at bugs.launchpad.net  Thu Aug 19 01:48:12 2021
From: 1934829 at bugs.launchpad.net (Sergio Durigan Junior)
Date: Thu, 19 Aug 2021 01:48:12 -0000
Subject: [Bug 1934829] Re: universal-ctags FTBFS  with glibc-2.33
References: <162561352934.24466.11087677901252740671.malonedeb@chaenomeles.canonical.com>
Message-ID: <162933769319.8712.14849367511447213942.malone@soybean.canonical.com>

Thanks for the thorough analysis, Athos.

I noticed that upstream has already approved your PR, and I agree with
your fix.  I'm now happy with the rest of the debdiff as well (but I
took the liberty to update the date of the d/changelog entry), so I'll
go ahead and upload the package.

$ dput universal-ctags_0+git20200824-1.1ubuntu1_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /home/sergio/work/universal-ctags/universal-ctags_0+git20200824-1.1ubuntu1_source.changes: Valid signature from 106DA1C8C3CBBF14
Checking signature on .dsc
gpg: /home/sergio/work/universal-ctags/universal-ctags_0+git20200824-1.1ubuntu1.dsc: Valid signature from 106DA1C8C3CBBF14
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading universal-ctags_0+git20200824-1.1ubuntu1.dsc: done.
  Uploading universal-ctags_0+git20200824-1.1ubuntu1.debian.tar.xz: done.
  Uploading universal-ctags_0+git20200824-1.1ubuntu1_source.buildinfo: done.
  Uploading universal-ctags_0+git20200824-1.1ubuntu1_source.changes: done.
Successfully uploaded packages.

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

Title:
  universal-ctags FTBFS  with glibc-2.33

Status in universal-ctags package in Ubuntu:
  New
Status in universal-ctags package in Debian:
  New

Bug description:
  The latest sync from Debian FTBFS [1][2]. This is due to the newer
  version of glibc (2.33) available in impish and in hirsute.

  Since glibc in Debian unstable is at 2.31, the issue does not manifest
  itself there.

  Moreover, this has been fixed upstream [3] and should be included in
  Debian when the package gets updated after the current freeze.
  Therefore, I am attaching a patch to unblock Ubuntu's migration, which
  was not forwarded to Debian. The package builds fine in impish and
  works as expected.

  [1] https://launchpad.net/ubuntu/+source/universal-ctags/0+git20200824-1.1
  [2] https://launchpad.net/ubuntu/+source/universal-ctags/0+git20200824-1.1/+build/21478505
  [3] https://github.com/universal-ctags/ctags/pull/2990

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/universal-ctags/+bug/1934829/+subscriptions



From 1918855 at bugs.launchpad.net  Thu Aug 19 05:53:42 2021
From: 1918855 at bugs.launchpad.net (Cyrus Lien)
Date: Thu, 19 Aug 2021 05:53:42 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162935242256.9565.15942987843172680597.malone@chaenomeles.canonical.com>

@Timo,

In bionic mesa (20.0.8-0ubuntu1~18.04.1) it prefer i965 by default over iris. 
rules: confflags_GALLIUM += -Dprefer-iris=false

Is it available to enable iris by default in bionic?

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1918855 at bugs.launchpad.net  Thu Aug 19 06:49:30 2021
From: 1918855 at bugs.launchpad.net (Timo Aaltonen)
Date: Thu, 19 Aug 2021 06:49:30 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162935577042.28677.7984608803296845430.malone@wampee.canonical.com>

that would require a newer libepoxy

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1918855 at bugs.launchpad.net  Thu Aug 19 06:50:42 2021
From: 1918855 at bugs.launchpad.net (Timo Aaltonen)
Date: Thu, 19 Aug 2021 06:50:42 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162935584221.27088.1045773045800565886.malone@wampee.canonical.com>

this bug was about iris, if you have some other issue that *requires
iris*, then file a new one

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1918855 at bugs.launchpad.net  Thu Aug 19 07:06:34 2021
From: 1918855 at bugs.launchpad.net (Daniel van Vugt)
Date: Thu, 19 Aug 2021 07:06:34 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162935679408.420.11915338228820370150.malone@wampee.canonical.com>

Also remember you can test iris using environment
MESA_LOADER_DRIVER_OVERRIDE=iris

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1918855 at bugs.launchpad.net  Thu Aug 19 07:20:29 2021
From: 1918855 at bugs.launchpad.net (Cyrus Lien)
Date: Thu, 19 Aug 2021 07:20:29 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162935762962.9832.2154594753690715951.malone@gac.canonical.com>

I encountered exactly same issue as this bug on bionic so I would like to leverage iris fix (iris-avoid-abort-if-enomem.diff) but bionic mesa prefer i965 by default over iris. 
Do I need to file a new one on mesa/i965 driver?

Aug 3 03:12:39 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexImage2D
Aug 3 03:12:50 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE)
Aug 3 03:12:50 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) Backtrace:
Aug 3 03:12:54 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 0: /usr/lib/xorg/Xorg (?+0x0) [0x556430b27080]
Aug 3 03:12:54 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (?+0x0) [0x7f7778ae697f]
Aug 3 03:12:56 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 2: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so (?+0x0) [0x7f7773960a70]
Aug 3 03:12:56 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so (?+0x0) [0x7f7773960d10]
Aug 3 03:12:56 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so (?+0x0) [0x7f7773960de0]

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1918855 at bugs.launchpad.net  Thu Aug 19 07:28:44 2021
From: 1918855 at bugs.launchpad.net (Daniel van Vugt)
Date: Thu, 19 Aug 2021 07:28:44 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162935812423.11903.8977946831782134320.malone@gac.canonical.com>

Although that stack trace is not useful the GL_OUT_OF_MEMORY does kind
of give it away that it's the same kind of issue as this. I would say it
makes sense to do a different fix for i965 but keep using this same bug
ID.

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1940439 at bugs.launchpad.net  Thu Aug 19 08:54:53 2021
From: 1940439 at bugs.launchpad.net (Simon Chopin)
Date: Thu, 19 Aug 2021 08:54:53 -0000
Subject: [Bug 1940439] Re: Merge haveged 1.9.14-1 from Debian
References: <162929669753.24756.4219577710722269932.malonedeb@gac.canonical.com>
Message-ID: <162936329438.24840.3999669290116704440.launchpad@wampee.canonical.com>

** Summary changed:

- Merge quassel 1.9.14-1 from Debian
+ Merge haveged 1.9.14-1 from Debian

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

Title:
  Merge haveged 1.9.14-1 from Debian

Status in haveged package in Ubuntu:
  In Progress

Bug description:
  New upstream version with bugfixes.

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



From 1932076 at bugs.launchpad.net  Thu Aug 19 14:30:41 2021
From: 1932076 at bugs.launchpad.net (Lucas Kanashiro)
Date: Thu, 19 Aug 2021 14:30:41 -0000
Subject: [Bug 1932076] Re: src:request-tracker5: ftbfs due to changes in gpg
 error messages
References: <162379050282.13849.15848709508592262107.malonedeb@wampee.canonical.com>
Message-ID: <162938344181.10095.12815462576144810582.malone@gac.canonical.com>

I applied the patch mentioned in comment #6 and request-tracker4 builds
fine with it. I do not believe Debian maintainers will be releasing this
fix before Impish release, then I am proposing to add this as a delta
now to get in the latest changes. I attached a debdiff with the proposed
package.

** Attachment added: "debdiff"
   https://bugs.launchpad.net/ubuntu/+source/request-tracker5/+bug/1932076/+attachment/5519080/+files/debdiff

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

Title:
  src:request-tracker5: ftbfs due to changes in gpg error messages

Status in request-tracker4 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/988905:

  Package: src:request-tracker5
  Version: 5.0.1+dfsg-1
  Severity: serious
  Tags: ftbfs
  Justification: fails to build from source

  Dear Maintainer,

  As can be seen at

  https://tests.reproducible-builds.org/debian/rb-
  pkg/unstable/amd64/request-tracker5.html

  or

  https://launchpad.net/ubuntu/+source/request-tracker5/5.0.1+dfsg-1

  the package fails to build with the current state of unstable / Ubuntu
  impish.

  The failures are:

  #   Failed test at t/mail/crypt-gnupg.t line 171.
  # found warning: gpg: error retrieving 'keyless at example.com' via WKD: Server indicated a failure
  # expected to find warning: (?^:public key not found|error retrieving 'keyless\@example.com' via WKD: No data)

  #   Failed test at t/web/crypt-gnupg.t line 358.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  #   Failed test at t/web/crypt-gnupg.t line 380.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  (the messages are actually slightly different in Ubuntu). This seems
  pretty benign really and probably the tests should be relaxed?

  Cheers,
  mwh

  -- System Information:
  Debian Release: bullseye/sid
    APT prefers focal-updates
    APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.4.0-73-generic (SMP w/8 CPU cores)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/request-tracker4/+bug/1932076/+subscriptions



From 1931857 at bugs.launchpad.net  Thu Aug 19 16:23:47 2021
From: 1931857 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 19 Aug 2021 16:23:47 -0000
Subject: [Bug 1931857] [NEW] [21.10 FEAT] Update PCRE2 for JIT and Performance
 Improvements on s390x
References: <162367016246.10774.11824450368735290843.malonedeb@wampee.canonical.com>
Message-ID: <162939022787.30223.3553930398296941316.launchpad@chaenomeles.canonical.com>

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

PCRE2 version 10.37 as available from https://ftp.pcre.org/pub/pcre/
contains the enablement of the JIT and provides some performance improvements

Version 10.38 to be released in November or December 2021 will contain
the complete implementation with full JIT performance.

To pick up the changes please configure with "--enable-jit" for s390x.

It may be beneficial to rebuild certain dependent packages after that
change, such as haproxy.

** Affects: ubuntu-z-systems
     Importance: High
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: Fix Committed

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


** Tags: architecture-s39064 bugnameltc-193238 fr-1553 patch severity-high targetmilestone-inin2110
-- 
[21.10 FEAT] Update PCRE2 for JIT and Performance Improvements on s390x
https://bugs.launchpad.net/bugs/1931857
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940336 at bugs.launchpad.net  Thu Aug 19 16:24:08 2021
From: 1940336 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 19 Aug 2021 16:24:08 -0000
Subject: [Bug 1940336] [NEW] Test wsh-libs.wsh causing segfault with glibc >=
 2.34
References: <162924551878.15261.9944361587170333186.malonedeb@chaenomeles.canonical.com>
Message-ID: <162939024842.30135.6890250870319389748.launchpad@chaenomeles.canonical.com>

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

This package has failing autopkgtests with glibc 2.34. There is a
segmentation fault somewhere in the wsh code.

** Affects: wcc (Ubuntu)
     Importance: Undecided
     Assignee: Brian Murray (brian-murray)
         Status: In Progress


** Tags: patch
-- 
Test wsh-libs.wsh causing segfault with glibc >= 2.34
https://bugs.launchpad.net/bugs/1940336
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940336 at bugs.launchpad.net  Thu Aug 19 16:24:08 2021
From: 1940336 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Thu, 19 Aug 2021 16:24:08 -0000
Subject: [Bug 1940336] Re: Test wsh-libs.wsh causing segfault with glibc >=
 2.34
References: <162924551878.15261.9944361587170333186.malonedeb@chaenomeles.canonical.com>
Message-ID: <162939024874.5833.14399407988492658196.malone@gac.canonical.com>

The attachment "No change rebuild" 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/1940336

Title:
  Test wsh-libs.wsh causing segfault with glibc >= 2.34

Status in wcc package in Ubuntu:
  In Progress

Bug description:
  This package has failing autopkgtests with glibc 2.34. There is a
  segmentation fault somewhere in the wsh code.

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



From 1932076 at bugs.launchpad.net  Thu Aug 19 16:23:50 2021
From: 1932076 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Thu, 19 Aug 2021 16:23:50 -0000
Subject: [Bug 1932076] Re: src:request-tracker5: ftbfs due to changes in gpg
 error messages
References: <162379050282.13849.15848709508592262107.malonedeb@wampee.canonical.com>
Message-ID: <162939023099.7192.7960850078753418826.launchpad@wampee.canonical.com>

** Tags added: patch

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

Title:
  src:request-tracker5: ftbfs due to changes in gpg error messages

Status in request-tracker4 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/988905:

  Package: src:request-tracker5
  Version: 5.0.1+dfsg-1
  Severity: serious
  Tags: ftbfs
  Justification: fails to build from source

  Dear Maintainer,

  As can be seen at

  https://tests.reproducible-builds.org/debian/rb-
  pkg/unstable/amd64/request-tracker5.html

  or

  https://launchpad.net/ubuntu/+source/request-tracker5/5.0.1+dfsg-1

  the package fails to build with the current state of unstable / Ubuntu
  impish.

  The failures are:

  #   Failed test at t/mail/crypt-gnupg.t line 171.
  # found warning: gpg: error retrieving 'keyless at example.com' via WKD: Server indicated a failure
  # expected to find warning: (?^:public key not found|error retrieving 'keyless\@example.com' via WKD: No data)

  #   Failed test at t/web/crypt-gnupg.t line 358.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  #   Failed test at t/web/crypt-gnupg.t line 380.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  (the messages are actually slightly different in Ubuntu). This seems
  pretty benign really and probably the tests should be relaxed?

  Cheers,
  mwh

  -- System Information:
  Debian Release: bullseye/sid
    APT prefers focal-updates
    APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.4.0-73-generic (SMP w/8 CPU cores)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/request-tracker4/+bug/1932076/+subscriptions



From 1931857 at bugs.launchpad.net  Thu Aug 19 16:23:48 2021
From: 1931857 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Thu, 19 Aug 2021 16:23:48 -0000
Subject: [Bug 1931857] Re: [21.10 FEAT] Update PCRE2 for JIT and Performance
 Improvements on s390x
References: <162367016246.10774.11824450368735290843.malonedeb@wampee.canonical.com>
Message-ID: <162939022815.6926.1690334233241943140.malone@gac.canonical.com>

The attachment "pcre2.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/1931857

Title:
  [21.10 FEAT] Update PCRE2 for JIT and Performance Improvements on
  s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in pcre2 package in Ubuntu:
  Fix Committed

Bug description:
  PCRE2 version 10.37 as available from https://ftp.pcre.org/pub/pcre/
  contains the enablement of the JIT and provides some performance improvements

  Version 10.38 to be released in November or December 2021 will contain
  the complete implementation with full JIT performance.

  To pick up the changes please configure with "--enable-jit" for s390x.

  It may be beneficial to rebuild certain dependent packages after that
  change, such as haproxy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931857/+subscriptions



From 1921658 at bugs.launchpad.net  Thu Aug 19 16:55:02 2021
From: 1921658 at bugs.launchpad.net (Dan Streetman)
Date: Thu, 19 Aug 2021 16:55:02 -0000
Subject: [Bug 1921658] Re: Can't compose kvm host with lvm storage on maas
 2.8.4 
References: <161697993430.18838.13362103946863867785.malonedeb@gac.canonical.com>
Message-ID: <162939210272.26563.17413833944480993995.malone@soybean.canonical.com>

@seyeongkim could you add the SRU template to the bug description?

https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

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

Title:
  Can't compose kvm host with lvm storage on maas 2.8.4

Status in MAAS:
  Triaged
Status in readline package in Ubuntu:
  Fix Released
Status in readline source package in Bionic:
  In Progress

Bug description:
  I can't compose kvm host on maas 2.8.4 ( bionic)

  I upgraded twisted and related component with pip but the symptom is
  the same.

  MaaS 2.9.x in Focal works fine.

  in 2.8.x, pexpect virsh vol-path should return [2] but returns [3]

  [2]
  /dev/maas_data_vg/8d4e8b04-4031-4a1b-b5f2-a8306192db11
  [3]
  2021-03-17 20:43:34 stderr: [error] Message: 'this is the result...\n'
  2021-03-17 20:43:34 stderr: [error] Arguments: ([' ', '<3ef-46ca-87c8-19171950592f --pool maas_guest_lvm_vg', "error: command 'attach-disk' doesn't support option --pool"],)

  sometimes it fails in

      def get_volume_path(self, pool, volume):
          """Return the path to the file from `pool` and `volume`."""
          output = self.run(["vol-path", volume, "--pool", pool])
          return output.strip()

  sometimes failes in

      def get_machine_xml(self, machine):
          # Check if we have a cached version of the XML.
          # This is a short-lived object, so we don't need to worry about
          # expiring objects in the cache.
          if machine in self.xml:
              return self.xml[machine]

          # Grab the XML from virsh if we don't have it already.
          output = self.run(["dumpxml", machine]).strip()
          if output.startswith("error:"):
              maaslog.error("%s: Failed to get XML for machine", machine)
              return None

          # Cache the XML, since we'll need it later to reconfigure the VM.
          self.xml[machine] = output
          return output

  I assume that run function has issue.

  Command line virsh vol-path and simple pepect python code works fine.

  
  Any advice for this issue?

  Thanks.

  Reproducer is below.[1]

  [1]

  1) Create file to be used as loopback device

  sudo dd if=/dev/zero of=lvm bs=16000 count=1M

  2) sudo losetup /dev/loop39 lvm

  3) sudo pvcreate /dev/loop39

  4) sudo vgcreate maas_data_vg /dev/loop39

  5) Save below xml:
  <pool type='logical'>
  <name>maas_guest_lvm_vg</name>
  <source>
  <name>maas_data_vg</name>
  <format type='lvm2'/>
  </source>
  <target>
  <path>/dev/maas_data_vg</path>
  </target>
  </pool>

  6) virsh pool-create maas_guest_lvm_vg.xml

  7) Add KVM host in MaaS

  8) Attempt to compose a POD using storage pool maas_guest_lvm_vg

  9) GUI will fail with:

  Pod unable to compose machine: Unable to compose machine because:
  Failed talking to pod: Start tag expected, '<' not found, line 1,
  column 1 (<string>, line 1)

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



From 1940141 at bugs.launchpad.net  Thu Aug 19 17:17:36 2021
From: 1940141 at bugs.launchpad.net (Nicolas Bock)
Date: Thu, 19 Aug 2021 17:17:36 -0000
Subject: [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request
 in a CertificateRequest
References: <162914012164.16193.1962205616306104875.malonedeb@soybean.canonical.com>
Message-ID: <162939345658.15481.13002723914177528688.launchpad@wampee.canonical.com>

** Description changed:

  [Impact]
  
  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.
  
  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.
  
  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780
  
  [Test Plan]
  
  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:
  
  ```
  openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5
  ```
  
  And running `s_client` like this:
  
  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```
  
  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:
  
  Received Record
  Header:
-   Version = TLS 1.2 (0x303)
-   Content Type = ApplicationData (23)
-   Length = 1591
-   Inner Content Type = Handshake (22)
-     CertificateRequest, Length=1570
-       request_context (len=0):
-       extensions, length = 1567
-         extension_type=status_request(5), length=1521
-           0000 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   ....0..........
-           000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   0.....+.....0..
-           001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   ....0...0......
-           002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   0..1.0...U....G
+   Version = TLS 1.2 (0x303)
+   Content Type = ApplicationData (23)
+   Length = 1591
+   Inner Content Type = Handshake (22)
+     CertificateRequest, Length=1570
+       request_context (len=0):
+       extensions, length = 1567
+         extension_type=status_request(5), length=1521
+           0000 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   ....0..........
+           000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   0.....+.....0..
+           001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   ....0...0......
+           002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   0..1.0...U....G
  ...more lines omitted...
  
  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.
  
  [Where problems could occur]
  
  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
- with this patch. As a non-empty reply is incorrect behavior
+ with this 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/1940141

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
      CertificateRequest, Length=1570
        request_context (len=0):
        extensions, length = 1567
          extension_type=status_request(5), length=1521
            0000 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   ....0..........
            000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   0.....+.....0..
            001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   ....0...0......
            002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   0..1.0...U....G
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

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



From 1932076 at bugs.launchpad.net  Thu Aug 19 19:21:05 2021
From: 1932076 at bugs.launchpad.net (Lucas Kanashiro)
Date: Thu, 19 Aug 2021 19:21:05 -0000
Subject: [Bug 1932076] Re: src:request-tracker5: ftbfs due to changes in gpg
 error messages
References: <162379050282.13849.15848709508592262107.malonedeb@wampee.canonical.com>
Message-ID: <162940086546.7278.11323718259908140398.malone@chaenomeles.canonical.com>

Since request-tracker5 is a new package in Impish I believe this would
not worth a delta, but since this is straightforward I am also attaching
a debdiff which fixes the FTBFS.

** Patch added: "request-tracker5.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/request-tracker5/+bug/1932076/+attachment/5519161/+files/request-tracker5.debdiff

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

Title:
  src:request-tracker5: ftbfs due to changes in gpg error messages

Status in request-tracker4 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/988905:

  Package: src:request-tracker5
  Version: 5.0.1+dfsg-1
  Severity: serious
  Tags: ftbfs
  Justification: fails to build from source

  Dear Maintainer,

  As can be seen at

  https://tests.reproducible-builds.org/debian/rb-
  pkg/unstable/amd64/request-tracker5.html

  or

  https://launchpad.net/ubuntu/+source/request-tracker5/5.0.1+dfsg-1

  the package fails to build with the current state of unstable / Ubuntu
  impish.

  The failures are:

  #   Failed test at t/mail/crypt-gnupg.t line 171.
  # found warning: gpg: error retrieving 'keyless at example.com' via WKD: Server indicated a failure
  # expected to find warning: (?^:public key not found|error retrieving 'keyless\@example.com' via WKD: No data)

  #   Failed test at t/web/crypt-gnupg.t line 358.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  #   Failed test at t/web/crypt-gnupg.t line 380.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  (the messages are actually slightly different in Ubuntu). This seems
  pretty benign really and probably the tests should be relaxed?

  Cheers,
  mwh

  -- System Information:
  Debian Release: bullseye/sid
    APT prefers focal-updates
    APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.4.0-73-generic (SMP w/8 CPU cores)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/request-tracker4/+bug/1932076/+subscriptions



From 1929046 at bugs.launchpad.net  Thu Aug 19 22:42:35 2021
From: 1929046 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 19 Aug 2021 22:42:35 -0000
Subject: [Bug 1929046] [NEW] [21.10 FEAT] Upgrade cryptsetup to latest version
 (crypto) (2.4.0)
References: <162150596757.761.5742760700633395945.malonedeb@soybean.canonical.com>
Message-ID: <162941295568.23580.11081656845094239427.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Matthieu Clemenceau (mclemenceau):

Upgrade cryptsetup to latest version 2.3.5

https://gitlab.com/cryptsetup/cryptsetup/-/tags/v2.3.5

** Affects: ubuntu-z-systems
     Importance: High
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: Triaged

** Affects: cryptsetup (Ubuntu)
     Importance: Undecided
     Assignee: Michael Hudson-Doyle (mwhudson)
         Status: New


** Tags: architecture-s39064 bugnameltc-192819 fr-1404 severity-high targetmilestone-inin2110
-- 
[21.10 FEAT] Upgrade cryptsetup to latest version (crypto) (2.4.0)
https://bugs.launchpad.net/bugs/1929046
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1918855 at bugs.launchpad.net  Fri Aug 20 02:06:45 2021
From: 1918855 at bugs.launchpad.net (Cyrus Lien)
Date: Fri, 20 Aug 2021 02:06:45 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162942520579.31295.10298156608671350512.malone@gac.canonical.com>

@Daniel @Timo,
I fund the root cause of my X crash issue, which is not same as this bug.
Please ignore my comments and thanks for your response.

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

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1929046 at bugs.launchpad.net  Fri Aug 20 06:06:18 2021
From: 1929046 at bugs.launchpad.net (Frank Heimes)
Date: Fri, 20 Aug 2021 06:06:18 -0000
Subject: [Bug 1929046] Re: [21.10 FEAT] Upgrade cryptsetup to latest version
 (crypto) (2.3.6)
References: <162150596757.761.5742760700633395945.malonedeb@soybean.canonical.com>
Message-ID: <162943957893.12893.8676987369741867962.malone@gac.canonical.com>

Hi Matt, yes, that's fine, since we initially wanted to wait for 2.4.0 only because to minimize the effort for repeating version bumps a bit.
Browsing the release notes it looks to me that the most important fixes (and changes) are in 2.3.5 anyway, so 2.3.6 is reasonable.

** Summary changed:

- [21.10 FEAT] Upgrade cryptsetup to latest version (crypto) (2.4.0)
+ [21.10 FEAT] Upgrade cryptsetup to latest version (crypto) (2.3.6)

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

Title:
  [21.10 FEAT] Upgrade cryptsetup to latest version (crypto) (2.3.6)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in cryptsetup package in Ubuntu:
  Fix Committed

Bug description:
  Upgrade cryptsetup to latest version 2.3.5

  https://gitlab.com/cryptsetup/cryptsetup/-/tags/v2.3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929046/+subscriptions



From 1929046 at bugs.launchpad.net  Fri Aug 20 06:06:59 2021
From: 1929046 at bugs.launchpad.net (Frank Heimes)
Date: Fri, 20 Aug 2021 06:06:59 -0000
Subject: [Bug 1929046] Re: [21.10 FEAT] Upgrade cryptsetup to latest version
 (crypto) (2.3.6)
References: <162150596757.761.5742760700633395945.malonedeb@soybean.canonical.com>
Message-ID: <162943961933.12856.186847918207413943.malone@wampee.canonical.com>

Since 2.3.6 landed in impish-proposed:
cryptsetup | 2:2.3.6-0ubuntu1   | impish-proposed
I'm updating the status to Fix Committed.

** Changed in: cryptsetup (Ubuntu)
       Status: New => Fix Committed

** Changed in: ubuntu-z-systems
       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/1929046

Title:
  [21.10 FEAT] Upgrade cryptsetup to latest version (crypto) (2.3.6)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in cryptsetup package in Ubuntu:
  Fix Committed

Bug description:
  Upgrade cryptsetup to latest version 2.3.5

  https://gitlab.com/cryptsetup/cryptsetup/-/tags/v2.3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929046/+subscriptions



From 1940629 at bugs.launchpad.net  Fri Aug 20 08:23:09 2021
From: 1940629 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 20 Aug 2021 08:23:09 -0000
Subject: [Bug 1940629] [NEW] Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162944779034.6259.7532557556082877207.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Andy Chi (andch):

[Impact]

 * Support thermald on Jasper Lake CPU.

 *

[Test Plan]

 * Use a machine with a Jasper Lake cpu.

 * systemctl status thermald

 * Status of thermald should be `running`

[Where problems could occur]

 * This change is to support Jasper Lake in thermald, which won't impact
other hardware.

[Other Info]
 
 * https://github.com/intel/thermal_daemon/issues/309

** Affects: oem-priority
     Importance: Undecided
         Status: New

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


** Tags: oem-priority originate-from-1925196 somerville
-- 
Support Jasper Lake
https://bugs.launchpad.net/bugs/1940629
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940629 at bugs.launchpad.net  Fri Aug 20 08:21:46 2021
From: 1940629 at bugs.launchpad.net (Andy Chi)
Date: Fri, 20 Aug 2021 08:21:46 -0000
Subject: [Bug 1940629] Re: Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162944770657.10164.17355121389344118147.malone@gac.canonical.com>

Upload debdiff for hirsute

** Patch added: "thermald_2.4.3-1ubuntu2.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940629/+attachment/5519338/+files/thermald_2.4.3-1ubuntu2.debdiff

** Tags added: oem-priority originate-from-1925196 somerville

** Changed in: oem-priority
     Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  Support Jasper Lake

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions



From 1940629 at bugs.launchpad.net  Fri Aug 20 08:39:25 2021
From: 1940629 at bugs.launchpad.net (Colin Ian King)
Date: Fri, 20 Aug 2021 08:39:25 -0000
Subject: [Bug 1940629] Re: Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162944876791.17601.759486862980940203.launchpad@wampee.canonical.com>

** Changed in: thermald (Ubuntu)
     Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu)
   Importance: Undecided => Critical

** Changed in: thermald (Ubuntu)
       Status: New => 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/1940629

Title:
  Support Jasper Lake

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions



From 1918855 at bugs.launchpad.net  Fri Aug 20 10:46:49 2021
From: 1918855 at bugs.launchpad.net (jeremyszu)
Date: Fri, 20 Aug 2021 10:46:49 -0000
Subject: [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
References: <161551870761.18670.9753510070069025951.malonedeb@soybean.canonical.com>
Message-ID: <162945641097.7096.15347643166802021222.launchpad@chaenomeles.canonical.com>

** Changed in: oem-priority
       Status: Triaged => 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/1918855

Title:
  Xorg crashed with SIGABRT when under memory pressure

Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions



From 1879923 at bugs.launchpad.net  Fri Aug 20 12:56:00 2021
From: 1879923 at bugs.launchpad.net (Bug Watch Updater)
Date: Fri, 20 Aug 2021 12:56:00 -0000
Subject: [Bug 1879923] Re: Update Scan Data Over Internet fails
References: <159005701176.1272.4566518412318297427.malonedeb@chaenomeles.canonical.com>
Message-ID: <162946416119.27939.2057285539189197033.launchpad@loganberry.canonical.com>

Launchpad has imported 4 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=436371.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2021-04-29T19:32:21+00:00 Oskar Alois Runggaldier wrote:

Created attachment 138009
Fehler

SUMMARY


STEPS TO REPRODUCE
1. Fernsehen einrichten
2. Suchlaufdaten über Internet aktualisieren
3. Aktualisierung fehlgeschlagen

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Ubuntu 21.04 >>>>>>>>   pls email : oskar.runggaldier at gmail.com

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/1879923/comments/2

------------------------------------------------------------------------
On 2021-04-30T06:39:46+00:00 Mchehab+huawei wrote:

Git commit 209a263ab2191f0b1d13f48a0a2fa67794357ad0 by Mauro Carvalho Chehab.
Committed on 30/04/2021 at 06:39.
Pushed by mauroc into branch 'master'.

dvbconfigdialog: increase max download size for scandata

By the time Kaffeine was written, a 64KB max limit were
enough, but nowadays, the scandata file has already 104KB.

Increase the limit up to 1MB, in order to fix download
issues with valid files.

While here, also improve the download messages to show
how much data was downloaded and to report the reason
why a download was aborted.

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei at kernel.org>

M  +21   -7    src/dvb/dvbconfigdialog.cpp
M  +1    -0    src/dvb/dvbconfigdialog.h

https://invent.kde.org/multimedia/kaffeine/commit/209a263ab2191f0b1d13f48a0a2fa67794357ad0

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/1879923/comments/3

------------------------------------------------------------------------
On 2021-04-30T06:50:27+00:00 Mchehab+huawei wrote:

(In reply to Oskar Alois from comment #0)

English please.

> STEPS TO REPRODUCE
> 1. Fernsehen einrichten
> 2. Suchlaufdaten über Internet aktualisieren
> 3. Aktualisierung fehlgeschlagen

STEPS TO REPRODUCE
1. Set up television
2. Update search data via the Internet
3. Update failed

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/1879923/comments/4

------------------------------------------------------------------------
On 2021-04-30T06:51:57+00:00 Mchehab+huawei wrote:

In order to prevent too big files, Kaffeine has an upper limit. The
current limit is too low for the size of the current scanfile (104KB).

Commit 209a263ab2191f0b1d13f48a0a2fa67794357ad0 increased the limit to
1MB.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/1879923/comments/5


** Changed in: kaffeine
       Status: Unknown => Fix Released

** Changed in: kaffeine
   Importance: Unknown => 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/1879923

Title:
  Update Scan Data Over Internet fails

Status in Kaffeine:
  Fix Released
Status in kaffeine package in Ubuntu:
  In Progress

Bug description:
  Workaround from Tj; 3 commands (ignore word-wrapping by launchpad):

  cd ~/.local/share/kaffeine
  mv scanfile.dvb{,.$(awk 'C==1{print;exit}/^\[date\]/{C=1}' scanfile.dvb)}
  wget https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/scantable.dvb -O scanfile.dvb

  ----

  
  Running Kaffeine 2.0.18 on Ubuntu 20.04 LTS Plasma Desktop.  Update Scan Data Over Internet fails with message: Scan data update failed

  I believe Kaffeine is looking for a file called scanfile.dvb or
  perhaps scanfile.dvb.qz

  https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/ shows a file
  called scantable.dvb  (Different file name)

  The wiki here (https://linuxtv.org/wiki/index.php/Dtv-scan-tables)
  says that this file will be autocreated and eventually be located
  here: https://autoconfig.kde.org/kaffeine/  The file i see at  this
  location is currently called: scantable.dvb.qz

  Perhaps this is just a file naming issue?

  Thanks,

  Iestyn Guest

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



From 1940629 at bugs.launchpad.net  Fri Aug 20 14:42:17 2021
From: 1940629 at bugs.launchpad.net (Colin Ian King)
Date: Fri, 20 Aug 2021 14:42:17 -0000
Subject: [Bug 1940629] Re: Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162947053769.24557.3525242262448967219.launchpad@soybean.canonical.com>

** Also affects: thermald (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: thermald (Ubuntu Impish)
   Importance: Critical
     Assignee: Colin Ian King (colin-king)
       Status: In Progress

** Also affects: thermald (Ubuntu Hirsute)
   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/1940629

Title:
  Support Jasper Lake

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Focal:
  New
Status in thermald source package in Hirsute:
  New
Status in thermald source package in Impish:
  In Progress

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions



From 1915819 at bugs.launchpad.net  Fri Aug 20 14:59:32 2021
From: 1915819 at bugs.launchpad.net (Bug Watch Updater)
Date: Fri, 20 Aug 2021 14:59:32 -0000
Subject: [Bug 1915819] Re: 'NoneType' object has no attribute 'encode' in
 requestReceived() when multipart body doesn't include content-disposition
References: <161348008246.20935.12756494153193548026.malonedeb@wampee.canonical.com>
Message-ID: <162947157357.20863.11070217731983077157.launchpad@loganberry.canonical.com>

** Changed in: twisted (Debian)
       Status: Unknown => 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/1915819

Title:
  'NoneType' object has no attribute 'encode' in requestReceived() when
  multipart body doesn't include content-disposition

Status in twisted package in Ubuntu:
  Fix Released
Status in twisted source package in Focal:
  Fix Released
Status in twisted source package in Groovy:
  Fix Released
Status in twisted source package in Hirsute:
  Fix Released
Status in twisted package in Debian:
  New

Bug description:
  [impact]

  python-twisted errors out with "'NoneType' object has no attribute
  'encode' in requestReceived()" when it tries to parse a multipart mime
  message and python3.7+ is used. This happens because before commit
  cc3fa20 in cpython, cgi.parse_multipart ignored parts without a name
  defined in "content-disposition" (or parts without headers for that
  matter) but after 3.7+ the return of the function can now contain
  NoneType keys, which fail to encode.

  [scope]

  Even though this bug affects all python3-twisted releases, I'll
  backport the fix just to Focal, Groovy and Hirsute. Bionic and Xenial
  do not have Python 3.7 as the default interpreter (required to trigger
  the issue), and the delta in python3-twisted might be to big to
  backport as the current packages do not contemplate _PY37PLUS at all.

  Fixed upstream with commit 310496249, available since 21.2.0rc1

  [test case]

  1. Save the following code as webserver.py

  from twisted.application.internet import TCPServer
  from twisted.application.service import Application
  from twisted.web.resource import Resource
  from twisted.web.server import Site

  class Foo(Resource):
      def render_POST(self, request):
          newdata = request.content.getvalue()
          print(newdata)
          return ''

  root = Resource()
  root.putChild("foo", Foo())
  application = Application("cgi.parse_multipart test")
  TCPServer(8080, Site(root)).setServiceParent(application)

  2. Save the following code as client.py (python3-httplib2 is required)

  #!/usr/bin/env python
  import httplib2

  def http_request(url, method, body=None, headers=None, insecure=False):
      """Issue an http request."""
      http = httplib2.Http(disable_ssl_certificate_validation=insecure)
      if isinstance(url, bytes):
          url = url.decode("ascii")
      return http.request(url, method, body=body, headers=headers)

  url = "http://localhost:8080"
  method = "POST"
  headers = {'Content-Type': 'multipart/form-data; boundary="8825899812428059282"'}
  emptyh = '--8825899812428059282\n\n--8825899812428059282--'

  print("== BODY: " + emptyh + "\n")
  response, content = http_request(url, method, emptyh, headers)

  3. Run the server with "twistd3 -y webserver.py"
  4. Run the client
  5. twistd will fail to encode the key and will drop this traceback in the log file (twistd.log)

  2021-02-16T13:41:39+0100 [_GenericHTTPChannelProtocol,7,127.0.0.1] Unhandled Error
          Traceback (most recent call last):
            File "/usr/lib/python3/dist-packages/twisted/python/log.py", line 103, in callWithLogger
              return callWithContext({"system": lp}, func, *args, **kw)
            File "/usr/lib/python3/dist-packages/twisted/python/log.py", line 86, in callWithContext
              return context.call({ILogContext: newCtx}, func, *args, **kw)
            File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 122, in callWithContext
              return self.currentContext().callWithContext(ctx, func, *args, **kw)
            File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 85, in callWithContext
              return func(*args,**kw)
          --- <exception caught here> ---
            File "/usr/lib/python3/dist-packages/twisted/internet/posixbase.py", line 614, in _doReadOrWrite
              why = selectable.doRead()
            File "/usr/lib/python3/dist-packages/twisted/internet/tcp.py", line 243, in doRead
              return self._dataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/internet/tcp.py", line 249, in _dataReceived
              rval = self.protocol.dataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2952, in dataReceived
              return self._channel.dataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2245, in dataReceived
              return basic.LineReceiver.dataReceived(self, data)
            File "/usr/lib/python3/dist-packages/twisted/protocols/basic.py", line 579, in dataReceived
              why = self.rawDataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2252, in rawDataReceived
              self._transferDecoder.dataReceived(data)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 1699, in dataReceived
              finishCallback(data[contentLength:])
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2115, in _finishRequestBody
              self.allContentReceived()
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 2224, in allContentReceived
              req.requestReceived(command, path, version)
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 898, in requestReceived
              self.args.update({
            File "/usr/lib/python3/dist-packages/twisted/web/http.py", line 899, in <dictcomp>
              x.encode('iso-8859-1'): \
          builtins.AttributeError: 'NoneType' object has no attribute 'encode'

  [regression potential]

  This affects the returned dictionaries with non-str keys, which were
  discarded in python3.6 or earlier before they reached twisted, so
  patching this will make its behavior consistent.

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



From 1940629 at bugs.launchpad.net  Fri Aug 20 15:11:47 2021
From: 1940629 at bugs.launchpad.net (Colin Ian King)
Date: Fri, 20 Aug 2021 15:11:47 -0000
Subject: [Bug 1940629] Re: Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162947230791.30562.16283111275406923294.malone@soybean.canonical.com>

I've uploaded the fix for thermald_2.4.6-2 impish to debian, will get
this sync'd over the next 24-36 hours into ubuntu.

I've uploaded the fixed for hirsute and focal and renamed the patches so
that they are in numerical order in the patch series.


** Changed in: thermald (Ubuntu Hirsute)
       Status: New => In Progress

** Changed in: thermald (Ubuntu Focal)
       Status: New => In Progress

** Changed in: thermald (Ubuntu Focal)
     Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Hirsute)
     Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Hirsute)
   Importance: Undecided => Critical

** Changed in: thermald (Ubuntu Focal)
   Importance: Undecided => Critical

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

Title:
  Support Jasper Lake

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Focal:
  In Progress
Status in thermald source package in Hirsute:
  In Progress
Status in thermald source package in Impish:
  In Progress

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions



From 1940629 at bugs.launchpad.net  Fri Aug 20 15:13:16 2021
From: 1940629 at bugs.launchpad.net (Colin Ian King)
Date: Fri, 20 Aug 2021 15:13:16 -0000
Subject: [Bug 1940629] Re: Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162947239667.18136.4208303654144537665.malone@wampee.canonical.com>

Thanks Andi for original patches and the bug report.

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

Title:
  Support Jasper Lake

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Focal:
  In Progress
Status in thermald source package in Hirsute:
  In Progress
Status in thermald source package in Impish:
  In Progress

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions



From 1875015 at bugs.launchpad.net  Sat Aug 21 02:39:14 2021
From: 1875015 at bugs.launchpad.net (tim O)
Date: Sat, 21 Aug 2021 02:39:14 -0000
Subject: [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
References: <158781861088.16872.17051645934170578366.malonedeb@wampee.canonical.com>
Message-ID: <162951355444.24515.11003511436546080221.malone@chaenomeles.canonical.com>

This issue should be resolved with 1.20.12 on Focal? Do the expected
release date will be? Thank you

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

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Hirsute:
  In Progress
Status in xorg-server source package in Impish:
  Fix Committed

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1875015/+subscriptions



From 1939751 at bugs.launchpad.net  Sat Aug 21 05:00:00 2021
From: 1939751 at bugs.launchpad.net (Bug Watch Updater)
Date: Sat, 21 Aug 2021 05:00:00 -0000
Subject: [Bug 1939751] Re: openssh FTBFS with glibc >= 2.34
References: <162880212312.6537.6691163062217728505.malonedeb@chaenomeles.canonical.com>
Message-ID: <162952200226.3010.17574736681967175905.launchpad@loganberry.canonical.com>

** Changed in: openssh (Debian)
       Status: Unknown => 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/1939751

Title:
  openssh FTBFS with glibc >= 2.34

Status in openssh package in Ubuntu:
  Confirmed
Status in openssh package in Debian:
  Fix Released

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

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



From 1940743 at bugs.launchpad.net  Sat Aug 21 13:56:51 2021
From: 1940743 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 21 Aug 2021 13:56:51 -0000
Subject: [Bug 1940743] [NEW] Sync awf-gtk 2.5.0-5 (universe) from Debian
 experimental (main)
References: <162955420919.1675.3171369079238197476.malonedeb@wampee.canonical.com>
Message-ID: <162955421140.22293.17388710754470852690.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Fabrice Creuzot (luigifab):

Please sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)

I am the developer of the program. I packaged and submitted it to Debian.
The package was accepted and uploaded to Debian experimental.
This is a new package for Ubuntu.

There is a little error with the changelog date.

All changelog entries:

awf-gtk (2.5.0-5) experimental; urgency=low

  * Initial debian package release (Closes: #959434)

 -- Fabrice Creuzot <code at luigifab.fr>  Thu, 09 Sep 2021 20:00:00 +0000

** Affects: ubuntu
     Importance: Undecided
         Status: New

-- 
Sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)
https://bugs.launchpad.net/bugs/1940743
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940743 at bugs.launchpad.net  Sat Aug 21 14:14:15 2021
From: 1940743 at bugs.launchpad.net (Fabrice Creuzot)
Date: Sat, 21 Aug 2021 14:14:15 -0000
Subject: [Bug 1940743] Re: Sync awf-gtk 2.5.0-5 (universe) from Debian
 experimental (main)
References: <162955420919.1675.3171369079238197476.malonedeb@wampee.canonical.com>
Message-ID: <162955525577.28069.13180885438532842842.malone@gac.canonical.com>

If new GTK 2 package is acceptable in Ubuntu, the source package can
also build a GTK 2 version of the program.

(The Debian package currently build a version for GTK 3 and a version
for GTK 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/1940743

Title:
  Sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)

Status in Ubuntu:
  New

Bug description:
  Please sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)

  I am the developer of the program. I packaged and submitted it to Debian.
  The package was accepted and uploaded to Debian experimental.
  This is a new package for Ubuntu.

  There is a little error with the changelog date.

  All changelog entries:

  awf-gtk (2.5.0-5) experimental; urgency=low

    * Initial debian package release (Closes: #959434)

   -- Fabrice Creuzot <code at luigifab.fr>  Thu, 09 Sep 2021 20:00:00
  +0000

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



From 1940743 at bugs.launchpad.net  Sat Aug 21 16:28:12 2021
From: 1940743 at bugs.launchpad.net (Paul White)
Date: Sat, 21 Aug 2021 16:28:12 -0000
Subject: [Bug 1940743] Re: Sync awf-gtk 2.5.0-5 (universe) from Debian
 experimental (main)
References: <162955420919.1675.3171369079238197476.malonedeb@wampee.canonical.com>
Message-ID: <162956329269.1847.2017822091462832688.launchpad@wampee.canonical.com>

** Tags added: needs-packaging

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

Title:
  Sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)

Status in Ubuntu:
  New

Bug description:
  Please sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)

  I am the developer of the program. I packaged and submitted it to Debian.
  The package was accepted and uploaded to Debian experimental.
  This is a new package for Ubuntu.

  There is a little error with the changelog date.

  All changelog entries:

  awf-gtk (2.5.0-5) experimental; urgency=low

    * Initial debian package release (Closes: #959434)

   -- Fabrice Creuzot <code at luigifab.fr>  Thu, 09 Sep 2021 20:00:00
  +0000

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



From 1940743 at bugs.launchpad.net  Sat Aug 21 23:55:03 2021
From: 1940743 at bugs.launchpad.net (Brian Murray)
Date: Sat, 21 Aug 2021 23:55:03 -0000
Subject: [Bug 1940743] Re: [needs-packaging] Sync awf-gtk 2.5.0-5 (universe)
 from Debian experimental (main)
References: <162955420919.1675.3171369079238197476.malonedeb@wampee.canonical.com>
Message-ID: <162959010371.23455.1997977179048366712.malone@wampee.canonical.com>

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

- Sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)
+ [needs-packaging] Sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)

** Changed in: 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/1940743

Title:
  [needs-packaging] Sync awf-gtk 2.5.0-5 (universe) from Debian
  experimental (main)

Status in Ubuntu:
  New

Bug description:
  Please sync awf-gtk 2.5.0-5 (universe) from Debian experimental (main)

  I am the developer of the program. I packaged and submitted it to Debian.
  The package was accepted and uploaded to Debian experimental.
  This is a new package for Ubuntu.

  There is a little error with the changelog date.

  All changelog entries:

  awf-gtk (2.5.0-5) experimental; urgency=low

    * Initial debian package release (Closes: #959434)

   -- Fabrice Creuzot <code at luigifab.fr>  Thu, 09 Sep 2021 20:00:00
  +0000

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



From 1879923 at bugs.launchpad.net  Sun Aug 22 13:26:17 2021
From: 1879923 at bugs.launchpad.net (Brian Murray)
Date: Sun, 22 Aug 2021 13:26:17 -0000
Subject: [Bug 1879923] Re: Update Scan Data Over Internet fails
References: <159005701176.1272.4566518412318297427.malonedeb@chaenomeles.canonical.com>
Message-ID: <162963877719.6588.2136207412016121850.malone@gac.canonical.com>

I've uploaded this for Impish.

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

Title:
  Update Scan Data Over Internet fails

Status in Kaffeine:
  Fix Released
Status in kaffeine package in Ubuntu:
  In Progress

Bug description:
  Workaround from Tj; 3 commands (ignore word-wrapping by launchpad):

  cd ~/.local/share/kaffeine
  mv scanfile.dvb{,.$(awk 'C==1{print;exit}/^\[date\]/{C=1}' scanfile.dvb)}
  wget https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/scantable.dvb -O scanfile.dvb

  ----

  
  Running Kaffeine 2.0.18 on Ubuntu 20.04 LTS Plasma Desktop.  Update Scan Data Over Internet fails with message: Scan data update failed

  I believe Kaffeine is looking for a file called scanfile.dvb or
  perhaps scanfile.dvb.qz

  https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/ shows a file
  called scantable.dvb  (Different file name)

  The wiki here (https://linuxtv.org/wiki/index.php/Dtv-scan-tables)
  says that this file will be autocreated and eventually be located
  here: https://autoconfig.kde.org/kaffeine/  The file i see at  this
  location is currently called: scantable.dvb.qz

  Perhaps this is just a file naming issue?

  Thanks,

  Iestyn Guest

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



From 1931857 at bugs.launchpad.net  Mon Aug 23 01:05:35 2021
From: 1931857 at bugs.launchpad.net (Mathew Hodson)
Date: Mon, 23 Aug 2021 01:05:35 -0000
Subject: [Bug 1931857] Re: [21.10 FEAT] Update PCRE2 for JIT and Performance
 Improvements on s390x
References: <162367016246.10774.11824450368735290843.malonedeb@wampee.canonical.com>
Message-ID: <162968073610.14879.5960994967065878672.launchpad@gac.canonical.com>

** Changed in: pcre2 (Ubuntu)
   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/1931857

Title:
  [21.10 FEAT] Update PCRE2 for JIT and Performance Improvements on
  s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in pcre2 package in Ubuntu:
  Fix Committed

Bug description:
  PCRE2 version 10.37 as available from https://ftp.pcre.org/pub/pcre/
  contains the enablement of the JIT and provides some performance improvements

  Version 10.38 to be released in November or December 2021 will contain
  the complete implementation with full JIT performance.

  To pick up the changes please configure with "--enable-jit" for s390x.

  It may be beneficial to rebuild certain dependent packages after that
  change, such as haproxy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931857/+subscriptions



From 1879923 at bugs.launchpad.net  Mon Aug 23 01:04:45 2021
From: 1879923 at bugs.launchpad.net (Mathew Hodson)
Date: Mon, 23 Aug 2021 01:04:45 -0000
Subject: [Bug 1879923] Re: Update Scan Data Over Internet fails
References: <159005701176.1272.4566518412318297427.malonedeb@chaenomeles.canonical.com>
Message-ID: <162968068654.331.3202684109211118094.launchpad@soybean.canonical.com>

** Changed in: kaffeine (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/1879923

Title:
  Update Scan Data Over Internet fails

Status in Kaffeine:
  Fix Released
Status in kaffeine package in Ubuntu:
  In Progress

Bug description:
  Workaround from Tj; 3 commands (ignore word-wrapping by launchpad):

  cd ~/.local/share/kaffeine
  mv scanfile.dvb{,.$(awk 'C==1{print;exit}/^\[date\]/{C=1}' scanfile.dvb)}
  wget https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/scantable.dvb -O scanfile.dvb

  ----

  
  Running Kaffeine 2.0.18 on Ubuntu 20.04 LTS Plasma Desktop.  Update Scan Data Over Internet fails with message: Scan data update failed

  I believe Kaffeine is looking for a file called scanfile.dvb or
  perhaps scanfile.dvb.qz

  https://linuxtv.org/downloads/dtv-scan-tables/kaffeine/ shows a file
  called scantable.dvb  (Different file name)

  The wiki here (https://linuxtv.org/wiki/index.php/Dtv-scan-tables)
  says that this file will be autocreated and eventually be located
  here: https://autoconfig.kde.org/kaffeine/  The file i see at  this
  location is currently called: scantable.dvb.qz

  Perhaps this is just a file naming issue?

  Thanks,

  Iestyn Guest

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



From 1929046 at bugs.launchpad.net  Mon Aug 23 01:07:31 2021
From: 1929046 at bugs.launchpad.net (Mathew Hodson)
Date: Mon, 23 Aug 2021 01:07:31 -0000
Subject: [Bug 1929046] Re: [21.10 FEAT] Upgrade cryptsetup to latest version
 (crypto) (2.3.6)
References: <162150596757.761.5742760700633395945.malonedeb@soybean.canonical.com>
Message-ID: <162968085283.28034.10345802679279949990.launchpad@chaenomeles.canonical.com>

** Changed in: cryptsetup (Ubuntu)
   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/1929046

Title:
  [21.10 FEAT] Upgrade cryptsetup to latest version (crypto) (2.3.6)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in cryptsetup package in Ubuntu:
  Fix Committed

Bug description:
  Upgrade cryptsetup to latest version 2.3.5

  https://gitlab.com/cryptsetup/cryptsetup/-/tags/v2.3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929046/+subscriptions



From 1940336 at bugs.launchpad.net  Mon Aug 23 01:13:04 2021
From: 1940336 at bugs.launchpad.net (Mathew Hodson)
Date: Mon, 23 Aug 2021 01:13:04 -0000
Subject: [Bug 1940336] Re: Test wsh-libs.wsh causing segfault with glibc >=
 2.34
References: <162924551878.15261.9944361587170333186.malonedeb@chaenomeles.canonical.com>
Message-ID: <162968118553.5331.5131203585984936104.launchpad@wampee.canonical.com>

** Changed in: wcc (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/1940336

Title:
  Test wsh-libs.wsh causing segfault with glibc >= 2.34

Status in wcc package in Ubuntu:
  In Progress

Bug description:
  This package has failing autopkgtests with glibc 2.34. There is a
  segmentation fault somewhere in the wsh code.

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



From 1937980 at bugs.launchpad.net  Mon Aug 23 02:28:28 2021
From: 1937980 at bugs.launchpad.net (Hui Wang)
Date: Mon, 23 Aug 2021 02:28:28 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <162968570853.20779.2052408947231073717.malone@wampee.canonical.com>

Re-write this SRU based on the latest ubuntu alsa-ucm-conf, and also
integrate another SRU (https://bugs.launchpad.net/ubuntu/+source/alsa-
ucm-conf/+bug/1940788)

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

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in alsa-ucm-conf source package in Hirsute:
  New
Status in alsa-ucm-conf source package in Impish:
  New

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1937980 at bugs.launchpad.net  Mon Aug 23 02:29:55 2021
From: 1937980 at bugs.launchpad.net (Hui Wang)
Date: Mon, 23 Aug 2021 02:29:55 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <162968579549.9569.16651837554974890090.malone@chaenomeles.canonical.com>

Hi sponsor team, This is the debdiff for hirsute. thx.



** Patch added: "alsa-ucm-conf_1.2.4-2ubuntu1.3.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980/+attachment/5519900/+files/alsa-ucm-conf_1.2.4-2ubuntu1.3.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/1937980

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in alsa-ucm-conf source package in Hirsute:
  New
Status in alsa-ucm-conf source package in Impish:
  New

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1937980 at bugs.launchpad.net  Mon Aug 23 02:45:55 2021
From: 1937980 at bugs.launchpad.net (Hui Wang)
Date: Mon, 23 Aug 2021 02:45:55 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <162968675570.14580.11594380955237418826.malone@chaenomeles.canonical.com>

Hi sponsor team, This is the debdiff for impish. thx.

** Patch added: "alsa-ucm-conf_1.2.4-2ubuntu4.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980/+attachment/5519901/+files/alsa-ucm-conf_1.2.4-2ubuntu4.debdiff

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Impish)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
     Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-ucm-conf (Ubuntu Focal)
     Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-ucm-conf (Ubuntu Focal)
       Status: New => 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/1937980

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1937980 at bugs.launchpad.net  Mon Aug 23 03:05:00 2021
From: 1937980 at bugs.launchpad.net (Hui Wang)
Date: Mon, 23 Aug 2021 03:05:00 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <162968790092.18206.14741042409373198383.malone@chaenomeles.canonical.com>

Hi sponsor team, This is the debdiff for impish. thx.

** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.10.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980/+attachment/5519903/+files/alsa-ucm-conf_1.2.2-1ubuntu0.10.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/1937980

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1937980 at bugs.launchpad.net  Mon Aug 23 03:05:59 2021
From: 1937980 at bugs.launchpad.net (Hui Wang)
Date: Mon, 23 Aug 2021 03:05:59 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <162968795972.26805.13377234997426380056.malone@wampee.canonical.com>

Hi sponsor team, This is the debdiff for focal. thx.

** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.10.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980/+attachment/5519904/+files/alsa-ucm-conf_1.2.2-1ubuntu0.10.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/1937980

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1940788 at bugs.launchpad.net  Mon Aug 23 03:28:47 2021
From: 1940788 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 23 Aug 2021 03:28:47 -0000
Subject: [Bug 1940788] [NEW] [SRU] the input volume of external mic for sof
 driver is 0 by default
References: <162968267413.21155.6753654366276453288.malonedeb@gac.canonical.com>
Message-ID: <162968932830.6567.7933787912016850784.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Hui Wang (hui.wang):

This bug is for tracking purpose.

https://github.com/alsa-project/alsa-ucm-conf/pull/107

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

** Affects: alsa-ucm-conf (Ubuntu)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: New

** Affects: alsa-ucm-conf (Ubuntu Focal)
     Importance: High
         Status: New

** Affects: alsa-ucm-conf (Ubuntu Hirsute)
     Importance: High
         Status: New

** Affects: alsa-ucm-conf (Ubuntu Impish)
     Importance: High
     Assignee: Hui Wang (hui.wang)
         Status: New


** Tags: oem-priority originate-from-1936797 originate-from-1937887 somerville
-- 
[SRU] the input volume of external mic for sof driver is 0 by default
https://bugs.launchpad.net/bugs/1940788
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940788 at bugs.launchpad.net  Mon Aug 23 03:31:30 2021
From: 1940788 at bugs.launchpad.net (Hui Wang)
Date: Mon, 23 Aug 2021 03:31:30 -0000
Subject: [Bug 1940788] Re: [SRU] the input volume of external mic for sof
 driver is 0 by default
References: <162968267413.21155.6753654366276453288.malonedeb@gac.canonical.com>
Message-ID: <162968949096.23399.8829986238665293954.malone@chaenomeles.canonical.com>

the debdiff of this SRU has been squashed to
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980.


** Description changed:

- This bug is for tracking purpose.
+ The change of this SRU has been squashed to
+ https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980.
  
- https://github.com/alsa-project/alsa-ucm-conf/pull/107
+ [Impact]
+ For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully.
+ 
+ [Fix]
+ Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume.
+ 
+ [Test]
+ sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully.
+ 
+ [Where problems will occur]
+ This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well.

** Changed in: alsa-ucm-conf (Ubuntu Focal)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Impish)
       Status: New => In Progress

** Tags added: originate-from-1940339

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

Title:
  [SRU] the input volume of external mic for sof driver is 0 by default

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress

Bug description:
  The change of this SRU has been squashed to
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980.

  [Impact]
  For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully.

  [Fix]
  Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume.

  [Test]
  sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully.

  [Where problems will occur]
  This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions



From 1940788 at bugs.launchpad.net  Mon Aug 23 03:58:06 2021
From: 1940788 at bugs.launchpad.net (Hui Wang)
Date: Mon, 23 Aug 2021 03:58:06 -0000
Subject: [Bug 1940788] Re: [SRU] the input volume of external mic for sof
 driver is 0 by default
References: <162968267413.21155.6753654366276453288.malonedeb@gac.canonical.com>
Message-ID: <162969108703.13720.10411631506663507486.launchpad@gac.canonical.com>

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
     Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-ucm-conf (Ubuntu Focal)
     Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  [SRU] the input volume of external mic for sof driver is 0 by default

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress

Bug description:
  The change of this SRU has been squashed to
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980.

  [Impact]
  For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully.

  [Fix]
  Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume.

  [Test]
  sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully.

  [Where problems will occur]
  This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions



From 1938438 at bugs.launchpad.net  Mon Aug 23 08:12:07 2021
From: 1938438 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Mon, 23 Aug 2021 08:12:07 -0000
Subject: [Bug 1938438] Re: sbsigntool does not build on riscv64
References: <162755865747.27382.10177718520268360098.malonedeb@chaenomeles.canonical.com>
Message-ID: <162970632741.3099.11578510346847570417.malone@gac.canonical.com>

sbsigntool_0.9.4-2ubuntu2 is available in ppa:xypron/gnu-efi for upload
to Impish.

** Patch added: "Diff from Debian 0.9.4-2 to Ubuntu 0.9.4-2ubuntu2"
   https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1938438/+attachment/5519934/+files/debian-0.9.4_to_ubuntu.new.diff

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

Title:
  sbsigntool does not build on riscv64

Status in sbsigntool package in Ubuntu:
  New

Bug description:
  We should enable building on riscv64 for release Impish.

  Current upstream version 0.9.4 is required for running U-Boot tests.

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



From 1940816 at bugs.launchpad.net  Mon Aug 23 13:53:16 2021
From: 1940816 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 23 Aug 2021 13:53:16 -0000
Subject: [Bug 1940816] [NEW] Autopkgtest fail with glibc 2.34
References: <162971257913.6852.5493409487311058013.malonedeb@chaenomeles.canonical.com>
Message-ID: <162972679642.10039.7036103869165715030.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

The autopkgtests fail with glibc 2.34, while running them with the plain
impish.

The superficial failure is that the script cannot find the expected
window name. Looking into it, it appears that this might be caused by
wmanager displaying an error popup instead of its main window. One
possible reason for such popup is not being able to read the wmanagerrc
file, which defaults in $HOME/.wmanagerrc (but the script sets it to a
custom location in /tmp).

Next step will be to find out exactly the cause of the failure.

** Affects: wmanager (Ubuntu)
     Importance: Undecided
     Assignee: Simon Chopin (schopin)
         Status: In Progress


** Tags: update-excuse
-- 
Autopkgtest fail with glibc 2.34
https://bugs.launchpad.net/bugs/1940816
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1938259 at bugs.launchpad.net  Mon Aug 23 14:38:44 2021
From: 1938259 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 23 Aug 2021 14:38:44 -0000
Subject: [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell
 models
References: <162745556987.5514.108453593921646683.malonedeb@wampee.canonical.com>
Message-ID: <162972952955.23502.4384734588118586900.launchpad@ackee.canonical.com>

** Merge proposal linked:
   https://code.launchpad.net/~hypothetical-lemon/ubuntu/+source/systemd/+git/systemd/+merge/407548

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  In Progress

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel 5.13, or kernel with this patch backported:
      https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions



From 1938259 at bugs.launchpad.net  Mon Aug 23 14:54:55 2021
From: 1938259 at bugs.launchpad.net (Heather Lemon)
Date: Mon, 23 Aug 2021 14:54:55 -0000
Subject: [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell
 models
References: <162745556987.5514.108453593921646683.malonedeb@wampee.canonical.com>
Message-ID: <162973049536.23279.1860382378182809580.launchpad@soybean.canonical.com>

** Merge proposal unlinked:
   https://code.launchpad.net/~hypothetical-lemon/ubuntu/+source/systemd/+git/systemd/+merge/407548

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  In Progress

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel 5.13, or kernel with this patch backported:
      https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions



From 1938259 at bugs.launchpad.net  Mon Aug 23 14:55:55 2021
From: 1938259 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 23 Aug 2021 14:55:55 -0000
Subject: [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell
 models
References: <162745556987.5514.108453593921646683.malonedeb@wampee.canonical.com>
Message-ID: <162973055598.23502.14679292725867960379.launchpad@ackee.canonical.com>

** Merge proposal linked:
   https://code.launchpad.net/~hypothetical-lemon/ubuntu/+source/systemd/+git/systemd/+merge/407551

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  In Progress

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel 5.13, or kernel with this patch backported:
      https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions



From 1938259 at bugs.launchpad.net  Mon Aug 23 14:57:32 2021
From: 1938259 at bugs.launchpad.net (Heather Lemon)
Date: Mon, 23 Aug 2021 14:57:32 -0000
Subject: [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell
 models
References: <162745556987.5514.108453593921646683.malonedeb@wampee.canonical.com>
Message-ID: <162973065312.23764.13852237502643631935.launchpad@soybean.canonical.com>

** Merge proposal unlinked:
   https://code.launchpad.net/~hypothetical-lemon/ubuntu/+source/systemd/+git/systemd/+merge/407551

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  In Progress

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel 5.13, or kernel with this patch backported:
      https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions



From 1940816 at bugs.launchpad.net  Mon Aug 23 14:58:29 2021
From: 1940816 at bugs.launchpad.net (Simon Chopin)
Date: Mon, 23 Aug 2021 14:58:29 -0000
Subject: [Bug 1940816] Re: Autopkgtest fail with glibc 2.34
References: <162971257913.6852.5493409487311058013.malonedeb@chaenomeles.canonical.com>
Message-ID: <162973070924.32284.5700751735486112172.malone@wampee.canonical.com>

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

Title:
  Autopkgtest fail with glibc 2.34

Status in wmanager package in Ubuntu:
  In Progress

Bug description:
  The autopkgtests fail with glibc 2.34, while running them with the
  plain impish.

  The superficial failure is that the script cannot find the expected
  window name. Looking into it, it appears that this might be caused by
  wmanager displaying an error popup instead of its main window. One
  possible reason for such popup is not being able to read the
  wmanagerrc file, which defaults in $HOME/.wmanagerrc (but the script
  sets it to a custom location in /tmp).

  Next step will be to find out exactly the cause of the failure.

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



From 1940816 at bugs.launchpad.net  Mon Aug 23 15:00:48 2021
From: 1940816 at bugs.launchpad.net (Simon Chopin)
Date: Mon, 23 Aug 2021 15:00:48 -0000
Subject: [Bug 1940816] Re: Autopkgtest fail with glibc 2.34
References: <162971257913.6852.5493409487311058013.malonedeb@chaenomeles.canonical.com>
Message-ID: <162973084816.20436.16403938641827908397.malone@chaenomeles.canonical.com>

New version with DEP-3 Forwarded field and LP bug number in changelog.

** Patch added: "wmanager.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/wmanager/+bug/1940816/+attachment/5520013/+files/wmanager.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/1940816

Title:
  Autopkgtest fail with glibc 2.34

Status in wmanager package in Ubuntu:
  In Progress

Bug description:
  The autopkgtests fail with glibc 2.34, while running them with the
  plain impish.

  The superficial failure is that the script cannot find the expected
  window name. Looking into it, it appears that this might be caused by
  wmanager displaying an error popup instead of its main window. One
  possible reason for such popup is not being able to read the
  wmanagerrc file, which defaults in $HOME/.wmanagerrc (but the script
  sets it to a custom location in /tmp).

  Next step will be to find out exactly the cause of the failure.

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



From 1938259 at bugs.launchpad.net  Mon Aug 23 15:06:44 2021
From: 1938259 at bugs.launchpad.net (Dan Streetman)
Date: Mon, 23 Aug 2021 15:06:44 -0000
Subject: [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell
 models
References: <162745556987.5514.108453593921646683.malonedeb@wampee.canonical.com>
Message-ID: <162973120426.6903.7496773708344418348.malone@gac.canonical.com>

> When will we upload the changes to -proposed?

i'll upload this week, so hopefully it can be released next week. The
focal point release is this week, so review of the upload may be
delayed, but hopefully not much.

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  In Progress

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel 5.13, or kernel with this patch backported:
      https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions



From 1939918 at bugs.launchpad.net  Mon Aug 23 16:30:08 2021
From: 1939918 at bugs.launchpad.net (Matthias Klose)
Date: Mon, 23 Aug 2021 16:30:08 -0000
Subject: [Bug 1939918] Re: FTBFS against glibc 2.34
References: <162888353293.31443.7107257617651384274.malonedeb@wampee.canonical.com>
Message-ID: <162973620958.24926.2421615853591151961.launchpad@wampee.canonical.com>

** Changed in: libnss-db (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/1939918

Title:
  FTBFS against glibc 2.34

Status in libnss-db package in Ubuntu:
  Fix Committed

Bug description:
  The package libnss-db failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-db/+bug/1939918/+subscriptions



From 1932076 at bugs.launchpad.net  Mon Aug 23 18:59:48 2021
From: 1932076 at bugs.launchpad.net (Lucas Kanashiro)
Date: Mon, 23 Aug 2021 18:59:48 -0000
Subject: [Bug 1932076] Re: src:request-tracker5: ftbfs due to changes in gpg
 error messages
References: <162379050282.13849.15848709508592262107.malonedeb@wampee.canonical.com>
Message-ID: <162974518837.29540.4690979268027379477.malone@gac.canonical.com>

After talking to bdmurray on IRC, I am uploading both packages, request-
tracker4 and request-tracker5 (attached debdiffs).

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

Title:
  src:request-tracker5: ftbfs due to changes in gpg error messages

Status in request-tracker4 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/988905:

  Package: src:request-tracker5
  Version: 5.0.1+dfsg-1
  Severity: serious
  Tags: ftbfs
  Justification: fails to build from source

  Dear Maintainer,

  As can be seen at

  https://tests.reproducible-builds.org/debian/rb-
  pkg/unstable/amd64/request-tracker5.html

  or

  https://launchpad.net/ubuntu/+source/request-tracker5/5.0.1+dfsg-1

  the package fails to build with the current state of unstable / Ubuntu
  impish.

  The failures are:

  #   Failed test at t/mail/crypt-gnupg.t line 171.
  # found warning: gpg: error retrieving 'keyless at example.com' via WKD: Server indicated a failure
  # expected to find warning: (?^:public key not found|error retrieving 'keyless\@example.com' via WKD: No data)

  #   Failed test at t/web/crypt-gnupg.t line 358.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  #   Failed test at t/web/crypt-gnupg.t line 380.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  (the messages are actually slightly different in Ubuntu). This seems
  pretty benign really and probably the tests should be relaxed?

  Cheers,
  mwh

  -- System Information:
  Debian Release: bullseye/sid
    APT prefers focal-updates
    APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.4.0-73-generic (SMP w/8 CPU cores)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/request-tracker4/+bug/1932076/+subscriptions



From 1940816 at bugs.launchpad.net  Mon Aug 23 20:08:49 2021
From: 1940816 at bugs.launchpad.net (Brian Murray)
Date: Mon, 23 Aug 2021 20:08:49 -0000
Subject: [Bug 1940816] Re: Autopkgtest fail with glibc 2.34
References: <162971257913.6852.5493409487311058013.malonedeb@chaenomeles.canonical.com>
Message-ID: <162974932930.13971.1838590679827640862.malone@wampee.canonical.com>

$ dput wmanager_0.3.0-2ubuntu1_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /tmp/pkgs/impish/wmanager_0.3.0-2ubuntu1_source.changes: Valid signature from 1E918B66765B3E31
Checking signature on .dsc
gpg: /tmp/pkgs/impish/wmanager_0.3.0-2ubuntu1.dsc: Valid signature from 1E918B66765B3E31
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading wmanager_0.3.0-2ubuntu1.dsc: done.
  Uploading wmanager_0.3.0-2ubuntu1.debian.tar.xz: done.
  Uploading wmanager_0.3.0-2ubuntu1_source.buildinfo: done.
  Uploading wmanager_0.3.0-2ubuntu1_source.changes: done.
Successfully uploaded packages.

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

Title:
  Autopkgtest fail with glibc 2.34

Status in wmanager package in Ubuntu:
  In Progress

Bug description:
  The autopkgtests fail with glibc 2.34, while running them with the
  plain impish.

  The superficial failure is that the script cannot find the expected
  window name. Looking into it, it appears that this might be caused by
  wmanager displaying an error popup instead of its main window. One
  possible reason for such popup is not being able to read the
  wmanagerrc file, which defaults in $HOME/.wmanagerrc (but the script
  sets it to a custom location in /tmp).

  Next step will be to find out exactly the cause of the failure.

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



From 1932076 at bugs.launchpad.net  Tue Aug 24 01:21:48 2021
From: 1932076 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 24 Aug 2021 01:21:48 -0000
Subject: [Bug 1932076] Re: src:request-tracker5: ftbfs due to changes in gpg
 error messages
References: <162379050282.13849.15848709508592262107.malonedeb@wampee.canonical.com>
Message-ID: <162976811100.22977.2462823229751000935.malone@ackee.canonical.com>

This bug was fixed in the package request-tracker4 - 4.4.4+dfsg-2ubuntu1

---------------
request-tracker4 (4.4.4+dfsg-2ubuntu1) impish; urgency=medium

  * d/p/rt_test_gnupg_disable_wkd.diff: Backport patch from Debian to disable
    using WKD on GnuPG tests that might attempt to use the network (LP: #1932076).

 -- Lucas Kanashiro <kanashiro at ubuntu.com>  Thu, 19 Aug 2021 11:15:04
-0300

** Changed in: request-tracker4 (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  src:request-tracker5: ftbfs due to changes in gpg error messages

Status in request-tracker4 package in Ubuntu:
  Fix Released
Status in request-tracker5 package in Ubuntu:
  Confirmed
Status in request-tracker5 package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/988905:

  Package: src:request-tracker5
  Version: 5.0.1+dfsg-1
  Severity: serious
  Tags: ftbfs
  Justification: fails to build from source

  Dear Maintainer,

  As can be seen at

  https://tests.reproducible-builds.org/debian/rb-
  pkg/unstable/amd64/request-tracker5.html

  or

  https://launchpad.net/ubuntu/+source/request-tracker5/5.0.1+dfsg-1

  the package fails to build with the current state of unstable / Ubuntu
  impish.

  The failures are:

  #   Failed test at t/mail/crypt-gnupg.t line 171.
  # found warning: gpg: error retrieving 'keyless at example.com' via WKD: Server indicated a failure
  # expected to find warning: (?^:public key not found|error retrieving 'keyless\@example.com' via WKD: No data)

  #   Failed test at t/web/crypt-gnupg.t line 358.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  #   Failed test at t/web/crypt-gnupg.t line 380.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  (the messages are actually slightly different in Ubuntu). This seems
  pretty benign really and probably the tests should be relaxed?

  Cheers,
  mwh

  -- System Information:
  Debian Release: bullseye/sid
    APT prefers focal-updates
    APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.4.0-73-generic (SMP w/8 CPU cores)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/request-tracker4/+bug/1932076/+subscriptions



From 1940788 at bugs.launchpad.net  Tue Aug 24 06:44:53 2021
From: 1940788 at bugs.launchpad.net (Hui Wang)
Date: Tue, 24 Aug 2021 06:44:53 -0000
Subject: [Bug 1940788] Re: [SRU] the input volume of external mic for sof
 driver is 0 by default
References: <162968267413.21155.6753654366276453288.malonedeb@gac.canonical.com>
Message-ID: <162978749391.1590.6798508475545362408.malone@chaenomeles.canonical.com>

The https://github.com/alsa-project/alsa-ucm-conf/pull/107 was merged to
upstream last night.

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

Title:
  [SRU] the input volume of external mic for sof driver is 0 by default

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress

Bug description:
  The change of this SRU has been squashed to
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980.

  [Impact]
  For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully.

  [Fix]
  Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume.

  [Test]
  sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully.

  [Where problems will occur]
  This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions



From 1937980 at bugs.launchpad.net  Tue Aug 24 06:45:44 2021
From: 1937980 at bugs.launchpad.net (Hui Wang)
Date: Tue, 24 Aug 2021 06:45:44 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <162978754431.3378.6659779437296970541.malone@chaenomeles.canonical.com>

The https://github.com/alsa-project/alsa-ucm-conf/pull/109 and
https://github.com/alsa-project/alsa-ucm-conf/pull/107 were merged to
upstream last night.

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

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1939751 at bugs.launchpad.net  Tue Aug 24 08:11:53 2021
From: 1939751 at bugs.launchpad.net (=?utf-8?q?Christian_Ehrhardt_=EE=83=BF?=)
Date: Tue, 24 Aug 2021 08:11:53 -0000
Subject: [Bug 1939751] Re: openssh FTBFS with glibc >= 2.34
References: <162880212312.6537.6691163062217728505.malonedeb@chaenomeles.canonical.com>
Message-ID: <162979271335.7477.7683735616700809042.malone@wampee.canonical.com>

This update includes one of the two changes we have as delta.
Another Fix (group collisions) and the fix for this issue here.

I think despite FF, this could be re-merged to resolve this and the other mentioned bugs.
I'll tag it to be more likely to be considered.

But to avoid collisions @William (or @cjatson) are you about to do that
merge already?

** Changed in: openssh (Ubuntu)
       Status: Confirmed => Triaged

** Tags added: server-next

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

Title:
  openssh FTBFS with glibc >= 2.34

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Fix Released

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

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



From 1921658 at bugs.launchpad.net  Tue Aug 24 08:17:05 2021
From: 1921658 at bugs.launchpad.net (Seyeong Kim)
Date: Tue, 24 Aug 2021 08:17:05 -0000
Subject: [Bug 1921658] Re: Can't compose kvm host with lvm storage on maas
 2.8.4 
References: <161697993430.18838.13362103946863867785.malonedeb@gac.canonical.com>
Message-ID: <162979302545.25882.17579336727500142266.malone@chaenomeles.canonical.com>

@ddstreet

sorry for late response, I updated description.

Thanks.

** Description changed:

+ [Impact]
+ 
  I can't compose kvm host on maas 2.8.4 ( bionic)
  
  I upgraded twisted and related component with pip but the symptom is the
  same.
  
  MaaS 2.9.x in Focal works fine.
  
  in 2.8.x, pexpect virsh vol-path should return [2] but returns [3]
  
  [2]
  /dev/maas_data_vg/8d4e8b04-4031-4a1b-b5f2-a8306192db11
  [3]
  2021-03-17 20:43:34 stderr: [error] Message: 'this is the result...\n'
  2021-03-17 20:43:34 stderr: [error] Arguments: ([' ', '<3ef-46ca-87c8-19171950592f --pool maas_guest_lvm_vg', "error: command 'attach-disk' doesn't support option --pool"],)
  
  sometimes it fails in
  
-     def get_volume_path(self, pool, volume):
-         """Return the path to the file from `pool` and `volume`."""
-         output = self.run(["vol-path", volume, "--pool", pool])
-         return output.strip()
+     def get_volume_path(self, pool, volume):
+         """Return the path to the file from `pool` and `volume`."""
+         output = self.run(["vol-path", volume, "--pool", pool])
+         return output.strip()
  
  sometimes failes in
  
-     def get_machine_xml(self, machine):
-         # Check if we have a cached version of the XML.
-         # This is a short-lived object, so we don't need to worry about
-         # expiring objects in the cache.
-         if machine in self.xml:
-             return self.xml[machine]
+     def get_machine_xml(self, machine):
+         # Check if we have a cached version of the XML.
+         # This is a short-lived object, so we don't need to worry about
+         # expiring objects in the cache.
+         if machine in self.xml:
+             return self.xml[machine]
  
-         # Grab the XML from virsh if we don't have it already.
-         output = self.run(["dumpxml", machine]).strip()
-         if output.startswith("error:"):
-             maaslog.error("%s: Failed to get XML for machine", machine)
-             return None
+         # Grab the XML from virsh if we don't have it already.
+         output = self.run(["dumpxml", machine]).strip()
+         if output.startswith("error:"):
+             maaslog.error("%s: Failed to get XML for machine", machine)
+             return None
  
-         # Cache the XML, since we'll need it later to reconfigure the VM.
-         self.xml[machine] = output
-         return output
+         # Cache the XML, since we'll need it later to reconfigure the VM.
+         self.xml[machine] = output
+         return output
  
  I assume that run function has issue.
  
  Command line virsh vol-path and simple pepect python code works fine.
  
- 
  Any advice for this issue?
  
  Thanks.
  
- Reproducer is below.[1]
+ [Test Plan]
  
- [1]
+ 0) deploy Bionic and MAAS 2.8
  
  1) Create file to be used as loopback device
  
  sudo dd if=/dev/zero of=lvm bs=16000 count=1M
  
  2) sudo losetup /dev/loop39 lvm
  
  3) sudo pvcreate /dev/loop39
  
  4) sudo vgcreate maas_data_vg /dev/loop39
  
  5) Save below xml:
  <pool type='logical'>
  <name>maas_guest_lvm_vg</name>
  <source>
  <name>maas_data_vg</name>
  <format type='lvm2'/>
  </source>
  <target>
  <path>/dev/maas_data_vg</path>
  </target>
  </pool>
  
  6) virsh pool-create maas_guest_lvm_vg.xml
  
  7) Add KVM host in MaaS
  
  8) Attempt to compose a POD using storage pool maas_guest_lvm_vg
  
  9) GUI will fail with:
  
  Pod unable to compose machine: Unable to compose machine because: Failed
  talking to pod: Start tag expected, '<' not found, line 1, column 1
  (<string>, line 1)
+ 
+ [Where problems could occer]
+ 
+ This patch is small peice of huge commit.
+ I tested by compiling test pkg with this patch. but actually it is kind of underlying library ( libreadline ), so It could affect to any application using libreadline.
+ e.g running command inside application by code can be affected.
+ 
+ 
+ [Other Info]

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

Title:
  Can't compose kvm host with lvm storage on maas 2.8.4

Status in MAAS:
  Triaged
Status in readline package in Ubuntu:
  Fix Released
Status in readline source package in Bionic:
  In Progress

Bug description:
  [Impact]

  I can't compose kvm host on maas 2.8.4 ( bionic)

  I upgraded twisted and related component with pip but the symptom is
  the same.

  MaaS 2.9.x in Focal works fine.

  in 2.8.x, pexpect virsh vol-path should return [2] but returns [3]

  [2]
  /dev/maas_data_vg/8d4e8b04-4031-4a1b-b5f2-a8306192db11
  [3]
  2021-03-17 20:43:34 stderr: [error] Message: 'this is the result...\n'
  2021-03-17 20:43:34 stderr: [error] Arguments: ([' ', '<3ef-46ca-87c8-19171950592f --pool maas_guest_lvm_vg', "error: command 'attach-disk' doesn't support option --pool"],)

  sometimes it fails in

      def get_volume_path(self, pool, volume):
          """Return the path to the file from `pool` and `volume`."""
          output = self.run(["vol-path", volume, "--pool", pool])
          return output.strip()

  sometimes failes in

      def get_machine_xml(self, machine):
          # Check if we have a cached version of the XML.
          # This is a short-lived object, so we don't need to worry about
          # expiring objects in the cache.
          if machine in self.xml:
              return self.xml[machine]

          # Grab the XML from virsh if we don't have it already.
          output = self.run(["dumpxml", machine]).strip()
          if output.startswith("error:"):
              maaslog.error("%s: Failed to get XML for machine", machine)
              return None

          # Cache the XML, since we'll need it later to reconfigure the VM.
          self.xml[machine] = output
          return output

  I assume that run function has issue.

  Command line virsh vol-path and simple pepect python code works fine.

  Any advice for this issue?

  Thanks.

  [Test Plan]

  0) deploy Bionic and MAAS 2.8

  1) Create file to be used as loopback device

  sudo dd if=/dev/zero of=lvm bs=16000 count=1M

  2) sudo losetup /dev/loop39 lvm

  3) sudo pvcreate /dev/loop39

  4) sudo vgcreate maas_data_vg /dev/loop39

  5) Save below xml:
  <pool type='logical'>
  <name>maas_guest_lvm_vg</name>
  <source>
  <name>maas_data_vg</name>
  <format type='lvm2'/>
  </source>
  <target>
  <path>/dev/maas_data_vg</path>
  </target>
  </pool>

  6) virsh pool-create maas_guest_lvm_vg.xml

  7) Add KVM host in MaaS

  8) Attempt to compose a POD using storage pool maas_guest_lvm_vg

  9) GUI will fail with:

  Pod unable to compose machine: Unable to compose machine because:
  Failed talking to pod: Start tag expected, '<' not found, line 1,
  column 1 (<string>, line 1)

  [Where problems could occer]

  This patch is small peice of huge commit.
  I tested by compiling test pkg with this patch. but actually it is kind of underlying library ( libreadline ), so It could affect to any application using libreadline.
  e.g running command inside application by code can be affected.

  
  [Other Info]

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



From 1921658 at bugs.launchpad.net  Tue Aug 24 08:48:12 2021
From: 1921658 at bugs.launchpad.net (Dariusz Gadomski)
Date: Tue, 24 Aug 2021 08:48:12 -0000
Subject: [Bug 1921658] Re: Can't compose kvm host with lvm storage on maas
 2.8.4 
References: <161697993430.18838.13362103946863867785.malonedeb@gac.canonical.com>
Message-ID: <162979489267.30891.11861197518927190766.malone@chaenomeles.canonical.com>

@seyeongkim hi, I'm working on sponsoring your patch right now.
I had to do some minor fixes in it:
1. Since we're adding delta in relation to Debian we should change version number to reflect that (e.g. 7.0-4ubuntu1).
2. The launchpad bug number has to follow the convention for the automation to correctly pick it up and close the bug automatically afterwards (i.e. LP: #1921658 and not "Closes: #1921658).
3. The patch header did not need the "+" signs in the beginning of the line.
4. There was a descriptive commit for one of the lines you backported (static int *local_prompt_newlines;) which you skipped. I think it should also be part of the backport as it explains why the variable is there in the first place.

I'll update this bug if needed.

Thanks for the patch Seyeong!

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

Title:
  Can't compose kvm host with lvm storage on maas 2.8.4

Status in MAAS:
  Triaged
Status in readline package in Ubuntu:
  Fix Released
Status in readline source package in Bionic:
  In Progress

Bug description:
  [Impact]

  I can't compose kvm host on maas 2.8.4 ( bionic)

  I upgraded twisted and related component with pip but the symptom is
  the same.

  MaaS 2.9.x in Focal works fine.

  in 2.8.x, pexpect virsh vol-path should return [2] but returns [3]

  [2]
  /dev/maas_data_vg/8d4e8b04-4031-4a1b-b5f2-a8306192db11
  [3]
  2021-03-17 20:43:34 stderr: [error] Message: 'this is the result...\n'
  2021-03-17 20:43:34 stderr: [error] Arguments: ([' ', '<3ef-46ca-87c8-19171950592f --pool maas_guest_lvm_vg', "error: command 'attach-disk' doesn't support option --pool"],)

  sometimes it fails in

      def get_volume_path(self, pool, volume):
          """Return the path to the file from `pool` and `volume`."""
          output = self.run(["vol-path", volume, "--pool", pool])
          return output.strip()

  sometimes failes in

      def get_machine_xml(self, machine):
          # Check if we have a cached version of the XML.
          # This is a short-lived object, so we don't need to worry about
          # expiring objects in the cache.
          if machine in self.xml:
              return self.xml[machine]

          # Grab the XML from virsh if we don't have it already.
          output = self.run(["dumpxml", machine]).strip()
          if output.startswith("error:"):
              maaslog.error("%s: Failed to get XML for machine", machine)
              return None

          # Cache the XML, since we'll need it later to reconfigure the VM.
          self.xml[machine] = output
          return output

  I assume that run function has issue.

  Command line virsh vol-path and simple pepect python code works fine.

  Any advice for this issue?

  Thanks.

  [Test Plan]

  0) deploy Bionic and MAAS 2.8

  1) Create file to be used as loopback device

  sudo dd if=/dev/zero of=lvm bs=16000 count=1M

  2) sudo losetup /dev/loop39 lvm

  3) sudo pvcreate /dev/loop39

  4) sudo vgcreate maas_data_vg /dev/loop39

  5) Save below xml:
  <pool type='logical'>
  <name>maas_guest_lvm_vg</name>
  <source>
  <name>maas_data_vg</name>
  <format type='lvm2'/>
  </source>
  <target>
  <path>/dev/maas_data_vg</path>
  </target>
  </pool>

  6) virsh pool-create maas_guest_lvm_vg.xml

  7) Add KVM host in MaaS

  8) Attempt to compose a POD using storage pool maas_guest_lvm_vg

  9) GUI will fail with:

  Pod unable to compose machine: Unable to compose machine because:
  Failed talking to pod: Start tag expected, '<' not found, line 1,
  column 1 (<string>, line 1)

  [Where problems could occer]

  This patch is small peice of huge commit.
  I tested by compiling test pkg with this patch. but actually it is kind of underlying library ( libreadline ), so It could affect to any application using libreadline.
  e.g running command inside application by code can be affected.

  
  [Other Info]

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



From 1934829 at bugs.launchpad.net  Tue Aug 24 11:30:41 2021
From: 1934829 at bugs.launchpad.net (Robie Basak)
Date: Tue, 24 Aug 2021 11:30:41 -0000
Subject: [Bug 1934829] Re: universal-ctags FTBFS  with glibc-2.33
References: <162561352934.24466.11087677901252740671.malonedeb@chaenomeles.canonical.com>
Message-ID: <162980464116.23209.16612930723587633844.malone@wampee.canonical.com>

Unsubscribing sponsors as there is nothing left to 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/1934829

Title:
  universal-ctags FTBFS  with glibc-2.33

Status in universal-ctags package in Ubuntu:
  New
Status in universal-ctags package in Debian:
  New

Bug description:
  The latest sync from Debian FTBFS [1][2]. This is due to the newer
  version of glibc (2.33) available in impish and in hirsute.

  Since glibc in Debian unstable is at 2.31, the issue does not manifest
  itself there.

  Moreover, this has been fixed upstream [3] and should be included in
  Debian when the package gets updated after the current freeze.
  Therefore, I am attaching a patch to unblock Ubuntu's migration, which
  was not forwarded to Debian. The package builds fine in impish and
  works as expected.

  [1] https://launchpad.net/ubuntu/+source/universal-ctags/0+git20200824-1.1
  [2] https://launchpad.net/ubuntu/+source/universal-ctags/0+git20200824-1.1/+build/21478505
  [3] https://github.com/universal-ctags/ctags/pull/2990

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/universal-ctags/+bug/1934829/+subscriptions



From 1933827 at bugs.launchpad.net  Tue Aug 24 11:31:44 2021
From: 1933827 at bugs.launchpad.net (Robie Basak)
Date: Tue, 24 Aug 2021 11:31:44 -0000
Subject: [Bug 1933827] Re: Symlink incorrectly installs to a sub-directory
 related to source name (github: 80)
References: <162488052806.11891.8249482976030040971.malonedeb@soybean.canonical.com>
Message-ID: <162980470427.18729.1291398628802539767.malone@gac.canonical.com>

Unsubscribing sponsors as there is nothing currently available to
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/1933827

Title:
  Symlink incorrectly installs to a sub-directory related to source name
  (github: 80)

Status in zmk package in Ubuntu:
  Fix Released
Status in zmk source package in Hirsute:
  In Progress

Bug description:
  This bug is a mirror of the GitHub issue
  https://github.com/zyga/zmk/issues/80 filed for the purpose of SRU

  The following makefile snippet illustrates the problem:

  # Symlink: sysota-rauc-hook -> sysotad
  cmd/sysotad/sysota-rauc-hook.InstallDir = $(cmd/sysotad/sysotad.InstallDir)
  cmd/sysotad/sysota-rauc-hook.SymlinkTarget = sysotad
  $(eval $(call ZMK.Expand,Symlink,cmd/sysotad/sysota-rauc-hook))

  The result of make install should be

  ln -s sysotad /usr/lib/sysotad/sysotad-rauc-hook

  With zmk << 0.5.1 it is

  ln -s sysotad /usr/lib/sysotad/cmd/sysotad/sysotad-rauc-hook

  This bug was fixed in zmk 0.5.1, which is available in Debian Unstable
  and Ubuntu Impish as 0.5.1-2

  [Impact]

  The issue is isolated to the ZMK Symlink template and is only visible
  when the path of the symbolic link, in the development tree, contains
  a sub-directory, like in the RAUC hook example above.

  [Test Case]
  Create a makefile with this content:

  include z.mk
  $(eval $(call ZMK.Import,Directories))
  subdir/symlink.InstallDir = $(bindir)
  subdir/symlink.SymlinkTarget = target
  $(eval $(call ZMK.Expand,Symlink,subdir/symlink))

  Issue the command: make -n install. The correct output is:

  ln -sf target /usr/local/bin/symlink

  In the broken case, the output is:

  ln -sf target /usr/local/bin/subdir/symlink

  [Where problems could occur]
  Since zmk is only used by my own software, most notably libzt, and libzt does not trigger this error, the regression potential is minimal.

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



From 1472288 at bugs.launchpad.net  Tue Aug 24 11:39:56 2021
From: 1472288 at bugs.launchpad.net (Robie Basak)
Date: Tue, 24 Aug 2021 11:39:56 -0000
Subject: [Bug 1472288] Re: Add additional attributes in /etc/os-release
References: <20150707143013.19061.97345.malonedeb@chaenomeles.canonical.com>
Message-ID: <162980519624.20496.6205242997750888297.malone@gac.canonical.com>

I'm just driving past the sponsorship queue.

How can we validate that the CPE_NAME you're adding is definitely the
correct one for us to use in Ubuntu?

Your debdiff doesn't include adding BUILD_ID, so maybe this bug needs
renaming to be specific to CPE_NAME? BUILD_ID sounds like something
based on the installer used - like /var/log/installer/media-info or
/etc/cloud/build.info. But that would mean that /etc/os-release could no
longer be a simple conffile and would have to be managed via a postinst
and ucf or something.

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

Title:
  Add additional attributes in /etc/os-release

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  Please add 'CPE_NAME' and 'BUILD_ID' to /etc/os-release.

  More at http://www.freedesktop.org/software/systemd/man/os-
  release.html.

  I'm not sure BUILD_ID should be something like 'vivid' etc, but it
  would be a nice use. Or introduce a new attribute/value pair like

  NICKNAME_ID="vivid"

  No rush. Thanks for adopting this convention so quickly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: base-files 7.2ubuntu9
  Uname: Linux 4.1.0-rc5carif-00007-ga8b253b x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul  7 10:26:02 2015
  Dependencies:
   
  InstallationDate: Installed on 2014-11-04 (245 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+subscriptions



From 1923642 at bugs.launchpad.net  Tue Aug 24 11:58:56 2021
From: 1923642 at bugs.launchpad.net (Robie Basak)
Date: Tue, 24 Aug 2021 11:58:56 -0000
Subject: [Bug 1923642] Re: glib can no longer be included in extern "C" blocks
References: <161833315017.13703.12575613470550208630.malonedeb@chaenomeles.canonical.com>
Message-ID: <162980633670.20938.2258333877282397858.malone@soybean.canonical.com>

Looks like upstream has fixed this now with
https://github.com/Gnucash/gnucash/commit/bbb4113a5a996dcd7bb3494e0be900b275b49a4f,
so it would probably be best if we cherry-picked that commit. Could you
prepare an upload with a quilt patch and dep3 headers against that
upstream commit please, and I'll sponsor it? Or I can do it, but I don't
want to steal your credit :)

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

Title:
  glib can no longer be included in extern "C" blocks

Status in GnuCash:
  Fix Released
Status in gnucash package in Ubuntu:
  New
Status in gnucash package in Debian:
  Confirmed

Bug description:
  Glib newer than 2.66 will not support extern "C" blocks.
  For more info: https://gitlab.gnome.org/GNOME/glib/-/issues/2331

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



From 1940954 at bugs.launchpad.net  Tue Aug 24 12:33:36 2021
From: 1940954 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 24 Aug 2021 12:33:36 -0000
Subject: [Bug 1940954] [NEW] Sync akira 0.0.15-1 (universe) from Debian
 experimental (main)
References: <162980840821.31621.15728399950938640379.malonedeb@gac.canonical.com>
Message-ID: <162980841658.852.1638119596277099552.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Rico Tzschichholz (ricotz):

Please sync akira 0.0.15-1 (universe) from Debian experimental (main)

Changelog entries since current impish version 0.0.13-3:

akira (0.0.15-1) experimental; urgency=medium

  [ upstream ]
  * new pre-release

  [ Jonas Smedegaard ]
  * unfuzz patches
  * copyright info: update coverage

 -- Jonas Smedegaard <dr at jones.dk>  Wed, 21 Jul 2021 16:07:25 +0200

akira (0.0.14-1~exp1) experimental; urgency=medium

  [ upstream ]
  * new pre-release

  [ Jonas Smedegaard ]
  * copyright info: update coverage
  * unfuzz patch 2001
  * add patch 2002 to use goocanvas 2.0 (not goocanvas 3.0)

 -- Jonas Smedegaard <dr at jones.dk>  Mon, 17 May 2021 09:07:40 +0200

** Affects: akira (Ubuntu)
     Importance: Wishlist
         Status: New

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


From 1940999 at bugs.launchpad.net  Tue Aug 24 21:22:43 2021
From: 1940999 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 24 Aug 2021 21:22:43 -0000
Subject: [Bug 1940999] [NEW] FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <162984016356.28976.4783207092056253173.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Dan Bungert (dbungert):

The package grep failed to build in a recent archive rebuild, see
https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#foundations-bugs .

The failure is in automated test, as follows:

stack-overflow: failed test: grep never printed "stack overflow"
FAIL: stack-overflow

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

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


From 1941067 at bugs.launchpad.net  Wed Aug 25 10:36:10 2021
From: 1941067 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 25 Aug 2021 10:36:10 -0000
Subject: [Bug 1941067] [NEW] Sync vala 0.52.5-1 (universe) from Debian
 experimental (main)
References: <162988776421.4898.11060217472194824922.malonedeb@soybean.canonical.com>
Message-ID: <162988777042.8026.3031299496760767175.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Rico Tzschichholz (ricotz):

Please sync vala 0.52.5-1 (universe) from Debian experimental (main)

Changelog entries since current impish version 0.52.5-1~sync1:

vala (0.52.5-1) experimental; urgency=medium

  * New upstream release
  * Rename packages for 0.48 → 0.52
  * Update symbols

 -- Rico Tzschichholz <ricotz at ubuntu.com>  Wed, 18 Aug 2021 12:42:08
+0100

** Affects: vala (Ubuntu)
     Importance: Wishlist
         Status: New

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


From 1940999 at bugs.launchpad.net  Wed Aug 25 12:00:44 2021
From: 1940999 at bugs.launchpad.net (Robie Basak)
Date: Wed, 25 Aug 2021 12:00:44 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <162989284430.27142.5509461865900993101.malone@soybean.canonical.com>

Thank you for working on this!

> To address this I propose picking up the new version of grep.

But you're picking up the new version of grep and then also disabling
the failing test in that update. So why is the new version of grep
necessary at all? Can't you just disable the failing test in the current
version of grep in Impish?

> +  * New upstream version 3.7 (LP: #1940999)
> +  * Add d/p/06-disable-test-regex.patch to disable failing test-regex

This bug is entitled "FTBFS against glibc 2.34" so the bug reference
should go against the second item there, not the first. Placing the
reference against the first entry makes it sound like this bug is
tracking the update of grep to 3.7, but according to the bug title as it
is at the moment, that isn't what this bug is tracking.

Please avoid refreshing quilt patches unnecessarily. Refreshing is only
needed for conflicts and if fuzz appears. Otherwise, not refreshing them
minimises diff noise and thus helps with review. Additionally, if forced
to refresh I always use QUILT_REFRESH_ARGS="-p ab --no-timestamps --no-
index" as documented at https://wiki.debian.org/UsingQuilt to reduce the
noise for next time.

It looks like fundamentally you're resolving the FTBFS by disabling the
failing test. But have you checked that the test is actually a false
positive? What if the test is working and picking up something that is
actually wrong with the new glibc? If you think it's a false positive
then I'd expect to see some explanation that it's a false positive and
why you think that, but I couldn't find anything. And if it is a false
positive, then a bug report to the test's origin (presumably upstream)
and a dep3 header linking to that would be appropriate.

> +Forwarded:   no - Debian not yet on glibc 2.34

It's still useful to forward, as Debian is expected to need that anyway.
I usually file such bugs in the Debian BTS explaining that it isn't
necessary to apply right now but will be useful in the future. However,
before forwarding, maybe we should get the fix right here first :)

** Tags added: ftbfs

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1940999 at bugs.launchpad.net  Wed Aug 25 12:10:09 2021
From: 1940999 at bugs.launchpad.net (Robie Basak)
Date: Wed, 25 Aug 2021 12:10:09 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <162989340921.20263.4309779198805690265.malone@chaenomeles.canonical.com>

> +Last-Update: Aug-24-2021

This should use ISO format according to the spec please
(https://dep.debian.net/deps/dep3/)

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1940629 at bugs.launchpad.net  Wed Aug 25 13:50:23 2021
From: 1940629 at bugs.launchpad.net (Robie Basak)
Date: Wed, 25 Aug 2021 13:50:23 -0000
Subject: [Bug 1940629] Re: Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162989942384.26161.11619372312025526450.malone@soybean.canonical.com>

Hello Andy, or anyone else affected,

Accepted thermald into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/thermald/2.4.3-1ubuntu2 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, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: thermald (Ubuntu Hirsute)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

** Changed in: thermald (Ubuntu Impish)
       Status: In Progress => 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/1940629

Title:
  Support Jasper Lake

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Focal:
  In Progress
Status in thermald source package in Hirsute:
  Fix Committed
Status in thermald source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions



From 1940629 at bugs.launchpad.net  Wed Aug 25 13:51:12 2021
From: 1940629 at bugs.launchpad.net (Robie Basak)
Date: Wed, 25 Aug 2021 13:51:12 -0000
Subject: [Bug 1940629] Re: Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162989947260.16113.679668819118055860.malone@gac.canonical.com>

SRU +1 for the current upload in Focal unapproved also, but this is
currently blocked on the 20.04.3 freeze.

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

Title:
  Support Jasper Lake

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Focal:
  In Progress
Status in thermald source package in Hirsute:
  Fix Committed
Status in thermald source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions



From 1940629 at bugs.launchpad.net  Wed Aug 25 13:51:33 2021
From: 1940629 at bugs.launchpad.net (Robie Basak)
Date: Wed, 25 Aug 2021 13:51:33 -0000
Subject: [Bug 1940629] Re: Support Jasper Lake
References: <162944706622.24812.18192361756967274391.malonedeb@soybean.canonical.com>
Message-ID: <162989949328.30117.12802510782471295859.malone@wampee.canonical.com>

Unsubscribing sponsors.

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

Title:
  Support Jasper Lake

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Focal:
  In Progress
Status in thermald source package in Hirsute:
  Fix Committed
Status in thermald source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940629/+subscriptions



From 1939751 at bugs.launchpad.net  Wed Aug 25 13:53:15 2021
From: 1939751 at bugs.launchpad.net (William Wilson)
Date: Wed, 25 Aug 2021 13:53:15 -0000
Subject: [Bug 1939751] Re: openssh FTBFS with glibc >= 2.34
References: <162880212312.6537.6691163062217728505.malonedeb@chaenomeles.canonical.com>
Message-ID: <162989959603.26828.12046709769645505580.malone@wampee.canonical.com>

@paelzer I would be happy to work on the merge if you would like.

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

Title:
  openssh FTBFS with glibc >= 2.34

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Fix Released

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

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



From 1939751 at bugs.launchpad.net  Wed Aug 25 14:35:07 2021
From: 1939751 at bugs.launchpad.net (=?utf-8?q?Christian_Ehrhardt_=EE=83=BF?=)
Date: Wed, 25 Aug 2021 14:35:07 -0000
Subject: [Bug 1939751] Re: openssh FTBFS with glibc >= 2.34
References: <162880212312.6537.6691163062217728505.malonedeb@chaenomeles.canonical.com>
Message-ID: <162990210800.26211.4849744509676233545.malone@chaenomeles.canonical.com>

Yeah that would be fine, we have assigned two FTFBSes but not yet this one.
Take it and thanks in advance.

I mean your debdiff could already be all that is needed - but is it test-built, tested, discussed and so on.
If you need any help/review please ping us here.

** Changed in: openssh (Ubuntu)
     Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  openssh FTBFS with glibc >= 2.34

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Fix Released

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

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



From 1938259 at bugs.launchpad.net  Wed Aug 25 14:47:51 2021
From: 1938259 at bugs.launchpad.net (Dan Streetman)
Date: Wed, 25 Aug 2021 14:47:51 -0000
Subject: [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell
 models
References: <162745556987.5514.108453593921646683.malonedeb@wampee.canonical.com>
Message-ID: <162990287132.31911.12458584470458232116.malone@chaenomeles.canonical.com>

included in impish in version 248.3-1ubuntu4


** Changed in: systemd (Ubuntu Impish)
       Status: In Progress => 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/1938259

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel 5.13, or kernel with this patch backported:
      https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions



From 1940999 at bugs.launchpad.net  Wed Aug 25 15:16:09 2021
From: 1940999 at bugs.launchpad.net (Dan Bungert)
Date: Wed, 25 Aug 2021 15:16:09 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
 <162989284430.27142.5509461865900993101.malone@soybean.canonical.com>
Message-ID: <YSZeuUJC0aGGrnbb@dbungert-desktop>

On Wed, Aug 25, 2021 at 12:00:44PM -0000, Robie Basak wrote:
> Thank you for working on this!

And thank you for the thoughtful review.

> > To address this I propose picking up the new version of grep.
> But you're picking up the new version of grep and then also disabling
> the failing test in that update. So why is the new version of grep
> necessary at all? Can't you just disable the failing test in the current
> version of grep in Impish?

I have been unclear.  With grep 3.6 + glibc 2.34, the failing test is a
different test - the 'stack-overflow' test fails with the following log
output:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

More verbose log attached.

So my general plan here is to add grep 3.7 to pick up the new version,
which addresses the 'stack-overflow' test, but does regress on
'test-regex', which I then disable.  There's another option here, to use
the built-in regex for grep, but I presumed that would be generally
undesired.

> > +  * New upstream version 3.7 (LP: #1940999)
> > +  * Add d/p/06-disable-test-regex.patch to disable failing test-regex
> This bug is entitled "FTBFS against glibc 2.34" so the bug reference
> should go against the second item there, not the first. Placing the
> reference against the first entry makes it sound like this bug is
> tracking the update of grep to 3.7, but according to the bug title as it
> is at the moment, that isn't what this bug is tracking.

With the new information above, I think the way I have structured it
matches the problem I'm trying to address - what do you think?

> Please avoid refreshing quilt patches unnecessarily. Refreshing is only
> needed for conflicts and if fuzz appears. Otherwise, not refreshing them
> minimises diff noise and thus helps with review.

Sounds reasonable to me.  I'll fix it.

> Additionally, if forced
> to refresh I always use QUILT_REFRESH_ARGS="-p ab --no-timestamps --no-
> index" as documented at https://wiki.debian.org/UsingQuilt to reduce the
> noise for next time.

Right, I used to hide the suggested quilt config behind a dquilt alias
but the use case for me doing that in the first place is no longer
relevant.  An easy fix.

> It looks like fundamentally you're resolving the FTBFS by disabling the
> failing test. But have you checked that the test is actually a false
> positive? What if the test is working and picking up something that is
> actually wrong with the new glibc? If you think it's a false positive
> then I'd expect to see some explanation that it's a false positive and
> why you think that, but I couldn't find anything. And if it is a false
> positive, then a bug report to the test's origin (presumably upstream)
> and a dep3 header linking to that would be appropriate.

I believe the issue with the stack-overflow test is consistent with this
description from upstream:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46227
Admittedly I have not analyzed further other than comparing the verbose
log output I have to that and concluding that it was the same problem.
I will dig further if you believe it worthwhile.

> > +Forwarded:   no - Debian not yet on glibc 2.34
> It's still useful to forward, as Debian is expected to need that anyway.
> I usually file such bugs in the Debian BTS explaining that it isn't
> necessary to apply right now but will be useful in the future. However,
> before forwarding, maybe we should get the fix right here first :)

OK, when we have agreement on the fix I will forward.

> > +Last-Update: Aug-24-2021
> This should use ISO format according to the spec please
> (https://dep.debian.net/deps/dep3/)

Will do.

-Dan


** Attachment added: "grep-3.6-vs-glibc2.34-stack-overflow.log"
   https://bugs.launchpad.net/bugs/1940999/+attachment/5520534/+files/grep-3.6-vs-glibc2.34-stack-overflow.log

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1932076 at bugs.launchpad.net  Wed Aug 25 18:29:56 2021
From: 1932076 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 25 Aug 2021 18:29:56 -0000
Subject: [Bug 1932076] Re: src:request-tracker5: ftbfs due to changes in gpg
 error messages
References: <162379050282.13849.15848709508592262107.malonedeb@wampee.canonical.com>
Message-ID: <162991619820.30931.15676527407844868115.malone@ackee.canonical.com>

This bug was fixed in the package request-tracker5 - 5.0.1+dfsg-1ubuntu1

---------------
request-tracker5 (5.0.1+dfsg-1ubuntu1) impish; urgency=medium

  * d/p/rt_test_gnupg_disable_wkd.diff: Backport patch from Debian to disable
    using WKD on GnuPG tests that might attempt to use the network (LP: #1932076).

 -- Lucas Kanashiro <kanashiro at ubuntu.com>  Thu, 19 Aug 2021 16:05:48
-0300

** Changed in: request-tracker5 (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  src:request-tracker5: ftbfs due to changes in gpg error messages

Status in request-tracker4 package in Ubuntu:
  Fix Released
Status in request-tracker5 package in Ubuntu:
  Fix Released
Status in request-tracker5 package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/988905:

  Package: src:request-tracker5
  Version: 5.0.1+dfsg-1
  Severity: serious
  Tags: ftbfs
  Justification: fails to build from source

  Dear Maintainer,

  As can be seen at

  https://tests.reproducible-builds.org/debian/rb-
  pkg/unstable/amd64/request-tracker5.html

  or

  https://launchpad.net/ubuntu/+source/request-tracker5/5.0.1+dfsg-1

  the package fails to build with the current state of unstable / Ubuntu
  impish.

  The failures are:

  #   Failed test at t/mail/crypt-gnupg.t line 171.
  # found warning: gpg: error retrieving 'keyless at example.com' via WKD: Server indicated a failure
  # expected to find warning: (?^:public key not found|error retrieving 'keyless\@example.com' via WKD: No data)

  #   Failed test at t/web/crypt-gnupg.t line 358.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  #   Failed test at t/web/crypt-gnupg.t line 380.
  # found warning: gpg: error retrieving 'nokey at example.com' via WKD: Server indicated a failure
  # found warning: Recipient 'nokey at example.com' is unusable, the reason is 'No specific reason given'
  # expected to find warning: (?^:nokey\@example.com: skipped: public key not found|error retrieving 'nokey\@example.com' via WKD: No data)
  # expected to find warning: (?^:Recipient 'nokey\@example.com' is unusable)

  (the messages are actually slightly different in Ubuntu). This seems
  pretty benign really and probably the tests should be relaxed?

  Cheers,
  mwh

  -- System Information:
  Debian Release: bullseye/sid
    APT prefers focal-updates
    APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (400, 'focal-proposed'), (100, 'focal-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.4.0-73-generic (SMP w/8 CPU cores)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/request-tracker4/+bug/1932076/+subscriptions



From 1940999 at bugs.launchpad.net  Wed Aug 25 20:11:28 2021
From: 1940999 at bugs.launchpad.net (Dan Bungert)
Date: Wed, 25 Aug 2021 20:11:28 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <162992228817.26951.14507478925869418017.malone@soybean.canonical.com>

One possibility that's starting to grow on me is adjusting grep to go
back to using the built-in regex instead of getting it from glibc.  This
causes some size bloat (+80k on amd64) but that might be tolerable.

Proof of concept:
https://launchpad.net/~dbungert/+archive/ubuntu/grep-lp-1940999

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1923642 at bugs.launchpad.net  Wed Aug 25 21:22:32 2021
From: 1923642 at bugs.launchpad.net (Heather Ellsworth)
Date: Wed, 25 Aug 2021 21:22:32 -0000
Subject: [Bug 1923642] Re: glib can no longer be included in extern "C" blocks
References: <161833315017.13703.12575613470550208630.malonedeb@chaenomeles.canonical.com>
Message-ID: <162992655310.724.2474891111259479424.launchpad@chaenomeles.canonical.com>

** Changed in: gnucash (Ubuntu)
     Assignee: (unassigned) => Heather Ellsworth (hellsworth)

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

Title:
  glib can no longer be included in extern "C" blocks

Status in GnuCash:
  Fix Released
Status in gnucash package in Ubuntu:
  New
Status in gnucash package in Debian:
  Confirmed

Bug description:
  Glib newer than 2.66 will not support extern "C" blocks.
  For more info: https://gitlab.gnome.org/GNOME/glib/-/issues/2331

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



From 1923642 at bugs.launchpad.net  Wed Aug 25 22:17:27 2021
From: 1923642 at bugs.launchpad.net (Heather Ellsworth)
Date: Wed, 25 Aug 2021 22:17:27 -0000
Subject: [Bug 1923642] Re: glib can no longer be included in extern "C" blocks
References: <161833315017.13703.12575613470550208630.malonedeb@chaenomeles.canonical.com>
Message-ID: <162992984769.13119.10919389940795450792.malone@gac.canonical.com>

This was just a case of not getting notified of my PR's activity and
forgetting.. sorry bout that.

I've updated the PR to get the fix pulled in debian.

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

Title:
  glib can no longer be included in extern "C" blocks

Status in GnuCash:
  Fix Released
Status in gnucash package in Ubuntu:
  New
Status in gnucash package in Debian:
  Confirmed

Bug description:
  Glib newer than 2.66 will not support extern "C" blocks.
  For more info: https://gitlab.gnome.org/GNOME/glib/-/issues/2331

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



From 1405452 at bugs.launchpad.net  Wed Aug 25 23:31:54 2021
From: 1405452 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 25 Aug 2021 23:31:54 -0000
Subject: [Bug 1405452] Re: Typo in man page ("introduce a much improvement
 mechanism")
References: <20141224162144.16813.94979.malonedeb@soybean.canonical.com>
Message-ID: <162993431550.6811.5756275691893339434.launchpad@wampee.canonical.com>

** Tags removed: patch-forwarded-upstream
** Tags added: patch-accepted-upstream

** Changed in: hundredpapercuts
       Status: Triaged => 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/1405452

Title:
  Typo in man page ("introduce a much improvement mechanism")

Status in One Hundred Papercuts:
  Fix Released
Status in wpa package in Ubuntu:
  Triaged
Status in wpa package in Debian:
  New

Bug description:
  "introduce a much improvement mechanism" should be "introduce a much
  improved mechanism".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: wpasupplicant 2.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 24 16:19:30 2014
  InstallationDate: Installed on 2014-12-19 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 1934518 at bugs.launchpad.net  Thu Aug 26 01:26:38 2021
From: 1934518 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 26 Aug 2021 01:26:38 -0000
Subject: [Bug 1934518] Re:  improper invalidation of authorization sessions 
References: <162523373063.25728.9542415532730002380.malonedeb@wampee.canonical.com>
Message-ID: <162994119990.30929.17950293799672919269.malone@ackee.canonical.com>

This bug was fixed in the package mongodb -
1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5.2

---------------
mongodb (1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5.2) focal-security; urgency=medium

  [Heather Lemon]
  * SECURITY UPDATE: account session reuse leads to unauthorized access (LP: #1934518)
    - d/p/CVE-2019-2386-SERVER-38984-Validate-unique-User-ID-on-UserCache-hi.patch:
      Attach ID to users.
      After user deletion in MongoDB Server the improper invalidation of
      authorization sessions allows an authenticated user's session to
      persist and become conflated with new accounts
    - CVE-2019-2386

  [Alex Murray]
  * Refresh
    d/p/CVE-2019-2386-SERVER-38984-Validate-unique-User-ID-on-UserCache-hi.patch
    with the version from the 3.4 upstream branch that is still licensed
    under the AGPL.

 -- Alex Murray <alex.murray at canonical.com>  Mon, 23 Aug 2021 17:01:06
+0930

** Changed in: mongodb (Ubuntu Focal)
       Status: Confirmed => Fix Released

** Changed in: mongodb (Ubuntu Bionic)
       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/1934518

Title:
   improper invalidation of authorization sessions

Status in mongodb source package in Trusty:
  Confirmed
Status in mongodb source package in Bionic:
  Fix Released
Status in mongodb source package in Focal:
  Fix Released

Bug description:
  CVE: https://ubuntu.com/security/CVE-2019-2386

  After user deletion in MongoDB Server the improper invalidation of
  authorization sessions allows an authenticated user’s session to
  persist and become conflated with new accounts, if those accounts
  reuse the names of deleted ones. This issue affects: MongoDB Inc.
  MongoDB Server v4.0 versions prior to 4.0.9; v3.6 versions prior to
  3.6.13; v3.4 versions prior to 3.4.22.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/mongodb/+bug/1934518/+subscriptions



From 1934518 at bugs.launchpad.net  Thu Aug 26 01:26:39 2021
From: 1934518 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 26 Aug 2021 01:26:39 -0000
Subject: [Bug 1934518] Re:  improper invalidation of authorization sessions 
References: <162523373063.25728.9542415532730002380.malonedeb@wampee.canonical.com>
Message-ID: <162994120187.30931.1201650919212662296.malone@ackee.canonical.com>

This bug was fixed in the package mongodb - 1:3.6.3-0ubuntu1.3

---------------
mongodb (1:3.6.3-0ubuntu1.3) bionic-security; urgency=medium

  [Heather Lemon]
  * SECURITY UPDATE: account session reuse leads to unauthorized access (LP: #1934518)
    - d/p/CVE-2019-2386-SERVER-38984-Validate-unique-User-ID-on-UserCache-hi.patch:
      Attach ID to users.
      After user deletion in MongoDB Server the improper invalidation of
      authorization sessions allows an authenticated user's session to
      persist and become conflated with new accounts
    - CVE-2019-2386

  [Alex Murray]
  * Refresh
    d/p/CVE-2019-2386-SERVER-38984-Validate-unique-User-ID-on-UserCache-hi.patch
    with the version from the 3.4 upstream branch that is still licensed
    under the AGPL.

 -- Alex Murray <alex.murray at canonical.com>  Fri, 06 Aug 2021 12:08:41
+0930

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

Title:
   improper invalidation of authorization sessions

Status in mongodb source package in Trusty:
  Confirmed
Status in mongodb source package in Bionic:
  Fix Released
Status in mongodb source package in Focal:
  Fix Released

Bug description:
  CVE: https://ubuntu.com/security/CVE-2019-2386

  After user deletion in MongoDB Server the improper invalidation of
  authorization sessions allows an authenticated user’s session to
  persist and become conflated with new accounts, if those accounts
  reuse the names of deleted ones. This issue affects: MongoDB Inc.
  MongoDB Server v4.0 versions prior to 4.0.9; v3.6 versions prior to
  3.6.13; v3.4 versions prior to 3.4.22.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/mongodb/+bug/1934518/+subscriptions



From 1940999 at bugs.launchpad.net  Thu Aug 26 02:41:14 2021
From: 1940999 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 26 Aug 2021 02:41:14 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <162994567562.571.10232089179520022858.launchpad@gac.canonical.com>

** Changed in: grep (Ubuntu)
   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/1940999

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1938438 at bugs.launchpad.net  Thu Aug 26 03:07:37 2021
From: 1938438 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 26 Aug 2021 03:07:37 -0000
Subject: [Bug 1938438] Re: sbsigntool does not build on riscv64
References: <162755865747.27382.10177718520268360098.malonedeb@chaenomeles.canonical.com>
Message-ID: <162994725832.5561.7709540830560268302.launchpad@gac.canonical.com>

** Changed in: sbsigntool (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/1938438

Title:
  sbsigntool does not build on riscv64

Status in sbsigntool package in Ubuntu:
  New

Bug description:
  We should enable building on riscv64 for release Impish.

  Current upstream version 0.9.4 is required for running U-Boot tests.

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



From 1941709 at bugs.launchpad.net  Thu Aug 26 08:04:36 2021
From: 1941709 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 26 Aug 2021 08:04:36 -0000
Subject: [Bug 1941709] [NEW] bpython: crash after a few seconds related to
 apparmor
References: <162996458904.3593.1031187351866276261.malonedeb@gac.canonical.com>
Message-ID: <162996507656.2420.12949068939535851463.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Simon Chopin (schopin):

Something goes wrong in the import completion code, as it tries to open
an apparmor-related sysfs file. The crash appears a few seconds after
launching bpython. Seems fixed upstream.

LANG=C bpython
bpython version 0.21 on top of Python 3.9.6 /usr/bin/python3
>>> 
Traceback (most recent call last):
  File "/usr/bin/bpython", line 33, in <module>
    sys.exit(load_entry_point('bpython==0.21', 'console_scripts', 'bpython')())
  File "/usr/lib/python3/dist-packages/bpython/curtsies.py", line 201, in main
    exit_value = repl.mainloop(True, paste)
  File "/usr/lib/python3/dist-packages/bpython/curtsies.py", line 115, in mainloop
    while self.module_gatherer.find_coroutine():
  File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 226, in find_coroutine
    next(self.find_iterator)
  File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 217, in find_all_modules
    for module in self.find_modules(p):
  File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 202, in find_modules
    for subname in self.find_modules(path_real):
  File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 202, in find_modules
    for subname in self.find_modules(path_real):
  File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 202, in find_modules
    for subname in self.find_modules(path_real):
  [Previous line repeated 12 more times]
  File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 199, in find_modules
    stat = path_real.stat()
  File "/usr/lib/python3.9/pathlib.py", line 1222, in stat
    return self._accessor.stat(self)
FileNotFoundError: [Errno 2] No such file or directory: '/sys/kernel/security/apparmor/apparmorfs:[15545]'

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

-- 
bpython: crash after a few seconds related to apparmor
https://bugs.launchpad.net/bugs/1941709
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1941709 at bugs.launchpad.net  Thu Aug 26 08:29:39 2021
From: 1941709 at bugs.launchpad.net (Simon Chopin)
Date: Thu, 26 Aug 2021 08:29:39 -0000
Subject: [Bug 1941709] Re: bpython: crash after a few seconds related to
 apparmor
References: <162996458904.3593.1031187351866276261.malonedeb@gac.canonical.com>
Message-ID: <162996658022.26156.13353255306704755167.launchpad@wampee.canonical.com>

** Tags added: patch patch-accepted-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/1941709

Title:
  bpython: crash after a few seconds related to apparmor

Status in bpython package in Ubuntu:
  New

Bug description:
  Something goes wrong in the import completion code, as it tries to
  open an apparmor-related sysfs file. The crash appears a few seconds
  after launching bpython. Seems fixed upstream.

  LANG=C bpython
  bpython version 0.21 on top of Python 3.9.6 /usr/bin/python3
  >>> 
  Traceback (most recent call last):
    File "/usr/bin/bpython", line 33, in <module>
      sys.exit(load_entry_point('bpython==0.21', 'console_scripts', 'bpython')())
    File "/usr/lib/python3/dist-packages/bpython/curtsies.py", line 201, in main
      exit_value = repl.mainloop(True, paste)
    File "/usr/lib/python3/dist-packages/bpython/curtsies.py", line 115, in mainloop
      while self.module_gatherer.find_coroutine():
    File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 226, in find_coroutine
      next(self.find_iterator)
    File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 217, in find_all_modules
      for module in self.find_modules(p):
    File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 202, in find_modules
      for subname in self.find_modules(path_real):
    File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 202, in find_modules
      for subname in self.find_modules(path_real):
    File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 202, in find_modules
      for subname in self.find_modules(path_real):
    [Previous line repeated 12 more times]
    File "/usr/lib/python3/dist-packages/bpython/importcompletion.py", line 199, in find_modules
      stat = path_real.stat()
    File "/usr/lib/python3.9/pathlib.py", line 1222, in stat
      return self._accessor.stat(self)
  FileNotFoundError: [Errno 2] No such file or directory: '/sys/kernel/security/apparmor/apparmorfs:[15545]'

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



From 1941738 at bugs.launchpad.net  Thu Aug 26 11:36:51 2021
From: 1941738 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 26 Aug 2021 11:36:51 -0000
Subject: [Bug 1941738] [NEW] Sync lomiri-url-dispatcher 0.1.0-4 (universe)
 from Debian unstable (main)
References: <162997780622.25227.2238029284413556286.malonedeb@chaenomeles.canonical.com>
Message-ID: <162997781123.22829.11740147302601249742.launchpad@chaenomeles.canonical.com>

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

Please sync lomiri-url-dispatcher 0.1.0-4 (universe) from Debian
unstable (main)

lomiri-url-dispatcher-dev is a Build-Depends for newer packaging
revisions of:

  * ayatana-indicator-datetime
  * ayatana-indicator-power
  * ayatana-indicator-session
  * ayatana-indicator-sound

lomiri-url-dispatcher was uploaded to Debian in December 2020, so I'm not sure why
it hasn't automatially synced to Ubuntu yet.

All changelog entries:

lomiri-url-dispatcher (0.1.0-4) unstable; urgency=medium

  * debian/rules:
    + Add dh_auto_test override. Run tests in --no-parallel mode.
  * debian/control:
    + Update versioned B-D on cmake-extras (>= 1.5-7~).
    + Drop alternative B-D on google-mock. B-D on googletest is sufficient these
      days.
    + Add B-D on libgtest-dev.
    + Bump Standards-Version: to 4.5.1. No changes needed.

 -- Mike Gabriel <sunweaver at debian.org>  Sun, 13 Dec 2020 16:03:30 +0100

lomiri-url-dispatcher (0.1.0-3) unstable; urgency=medium

  * debian/patches:
    + Add 1001_fix-runtime-error-fftbfs.patch. Add missing include of
      <stdexcept>. Fixes FTBFS against GCC-10.

 -- Mike Gabriel <sunweaver at debian.org>  Sun, 27 Sep 2020 16:10:28 +0200

lomiri-url-dispatcher (0.1.0-2) unstable; urgency=medium

  * debian/control:
    + Fix Vcs-*: URLs.

 -- Mike Gabriel <sunweaver at debian.org>  Mon, 07 Sep 2020 21:44:44 +0200

lomiri-url-dispatcher (0.1.0-1) unstable; urgency=medium

  * Initial upload to Debian. (Closes: #961698).
  * Adapt for packaging Lomiri's fork of URL Dispatcher.
  * Adapt for uploading to Debian (instead of Ubuntu).

  * debian/control:
    + Bump DH compat level to version 13.
    + Drop full-stop from SYNOPSIS fields.
    + Drop ${python3:Depends} from D (lomiri-url-dispatcher-testability).
    + Update not-yet-available Ds and mark with FIXME.
  * debian/rules:
    + Add get-orig-source target.
    + Set hardening build flags.
  * debian/copyright:
    + Update URLs. Use secure proto.
    + Add auto-generated copyright.in file for tracking copyright changes.
    + Update copyright attributions.
  * debian/watch:
    + Add file.
  * lintian:
    + Override desktop-command-not-in-package for QML application.
    + Override binary-without-manpage (for now).

 -- Mike Gabriel <sunweaver at debian.org>  Thu, 28 May 2020 08:40:36 +0200

url-dispatcher (0.2+ubports) bionic; urgency=medium

  * Imported to UBports

 -- UBports auto importer <infra at ubports.com>  Fri, 13 Oct 2017 19:54:36
+0200

url-dispatcher (0.1+17.04.20170328-0ubuntu1) zesty; urgency=medium

  * Fix deprecation warning in mir mock.
  * The unity8-dash interface is actually com.canonical.UnityDash.
  * Use libwhoopsie for reporting recoverable problems.
  * Convert service main process and url-dispatcher tool code to C++.

 -- Rodney Dawes <rodney.dawes at canonical.com>  Tue, 28 Mar 2017 18:29:07
+0000

url-dispatcher (0.1+17.04.20170318-0ubuntu1) zesty; urgency=medium

  * Update bad-url exec tool to UAL C++ interface
  * Remove Upstart from the test suite and replace it with systemd

 -- Ted Gould <ted at gould.cx>  Sat, 18 Mar 2017 19:59:26 +0000

url-dispatcher (0.1+17.04.20170314-0ubuntu1) zesty; urgency=medium

  [ Charles Kerr ]
  * Honor XDG_CACHE_HOME in url-dispatcher-dump and url-dispatcher.conf

  [ Rodney Dawes ]
  * Remove click usage and support.
  * Use gmock module from cmake-extras.
  * Use the coverage support from cmake-extras.
  * Use cmake-extras intltool support.
  * Use gdbus integration from cmake-extras.
  * Remove unused gsettings cmake module.

 -- Rodney Dawes <rodney.dawes at canonical.com>  Tue, 14 Mar 2017 14:35:03
+0000

url-dispatcher (0.1+17.04.20170308.1-0ubuntu1) zesty; urgency=medium

  * Don't use upstart to get unity8 pid.

 -- Rodney Dawes <rodney.dawes at canonical.com>  Wed, 08 Mar 2017 20:43:30
+0000

url-dispatcher (0.1+17.04.20170227.2-0ubuntu1) zesty; urgency=medium

  [ Ken VanDine ]
  * Handle UAL API bump

  [ Rodney Dawes ]
  * Remove tests that depend on libertine, as url-dispatcher has no
    support for handlers in libertine anyway.

 -- Rodney Dawes <rodney.dawes at canonical.com>  Mon, 27 Feb 2017 19:07:50
+0000

url-dispatcher (0.1+17.04.20161206-0ubuntu1) zesty; urgency=medium

  [ Ted Gould ]
  * Instead of sleeping make the refresh tasks low enough priority they
    don't get in the way (LP: #1645793)
  * Start after Unity8 so it has a chance to set the MIR_SOCKET

 -- Michael Terry <michael.terry at canonical.com>  Tue, 06 Dec 2016
14:38:17 +0000

url-dispatcher (0.1+17.04.20161108-0ubuntu1) zesty; urgency=medium

  * Support running inside a snap.

 -- Michael Terry <michael.terry at canonical.com>  Tue, 08 Nov 2016
22:16:56 +0000

url-dispatcher (0.1+17.04.20161107-0ubuntu1) zesty; urgency=medium

  [ Florian Boucault ]
  * Crossbuilding Fixes

  [ Larry Price ]
  * App ID should allow package names with dots. (LP: #1591342) (LP: #1606498)

  [ Ted Gould ]
  * Check versions of appid:// urls to reduce the number of invalid appids
    we send to UAL (LP: #1352656)
  * Scope testing for the scope:// URL and overlays that should be over
    the dash
  * Protect the dash from getting NULL urls (LP: #1476257)
  * Make sure URL Overlays are shutdown on exit
  * Remove the wildcard that is confusing the update script (LP: #1461496)
  * Not using a message that isn't set properly (LP: #1608009)
  * Fixing tests to adjust for UAL changes
  * Add a small GUI helper tool for testing
  * Show error dialog over apps that use Bad URLs (LP: #1370008)

 -- Ted Gould <ted at gould.cx>  Mon, 07 Nov 2016 16:33:15 +0000

url-dispatcher (0.1+16.10.20160816.1-0ubuntu1) yakkety; urgency=medium

  * No chnage rebuild for UAL migration

 -- Ted Gould <ted at gould.cx>  Tue, 16 Aug 2016 15:20:27 +0000

url-dispatcher (0.1+16.04.20151110-0ubuntu2) xenial; urgency=high

  * No change rebuild for s390x.

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Fri, 11 Dec 2015 01:30:51
+0000

url-dispatcher (0.1+16.04.20151110-0ubuntu1) xenial; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Ted Gould ]
  * Remove the cache if the service fails to start. Fail to start if we
    can't create the database. (LP: #1483854)

 -- Bill Filler <ci-train-bot at canonical.com>  Tue, 10 Nov 2015 14:37:07
+0000

url-dispatcher (0.1+15.10.20150717-0ubuntu1) wily; urgency=medium

  [ Andreas Pokorny ]
  * unchagned for mir release 0.14.0

 -- CI Train Bot <ci-train-bot at canonical.com>  Fri, 17 Jul 2015 12:37:44
+0000

url-dispatcher (0.1+15.10.20150612-0ubuntu1) wily; urgency=medium

  [ Ted Gould ]
  * Add upstart build dep for tests on Wily
  * Provide a small tool to dump the URL DB in a readable form
  * Support URL Overlays of content in a trusted session without a
    desktop file

 -- CI Train Bot <ci-train-bot at canonical.com>  Fri, 12 Jun 2015 16:00:40
+0000

url-dispatcher (0.1+15.04.20150123-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Special handling for intent URLs (LP: #1407709)

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 23 Jan
2015 15:19:33 +0000

url-dispatcher (0.1+15.04.20141211-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Fix domain handling in generic regular expression (LP: #1401612)

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 11 Dec
2014 19:43:40 +0000

url-dispatcher (0.1+15.04.20141031-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Making generic regular expression more robust (LP: #1351222)

  [ Jussi Pakkanen ]
  * General cleanups
  * Do a rollback when update operations fail so there are no dangling
    transactions.
  * Ensure that tables always exist.

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 31 Oct
2014 15:51:36 +0000

url-dispatcher (0.1+14.10.20140925-0ubuntu1) utopic; urgency=low

  [ Ted Gould ]
  * Drop file based URLs for Music and Video (LP: #1340952)
  * Update tests to work with new UAL requirements (LP: #1370735)

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 25 Sep
2014 13:29:40 +0000

url-dispatcher (0.1+14.10.20140905.1-0ubuntu1) utopic; urgency=low

  [ Ted Gould ]
  * Throw a bad_url on the appid 'unconfined'

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 05 Sep
2014 03:40:44 +0000

url-dispatcher (0.1+14.10.20140827-0ubuntu1) utopic; urgency=low

  [ Ted Gould ]
  * Split update jobs into independent jobs
  * Support for unity8-dash URLs even though it's not an application
    (LP: #1361349)

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Wed, 27 Aug
2014 02:10:21 +0000

url-dispatcher (0.1+14.10.20140819.1-0ubuntu1) utopic; urgency=low

  [ Ted Gould ]
  * Ensure send works even without a mainloop (LP: #1356077)
  * Test replacing a timestamp

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 19 Aug
2014 21:01:10 +0000

url-dispatcher (0.1+14.10.20140724-0ubuntu1) utopic; urgency=low

  [ Ubuntu daily release ]
  * debian/liburl-dispatcher1.symbols: auto-update to released version

  [ Ted Gould ]
  * Make the database handle multiple writers more robustly
  * Add a TestURL function to determine which AppID will be used for a
    given URL

  [ Leo Arias ]
  * Add url-dispatcher-testability binary package.

  [ Brendan Donegan ]
  * Add url-dispatcher-testability binary package.

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 24 Jul
2014 17:10:14 +0000

url-dispatcher (0.1+14.10.20140619-0ubuntu1) utopic; urgency=low

  [ Ted Gould ]
  * Improving error messages and collecting more data

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 19 Jun
2014 02:43:30 +0000

url-dispatcher (0.1+14.10.20140604-0ubuntu1) utopic; urgency=low

  [ Ted Gould ]
  * Merge and review policies
  * Recoverable errors on DB errors on update

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Wed, 04 Jun
2014 19:07:02 +0000

url-dispatcher (0.1+14.10.20140601-0ubuntu1) utopic; urgency=low

  [ Ted Gould ]
  * Changing to Ubuntu App Launch

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Sun, 01 Jun
2014 20:53:35 +0000

url-dispatcher (0.1+14.04.20140403-0ubuntu1) trusty; urgency=low

  [ Ted Gould ]
  * Fix cache directory permissions if they got messed up (LP: #1290997)

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 03 Apr
2014 21:17:00 +0000

url-dispatcher (0.1+14.04.20140331.1-0ubuntu1) trusty; urgency=low

  [ Ted Gould ]
  * Make it so that URLs can be installed with configuration files.
  * Switch to using libupstart-app-launch for discovering AppIDs
  * Migrate test suite to use libclick based libual

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 31 Mar
2014 17:18:43 +0000

url-dispatcher (0.1+14.04.20140217.1-0ubuntu1) trusty; urgency=low

  [ Ted Gould ]
  * Add tests for the library and service as a binary.
  * Upgrading to libupstart-app-launch v2.
  * Flushing trunk with a release
  * Update Upstart mock for the new UAL

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 17 Feb
2014 17:58:44 +0000

url-dispatcher (0.1+14.04.20131209.1-0ubuntu2) trusty; urgency=low

  * Restrict on which arch we build url-dispatcher due to the ust build-
dep

 -- Didier Roche <didrocks at ubuntu.com>  Mon, 09 Dec 2013 13:41:41 +0100

url-dispatcher (0.1+14.04.20131209.1-0ubuntu1) trusty; urgency=low

  * Cherry-pick libupstart-app-launch API/ABI bump from trunk

 -- Łukasz 'sil2100' Zemczak <lukasz.zemczak at canonical.com>  Fri, 06 Dec
2013 14:32:26 +0100

url-dispatcher (0.1+13.10.20131014.2-0ubuntu1) saucy; urgency=low

  [ Michal Hruby ]
  * Revert the definition change for mediaplayer, it'll remain a non-
    click app for now.

  [ Ted Gould ]
  * Adds the appid:// URL format.
  * Use 'click info' to get the manifest. (LP: #1232118)
  * Allow custom URIs to have variable based package specifications.
  * Switching many core apps to Click App ID's.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 38

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 14 Oct
2013 18:07:27 +0000

url-dispatcher (0.1+13.10.20131003-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Enfoce the ///. (LP: #1231444)
  * Make dispatcher more testable and add some application:/// tests.
  * Adding a calendar URL. (LP: #1231136)
  * Adding the alarm URL pattern. (LP: #1233176)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 32

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 03 Oct
2013 02:08:19 +0000

url-dispatcher (0.1+13.10.20130924.1-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Report a recoverable problem on Bad URLs.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 27

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 24 Sep
2013 06:09:10 +0000

url-dispatcher (0.1+13.10.20130919.3-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Fix the name of the dialer-app.
  * Fix the URI environment variable by properly using libupstart-app-
    launch.
  * Add URLs for PIM apps.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 25

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 19 Sep
2013 14:05:04 +0000

url-dispatcher (0.1+13.10.20130917.1-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Call webbrowser for http/https URLs.
  * Switch the library relationship to the service to a Suggests.
  * URLs for music and video application launching.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 21

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 17 Sep
2013 22:11:05 +0000

url-dispatcher (0.1+13.10.20130823-0ubuntu1) saucy; urgency=low

  [ Ted Gould ]
  * Adding a URL format for system settings.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 17

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 23 Aug
2013 02:06:01 +0000

url-dispatcher (0.1+13.10.20130726-0ubuntu1) saucy; urgency=low

  [ Łukasz 'sil2100' Zemczak ]
  * Add symbols file, modify the package's short descriptions.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 15

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 26 Jul
2013 00:02:46 +0000

url-dispatcher (0.1+13.10.20130725.1-0ubuntu1) saucy; urgency=low

  [ Łukasz 'sil2100' Zemczak ]
  * Remove debian/watch
  * debian/control:
    - Modifications related to compliance with our packaging standards
  * Add copyright info to the source code
  * Automatic snapshot from revision 11 (bootstrap)
  * Additional packaging changes, since some things got missed last
    time.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 13

 -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 25 Jul
2013 07:52:47 +0000

url-dispatcher (0.1-0ubuntu1) saucy; urgency=low

  * Start

 -- Ted Gould <ted at ubuntu.com>  Thu, 27 Jun 2013 11:36:18 -0500

** Affects: ubuntu
     Importance: Wishlist
         Status: New

-- 
Sync lomiri-url-dispatcher 0.1.0-4 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1941738
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1941740 at bugs.launchpad.net  Thu Aug 26 11:43:49 2021
From: 1941740 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 26 Aug 2021 11:43:49 -0000
Subject: [Bug 1941740] [NEW] Sync ayatana-indicator-messages 0.8.2-1
 (universe) from Debian unstable (main)
References: <162997822537.12927.7434014460143517533.malonedeb@soybean.canonical.com>
Message-ID: <162997822937.7123.16357275692544852888.launchpad@wampee.canonical.com>

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

Please sync ayatana-indicator-messages 0.8.2-1 (universe) from Debian
unstable (main)

This is part of the suite of Ayatana Indicators and Ubuntu MATE users are
requesting this package is made available following our recent migration to
Ayatana Indicators.

All changelog entries:

ayatana-indicator-messages (0.8.2-1) unstable; urgency=medium

  * New upstream release.
  * debian/control:
    + Bump Standards-Version: to 4.5.1. No changes needed.
    + Fix capitalization of the word 'Xfce'.
  * debian/watch:
    + Update format version to 4.
  * debian/rules:
    + Move gtk-doc html files into package's doc folder.
  * debian/libmessaging-menu-dev.doc-base:
    + Add file.

 -- Mike Gabriel <sunweaver at debian.org>  Wed, 03 Feb 2021 13:15:27 +0100

ayatana-indicator-messages (0.8.1-2) unstable; urgency=medium

  * debian/control:
    + Add Debian UBports Team to Uploaders: field.
    + Mention desktop envs that support system indicators in LONG_DESCRIPTION.
    + Typo fix in LONG_DESCRIPTION.

 -- Mike Gabriel <sunweaver at debian.org>  Sat, 07 Nov 2020 15:12:17 +0100

ayatana-indicator-messages (0.8.1-1) unstable; urgency=medium

  * New upstream release.

 -- Mike Gabriel <sunweaver at debian.org>  Thu, 10 Sep 2020 22:36:48 +0200

ayatana-indicator-messages (0.8.0-3) unstable; urgency=medium

  * Source-only upload as is.

 -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 11:56:27 +0200

ayatana-indicator-messages (0.8.0-2) unstable; urgency=medium

  * debian/control:
    + Add B-D systemd for [linux-any] architectures.
    + Add B-D: dh-exec.
  * debian/ayatana-indicator-messages.install:
    + Install systemd service file only for [linux-any] architectures.

 -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 11:49:04 +0200

ayatana-indicator-messages (0.8.0-1) unstable; urgency=medium

  * New upstream release.
  * debian/control:
    + Add to D (ayatana-indicator-messages): ayatana-indicator-common
      (>= 0.8.0).
  * debian/copyright:
    + Update copyright attributions.
  * debian/ayatana-indicator-messages.install:
    + Drop upstart conf file, add systemd service file.

 -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 09:48:49 +0200

ayatana-indicator-messages (0.6.2-1) unstable; urgency=medium

  * New upstream release.
  * debian/control:
    + Bump DH compat level to version 13.

 -- Mike Gabriel <sunweaver at debian.org>  Thu, 06 Aug 2020 14:20:11 +0200

ayatana-indicator-messages (0.6.1-1) unstable; urgency=medium

  * New upstream release.
    - Stop using deprecated g_type_class_add_private. (Closes: #951994).
  * debian/patches:
    + Drop 0001_Fix-pkg-config-file-library-and-path-flags.patch. Applied
      upstream.
  * debian/control:
    + Bump Standards-Version: to 4.5.0. No changes needed.
    + Add Rules-Requires-Root: field and set it to 'no'.
  * debian/{control,compat}:
    + Switch to debhelper-compat notation, bump DH compat level to version 12.
  * debian/rules:
    + Switch from dh_install --fail-missing to dh_missing --fail-missing.
  * debian/ayatana-indicator-messages.install:
    + Adapt installation path. Service executable now gets installed to
      /usr/libexec/.
  * debian/libmessaging-menu0.symbols:
    + Add Build-Depends-Package: metadata field.

 -- Mike Gabriel <sunweaver at debian.org>  Mon, 24 Feb 2020 10:08:04 +0100

ayatana-indicator-messages (0.6.0-3) unstable; urgency=medium

  * debian/control:
    + Add B/R for indicator-messages. The a-i-messages and i-messages bin:pkgs
      share the same artwork files.
    + Bump Standards-Version: to 4.4.0. No changes needed.
  * debian/patches:
    + Add 0001_Fix-pkg-config-file-library-and-path-flags.patch. Adapt paths and
      filenames to recently reworked install target. (Closes: #923958).

 -- Mike Gabriel <sunweaver at debian.org>  Wed, 07 Aug 2019 01:54:05 +0200

ayatana-indicator-messages (0.6.0-2) unstable; urgency=medium

  * debian/control:
    + Update Vcs-*: fields. Packaging Git has been migrated to salsa.debian.org.
    + Bump Standards-Version: to 4.2.0. No changes needed.
  * debian/upstream/metadata:
    + Add file. Comply with DEP-12.

 -- Mike Gabriel <sunweaver at debian.org>  Tue, 14 Aug 2018 18:51:18 +0200

ayatana-indicator-messages (0.6.0-1) unstable; urgency=medium

  * Initial release to Debian. (Closes: #893875).

 -- Mike Gabriel <sunweaver at debian.org>  Fri, 23 Mar 2018 15:16:57 +0100

** Affects: ubuntu
     Importance: Wishlist
         Status: New

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


From 1941740 at bugs.launchpad.net  Thu Aug 26 11:45:48 2021
From: 1941740 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 26 Aug 2021 11:45:48 -0000
Subject: [Bug 1941740] Re: Sync ayatana-indicator-messages 0.8.2-1 (universe)
 from Debian unstable (main)
References: <162997822537.12927.7434014460143517533.malonedeb@soybean.canonical.com>
Message-ID: <162997834946.8768.15148178947041278760.malone@wampee.canonical.com>

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

** Changed in: 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/1941740

Title:
  Sync ayatana-indicator-messages 0.8.2-1 (universe) from Debian
  unstable (main)

Status in Ubuntu:
  Confirmed

Bug description:
  Please sync ayatana-indicator-messages 0.8.2-1 (universe) from Debian
  unstable (main)

  This is part of the suite of Ayatana Indicators and Ubuntu MATE users are
  requesting this package is made available following our recent migration to
  Ayatana Indicators.

  All changelog entries:

  ayatana-indicator-messages (0.8.2-1) unstable; urgency=medium

    * New upstream release.
    * debian/control:
      + Bump Standards-Version: to 4.5.1. No changes needed.
      + Fix capitalization of the word 'Xfce'.
    * debian/watch:
      + Update format version to 4.
    * debian/rules:
      + Move gtk-doc html files into package's doc folder.
    * debian/libmessaging-menu-dev.doc-base:
      + Add file.

   -- Mike Gabriel <sunweaver at debian.org>  Wed, 03 Feb 2021 13:15:27
  +0100

  ayatana-indicator-messages (0.8.1-2) unstable; urgency=medium

    * debian/control:
      + Add Debian UBports Team to Uploaders: field.
      + Mention desktop envs that support system indicators in LONG_DESCRIPTION.
      + Typo fix in LONG_DESCRIPTION.

   -- Mike Gabriel <sunweaver at debian.org>  Sat, 07 Nov 2020 15:12:17
  +0100

  ayatana-indicator-messages (0.8.1-1) unstable; urgency=medium

    * New upstream release.

   -- Mike Gabriel <sunweaver at debian.org>  Thu, 10 Sep 2020 22:36:48
  +0200

  ayatana-indicator-messages (0.8.0-3) unstable; urgency=medium

    * Source-only upload as is.

   -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 11:56:27
  +0200

  ayatana-indicator-messages (0.8.0-2) unstable; urgency=medium

    * debian/control:
      + Add B-D systemd for [linux-any] architectures.
      + Add B-D: dh-exec.
    * debian/ayatana-indicator-messages.install:
      + Install systemd service file only for [linux-any] architectures.

   -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 11:49:04
  +0200

  ayatana-indicator-messages (0.8.0-1) unstable; urgency=medium

    * New upstream release.
    * debian/control:
      + Add to D (ayatana-indicator-messages): ayatana-indicator-common
        (>= 0.8.0).
    * debian/copyright:
      + Update copyright attributions.
    * debian/ayatana-indicator-messages.install:
      + Drop upstart conf file, add systemd service file.

   -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 09:48:49
  +0200

  ayatana-indicator-messages (0.6.2-1) unstable; urgency=medium

    * New upstream release.
    * debian/control:
      + Bump DH compat level to version 13.

   -- Mike Gabriel <sunweaver at debian.org>  Thu, 06 Aug 2020 14:20:11
  +0200

  ayatana-indicator-messages (0.6.1-1) unstable; urgency=medium

    * New upstream release.
      - Stop using deprecated g_type_class_add_private. (Closes: #951994).
    * debian/patches:
      + Drop 0001_Fix-pkg-config-file-library-and-path-flags.patch. Applied
        upstream.
    * debian/control:
      + Bump Standards-Version: to 4.5.0. No changes needed.
      + Add Rules-Requires-Root: field and set it to 'no'.
    * debian/{control,compat}:
      + Switch to debhelper-compat notation, bump DH compat level to version 12.
    * debian/rules:
      + Switch from dh_install --fail-missing to dh_missing --fail-missing.
    * debian/ayatana-indicator-messages.install:
      + Adapt installation path. Service executable now gets installed to
        /usr/libexec/.
    * debian/libmessaging-menu0.symbols:
      + Add Build-Depends-Package: metadata field.

   -- Mike Gabriel <sunweaver at debian.org>  Mon, 24 Feb 2020 10:08:04
  +0100

  ayatana-indicator-messages (0.6.0-3) unstable; urgency=medium

    * debian/control:
      + Add B/R for indicator-messages. The a-i-messages and i-messages bin:pkgs
        share the same artwork files.
      + Bump Standards-Version: to 4.4.0. No changes needed.
    * debian/patches:
      + Add 0001_Fix-pkg-config-file-library-and-path-flags.patch. Adapt paths and
        filenames to recently reworked install target. (Closes: #923958).

   -- Mike Gabriel <sunweaver at debian.org>  Wed, 07 Aug 2019 01:54:05
  +0200

  ayatana-indicator-messages (0.6.0-2) unstable; urgency=medium

    * debian/control:
      + Update Vcs-*: fields. Packaging Git has been migrated to salsa.debian.org.
      + Bump Standards-Version: to 4.2.0. No changes needed.
    * debian/upstream/metadata:
      + Add file. Comply with DEP-12.

   -- Mike Gabriel <sunweaver at debian.org>  Tue, 14 Aug 2018 18:51:18
  +0200

  ayatana-indicator-messages (0.6.0-1) unstable; urgency=medium

    * Initial release to Debian. (Closes: #893875).

   -- Mike Gabriel <sunweaver at debian.org>  Fri, 23 Mar 2018 15:16:57
  +0100

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



From 1941738 at bugs.launchpad.net  Thu Aug 26 11:45:36 2021
From: 1941738 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 26 Aug 2021 11:45:36 -0000
Subject: [Bug 1941738] Re: Sync lomiri-url-dispatcher 0.1.0-4 (universe) from
 Debian unstable (main)
References: <162997780622.25227.2238029284413556286.malonedeb@chaenomeles.canonical.com>
Message-ID: <162997833648.26458.18197950885784086274.malone@gac.canonical.com>

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

** Changed in: 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/1941738

Title:
  Sync lomiri-url-dispatcher 0.1.0-4 (universe) from Debian unstable
  (main)

Status in Ubuntu:
  Confirmed

Bug description:
  Please sync lomiri-url-dispatcher 0.1.0-4 (universe) from Debian
  unstable (main)

  lomiri-url-dispatcher-dev is a Build-Depends for newer packaging
  revisions of:

    * ayatana-indicator-datetime
    * ayatana-indicator-power
    * ayatana-indicator-session
    * ayatana-indicator-sound

  lomiri-url-dispatcher was uploaded to Debian in December 2020, so I'm not sure why
  it hasn't automatially synced to Ubuntu yet.

  All changelog entries:

  lomiri-url-dispatcher (0.1.0-4) unstable; urgency=medium

    * debian/rules:
      + Add dh_auto_test override. Run tests in --no-parallel mode.
    * debian/control:
      + Update versioned B-D on cmake-extras (>= 1.5-7~).
      + Drop alternative B-D on google-mock. B-D on googletest is sufficient these
        days.
      + Add B-D on libgtest-dev.
      + Bump Standards-Version: to 4.5.1. No changes needed.

   -- Mike Gabriel <sunweaver at debian.org>  Sun, 13 Dec 2020 16:03:30
  +0100

  lomiri-url-dispatcher (0.1.0-3) unstable; urgency=medium

    * debian/patches:
      + Add 1001_fix-runtime-error-fftbfs.patch. Add missing include of
        <stdexcept>. Fixes FTBFS against GCC-10.

   -- Mike Gabriel <sunweaver at debian.org>  Sun, 27 Sep 2020 16:10:28
  +0200

  lomiri-url-dispatcher (0.1.0-2) unstable; urgency=medium

    * debian/control:
      + Fix Vcs-*: URLs.

   -- Mike Gabriel <sunweaver at debian.org>  Mon, 07 Sep 2020 21:44:44
  +0200

  lomiri-url-dispatcher (0.1.0-1) unstable; urgency=medium

    * Initial upload to Debian. (Closes: #961698).
    * Adapt for packaging Lomiri's fork of URL Dispatcher.
    * Adapt for uploading to Debian (instead of Ubuntu).

    * debian/control:
      + Bump DH compat level to version 13.
      + Drop full-stop from SYNOPSIS fields.
      + Drop ${python3:Depends} from D (lomiri-url-dispatcher-testability).
      + Update not-yet-available Ds and mark with FIXME.
    * debian/rules:
      + Add get-orig-source target.
      + Set hardening build flags.
    * debian/copyright:
      + Update URLs. Use secure proto.
      + Add auto-generated copyright.in file for tracking copyright changes.
      + Update copyright attributions.
    * debian/watch:
      + Add file.
    * lintian:
      + Override desktop-command-not-in-package for QML application.
      + Override binary-without-manpage (for now).

   -- Mike Gabriel <sunweaver at debian.org>  Thu, 28 May 2020 08:40:36
  +0200

  url-dispatcher (0.2+ubports) bionic; urgency=medium

    * Imported to UBports

   -- UBports auto importer <infra at ubports.com>  Fri, 13 Oct 2017
  19:54:36 +0200

  url-dispatcher (0.1+17.04.20170328-0ubuntu1) zesty; urgency=medium

    * Fix deprecation warning in mir mock.
    * The unity8-dash interface is actually com.canonical.UnityDash.
    * Use libwhoopsie for reporting recoverable problems.
    * Convert service main process and url-dispatcher tool code to C++.

   -- Rodney Dawes <rodney.dawes at canonical.com>  Tue, 28 Mar 2017
  18:29:07 +0000

  url-dispatcher (0.1+17.04.20170318-0ubuntu1) zesty; urgency=medium

    * Update bad-url exec tool to UAL C++ interface
    * Remove Upstart from the test suite and replace it with systemd

   -- Ted Gould <ted at gould.cx>  Sat, 18 Mar 2017 19:59:26 +0000

  url-dispatcher (0.1+17.04.20170314-0ubuntu1) zesty; urgency=medium

    [ Charles Kerr ]
    * Honor XDG_CACHE_HOME in url-dispatcher-dump and url-dispatcher.conf

    [ Rodney Dawes ]
    * Remove click usage and support.
    * Use gmock module from cmake-extras.
    * Use the coverage support from cmake-extras.
    * Use cmake-extras intltool support.
    * Use gdbus integration from cmake-extras.
    * Remove unused gsettings cmake module.

   -- Rodney Dawes <rodney.dawes at canonical.com>  Tue, 14 Mar 2017
  14:35:03 +0000

  url-dispatcher (0.1+17.04.20170308.1-0ubuntu1) zesty; urgency=medium

    * Don't use upstart to get unity8 pid.

   -- Rodney Dawes <rodney.dawes at canonical.com>  Wed, 08 Mar 2017
  20:43:30 +0000

  url-dispatcher (0.1+17.04.20170227.2-0ubuntu1) zesty; urgency=medium

    [ Ken VanDine ]
    * Handle UAL API bump

    [ Rodney Dawes ]
    * Remove tests that depend on libertine, as url-dispatcher has no
      support for handlers in libertine anyway.

   -- Rodney Dawes <rodney.dawes at canonical.com>  Mon, 27 Feb 2017
  19:07:50 +0000

  url-dispatcher (0.1+17.04.20161206-0ubuntu1) zesty; urgency=medium

    [ Ted Gould ]
    * Instead of sleeping make the refresh tasks low enough priority they
      don't get in the way (LP: #1645793)
    * Start after Unity8 so it has a chance to set the MIR_SOCKET

   -- Michael Terry <michael.terry at canonical.com>  Tue, 06 Dec 2016
  14:38:17 +0000

  url-dispatcher (0.1+17.04.20161108-0ubuntu1) zesty; urgency=medium

    * Support running inside a snap.

   -- Michael Terry <michael.terry at canonical.com>  Tue, 08 Nov 2016
  22:16:56 +0000

  url-dispatcher (0.1+17.04.20161107-0ubuntu1) zesty; urgency=medium

    [ Florian Boucault ]
    * Crossbuilding Fixes

    [ Larry Price ]
    * App ID should allow package names with dots. (LP: #1591342) (LP: #1606498)

    [ Ted Gould ]
    * Check versions of appid:// urls to reduce the number of invalid appids
      we send to UAL (LP: #1352656)
    * Scope testing for the scope:// URL and overlays that should be over
      the dash
    * Protect the dash from getting NULL urls (LP: #1476257)
    * Make sure URL Overlays are shutdown on exit
    * Remove the wildcard that is confusing the update script (LP: #1461496)
    * Not using a message that isn't set properly (LP: #1608009)
    * Fixing tests to adjust for UAL changes
    * Add a small GUI helper tool for testing
    * Show error dialog over apps that use Bad URLs (LP: #1370008)

   -- Ted Gould <ted at gould.cx>  Mon, 07 Nov 2016 16:33:15 +0000

  url-dispatcher (0.1+16.10.20160816.1-0ubuntu1) yakkety; urgency=medium

    * No chnage rebuild for UAL migration

   -- Ted Gould <ted at gould.cx>  Tue, 16 Aug 2016 15:20:27 +0000

  url-dispatcher (0.1+16.04.20151110-0ubuntu2) xenial; urgency=high

    * No change rebuild for s390x.

   -- Dimitri John Ledkov <xnox at ubuntu.com>  Fri, 11 Dec 2015 01:30:51
  +0000

  url-dispatcher (0.1+16.04.20151110-0ubuntu1) xenial; urgency=medium

    [ CI Train Bot ]
    * New rebuild forced.

    [ Ted Gould ]
    * Remove the cache if the service fails to start. Fail to start if we
      can't create the database. (LP: #1483854)

   -- Bill Filler <ci-train-bot at canonical.com>  Tue, 10 Nov 2015
  14:37:07 +0000

  url-dispatcher (0.1+15.10.20150717-0ubuntu1) wily; urgency=medium

    [ Andreas Pokorny ]
    * unchagned for mir release 0.14.0

   -- CI Train Bot <ci-train-bot at canonical.com>  Fri, 17 Jul 2015
  12:37:44 +0000

  url-dispatcher (0.1+15.10.20150612-0ubuntu1) wily; urgency=medium

    [ Ted Gould ]
    * Add upstart build dep for tests on Wily
    * Provide a small tool to dump the URL DB in a readable form
    * Support URL Overlays of content in a trusted session without a
      desktop file

   -- CI Train Bot <ci-train-bot at canonical.com>  Fri, 12 Jun 2015
  16:00:40 +0000

  url-dispatcher (0.1+15.04.20150123-0ubuntu1) vivid; urgency=low

    [ Ted Gould ]
    * Special handling for intent URLs (LP: #1407709)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 23 Jan
  2015 15:19:33 +0000

  url-dispatcher (0.1+15.04.20141211-0ubuntu1) vivid; urgency=low

    [ Ted Gould ]
    * Fix domain handling in generic regular expression (LP: #1401612)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 11 Dec
  2014 19:43:40 +0000

  url-dispatcher (0.1+15.04.20141031-0ubuntu1) vivid; urgency=low

    [ Ted Gould ]
    * Making generic regular expression more robust (LP: #1351222)

    [ Jussi Pakkanen ]
    * General cleanups
    * Do a rollback when update operations fail so there are no dangling
      transactions.
    * Ensure that tables always exist.

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 31 Oct
  2014 15:51:36 +0000

  url-dispatcher (0.1+14.10.20140925-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Drop file based URLs for Music and Video (LP: #1340952)
    * Update tests to work with new UAL requirements (LP: #1370735)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 25 Sep
  2014 13:29:40 +0000

  url-dispatcher (0.1+14.10.20140905.1-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Throw a bad_url on the appid 'unconfined'

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 05 Sep
  2014 03:40:44 +0000

  url-dispatcher (0.1+14.10.20140827-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Split update jobs into independent jobs
    * Support for unity8-dash URLs even though it's not an application
      (LP: #1361349)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Wed, 27 Aug
  2014 02:10:21 +0000

  url-dispatcher (0.1+14.10.20140819.1-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Ensure send works even without a mainloop (LP: #1356077)
    * Test replacing a timestamp

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 19 Aug
  2014 21:01:10 +0000

  url-dispatcher (0.1+14.10.20140724-0ubuntu1) utopic; urgency=low

    [ Ubuntu daily release ]
    * debian/liburl-dispatcher1.symbols: auto-update to released version

    [ Ted Gould ]
    * Make the database handle multiple writers more robustly
    * Add a TestURL function to determine which AppID will be used for a
      given URL

    [ Leo Arias ]
    * Add url-dispatcher-testability binary package.

    [ Brendan Donegan ]
    * Add url-dispatcher-testability binary package.

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 24 Jul
  2014 17:10:14 +0000

  url-dispatcher (0.1+14.10.20140619-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Improving error messages and collecting more data

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 19 Jun
  2014 02:43:30 +0000

  url-dispatcher (0.1+14.10.20140604-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Merge and review policies
    * Recoverable errors on DB errors on update

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Wed, 04 Jun
  2014 19:07:02 +0000

  url-dispatcher (0.1+14.10.20140601-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Changing to Ubuntu App Launch

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Sun, 01 Jun
  2014 20:53:35 +0000

  url-dispatcher (0.1+14.04.20140403-0ubuntu1) trusty; urgency=low

    [ Ted Gould ]
    * Fix cache directory permissions if they got messed up (LP: #1290997)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 03 Apr
  2014 21:17:00 +0000

  url-dispatcher (0.1+14.04.20140331.1-0ubuntu1) trusty; urgency=low

    [ Ted Gould ]
    * Make it so that URLs can be installed with configuration files.
    * Switch to using libupstart-app-launch for discovering AppIDs
    * Migrate test suite to use libclick based libual

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 31 Mar
  2014 17:18:43 +0000

  url-dispatcher (0.1+14.04.20140217.1-0ubuntu1) trusty; urgency=low

    [ Ted Gould ]
    * Add tests for the library and service as a binary.
    * Upgrading to libupstart-app-launch v2.
    * Flushing trunk with a release
    * Update Upstart mock for the new UAL

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 17 Feb
  2014 17:58:44 +0000

  url-dispatcher (0.1+14.04.20131209.1-0ubuntu2) trusty; urgency=low

    * Restrict on which arch we build url-dispatcher due to the ust
  build-dep

   -- Didier Roche <didrocks at ubuntu.com>  Mon, 09 Dec 2013 13:41:41
  +0100

  url-dispatcher (0.1+14.04.20131209.1-0ubuntu1) trusty; urgency=low

    * Cherry-pick libupstart-app-launch API/ABI bump from trunk

   -- Łukasz 'sil2100' Zemczak <lukasz.zemczak at canonical.com>  Fri, 06
  Dec 2013 14:32:26 +0100

  url-dispatcher (0.1+13.10.20131014.2-0ubuntu1) saucy; urgency=low

    [ Michal Hruby ]
    * Revert the definition change for mediaplayer, it'll remain a non-
      click app for now.

    [ Ted Gould ]
    * Adds the appid:// URL format.
    * Use 'click info' to get the manifest. (LP: #1232118)
    * Allow custom URIs to have variable based package specifications.
    * Switching many core apps to Click App ID's.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 38

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 14 Oct
  2013 18:07:27 +0000

  url-dispatcher (0.1+13.10.20131003-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Enfoce the ///. (LP: #1231444)
    * Make dispatcher more testable and add some application:/// tests.
    * Adding a calendar URL. (LP: #1231136)
    * Adding the alarm URL pattern. (LP: #1233176)

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 32

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 03 Oct
  2013 02:08:19 +0000

  url-dispatcher (0.1+13.10.20130924.1-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Report a recoverable problem on Bad URLs.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 27

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 24 Sep
  2013 06:09:10 +0000

  url-dispatcher (0.1+13.10.20130919.3-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Fix the name of the dialer-app.
    * Fix the URI environment variable by properly using libupstart-app-
      launch.
    * Add URLs for PIM apps.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 25

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 19 Sep
  2013 14:05:04 +0000

  url-dispatcher (0.1+13.10.20130917.1-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Call webbrowser for http/https URLs.
    * Switch the library relationship to the service to a Suggests.
    * URLs for music and video application launching.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 21

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 17 Sep
  2013 22:11:05 +0000

  url-dispatcher (0.1+13.10.20130823-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Adding a URL format for system settings.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 17

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 23 Aug
  2013 02:06:01 +0000

  url-dispatcher (0.1+13.10.20130726-0ubuntu1) saucy; urgency=low

    [ Łukasz 'sil2100' Zemczak ]
    * Add symbols file, modify the package's short descriptions.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 15

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 26 Jul
  2013 00:02:46 +0000

  url-dispatcher (0.1+13.10.20130725.1-0ubuntu1) saucy; urgency=low

    [ Łukasz 'sil2100' Zemczak ]
    * Remove debian/watch
    * debian/control:
      - Modifications related to compliance with our packaging standards
    * Add copyright info to the source code
    * Automatic snapshot from revision 11 (bootstrap)
    * Additional packaging changes, since some things got missed last
      time.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 13

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 25 Jul
  2013 07:52:47 +0000

  url-dispatcher (0.1-0ubuntu1) saucy; urgency=low

    * Start

   -- Ted Gould <ted at ubuntu.com>  Thu, 27 Jun 2013 11:36:18 -0500

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



From 1941740 at bugs.launchpad.net  Thu Aug 26 14:03:41 2021
From: 1941740 at bugs.launchpad.net (Norbert)
Date: Thu, 26 Aug 2021 14:03:41 -0000
Subject: [Bug 1941740] Re: Sync ayatana-indicator-messages 0.8.2-1 (universe)
 from Debian unstable (main)
References: <162997822537.12927.7434014460143517533.malonedeb@soybean.canonical.com>
Message-ID: <162998662187.16727.5784524719056948891.launchpad@soybean.canonical.com>

** Tags added: impish

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

Title:
  Sync ayatana-indicator-messages 0.8.2-1 (universe) from Debian
  unstable (main)

Status in Ubuntu:
  Confirmed

Bug description:
  Please sync ayatana-indicator-messages 0.8.2-1 (universe) from Debian
  unstable (main)

  This is part of the suite of Ayatana Indicators and Ubuntu MATE users are
  requesting this package is made available following our recent migration to
  Ayatana Indicators.

  All changelog entries:

  ayatana-indicator-messages (0.8.2-1) unstable; urgency=medium

    * New upstream release.
    * debian/control:
      + Bump Standards-Version: to 4.5.1. No changes needed.
      + Fix capitalization of the word 'Xfce'.
    * debian/watch:
      + Update format version to 4.
    * debian/rules:
      + Move gtk-doc html files into package's doc folder.
    * debian/libmessaging-menu-dev.doc-base:
      + Add file.

   -- Mike Gabriel <sunweaver at debian.org>  Wed, 03 Feb 2021 13:15:27
  +0100

  ayatana-indicator-messages (0.8.1-2) unstable; urgency=medium

    * debian/control:
      + Add Debian UBports Team to Uploaders: field.
      + Mention desktop envs that support system indicators in LONG_DESCRIPTION.
      + Typo fix in LONG_DESCRIPTION.

   -- Mike Gabriel <sunweaver at debian.org>  Sat, 07 Nov 2020 15:12:17
  +0100

  ayatana-indicator-messages (0.8.1-1) unstable; urgency=medium

    * New upstream release.

   -- Mike Gabriel <sunweaver at debian.org>  Thu, 10 Sep 2020 22:36:48
  +0200

  ayatana-indicator-messages (0.8.0-3) unstable; urgency=medium

    * Source-only upload as is.

   -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 11:56:27
  +0200

  ayatana-indicator-messages (0.8.0-2) unstable; urgency=medium

    * debian/control:
      + Add B-D systemd for [linux-any] architectures.
      + Add B-D: dh-exec.
    * debian/ayatana-indicator-messages.install:
      + Install systemd service file only for [linux-any] architectures.

   -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 11:49:04
  +0200

  ayatana-indicator-messages (0.8.0-1) unstable; urgency=medium

    * New upstream release.
    * debian/control:
      + Add to D (ayatana-indicator-messages): ayatana-indicator-common
        (>= 0.8.0).
    * debian/copyright:
      + Update copyright attributions.
    * debian/ayatana-indicator-messages.install:
      + Drop upstart conf file, add systemd service file.

   -- Mike Gabriel <sunweaver at debian.org>  Tue, 18 Aug 2020 09:48:49
  +0200

  ayatana-indicator-messages (0.6.2-1) unstable; urgency=medium

    * New upstream release.
    * debian/control:
      + Bump DH compat level to version 13.

   -- Mike Gabriel <sunweaver at debian.org>  Thu, 06 Aug 2020 14:20:11
  +0200

  ayatana-indicator-messages (0.6.1-1) unstable; urgency=medium

    * New upstream release.
      - Stop using deprecated g_type_class_add_private. (Closes: #951994).
    * debian/patches:
      + Drop 0001_Fix-pkg-config-file-library-and-path-flags.patch. Applied
        upstream.
    * debian/control:
      + Bump Standards-Version: to 4.5.0. No changes needed.
      + Add Rules-Requires-Root: field and set it to 'no'.
    * debian/{control,compat}:
      + Switch to debhelper-compat notation, bump DH compat level to version 12.
    * debian/rules:
      + Switch from dh_install --fail-missing to dh_missing --fail-missing.
    * debian/ayatana-indicator-messages.install:
      + Adapt installation path. Service executable now gets installed to
        /usr/libexec/.
    * debian/libmessaging-menu0.symbols:
      + Add Build-Depends-Package: metadata field.

   -- Mike Gabriel <sunweaver at debian.org>  Mon, 24 Feb 2020 10:08:04
  +0100

  ayatana-indicator-messages (0.6.0-3) unstable; urgency=medium

    * debian/control:
      + Add B/R for indicator-messages. The a-i-messages and i-messages bin:pkgs
        share the same artwork files.
      + Bump Standards-Version: to 4.4.0. No changes needed.
    * debian/patches:
      + Add 0001_Fix-pkg-config-file-library-and-path-flags.patch. Adapt paths and
        filenames to recently reworked install target. (Closes: #923958).

   -- Mike Gabriel <sunweaver at debian.org>  Wed, 07 Aug 2019 01:54:05
  +0200

  ayatana-indicator-messages (0.6.0-2) unstable; urgency=medium

    * debian/control:
      + Update Vcs-*: fields. Packaging Git has been migrated to salsa.debian.org.
      + Bump Standards-Version: to 4.2.0. No changes needed.
    * debian/upstream/metadata:
      + Add file. Comply with DEP-12.

   -- Mike Gabriel <sunweaver at debian.org>  Tue, 14 Aug 2018 18:51:18
  +0200

  ayatana-indicator-messages (0.6.0-1) unstable; urgency=medium

    * Initial release to Debian. (Closes: #893875).

   -- Mike Gabriel <sunweaver at debian.org>  Fri, 23 Mar 2018 15:16:57
  +0100

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



From 1941738 at bugs.launchpad.net  Thu Aug 26 14:03:53 2021
From: 1941738 at bugs.launchpad.net (Norbert)
Date: Thu, 26 Aug 2021 14:03:53 -0000
Subject: [Bug 1941738] Re: Sync lomiri-url-dispatcher 0.1.0-4 (universe) from
 Debian unstable (main)
References: <162997780622.25227.2238029284413556286.malonedeb@chaenomeles.canonical.com>
Message-ID: <162998663413.29715.9608192909893725655.launchpad@gac.canonical.com>

** Tags added: impish

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

Title:
  Sync lomiri-url-dispatcher 0.1.0-4 (universe) from Debian unstable
  (main)

Status in Ubuntu:
  Confirmed

Bug description:
  Please sync lomiri-url-dispatcher 0.1.0-4 (universe) from Debian
  unstable (main)

  lomiri-url-dispatcher-dev is a Build-Depends for newer packaging
  revisions of:

    * ayatana-indicator-datetime
    * ayatana-indicator-power
    * ayatana-indicator-session
    * ayatana-indicator-sound

  lomiri-url-dispatcher was uploaded to Debian in December 2020, so I'm not sure why
  it hasn't automatially synced to Ubuntu yet.

  All changelog entries:

  lomiri-url-dispatcher (0.1.0-4) unstable; urgency=medium

    * debian/rules:
      + Add dh_auto_test override. Run tests in --no-parallel mode.
    * debian/control:
      + Update versioned B-D on cmake-extras (>= 1.5-7~).
      + Drop alternative B-D on google-mock. B-D on googletest is sufficient these
        days.
      + Add B-D on libgtest-dev.
      + Bump Standards-Version: to 4.5.1. No changes needed.

   -- Mike Gabriel <sunweaver at debian.org>  Sun, 13 Dec 2020 16:03:30
  +0100

  lomiri-url-dispatcher (0.1.0-3) unstable; urgency=medium

    * debian/patches:
      + Add 1001_fix-runtime-error-fftbfs.patch. Add missing include of
        <stdexcept>. Fixes FTBFS against GCC-10.

   -- Mike Gabriel <sunweaver at debian.org>  Sun, 27 Sep 2020 16:10:28
  +0200

  lomiri-url-dispatcher (0.1.0-2) unstable; urgency=medium

    * debian/control:
      + Fix Vcs-*: URLs.

   -- Mike Gabriel <sunweaver at debian.org>  Mon, 07 Sep 2020 21:44:44
  +0200

  lomiri-url-dispatcher (0.1.0-1) unstable; urgency=medium

    * Initial upload to Debian. (Closes: #961698).
    * Adapt for packaging Lomiri's fork of URL Dispatcher.
    * Adapt for uploading to Debian (instead of Ubuntu).

    * debian/control:
      + Bump DH compat level to version 13.
      + Drop full-stop from SYNOPSIS fields.
      + Drop ${python3:Depends} from D (lomiri-url-dispatcher-testability).
      + Update not-yet-available Ds and mark with FIXME.
    * debian/rules:
      + Add get-orig-source target.
      + Set hardening build flags.
    * debian/copyright:
      + Update URLs. Use secure proto.
      + Add auto-generated copyright.in file for tracking copyright changes.
      + Update copyright attributions.
    * debian/watch:
      + Add file.
    * lintian:
      + Override desktop-command-not-in-package for QML application.
      + Override binary-without-manpage (for now).

   -- Mike Gabriel <sunweaver at debian.org>  Thu, 28 May 2020 08:40:36
  +0200

  url-dispatcher (0.2+ubports) bionic; urgency=medium

    * Imported to UBports

   -- UBports auto importer <infra at ubports.com>  Fri, 13 Oct 2017
  19:54:36 +0200

  url-dispatcher (0.1+17.04.20170328-0ubuntu1) zesty; urgency=medium

    * Fix deprecation warning in mir mock.
    * The unity8-dash interface is actually com.canonical.UnityDash.
    * Use libwhoopsie for reporting recoverable problems.
    * Convert service main process and url-dispatcher tool code to C++.

   -- Rodney Dawes <rodney.dawes at canonical.com>  Tue, 28 Mar 2017
  18:29:07 +0000

  url-dispatcher (0.1+17.04.20170318-0ubuntu1) zesty; urgency=medium

    * Update bad-url exec tool to UAL C++ interface
    * Remove Upstart from the test suite and replace it with systemd

   -- Ted Gould <ted at gould.cx>  Sat, 18 Mar 2017 19:59:26 +0000

  url-dispatcher (0.1+17.04.20170314-0ubuntu1) zesty; urgency=medium

    [ Charles Kerr ]
    * Honor XDG_CACHE_HOME in url-dispatcher-dump and url-dispatcher.conf

    [ Rodney Dawes ]
    * Remove click usage and support.
    * Use gmock module from cmake-extras.
    * Use the coverage support from cmake-extras.
    * Use cmake-extras intltool support.
    * Use gdbus integration from cmake-extras.
    * Remove unused gsettings cmake module.

   -- Rodney Dawes <rodney.dawes at canonical.com>  Tue, 14 Mar 2017
  14:35:03 +0000

  url-dispatcher (0.1+17.04.20170308.1-0ubuntu1) zesty; urgency=medium

    * Don't use upstart to get unity8 pid.

   -- Rodney Dawes <rodney.dawes at canonical.com>  Wed, 08 Mar 2017
  20:43:30 +0000

  url-dispatcher (0.1+17.04.20170227.2-0ubuntu1) zesty; urgency=medium

    [ Ken VanDine ]
    * Handle UAL API bump

    [ Rodney Dawes ]
    * Remove tests that depend on libertine, as url-dispatcher has no
      support for handlers in libertine anyway.

   -- Rodney Dawes <rodney.dawes at canonical.com>  Mon, 27 Feb 2017
  19:07:50 +0000

  url-dispatcher (0.1+17.04.20161206-0ubuntu1) zesty; urgency=medium

    [ Ted Gould ]
    * Instead of sleeping make the refresh tasks low enough priority they
      don't get in the way (LP: #1645793)
    * Start after Unity8 so it has a chance to set the MIR_SOCKET

   -- Michael Terry <michael.terry at canonical.com>  Tue, 06 Dec 2016
  14:38:17 +0000

  url-dispatcher (0.1+17.04.20161108-0ubuntu1) zesty; urgency=medium

    * Support running inside a snap.

   -- Michael Terry <michael.terry at canonical.com>  Tue, 08 Nov 2016
  22:16:56 +0000

  url-dispatcher (0.1+17.04.20161107-0ubuntu1) zesty; urgency=medium

    [ Florian Boucault ]
    * Crossbuilding Fixes

    [ Larry Price ]
    * App ID should allow package names with dots. (LP: #1591342) (LP: #1606498)

    [ Ted Gould ]
    * Check versions of appid:// urls to reduce the number of invalid appids
      we send to UAL (LP: #1352656)
    * Scope testing for the scope:// URL and overlays that should be over
      the dash
    * Protect the dash from getting NULL urls (LP: #1476257)
    * Make sure URL Overlays are shutdown on exit
    * Remove the wildcard that is confusing the update script (LP: #1461496)
    * Not using a message that isn't set properly (LP: #1608009)
    * Fixing tests to adjust for UAL changes
    * Add a small GUI helper tool for testing
    * Show error dialog over apps that use Bad URLs (LP: #1370008)

   -- Ted Gould <ted at gould.cx>  Mon, 07 Nov 2016 16:33:15 +0000

  url-dispatcher (0.1+16.10.20160816.1-0ubuntu1) yakkety; urgency=medium

    * No chnage rebuild for UAL migration

   -- Ted Gould <ted at gould.cx>  Tue, 16 Aug 2016 15:20:27 +0000

  url-dispatcher (0.1+16.04.20151110-0ubuntu2) xenial; urgency=high

    * No change rebuild for s390x.

   -- Dimitri John Ledkov <xnox at ubuntu.com>  Fri, 11 Dec 2015 01:30:51
  +0000

  url-dispatcher (0.1+16.04.20151110-0ubuntu1) xenial; urgency=medium

    [ CI Train Bot ]
    * New rebuild forced.

    [ Ted Gould ]
    * Remove the cache if the service fails to start. Fail to start if we
      can't create the database. (LP: #1483854)

   -- Bill Filler <ci-train-bot at canonical.com>  Tue, 10 Nov 2015
  14:37:07 +0000

  url-dispatcher (0.1+15.10.20150717-0ubuntu1) wily; urgency=medium

    [ Andreas Pokorny ]
    * unchagned for mir release 0.14.0

   -- CI Train Bot <ci-train-bot at canonical.com>  Fri, 17 Jul 2015
  12:37:44 +0000

  url-dispatcher (0.1+15.10.20150612-0ubuntu1) wily; urgency=medium

    [ Ted Gould ]
    * Add upstart build dep for tests on Wily
    * Provide a small tool to dump the URL DB in a readable form
    * Support URL Overlays of content in a trusted session without a
      desktop file

   -- CI Train Bot <ci-train-bot at canonical.com>  Fri, 12 Jun 2015
  16:00:40 +0000

  url-dispatcher (0.1+15.04.20150123-0ubuntu1) vivid; urgency=low

    [ Ted Gould ]
    * Special handling for intent URLs (LP: #1407709)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 23 Jan
  2015 15:19:33 +0000

  url-dispatcher (0.1+15.04.20141211-0ubuntu1) vivid; urgency=low

    [ Ted Gould ]
    * Fix domain handling in generic regular expression (LP: #1401612)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 11 Dec
  2014 19:43:40 +0000

  url-dispatcher (0.1+15.04.20141031-0ubuntu1) vivid; urgency=low

    [ Ted Gould ]
    * Making generic regular expression more robust (LP: #1351222)

    [ Jussi Pakkanen ]
    * General cleanups
    * Do a rollback when update operations fail so there are no dangling
      transactions.
    * Ensure that tables always exist.

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 31 Oct
  2014 15:51:36 +0000

  url-dispatcher (0.1+14.10.20140925-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Drop file based URLs for Music and Video (LP: #1340952)
    * Update tests to work with new UAL requirements (LP: #1370735)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 25 Sep
  2014 13:29:40 +0000

  url-dispatcher (0.1+14.10.20140905.1-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Throw a bad_url on the appid 'unconfined'

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 05 Sep
  2014 03:40:44 +0000

  url-dispatcher (0.1+14.10.20140827-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Split update jobs into independent jobs
    * Support for unity8-dash URLs even though it's not an application
      (LP: #1361349)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Wed, 27 Aug
  2014 02:10:21 +0000

  url-dispatcher (0.1+14.10.20140819.1-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Ensure send works even without a mainloop (LP: #1356077)
    * Test replacing a timestamp

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 19 Aug
  2014 21:01:10 +0000

  url-dispatcher (0.1+14.10.20140724-0ubuntu1) utopic; urgency=low

    [ Ubuntu daily release ]
    * debian/liburl-dispatcher1.symbols: auto-update to released version

    [ Ted Gould ]
    * Make the database handle multiple writers more robustly
    * Add a TestURL function to determine which AppID will be used for a
      given URL

    [ Leo Arias ]
    * Add url-dispatcher-testability binary package.

    [ Brendan Donegan ]
    * Add url-dispatcher-testability binary package.

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 24 Jul
  2014 17:10:14 +0000

  url-dispatcher (0.1+14.10.20140619-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Improving error messages and collecting more data

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 19 Jun
  2014 02:43:30 +0000

  url-dispatcher (0.1+14.10.20140604-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Merge and review policies
    * Recoverable errors on DB errors on update

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Wed, 04 Jun
  2014 19:07:02 +0000

  url-dispatcher (0.1+14.10.20140601-0ubuntu1) utopic; urgency=low

    [ Ted Gould ]
    * Changing to Ubuntu App Launch

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Sun, 01 Jun
  2014 20:53:35 +0000

  url-dispatcher (0.1+14.04.20140403-0ubuntu1) trusty; urgency=low

    [ Ted Gould ]
    * Fix cache directory permissions if they got messed up (LP: #1290997)

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 03 Apr
  2014 21:17:00 +0000

  url-dispatcher (0.1+14.04.20140331.1-0ubuntu1) trusty; urgency=low

    [ Ted Gould ]
    * Make it so that URLs can be installed with configuration files.
    * Switch to using libupstart-app-launch for discovering AppIDs
    * Migrate test suite to use libclick based libual

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 31 Mar
  2014 17:18:43 +0000

  url-dispatcher (0.1+14.04.20140217.1-0ubuntu1) trusty; urgency=low

    [ Ted Gould ]
    * Add tests for the library and service as a binary.
    * Upgrading to libupstart-app-launch v2.
    * Flushing trunk with a release
    * Update Upstart mock for the new UAL

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 17 Feb
  2014 17:58:44 +0000

  url-dispatcher (0.1+14.04.20131209.1-0ubuntu2) trusty; urgency=low

    * Restrict on which arch we build url-dispatcher due to the ust
  build-dep

   -- Didier Roche <didrocks at ubuntu.com>  Mon, 09 Dec 2013 13:41:41
  +0100

  url-dispatcher (0.1+14.04.20131209.1-0ubuntu1) trusty; urgency=low

    * Cherry-pick libupstart-app-launch API/ABI bump from trunk

   -- Łukasz 'sil2100' Zemczak <lukasz.zemczak at canonical.com>  Fri, 06
  Dec 2013 14:32:26 +0100

  url-dispatcher (0.1+13.10.20131014.2-0ubuntu1) saucy; urgency=low

    [ Michal Hruby ]
    * Revert the definition change for mediaplayer, it'll remain a non-
      click app for now.

    [ Ted Gould ]
    * Adds the appid:// URL format.
    * Use 'click info' to get the manifest. (LP: #1232118)
    * Allow custom URIs to have variable based package specifications.
    * Switching many core apps to Click App ID's.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 38

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Mon, 14 Oct
  2013 18:07:27 +0000

  url-dispatcher (0.1+13.10.20131003-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Enfoce the ///. (LP: #1231444)
    * Make dispatcher more testable and add some application:/// tests.
    * Adding a calendar URL. (LP: #1231136)
    * Adding the alarm URL pattern. (LP: #1233176)

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 32

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 03 Oct
  2013 02:08:19 +0000

  url-dispatcher (0.1+13.10.20130924.1-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Report a recoverable problem on Bad URLs.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 27

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 24 Sep
  2013 06:09:10 +0000

  url-dispatcher (0.1+13.10.20130919.3-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Fix the name of the dialer-app.
    * Fix the URI environment variable by properly using libupstart-app-
      launch.
    * Add URLs for PIM apps.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 25

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 19 Sep
  2013 14:05:04 +0000

  url-dispatcher (0.1+13.10.20130917.1-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Call webbrowser for http/https URLs.
    * Switch the library relationship to the service to a Suggests.
    * URLs for music and video application launching.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 21

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Tue, 17 Sep
  2013 22:11:05 +0000

  url-dispatcher (0.1+13.10.20130823-0ubuntu1) saucy; urgency=low

    [ Ted Gould ]
    * Adding a URL format for system settings.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 17

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 23 Aug
  2013 02:06:01 +0000

  url-dispatcher (0.1+13.10.20130726-0ubuntu1) saucy; urgency=low

    [ Łukasz 'sil2100' Zemczak ]
    * Add symbols file, modify the package's short descriptions.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 15

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Fri, 26 Jul
  2013 00:02:46 +0000

  url-dispatcher (0.1+13.10.20130725.1-0ubuntu1) saucy; urgency=low

    [ Łukasz 'sil2100' Zemczak ]
    * Remove debian/watch
    * debian/control:
      - Modifications related to compliance with our packaging standards
    * Add copyright info to the source code
    * Automatic snapshot from revision 11 (bootstrap)
    * Additional packaging changes, since some things got missed last
      time.

    [ Ubuntu daily release ]
    * Automatic snapshot from revision 13

   -- Ubuntu daily release <ps-jenkins at lists.canonical.com>  Thu, 25 Jul
  2013 07:52:47 +0000

  url-dispatcher (0.1-0ubuntu1) saucy; urgency=low

    * Start

   -- Ted Gould <ted at ubuntu.com>  Thu, 27 Jun 2013 11:36:18 -0500

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



From 1933520 at bugs.launchpad.net  Thu Aug 26 16:48:01 2021
From: 1933520 at bugs.launchpad.net (Heather Lemon)
Date: Thu, 26 Aug 2021 16:48:01 -0000
Subject: [Bug 1933520] Re: message decompressor to incorrectly allocate memory
References: <162455012060.17952.5873516193423039097.malonedeb@gac.canonical.com>
Message-ID: <162999648275.20572.14095680360457776342.launchpad@wampee.canonical.com>

** Changed in: mongodb (Ubuntu Focal)
     Assignee: (unassigned) => Heather Lemon (hypothetical-lemon)

** Changed in: mongodb (Ubuntu Bionic)
     Assignee: (unassigned) => Heather Lemon (hypothetical-lemon)

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

Title:
  message decompressor to incorrectly allocate memory

Status in mongodb source package in Bionic:
  Confirmed
Status in mongodb source package in Focal:
  Confirmed

Bug description:
  CVE 2019-20925: https://ubuntu.com/security/CVE-2019-20925

  An unauthenticated client can trigger denial of service by issuing
  specially crafted wire protocol messages, which cause the message
  decompressor to incorrectly allocate memory. This issue affects:
  MongoDB Inc. MongoDB Server v4.2 versions prior to 4.2.1; v4.0
  versions prior to 4.0.13; v3.6 versions prior to 3.6.15; v3.4 versions
  prior to 3.4.24.

  commit:
  https://github.com/mongodb/mongo/commit/c1a956e084d39e6da75cd347e63d0064ed9151a8

  Affected versions
  Ubuntu 18.04 LTS (Bionic Beaver)
  Ubuntu 20.04 LTS (Focal Fossa)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+subscriptions



From 1933520 at bugs.launchpad.net  Thu Aug 26 17:00:26 2021
From: 1933520 at bugs.launchpad.net (Heather Lemon)
Date: Thu, 26 Aug 2021 17:00:26 -0000
Subject: [Bug 1933520] Re: message decompressor to incorrectly allocate memory
References: <162455012060.17952.5873516193423039097.malonedeb@gac.canonical.com>
Message-ID: <162999722642.26981.13675495317750874163.malone@soybean.canonical.com>

focal cve-2019-20925

** Patch added: "lp1933520-focal-CVE-2019-20925.debdiff"
   https://bugs.launchpad.net/ubuntu/focal/+source/mongodb/+bug/1933520/+attachment/5520915/+files/lp1933520-focal-CVE-2019-20925.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/1933520

Title:
  message decompressor to incorrectly allocate memory

Status in mongodb source package in Bionic:
  Confirmed
Status in mongodb source package in Focal:
  Confirmed

Bug description:
  CVE 2019-20925: https://ubuntu.com/security/CVE-2019-20925

  An unauthenticated client can trigger denial of service by issuing
  specially crafted wire protocol messages, which cause the message
  decompressor to incorrectly allocate memory. This issue affects:
  MongoDB Inc. MongoDB Server v4.2 versions prior to 4.2.1; v4.0
  versions prior to 4.0.13; v3.6 versions prior to 3.6.15; v3.4 versions
  prior to 3.4.24.

  commit:
  https://github.com/mongodb/mongo/commit/c1a956e084d39e6da75cd347e63d0064ed9151a8

  Affected versions
  Ubuntu 18.04 LTS (Bionic Beaver)
  Ubuntu 20.04 LTS (Focal Fossa)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/bionic/+source/mongodb/+bug/1933520/+subscriptions



From 1923642 at bugs.launchpad.net  Fri Aug 27 12:22:44 2021
From: 1923642 at bugs.launchpad.net (Robie Basak)
Date: Fri, 27 Aug 2021 12:22:44 -0000
Subject: [Bug 1923642] Re: glib can no longer be included in extern "C" blocks
References: <161833315017.13703.12575613470550208630.malonedeb@chaenomeles.canonical.com>
Message-ID: <163006696469.29026.17664183561942744271.malone@gac.canonical.com>

Thank you for working on getting this pulled into Debian!

What's your plan for Ubuntu? Are you holding on to see if Debian uploads
soon so that Ubuntu can sync it? Or do you want your fix uploaded into
Ubuntu ahead of Debian, pending it being fixed in Debian?

I would normally expect the latter for an FTBFS fix in Ubuntu, but if
that's not your plan then we can leave it open. I'm just not sure what
you intend because this bug still has ~ubuntu-sponsors subscribed but
there's nothing ready for upload in Ubuntu right now, I don't think?

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

Title:
  glib can no longer be included in extern "C" blocks

Status in GnuCash:
  Fix Released
Status in gnucash package in Ubuntu:
  New
Status in gnucash package in Debian:
  Confirmed

Bug description:
  Glib newer than 2.66 will not support extern "C" blocks.
  For more info: https://gitlab.gnome.org/GNOME/glib/-/issues/2331

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



From 1940999 at bugs.launchpad.net  Fri Aug 27 12:30:00 2021
From: 1940999 at bugs.launchpad.net (Robie Basak)
Date: Fri, 27 Aug 2021 12:30:00 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <163006740032.20699.630997797217702916.malone@wampee.canonical.com>

Ah, sorry. I saw "disable-regex" and thought that was a description of
the resolution to the failing stack-overflow test!

If updating grep to 3.7 is the easiest way to fix the problem then we
can consider that. But since we're in Feature Freeze for Impish, this
needs an assessment for feature changes. I see you posted the changes
from 3.6 to 3.7. Does this mean you already made the assessment and if
so, what was your conclusion? If feature changes exist then we'll need a
freeze exception from the release team to proceed down this path.

> With the new information above, I think the way I have structured it
> matches the problem I'm trying to address - what do you think?

It's certainly closer but I still think it's a little misleading. Maybe
if we expanded the text it'd be closer. How about:

* New upstream version 3.7 to fix FTBFS (LP: #1940999)
* Add d/p/06-disable-test-regex.patch to disable failing test-regex

But in any case, we can leave it until we've concluded the question on
the best approach to take.

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1938438 at bugs.launchpad.net  Fri Aug 27 14:02:52 2021
From: 1938438 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Fri, 27 Aug 2021 14:02:52 -0000
Subject: [Bug 1938438] Re: sbsigntool does not build on riscv64
References: <162755865747.27382.10177718520268360098.malonedeb@chaenomeles.canonical.com>
Message-ID: <163007297217.26574.13877955651376349098.malone@chaenomeles.canonical.com>

FFe for sbsigntool was approved:
https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1941888, now
looking for a 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/1938438

Title:
  sbsigntool does not build on riscv64

Status in sbsigntool package in Ubuntu:
  New

Bug description:
  We should enable building on riscv64 for release Impish.

  Current upstream version 0.9.4 is required for running U-Boot tests.

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



From 1938438 at bugs.launchpad.net  Fri Aug 27 14:27:33 2021
From: 1938438 at bugs.launchpad.net (Thomas Ward)
Date: Fri, 27 Aug 2021 14:27:33 -0000
Subject: [Bug 1938438] Re: sbsigntool does not build on riscv64
References: <162755865747.27382.10177718520268360098.malonedeb@chaenomeles.canonical.com>
Message-ID: <163007445370.32320.4473284845429060953.malone@chaenomeles.canonical.com>

*** This bug is a duplicate of bug 1941888 ***
    https://bugs.launchpad.net/bugs/1941888

Only one bug is needed to track the upload and fix.  The FFe bug has
been designated the master for this as this and the FFe are essentially
identical.

** Changed in: sbsigntool (Ubuntu)
     Assignee: (unassigned) => Thomas Ward (teward)

** Changed in: sbsigntool (Ubuntu)
       Status: New => In Progress

** This bug has been marked a duplicate of bug 1941888
   FFe: sbsigntools 0.9.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/1938438

Title:
  sbsigntool does not build on riscv64

Status in sbsigntool package in Ubuntu:
  In Progress

Bug description:
  We should enable building on riscv64 for release Impish.

  Current upstream version 0.9.4 is required for running U-Boot tests.

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



From 1941888 at bugs.launchpad.net  Fri Aug 27 15:21:12 2021
From: 1941888 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 27 Aug 2021 15:21:12 -0000
Subject: [Bug 1941888] [NEW] FFe: sbsigntools 0.9.4
References: <163005762971.22667.819933443763571103.malonedeb@soybean.canonical.com>
Message-ID: <163007767276.13028.16895714199251811475.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Thomas Ward (teward):

FFe: sbsigntools 0.9.4

The current sbsigntool-0.9.2-2ubuntu4 package lacks support for the riscv64
architecture.

For developing UEFI booting on RISC-V we need these tools.

Since release 0.9.2 several bugs have been resolved. A major one leads
to incorrect signatures for EFI binaries.

0.9.4 brought one additional feature:

The command sbsign received an additional optional parameter --addcert for
specifying intermediate certificates.

I have prepared an upload in my PPA, which builds on all EFI enabled
architectures including riscv64 and I have tested the package locally
on riscv64 and amd64 and it works for me. There are no autopackage tests
available and device certification should test on all relevant
architectures.

Please consider a feature freeze exception for sbsigntools 0.9.4.

sbsigntool 0.9.4-2ubuntu2 is availabe in ppa:xypron/gnu-efi

Changelog:

Version 0.9.4

* sbsign: allow for adding intermediate certificates
* sbverify: fix verification with intermediate certificates
* Tests: Add intermediate certificate tests to the sign-verify cases
* Fix some openssl 1.1.0 deprecated functions
* sbvarsign: remove unused global variable
* sbverify: refer to unused function
* Fix errors on 32 bit
* Enable -Werror for builds
* docs: add man page for sbkeysync

Version 0.9.3

* README: update git location and add mailing list information
* sbvarsign: fix "EFI_VARIABLE_AUTHENTICATION_2.TimeStamp.Year" assignment
* Fix PE/COFF checksum calculation

** Affects: sbsigntool (Ubuntu)
     Importance: Undecided
     Assignee: Thomas Ward (teward)
         Status: Triaged


** Tags: riscv64
-- 
FFe: sbsigntools 0.9.4
https://bugs.launchpad.net/bugs/1941888
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1941888 at bugs.launchpad.net  Fri Aug 27 15:58:44 2021
From: 1941888 at bugs.launchpad.net (Thomas Ward)
Date: Fri, 27 Aug 2021 15:58:44 -0000
Subject: [Bug 1941888] Re: FFe: sbsigntools 0.9.4
References: <163005762971.22667.819933443763571103.malonedeb@soybean.canonical.com>
Message-ID: <163007992493.17881.12355414176561540875.malone@gac.canonical.com>

Build was successful against Impish Proposed, uploading with the changes
I mentioned - the correct version string and the full path to the
sbkeysync patch in the changelog.  Also adjusted the bug number to point
to this FFe bug, which as stated in the dupe I've defined as the
'master' tracker for this.

In future, only *one* bug is needed, and an FFe request can be done
within the original bug.  No need to make new bugs for the FFe request
and the 'new version to build in riscv' bug, they're the same bug
basically.

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

Title:
  FFe: sbsigntools 0.9.4

Status in sbsigntool package in Ubuntu:
  Triaged

Bug description:
  FFe: sbsigntools 0.9.4

  The current sbsigntool-0.9.2-2ubuntu4 package lacks support for the riscv64
  architecture.

  For developing UEFI booting on RISC-V we need these tools.

  Since release 0.9.2 several bugs have been resolved. A major one leads
  to incorrect signatures for EFI binaries.

  0.9.4 brought one additional feature:

  The command sbsign received an additional optional parameter --addcert for
  specifying intermediate certificates.

  I have prepared an upload in my PPA, which builds on all EFI enabled
  architectures including riscv64 and I have tested the package locally
  on riscv64 and amd64 and it works for me. There are no autopackage tests
  available and device certification should test on all relevant
  architectures.

  Please consider a feature freeze exception for sbsigntools 0.9.4.

  sbsigntool 0.9.4-2ubuntu2 is availabe in ppa:xypron/gnu-efi

  Changelog:

  Version 0.9.4

  * sbsign: allow for adding intermediate certificates
  * sbverify: fix verification with intermediate certificates
  * Tests: Add intermediate certificate tests to the sign-verify cases
  * Fix some openssl 1.1.0 deprecated functions
  * sbvarsign: remove unused global variable
  * sbverify: refer to unused function
  * Fix errors on 32 bit
  * Enable -Werror for builds
  * docs: add man page for sbkeysync

  Version 0.9.3

  * README: update git location and add mailing list information
  * sbvarsign: fix "EFI_VARIABLE_AUTHENTICATION_2.TimeStamp.Year" assignment
  * Fix PE/COFF checksum calculation

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



From 1941799 at bugs.launchpad.net  Fri Aug 27 17:52:38 2021
From: 1941799 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 27 Aug 2021 17:52:38 -0000
Subject: [Bug 1941799] [NEW] Please merge openssh 1:8.4p1-6 from Debian
 unstable
References: <163001202025.13938.11546441691740751547.malonedeb@wampee.canonical.com>
Message-ID: <163008675937.15847.12032857977467806762.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by William Wilson (jawn-smith):

This merge is needed because there are changes in Ubuntu that are not
present in Debian.

** Affects: openssh (Ubuntu)
     Importance: Undecided
     Assignee: William Wilson (jawn-smith)
         Status: In Progress

-- 
Please merge openssh 1:8.4p1-6 from Debian unstable
https://bugs.launchpad.net/bugs/1941799
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1941799 at bugs.launchpad.net  Fri Aug 27 17:51:50 2021
From: 1941799 at bugs.launchpad.net (William Wilson)
Date: Fri, 27 Aug 2021 17:51:50 -0000
Subject: [Bug 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
References: <163001202025.13938.11546441691740751547.malonedeb@wampee.canonical.com>
Message-ID: <163008671068.14340.4588760503072996995.malone@soybean.canonical.com>

** Patch added: "Diff from 1:8.4p1-5ubuntu2"
   https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+attachment/5521261/+files/lp1941799-ubuntu-ubuntu.debdiff

** Changed in: openssh (Ubuntu)
     Assignee: William Wilson (jawn-smith) => (unassigned)

** Changed in: openssh (Ubuntu)
       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/1941799

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

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



From 1939751 at bugs.launchpad.net  Fri Aug 27 17:54:15 2021
From: 1939751 at bugs.launchpad.net (William Wilson)
Date: Fri, 27 Aug 2021 17:54:15 -0000
Subject: [Bug 1939751] Re: openssh FTBFS with glibc >= 2.34
References: <162880212312.6537.6691163062217728505.malonedeb@chaenomeles.canonical.com>
Message-ID: <163008685578.14841.8033217851773401204.malone@gac.canonical.com>

paelzer: I worked the merge under
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799

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

Title:
  openssh FTBFS with glibc >= 2.34

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Fix Released

Bug description:
  Due to an incompatible function prototype in openbsd-compat tests,
  this package FTBFS with glibc >= 2.34. There is an upstream patch
  already in place to address this.

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



From 1933378 at bugs.launchpad.net  Fri Aug 27 17:54:19 2021
From: 1933378 at bugs.launchpad.net (Heather Lemon)
Date: Fri, 27 Aug 2021 17:54:19 -0000
Subject: [Bug 1933378] Re: Unable to build from source mongodb-server-core -
 focal
References: <162447768242.11399.4417803654669191530.malonedeb@soybean.canonical.com>
Message-ID: <163008686002.18519.14347500588860931020.launchpad@chaenomeles.canonical.com>

** Changed in: mongodb (Ubuntu Focal)
     Assignee: Heather Lemon (hypothetical-lemon) => (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/1933378

Title:
  Unable to build from source mongodb-server-core - focal

Status in mongodb source package in Focal:
  Confirmed

Bug description:
  root at focal:~/mongodb-3.6.9+really3.6.8+90~g8e540c0b6d# apt build-dep .
  Note, using directory '.' to get the build dependencies
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   builddeps:. : Depends: python-requests but it is not installable
  E: Unable to correct problems, you have held broken packages.

  root at focal:~/mongodb-3.6.9+really3.6.8+90~g8e540c0b6d# apt-get install python-requests
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  E: Unable to locate package python-requests

  ------
  Need to drop support for Python2 in mongodb-server-core focal [0] 
  [0] https://launchpad.net/ubuntu/+source/requests/2.22.0-2ubuntu1

  installed version: 1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5
  series release: focal 
  container: LXD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/focal/+source/mongodb/+bug/1933378/+subscriptions



From 1940788 at bugs.launchpad.net  Mon Aug 30 09:04:01 2021
From: 1940788 at bugs.launchpad.net (Sebastien Bacher)
Date: Mon, 30 Aug 2021 09:04:01 -0000
Subject: [Bug 1940788] Re: [SRU] the input volume of external mic for sof
 driver is 0 by default
References: <162968267413.21155.6753654366276453288.malonedeb@gac.canonical.com>
Message-ID: <163031424219.29301.2884706494514988311.launchpad@soybean.canonical.com>

** Changed in: alsa-ucm-conf (Ubuntu Impish)
       Status: In Progress => 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/1940788

Title:
  [SRU] the input volume of external mic for sof driver is 0 by default

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed

Bug description:
  The change of this SRU has been squashed to
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980.

  [Impact]
  For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully.

  [Fix]
  Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume.

  [Test]
  sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully.

  [Where problems will occur]
  This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions



From 1937980 at bugs.launchpad.net  Mon Aug 30 09:05:06 2021
From: 1937980 at bugs.launchpad.net (Sebastien Bacher)
Date: Mon, 30 Aug 2021 09:05:06 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <163031430676.32022.9128576301869306993.malone@soybean.canonical.com>

Thanks, uploaded to impish now. A small side comment since that's the
first time I notice that but somehow you end up adding empty lines
between debian/patches/series entries

** Changed in: alsa-ucm-conf (Ubuntu Impish)
       Status: In Progress => 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/1937980

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1937980 at bugs.launchpad.net  Mon Aug 30 09:10:43 2021
From: 1937980 at bugs.launchpad.net (Sebastien Bacher)
Date: Mon, 30 Aug 2021 09:10:43 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <163031464498.32488.13248476209796930614.launchpad@soybean.canonical.com>

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
       Status: In Progress => 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/1937980

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1937980 at bugs.launchpad.net  Mon Aug 30 09:23:04 2021
From: 1937980 at bugs.launchpad.net (Sebastien Bacher)
Date: Mon, 30 Aug 2021 09:23:04 -0000
Subject: [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca
 machine with kernel-5.13
References: <162726858285.21646.11473475819033453169.malonedeb@gac.canonical.com>
Message-ID: <163031538485.8795.11082320617134810639.malone@gac.canonical.com>

Upload to hirsute and focal as well now

** Changed in: alsa-ucm-conf (Ubuntu Focal)
       Status: In Progress => 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/1937980

Title:
  [SRU] the speaker doesn't work on Dell sdw sdca machine with
  kernel-5.13

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316.

  [Fix]
  Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec.

  [Test]
  sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well.

  [Where problems will occur]
  The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions



From 1941799 at bugs.launchpad.net  Mon Aug 30 19:50:02 2021
From: 1941799 at bugs.launchpad.net (Bryce Harrington)
Date: Mon, 30 Aug 2021 19:50:02 -0000
Subject: [Bug 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
References: <163001202025.13938.11546441691740751547.malonedeb@wampee.canonical.com>
Message-ID: <163035300329.27685.5652564417487017416.launchpad@soybean.canonical.com>

** Tags added: server-next

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

** Changed in: openssh (Ubuntu)
       Status: Confirmed => In Progress

** Changed in: openssh (Ubuntu)
     Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

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



From 1875129 at bugs.launchpad.net  Mon Aug 30 20:15:54 2021
From: 1875129 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 30 Aug 2021 20:15:54 -0000
Subject: [Bug 1875129] Re: [SRU] Upgrade to 1.7.3.4 to fix regression breaking
 Epoptes
References: <158787879129.23585.10689722767656581222.malonedeb@chaenomeles.canonical.com>
Message-ID: <163035455513.24930.11629026895726785297.malone@chaenomeles.canonical.com>

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

** Changed in: socat (Ubuntu Focal)
       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/1875129

Title:
  [SRU] Upgrade to 1.7.3.4 to fix regression breaking Epoptes

Status in socat package in Ubuntu:
  Fix Released
Status in socat source package in Focal:
  Confirmed
Status in socat package in Debian:
  Fix Released

Bug description:
  [Impact]
  The socat version in Focal, 1.7.3.3, has a regression that breaks the "remote terminal" functionality of the "epoptes" package.

  I reported it to Debian, and the Debian maintainer packaged the new socat 1.7.3.4 which solves the issue:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958452

  This new upstream version is a bug fixing release which I believe can be considered a microrelease:
  https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases

  Please sync it to focal-proposed.

  [Test case]
  Here are the regression details, in order to be able to reproduce it:

  Epoptes is a computer lab management tool, I'm upstream and Debian
  maintainer for it. Among other things, it uses socat to forward a
  "student" terminal to the "teacher". To reproduce the issue without
  installing Epoptes, the following similar commands may be used
  instead:

  Teacher (just run it in a terminal tab):
  xterm -e socat tcp-listen:1234,reuseaddr,keepalive=1 stdio,raw,echo=0

  Student (just run it in another terminal tab):
  TERM=xterm socat EXEC:'screen bash -l',pty,stderr tcp:localhost:1234

  This works fine with all socat versions except 1.7.3.3.
  In 1.7.3.3, it's like line buffering is enabled or something similar, and pressing for example the up arrow in the keyboard shows "^[OA" instead of displaying the last bash command. Thus, the forwarded xterm is almost unusable.

  [Regression potential]
  Low. It's a bug fixing upstream release.
  I have compiled 1.7.3.4 from source and I've been using it for about a month with no visible issues. I also installed the .deb from sid to my focal box today and it appears to work fine.
  Note though that https://tracker.debian.org/pkg/socat shows a unit test failure on arm64 (networkd-test.py), I don't know if that was the case with previous versions or not.

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



From 1942131 at bugs.launchpad.net  Mon Aug 30 20:51:58 2021
From: 1942131 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 30 Aug 2021 20:51:58 -0000
Subject: [Bug 1942131] [NEW] golang-github-ajg-form FTBFS with go 1.17
References: <163035495329.3549.10161938336212277508.malonedeb@soybean.canonical.com>
Message-ID: <163035671887.25385.8622299490638688515.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by William Wilson (jawn-smith):

Due to changes in the valid separators accepted by net/url, this package
FTBFS with go 1.17. For more information see
https://golang.org/doc/go1.17#semicolons

** Affects: golang-github-ajg-form (Ubuntu)
     Importance: Undecided
     Assignee: William Wilson (jawn-smith)
         Status: New

-- 
golang-github-ajg-form FTBFS with go 1.17
https://bugs.launchpad.net/bugs/1942131
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1942131 at bugs.launchpad.net  Mon Aug 30 20:58:47 2021
From: 1942131 at bugs.launchpad.net (William Wilson)
Date: Mon, 30 Aug 2021 20:58:47 -0000
Subject: [Bug 1942131] Re: golang-github-ajg-form FTBFS with go 1.17
References: <163035495329.3549.10161938336212277508.malonedeb@soybean.canonical.com>
Message-ID: <163035712722.1704.10571721350511196005.launchpad@chaenomeles.canonical.com>

** Bug watch added: Debian Bug tracker #993327
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993327

** Also affects: golang-github-ajg-form (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993327
   Importance: Unknown
       Status: Unknown

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

Title:
  golang-github-ajg-form FTBFS with go 1.17

Status in golang-github-ajg-form package in Ubuntu:
  New
Status in golang-github-ajg-form package in Debian:
  Unknown

Bug description:
  Due to changes in the valid separators accepted by net/url, this
  package FTBFS with go 1.17. For more information see
  https://golang.org/doc/go1.17#semicolons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-ajg-form/+bug/1942131/+subscriptions



From 1941799 at bugs.launchpad.net  Mon Aug 30 22:25:32 2021
From: 1941799 at bugs.launchpad.net (Bryce Harrington)
Date: Mon, 30 Aug 2021 22:25:32 -0000
Subject: [Bug 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
References: <163001202025.13938.11546441691740751547.malonedeb@wampee.canonical.com>
Message-ID: <163036233212.30767.6336578113562388145.malone@gac.canonical.com>

Verified locally that it builds.
The dropped change was taken upstream, and the remaining delta still looks relevant to carry.
LGTM, +1.

I've added the merge changes to git-ubuntu and sponsored the upload:

$ debuild -S -sa $(git ubuntu push-for-upload)
...
Now signing changes and any dsc files...
 signfile dsc openssh_8.4p1-6ubuntu1.dsc A661100B3DAC1D4F2CAD8A54E603B2578FB8F0FB

 fixup_buildinfo openssh_8.4p1-6ubuntu1.dsc openssh_8.4p1-6ubuntu1_source.buildinfo
 signfile buildinfo openssh_8.4p1-6ubuntu1_source.buildinfo A661100B3DAC1D4F2CAD8A54E603B2578FB8F0FB

 fixup_changes dsc openssh_8.4p1-6ubuntu1.dsc openssh_8.4p1-6ubuntu1_source.changes
 fixup_changes buildinfo openssh_8.4p1-6ubuntu1_source.buildinfo openssh_8.4p1-6ubuntu1_source.changes
 signfile changes openssh_8.4p1-6ubuntu1_source.changes A661100B3DAC1D4F2CAD8A54E603B2578FB8F0FB

Successfully signed dsc, buildinfo, changes files

$ dput ubuntu ../openssh_8.4p1-6ubuntu1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: ../openssh_8.4p1-6ubuntu1_source.changes: Valid signature from E603B2578FB8F0FB
Checking signature on .dsc
gpg: ../openssh_8.4p1-6ubuntu1.dsc: Valid signature from E603B2578FB8F0FB
Package includes an .orig.tar.gz file although the debian revision suggests
that it might not be required. Multiple uploads of the .orig.tar.gz may be
rejected by the upload queue management software.
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading openssh_8.4p1-6ubuntu1.dsc: done.
  Uploading openssh_8.4p1.orig.tar.gz: done.      
  Uploading openssh_8.4p1-6ubuntu1.debian.tar.xz: done.    
  Uploading openssh_8.4p1-6ubuntu1_source.buildinfo: done.  
  Uploading openssh_8.4p1-6ubuntu1_source.changes: done.
Successfully uploaded packages.

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

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



From 1941799 at bugs.launchpad.net  Mon Aug 30 22:33:30 2021
From: 1941799 at bugs.launchpad.net (Bryce Harrington)
Date: Mon, 30 Aug 2021 22:33:30 -0000
Subject: [Bug 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
References: <163001202025.13938.11546441691740751547.malonedeb@wampee.canonical.com>
Message-ID: <163036281048.16408.5743625436585435930.malone@wampee.canonical.com>

$ rmad openssh
 openssh | 1:8.4p1-6ubuntu1   | impish-proposed

The package was accepted to -proposed and has built successfully for all
architectures.  It'd be helpful if you could keep an eye on the update-
excuses page to make sure its autopkgtests pass successfully.  The
autopkgtests failed in my local environment due to warnings about
permissions on some tmp dirs; possibly this issue won't affect the
buildd environment so the tests will be ok, but worth watching.

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

Title:
  Please merge openssh 1:8.4p1-6 from Debian unstable

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  This merge is needed because there are changes in Ubuntu that are not
  present in Debian.

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



From 1940999 at bugs.launchpad.net  Mon Aug 30 23:40:46 2021
From: 1940999 at bugs.launchpad.net (Dan Bungert)
Date: Mon, 30 Aug 2021 23:40:46 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <163036684644.819.12215727630655435825.malone@chaenomeles.canonical.com>

Add upstream NEWS file diff.
One change that upstream felt relevant enough to point out, outside of bug fixes, was a change to a Windows only option.

** Attachment removed: "grep_3.7-0ubuntu1.debian.tar.xz"
   https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520320/+files/grep_3.7-0ubuntu1.debian.tar.xz

** Attachment removed: "grep_3.7-0ubuntu1.dsc"
   https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520321/+files/grep_3.7-0ubuntu1.dsc

** Attachment removed: "changes.summary"
   https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520322/+files/changes.summary

** Patch added: "upstream-NEWS.diff"
   https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521727/+files/upstream-NEWS.diff

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1940999 at bugs.launchpad.net  Mon Aug 30 23:41:31 2021
From: 1940999 at bugs.launchpad.net (Dan Bungert)
Date: Mon, 30 Aug 2021 23:41:31 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <163036689154.28672.14417865558997969550.malone@wampee.canonical.com>

** Attachment added: "grep_3.7-0ubuntu1.debian.tar.xz"
   https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521728/+files/grep_3.7-0ubuntu1.debian.tar.xz

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1940999 at bugs.launchpad.net  Mon Aug 30 23:42:06 2021
From: 1940999 at bugs.launchpad.net (Dan Bungert)
Date: Mon, 30 Aug 2021 23:42:06 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <163036692631.30650.7502171560062911273.malone@wampee.canonical.com>

** Attachment added: "grep_3.7-0ubuntu1.dsc"
   https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521729/+files/grep_3.7-0ubuntu1.dsc

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1940999 at bugs.launchpad.net  Mon Aug 30 23:53:32 2021
From: 1940999 at bugs.launchpad.net (Dan Bungert)
Date: Mon, 30 Aug 2021 23:53:32 -0000
Subject: [Bug 1940999] Re: FTBFS against glibc 2.34
References: <162983252548.29949.12868510397424369973.malonedeb@gac.canonical.com>
Message-ID: <163036761223.17561.13209197443866530470.malone@soybean.canonical.com>

> How about:
> * New upstream version 3.7 to fix FTBFS (LP: #1940999)

Yes, I like that better.


OK, I have updated my proposal.  I recommend that we address this FTBFS by using grep 3.7 with built-in regex.  This is a change from current and will increase binary size.   (180k -> 260k when built locally) but passes all tests without adding a skip directive.

grep 3.7 looks reasonably benign in terms of a new release.  One change
is called out as neither a feature nor a bug fix, but upstream says it's
only relevant to Windows.  See the NEWS diff for the wording there.  I'm
happy to go the feature freeze exception route, but I think we are
covered based on that ChangeLog/NEWS.  That said, I will defer to
suggestions here.

> If updating grep to 3.7 is the easiest way to fix the problem then we
can consider that.

We could pull out the fix(es) as needed from the gnulib updates but that
sounds like not a generally wise choice.  I have not investigated this
angle.

I believe all feedback has been addressed, except for the forward to
Debian step which I'm intentionally deferring while we discuss
solutions.

Please let me know what you think, Robie.  Thanks!

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

Title:
  FTBFS against glibc 2.34

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  The package grep failed to build in a recent archive rebuild, see
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#foundations-bugs .

  The failure is in automated test, as follows:

  stack-overflow: failed test: grep never printed "stack overflow"
  FAIL: stack-overflow

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



From 1938582 at bugs.launchpad.net  Tue Aug 31 08:01:45 2021
From: 1938582 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 31 Aug 2021 08:01:45 -0000
Subject: [Bug 1938582] [NEW] efitools does not build on RISC-V
References: <162765884370.19236.15559321356354507181.malonedeb@wampee.canonical.com>
Message-ID: <163039690572.17090.17118751849790931136.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Heinrich Schuchardt (xypron):

make.rules must be adjusted for building on RISC-V.

** Affects: efitools (Ubuntu)
     Importance: Undecided
         Status: In Progress


** Tags: fr-1543 riscv64
-- 
efitools does not build on RISC-V
https://bugs.launchpad.net/bugs/1938582
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1923335 at bugs.launchpad.net  Tue Aug 31 08:02:44 2021
From: 1923335 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 31 Aug 2021 08:02:44 -0000
Subject: [Bug 1923335] [NEW] [i915] At shutdown the spinner logo disappears
 and a second later it comes back frozen for a while (in kernel 5.11 and
 later)
References: <161812658454.9383.11225962805230887164.malonedeb@chaenomeles.canonical.com>
Message-ID: <163039696503.23109.8697475020542904893.launchpad@soybean.canonical.com>

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

At shutdown the spinner logo disapear and a scond later it comes back and stay for 15sec. When I remove "splash" from the grub commandline the shutdown is fast (no extra 15 sec.). I can't find any hints in the log. It seem to happen after the log stopped.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-01-29 (71 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210129)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5580
Package: plymouth 0.9.5-0ubuntu3
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Tags:  wayland-session hirsute
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 5.11.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/25/2020
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.2
dmi.board.name: 00C013
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd09/25/2020:br1.18:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn00C013:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5580
dmi.product.sku: 07A8
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
     Importance: Medium
         Status: Won't Fix

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

** Affects: plymouth (Fedora)
     Importance: Unknown
         Status: Unknown


** Tags: apport-collected hirsute impish performance regression-release rls-ii-incoming wayland-session
-- 
[i915] At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 and later)
https://bugs.launchpad.net/bugs/1923335
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1938582 at bugs.launchpad.net  Tue Aug 31 08:17:20 2021
From: 1938582 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Tue, 31 Aug 2021 08:17:20 -0000
Subject: [Bug 1938582] Re: efitools does not build on RISC-V
References: <162765884370.19236.15559321356354507181.malonedeb@wampee.canonical.com>
Message-ID: <163039784055.9506.489578845265189581.malone@wampee.canonical.com>

efitools - 1.9.2-1ubuntu3 is available in ppa:xypron/gnu-efi needing a
sponsor.

** Patch added: "efitools_1.9.2-1ubuntu1-1.9.2-1ubuntu3.diff"
   https://bugs.launchpad.net/ubuntu/+source/efitools/+bug/1938582/+attachment/5521845/+files/efitools_1.9.2-1ubuntu1-1.9.2-1ubuntu3.diff

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

Title:
  efitools does not build on RISC-V

Status in efitools package in Ubuntu:
  In Progress

Bug description:
  make.rules must be adjusted for building on RISC-V.

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



From 1940453 at bugs.launchpad.net  Tue Aug 31 09:34:39 2021
From: 1940453 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 31 Aug 2021 09:34:39 -0000
Subject: [Bug 1940453] [NEW] libguestfs: virt-make-fs fails on RISC-V
References: <162930289584.14500.89465326521382460.malonedeb@soybean.canonical.com>
Message-ID: <163040247962.17885.7305512845615006538.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Heinrich Schuchardt (xypron):

On RISC-V we have no KVM support yet.

LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 \
virt-make-fs --partition=gpt --size=+1M --type=vfat \
directory/ file.img

fails with

/usr/bin/qemu-system-riscv64 \
    -global virtio-blk-pci.scsi=off \
    -no-user-config \
    -enable-fips \
    -nodefaults \
    -display none \
    -machine accel=kvm:tcg \
    -m 1280 \
    -no-reboot \
    -rtc driftfix=slew \
    -kernel /var/tmp/.guestfs-1000/appliance.d/kernel \
    -initrd /var/tmp/.guestfs-1000/appliance.d/initrd \
    -object rng-random,filename=/dev/urandom,id=rng0 \
    -device virtio-rng-pci,rng=rng0 \
    -device virtio-scsi-pci,id=scsi \
    -drive file=file.img,cache=writeback,format=raw,id=hd0,if=none \
    -device scsi-hd,drive=hd0 \
    -drive file=/var/tmp/.guestfs-1000/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none,format=raw \
    -device scsi-hd,drive=appliance \
    -device virtio-serial-pci \
    -serial stdio \
    -chardev socket,path=/run/user/1000/libguestfsDDkZA7/guestfsd.sock,id=channel0 \
    -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
    -append "panic=1 console=ttyS0 edd=off udevtimeout=6000 udev.event-timeout=6000 no_timer_check lpj=4000 printk.time=1 cgroup_disable=memory usbcore.nousb cryptomgr.notests tsc=reliable 8250.nr_uarts=1 root=UUID=446eed97-23e2-4547-8f1a-288406261495 selinux=0 guestfs_verbose=1 TERM=xterm-256color"
qemu-system-riscv64: -enable-fips: warning: -enable-fips is deprecated, please build QEMU with the `libgcrypt` library as the cryptography provider to enable FIPS compliance
qemu-system-riscv64: invalid accelerator kvm
qemu-system-riscv64: falling back to tcg
qemu-system-riscv64: -device virtio-rng-pci,rng=rng0: No 'PCI' bus found for device 'virtio-rng-pci'
libguestfs: error: appliance closed the connection unexpectedly, see earlier error messages
libguestfs: child_cleanup: 0x2ae5d0ae80: child process died
libguestfs: sending SIGTERM to process 74693
libguestfs: error: /usr/bin/qemu-system-riscv64 exited with error status 1, see debug messages above

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


** Tags: fr-1630 riscv64
-- 
libguestfs: virt-make-fs fails on RISC-V
https://bugs.launchpad.net/bugs/1940453
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1940453 at bugs.launchpad.net  Tue Aug 31 09:35:03 2021
From: 1940453 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Tue, 31 Aug 2021 09:35:03 -0000
Subject: [Bug 1940453] Re: libguestfs: virt-make-fs fails on RISC-V
References: <162930289584.14500.89465326521382460.malonedeb@soybean.canonical.com>
Message-ID: <163040250356.16935.15794062663863918345.malone@soybean.canonical.com>

libguestfs (1:1.44.1-1ubuntu8) is available in ppa:xypron/gnu-efi
looking for a 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/1940453

Title:
  libguestfs: virt-make-fs fails on RISC-V

Status in libguestfs package in Ubuntu:
  New

Bug description:
  On RISC-V we have no KVM support yet.

  LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 \
  virt-make-fs --partition=gpt --size=+1M --type=vfat \
  directory/ file.img

  fails with

  /usr/bin/qemu-system-riscv64 \
      -global virtio-blk-pci.scsi=off \
      -no-user-config \
      -enable-fips \
      -nodefaults \
      -display none \
      -machine accel=kvm:tcg \
      -m 1280 \
      -no-reboot \
      -rtc driftfix=slew \
      -kernel /var/tmp/.guestfs-1000/appliance.d/kernel \
      -initrd /var/tmp/.guestfs-1000/appliance.d/initrd \
      -object rng-random,filename=/dev/urandom,id=rng0 \
      -device virtio-rng-pci,rng=rng0 \
      -device virtio-scsi-pci,id=scsi \
      -drive file=file.img,cache=writeback,format=raw,id=hd0,if=none \
      -device scsi-hd,drive=hd0 \
      -drive file=/var/tmp/.guestfs-1000/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none,format=raw \
      -device scsi-hd,drive=appliance \
      -device virtio-serial-pci \
      -serial stdio \
      -chardev socket,path=/run/user/1000/libguestfsDDkZA7/guestfsd.sock,id=channel0 \
      -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
      -append "panic=1 console=ttyS0 edd=off udevtimeout=6000 udev.event-timeout=6000 no_timer_check lpj=4000 printk.time=1 cgroup_disable=memory usbcore.nousb cryptomgr.notests tsc=reliable 8250.nr_uarts=1 root=UUID=446eed97-23e2-4547-8f1a-288406261495 selinux=0 guestfs_verbose=1 TERM=xterm-256color"
  qemu-system-riscv64: -enable-fips: warning: -enable-fips is deprecated, please build QEMU with the `libgcrypt` library as the cryptography provider to enable FIPS compliance
  qemu-system-riscv64: invalid accelerator kvm
  qemu-system-riscv64: falling back to tcg
  qemu-system-riscv64: -device virtio-rng-pci,rng=rng0: No 'PCI' bus found for device 'virtio-rng-pci'
  libguestfs: error: appliance closed the connection unexpectedly, see earlier error messages
  libguestfs: child_cleanup: 0x2ae5d0ae80: child process died
  libguestfs: sending SIGTERM to process 74693
  libguestfs: error: /usr/bin/qemu-system-riscv64 exited with error status 1, see debug messages above

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



From 1940453 at bugs.launchpad.net  Tue Aug 31 12:36:44 2021
From: 1940453 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Tue, 31 Aug 2021 12:36:44 -0000
Subject: [Bug 1940453] Re: libguestfs: virt-make-fs fails on RISC-V
References: <162930289584.14500.89465326521382460.malonedeb@soybean.canonical.com>
Message-ID: <163041340624.12779.12224937691667714553.launchpad@chaenomeles.canonical.com>

** Changed in: libguestfs (Ubuntu)
       Status: New => 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/1940453

Title:
  libguestfs: virt-make-fs fails on RISC-V

Status in libguestfs package in Ubuntu:
  In Progress

Bug description:
  On RISC-V we have no KVM support yet.

  LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1 \
  virt-make-fs --partition=gpt --size=+1M --type=vfat \
  directory/ file.img

  fails with

  /usr/bin/qemu-system-riscv64 \
      -global virtio-blk-pci.scsi=off \
      -no-user-config \
      -enable-fips \
      -nodefaults \
      -display none \
      -machine accel=kvm:tcg \
      -m 1280 \
      -no-reboot \
      -rtc driftfix=slew \
      -kernel /var/tmp/.guestfs-1000/appliance.d/kernel \
      -initrd /var/tmp/.guestfs-1000/appliance.d/initrd \
      -object rng-random,filename=/dev/urandom,id=rng0 \
      -device virtio-rng-pci,rng=rng0 \
      -device virtio-scsi-pci,id=scsi \
      -drive file=file.img,cache=writeback,format=raw,id=hd0,if=none \
      -device scsi-hd,drive=hd0 \
      -drive file=/var/tmp/.guestfs-1000/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none,format=raw \
      -device scsi-hd,drive=appliance \
      -device virtio-serial-pci \
      -serial stdio \
      -chardev socket,path=/run/user/1000/libguestfsDDkZA7/guestfsd.sock,id=channel0 \
      -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
      -append "panic=1 console=ttyS0 edd=off udevtimeout=6000 udev.event-timeout=6000 no_timer_check lpj=4000 printk.time=1 cgroup_disable=memory usbcore.nousb cryptomgr.notests tsc=reliable 8250.nr_uarts=1 root=UUID=446eed97-23e2-4547-8f1a-288406261495 selinux=0 guestfs_verbose=1 TERM=xterm-256color"
  qemu-system-riscv64: -enable-fips: warning: -enable-fips is deprecated, please build QEMU with the `libgcrypt` library as the cryptography provider to enable FIPS compliance
  qemu-system-riscv64: invalid accelerator kvm
  qemu-system-riscv64: falling back to tcg
  qemu-system-riscv64: -device virtio-rng-pci,rng=rng0: No 'PCI' bus found for device 'virtio-rng-pci'
  libguestfs: error: appliance closed the connection unexpectedly, see earlier error messages
  libguestfs: child_cleanup: 0x2ae5d0ae80: child process died
  libguestfs: sending SIGTERM to process 74693
  libguestfs: error: /usr/bin/qemu-system-riscv64 exited with error status 1, see debug messages above

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



From 1934988 at bugs.launchpad.net  Tue Aug 31 13:34:02 2021
From: 1934988 at bugs.launchpad.net (Frank Heimes)
Date: Tue, 31 Aug 2021 13:34:02 -0000
Subject: [Bug 1934988] Re: Upgrade s390-tools to latest version (2.17.0)
References: <162572924867.28009.10648315418671617816.malonedeb@chaenomeles.canonical.com>
Message-ID: <163041684249.24614.15763440511435400465.launchpad@chaenomeles.canonical.com>

** Also affects: ubuntu-z-systems
   Importance: Undecided
       Status: New

** Changed in: ubuntu-z-systems
       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/1934988

Title:
  Upgrade s390-tools to latest version (2.17.0)

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Impish:
  Fix Released

Bug description:
  Include latest version of s390-tools 2.17.0 related to kernel 5.12+

  v2.17.0 was just released:
  https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.17.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1934988/+subscriptions



From 1782984 at bugs.launchpad.net  Tue Aug 31 17:20:08 2021
From: 1782984 at bugs.launchpad.net (Brian Murray)
Date: Tue, 31 Aug 2021 17:20:08 -0000
Subject: [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed
 with multiple applications
References: <153226365365.23524.716838067617811954.malonedeb@soybean.canonical.com>
Message-ID: <163043040816.8112.13615010746549850344.malone@soybean.canonical.com>

Hello Stephen, or anyone else affected,

Accepted libx11 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libx11/2:1.6.9-2ubuntu1.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, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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: libx11 (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  In Progress
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio <fziglio at redhat.com>
  Date: Wed, 29 Jan 2020 09:06:54 +0000
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
    to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
    server reply with an event (say sequence N) and the reply to our
    last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
    last_request_read is less than N the number is widened to N + 2^32
    (assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
    request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==================
  The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation.

  EXPECTED RESULTS
  ================
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==============
  All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =================
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  ============
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  ================
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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



From 1782984 at bugs.launchpad.net  Tue Aug 31 17:30:09 2021
From: 1782984 at bugs.launchpad.net (Brian Murray)
Date: Tue, 31 Aug 2021 17:30:09 -0000
Subject: [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed
 with multiple applications
References: <153226365365.23524.716838067617811954.malonedeb@soybean.canonical.com>
Message-ID: <163043100979.12208.7385444960225096046.malone@soybean.canonical.com>

Hello Stephen, or anyone else affected,

Accepted libx11 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.5 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, what testing has been
performed on the package 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.

** Changed in: libx11 (Ubuntu Bionic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio <fziglio at redhat.com>
  Date: Wed, 29 Jan 2020 09:06:54 +0000
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
    to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
    server reply with an event (say sequence N) and the reply to our
    last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
    last_request_read is less than N the number is widened to N + 2^32
    (assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
    request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==================
  The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation.

  EXPECTED RESULTS
  ================
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==============
  All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =================
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  ============
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  ================
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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



From 1923335 at bugs.launchpad.net  Tue Aug 31 19:50:01 2021
From: 1923335 at bugs.launchpad.net (Norbert)
Date: Tue, 31 Aug 2021 19:50:01 -0000
Subject: [Bug 1923335] Re: [i915] At shutdown the spinner logo disappears and
 a second later it comes back frozen for a while (in kernel 5.11 and later)
References: <161812658454.9383.11225962805230887164.malonedeb@chaenomeles.canonical.com>
Message-ID: <163043940203.13239.11944239379041521607.malone@soybean.canonical.com>

This version work for me.

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

Title:
  [i915] At shutdown the spinner logo disappears and a second later it
  comes back frozen for a while (in kernel 5.11 and later)

Status in linux package in Ubuntu:
  Won't Fix
Status in plymouth package in Ubuntu:
  In Progress
Status in plymouth package in Fedora:
  Unknown

Bug description:
  At shutdown the spinner logo disapear and a scond later it comes back and stay for 15sec. When I remove "splash" from the grub commandline the shutdown is fast (no extra 15 sec.). I can't find any hints in the log. It seem to happen after the log stopped.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-01-29 (71 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210129)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5580
  Package: plymouth 0.9.5-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Tags:  wayland-session hirsute
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 5.11.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.2
  dmi.board.name: 00C013
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd09/25/2020:br1.18:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn00C013:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5580
  dmi.product.sku: 07A8
  dmi.sys.vendor: Dell Inc.

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



From 1879798 at bugs.launchpad.net  Tue Aug 31 20:24:03 2021
From: 1879798 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 31 Aug 2021 20:24:03 -0000
Subject: [Bug 1879798] [NEW] designate-manage pool update doesn't reflects
 targets master dns servers into zones.
References: <159001172853.19893.11183609660862809256.malonedeb@soybean.canonical.com>
Message-ID: <163044144414.30394.17177621298710286063.launchpad@chaenomeles.canonical.com>

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

[Environment]

Ubuntu + Ussuri

[Description]

If running designate-manage pool update with new targets, those targets
gets properly updated in the pool target masters list, but those aren't
reflected into the zones that belongs to this pool, therefore, the masters
associated to that zones aren't updated causing failures as the expressed
in the Further Information section.

designate-manager pool update should offer an option to update the zones
associated to the pools with the new target masters and be able to apply
these changes into existing zones.

For the case of the bind9 backend the current workaround is to manually
run the rndc modzone command with the new masters, but that's not suitable
for large installations with multiple zones and pools.


[Further information]

We have a designate/designate-bind setup. We migrated designate units to
different machines, replacing 3 designate units with 3 new units.
However, this caused issues with existing zones, including creating new
recordsets for these zones. The zone would result in having an ERROR
status and a CREATE action.

Looking at the designate bind units, we see that designate is attempting
to run:

'addzone $zone { type slave; masters {$new_designate_ips port 5354;};
file "slave.$zone.$hash"; };'

This addzone fails due to the zone already existing. However, we found
that the zone configuration (using 'rndc showzone $zone' from designate-
bind unit) still had the old designate ips for its masters. There are
also logs in /var/log/syslog like the following:

May 20 06:27:10 juju-c27f05-15-lxd-1 named[72648]: transfer of '$zone'
from $old_designate_ip#5354: failed to connect: host unreachable

We were able to resolve this issue by modifying the zone config on all
designate-bind units:

juju run -a designate-bind -- rndc modzone $zone '{ type slave; file
"slave.$zone.$hash"; masters { $new_designate_ip_1 port 5354;
$new_designate_ip_2 port 5354; $new_designate_ip_3 port 5354; }; };'

After modifying the zone, the recordset creations completed and resolved
almost immediately.

Would this be something the charm could do in an automated way when
masters are removed/replaced, or is there a better way of fixing the
zone configurations? For these designate migrations, we will have to
enumerate over every zone to fix their configurations.

** Affects: charm-designate
     Importance: Undecided
     Assignee: Jorge Niedbalski (niedbalski)
         Status: Invalid

** Affects: charm-designate-bind
     Importance: Undecided
     Assignee: Jorge Niedbalski (niedbalski)
         Status: Invalid

** Affects: cloud-archive
     Importance: Undecided
         Status: Fix Released

** Affects: cloud-archive/stein
     Importance: Undecided
         Status: New

** Affects: cloud-archive/train
     Importance: Undecided
         Status: New

** Affects: cloud-archive/ussuri
     Importance: Undecided
         Status: New

** Affects: cloud-archive/victoria
     Importance: Undecided
         Status: New

** Affects: cloud-archive/wallaby
     Importance: Undecided
         Status: Fix Released

** Affects: cloud-archive/xena
     Importance: Undecided
         Status: Fix Released

** Affects: designate (Ubuntu)
     Importance: Undecided
     Assignee: Jorge Niedbalski (niedbalski)
         Status: Fix Committed

** Affects: designate (Ubuntu Focal)
     Importance: Undecided
         Status: New


** Tags: patch scaleback
-- 
designate-manage pool update doesn't reflects targets master dns servers into zones.
https://bugs.launchpad.net/bugs/1879798
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1879798 at bugs.launchpad.net  Tue Aug 31 20:24:04 2021
From: 1879798 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Tue, 31 Aug 2021 20:24:04 -0000
Subject: [Bug 1879798] Re: designate-manage pool update doesn't reflects
 targets master dns servers into zones.
References: <159001172853.19893.11183609660862809256.malonedeb@soybean.canonical.com>
Message-ID: <163044144453.28413.17923636020746073937.malone@chaenomeles.canonical.com>

The attachment "designate-bionic-stein.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/1879798

Title:
  designate-manage pool update doesn't reflects targets master dns
  servers into zones.

Status in OpenStack Designate Charm:
  Invalid
Status in OpenStack Designate-Bind Charm:
  Invalid
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  New
Status in Ubuntu Cloud Archive train series:
  New
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in Ubuntu Cloud Archive victoria series:
  New
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
Status in Ubuntu Cloud Archive xena series:
  Fix Released
Status in designate package in Ubuntu:
  Fix Committed
Status in designate source package in Focal:
  New

Bug description:
  [Environment]

  Ubuntu + Ussuri

  [Description]

  If running designate-manage pool update with new targets, those targets
  gets properly updated in the pool target masters list, but those aren't
  reflected into the zones that belongs to this pool, therefore, the masters
  associated to that zones aren't updated causing failures as the expressed
  in the Further Information section.

  designate-manager pool update should offer an option to update the zones
  associated to the pools with the new target masters and be able to apply
  these changes into existing zones.

  For the case of the bind9 backend the current workaround is to manually
  run the rndc modzone command with the new masters, but that's not suitable
  for large installations with multiple zones and pools.

  
  [Further information]

  We have a designate/designate-bind setup. We migrated designate units
  to different machines, replacing 3 designate units with 3 new units.
  However, this caused issues with existing zones, including creating
  new recordsets for these zones. The zone would result in having an
  ERROR status and a CREATE action.

  Looking at the designate bind units, we see that designate is
  attempting to run:

  'addzone $zone { type slave; masters {$new_designate_ips port 5354;};
  file "slave.$zone.$hash"; };'

  This addzone fails due to the zone already existing. However, we found
  that the zone configuration (using 'rndc showzone $zone' from
  designate-bind unit) still had the old designate ips for its masters.
  There are also logs in /var/log/syslog like the following:

  May 20 06:27:10 juju-c27f05-15-lxd-1 named[72648]: transfer of '$zone'
  from $old_designate_ip#5354: failed to connect: host unreachable

  We were able to resolve this issue by modifying the zone config on all
  designate-bind units:

  juju run -a designate-bind -- rndc modzone $zone '{ type slave; file
  "slave.$zone.$hash"; masters { $new_designate_ip_1 port 5354;
  $new_designate_ip_2 port 5354; $new_designate_ip_3 port 5354; }; };'

  After modifying the zone, the recordset creations completed and
  resolved almost immediately.

  Would this be something the charm could do in an automated way when
  masters are removed/replaced, or is there a better way of fixing the
  zone configurations? For these designate migrations, we will have to
  enumerate over every zone to fix their configurations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-designate/+bug/1879798/+subscriptions



From 1405452 at bugs.launchpad.net  Tue Aug 31 23:23:23 2021
From: 1405452 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 31 Aug 2021 23:23:23 -0000
Subject: [Bug 1405452] Re: Typo in man page ("introduce a much improvement
 mechanism")
References: <20141224162144.16813.94979.malonedeb@soybean.canonical.com>
Message-ID: <163045220413.15276.3734936757946753713.launchpad@gac.canonical.com>

** Changed in: wpa (Ubuntu)
       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/1405452

Title:
  Typo in man page ("introduce a much improvement mechanism")

Status in One Hundred Papercuts:
  Fix Released
Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa package in Debian:
  New

Bug description:
  "introduce a much improvement mechanism" should be "introduce a much
  improved mechanism".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: wpasupplicant 2.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 24 16:19:30 2014
  InstallationDate: Installed on 2014-12-19 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 1879798 at bugs.launchpad.net  Tue Aug 31 23:34:38 2021
From: 1879798 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 31 Aug 2021 23:34:38 -0000
Subject: [Bug 1879798] Re: designate-manage pool update doesn't reflects
 targets master dns servers into zones.
References: <159001172853.19893.11183609660862809256.malonedeb@soybean.canonical.com>
Message-ID: <163045288046.1382.6315165197317821664.launchpad@soybean.canonical.com>

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

** Changed in: designate (Ubuntu Focal)
   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/1879798

Title:
  designate-manage pool update doesn't reflects targets master dns
  servers into zones.

Status in OpenStack Designate Charm:
  Invalid
Status in OpenStack Designate-Bind Charm:
  Invalid
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  New
Status in Ubuntu Cloud Archive train series:
  New
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in Ubuntu Cloud Archive victoria series:
  New
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
Status in Ubuntu Cloud Archive xena series:
  Fix Released
Status in designate package in Ubuntu:
  Fix Committed
Status in designate source package in Focal:
  New

Bug description:
  [Environment]

  Ubuntu + Ussuri

  [Description]

  If running designate-manage pool update with new targets, those targets
  gets properly updated in the pool target masters list, but those aren't
  reflected into the zones that belongs to this pool, therefore, the masters
  associated to that zones aren't updated causing failures as the expressed
  in the Further Information section.

  designate-manager pool update should offer an option to update the zones
  associated to the pools with the new target masters and be able to apply
  these changes into existing zones.

  For the case of the bind9 backend the current workaround is to manually
  run the rndc modzone command with the new masters, but that's not suitable
  for large installations with multiple zones and pools.

  
  [Further information]

  We have a designate/designate-bind setup. We migrated designate units
  to different machines, replacing 3 designate units with 3 new units.
  However, this caused issues with existing zones, including creating
  new recordsets for these zones. The zone would result in having an
  ERROR status and a CREATE action.

  Looking at the designate bind units, we see that designate is
  attempting to run:

  'addzone $zone { type slave; masters {$new_designate_ips port 5354;};
  file "slave.$zone.$hash"; };'

  This addzone fails due to the zone already existing. However, we found
  that the zone configuration (using 'rndc showzone $zone' from
  designate-bind unit) still had the old designate ips for its masters.
  There are also logs in /var/log/syslog like the following:

  May 20 06:27:10 juju-c27f05-15-lxd-1 named[72648]: transfer of '$zone'
  from $old_designate_ip#5354: failed to connect: host unreachable

  We were able to resolve this issue by modifying the zone config on all
  designate-bind units:

  juju run -a designate-bind -- rndc modzone $zone '{ type slave; file
  "slave.$zone.$hash"; masters { $new_designate_ip_1 port 5354;
  $new_designate_ip_2 port 5354; $new_designate_ip_3 port 5354; }; };'

  After modifying the zone, the recordset creations completed and
  resolved almost immediately.

  Would this be something the charm could do in an automated way when
  masters are removed/replaced, or is there a better way of fixing the
  zone configurations? For these designate migrations, we will have to
  enumerate over every zone to fix their configurations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-designate/+bug/1879798/+subscriptions



