From 2071891 at bugs.launchpad.net  Wed Oct  1 06:33:49 2025
From: 2071891 at bugs.launchpad.net (Julian Andres Klode)
Date: Wed, 01 Oct 2025 06:33:49 -0000
Subject: [Bug 2071891] Re: tcpdump segv if -Z and -w is specified
References: <172007579161.877829.11924843823081269254.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175930042934.1963047.4728591243581095816.malone@juju-98d295-prod-launchpad-3>

Hello Lars, or anyone else affected,

Accepted tcpdump into plucky-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tcpdump/4.99.4-3ubuntu4.25.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-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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: tcpdump (Ubuntu Plucky)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-plucky

** Changed in: tcpdump (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-noble

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

Title:
  tcpdump segv if -Z and -w is specified

Status in tcpdump package in Ubuntu:
  Fix Released
Status in tcpdump source package in Noble:
  Fix Committed
Status in tcpdump source package in Oracular:
  Won't Fix
Status in tcpdump source package in Plucky:
  Fix Committed
Status in tcpdump source package in Questing:
  Fix Released
Status in tcpdump package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  There is currently a bug in tcpdump causing it to segfault on Noble
  machines and newer.

  This is because of a bad interaction with d/p/drop-privs-only-if-non-root.diff
  where using -Z root sets username to NULL, causing a null pointer dereference and subsequent segmentation fault.

  [ Test Plan ]

  Make sure you are on a noble machine or newer and that tcpdump is
  installed.

  $ sudo apt install tcpdump

  To reproduce the issue simply run the following command:

  $ sudo tcpdump -Z root -ni lo -w /tmp/lo.pcap

  Note that running it with sudo or being in a root shell is a requirement to trigger the crash.
  You will see the following when reproducing the crash:
  ```
  ghadi at XPS-17-9720 ~ » sudo tcpdump -Z root -ni lo -w /tmp/lo.pcap
  [1]    1250151 segmentation fault  sudo tcpdump -Z root -ni lo -w /tmp/lo.pcap
  ```

  [ Where problems could occur ]

  Since the patch makes sure that the username is valid before changing
  ownership, a possible regression might be that tcpdump fails to run
  due to permission issues, or that it still segfaults due to other
  checks that might be required.

  [ Other info ]

  The bug has been fixed in debian upstream here:
  https://salsa.debian.org/debian/tcpdump/-/blob/master/debian/patches/drop-
  privs-after-opening-savefile.diff

  There is also a discussion about it on the debian bug tracker:
  https://bugs.debian.org/935112

  This was fixed in:

  commit b4b1230f07df973f8c8c339ec022f2357bc1179e 
  From: Romain Francoise <rfrancoise at debian.org>
  Date: Fri, 23 Aug 2024 18:39:26 +0200
  Subject: Avoid getpwnam(NULL) when called with `-Z root' (#1078771)
  Link: https://salsa.debian.org/debian/tcpdump/-/commit/b4b1230f07df973f8c8c339ec022f2357bc1179e

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



From 2071891 at bugs.launchpad.net  Wed Oct  1 06:34:41 2025
From: 2071891 at bugs.launchpad.net (Julian Andres Klode)
Date: Wed, 01 Oct 2025 06:34:41 -0000
Subject: [Bug 2071891] Please test proposed package
References: <172007579161.877829.11924843823081269254.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175930048198.3374363.3629942537630902324.malone@juju-98d295-prod-launchpad-7>

Hello Lars, or anyone else affected,

Accepted tcpdump into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tcpdump/4.99.4-3ubuntu4.24.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2071891

Title:
  tcpdump segv if -Z and -w is specified

Status in tcpdump package in Ubuntu:
  Fix Released
Status in tcpdump source package in Noble:
  Fix Committed
Status in tcpdump source package in Oracular:
  Won't Fix
Status in tcpdump source package in Plucky:
  Fix Committed
Status in tcpdump source package in Questing:
  Fix Released
Status in tcpdump package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  There is currently a bug in tcpdump causing it to segfault on Noble
  machines and newer.

  This is because of a bad interaction with d/p/drop-privs-only-if-non-root.diff
  where using -Z root sets username to NULL, causing a null pointer dereference and subsequent segmentation fault.

  [ Test Plan ]

  Make sure you are on a noble machine or newer and that tcpdump is
  installed.

  $ sudo apt install tcpdump

  To reproduce the issue simply run the following command:

  $ sudo tcpdump -Z root -ni lo -w /tmp/lo.pcap

  Note that running it with sudo or being in a root shell is a requirement to trigger the crash.
  You will see the following when reproducing the crash:
  ```
  ghadi at XPS-17-9720 ~ » sudo tcpdump -Z root -ni lo -w /tmp/lo.pcap
  [1]    1250151 segmentation fault  sudo tcpdump -Z root -ni lo -w /tmp/lo.pcap
  ```

  [ Where problems could occur ]

  Since the patch makes sure that the username is valid before changing
  ownership, a possible regression might be that tcpdump fails to run
  due to permission issues, or that it still segfaults due to other
  checks that might be required.

  [ Other info ]

  The bug has been fixed in debian upstream here:
  https://salsa.debian.org/debian/tcpdump/-/blob/master/debian/patches/drop-
  privs-after-opening-savefile.diff

  There is also a discussion about it on the debian bug tracker:
  https://bugs.debian.org/935112

  This was fixed in:

  commit b4b1230f07df973f8c8c339ec022f2357bc1179e 
  From: Romain Francoise <rfrancoise at debian.org>
  Date: Fri, 23 Aug 2024 18:39:26 +0200
  Subject: Avoid getpwnam(NULL) when called with `-Z root' (#1078771)
  Link: https://salsa.debian.org/debian/tcpdump/-/commit/b4b1230f07df973f8c8c339ec022f2357bc1179e

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



From 2122640 at bugs.launchpad.net  Wed Oct  1 15:10:31 2025
From: 2122640 at bugs.launchpad.net (Ken VanDine)
Date: Wed, 01 Oct 2025 15:10:31 -0000
Subject: [Bug 2122640] Re: When switching between the audio profiles of a
 bluetooth device, a sound glitch can be heard on another device
References: <175766059776.3883154.4764375481303445809.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175933143122.2822593.10489583107209099254.malone@juju-98d295-prod-launchpad-3>

I've sponsored this.

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

Title:
  When switching between the audio profiles of a bluetooth device, a
  sound glitch can be heard on another device

Status in wireplumber package in Ubuntu:
  Invalid
Status in wireplumber source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [ Impact ]

   * When switching between different bluetooth profiles of the same
  device (ex: headphones / handsfree), the sound sometimes goes out from
  the default sound output (USB, HDMI...) for half a second, roughly.

   * After Wireplumber 0.5.6 and this fix:
  https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/655,
  the problem goes away. Plucky and Questing are fine.

   * Noble uses Wireplumber 0.4.17 and suffers from this bug.

  [ Fix ]

   * Upstream wireplumber 0.5.x got a huge refacto compared to what's in
  Noble. The fix I mentioned above does not apply, at all, given the
  architecture changed significantly.

  * I rewrote a patch, taking ideas from the original patch.

  * The idea is to detect these transition of bluetooth devices and,
  when they happen, prevent non-bluetooth devices to be linked with apps
  for a few (2) seconds.

  [ Test Plan ]

   1. Connect at least 3 devices to the system: 2 bluetooth devices
  (with several profiles each) one wired device

  2. Play at least 2 audio streams from different apps. Ex: using
  Youtube from both chromium and firefox.

  3. Switch between devices, switch between profiles. For each switch,
  the audio must transition to the right device without hearing a glitch
  anymore. With all devices and profiles, the transition must be quick.
  One should be able to click somewhere else on the Youtube video
  without causing a lag (it will trigger a transition).

  [ Where problems could occur ]

  Given the nature of the fix, 2 problems could occur

  1. Some unexpected transitions could now take 2 second instead of
  being instant. I tried to cover all the edge case in my patch, and in
  the test cases, to address that.

  2. Some transitions could not happen at all, causing the sound to be
  buffering. Again, the test plan covers that.

  If I forgot about some edge cases in the test plan, I will be happy to
  add some.

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



From 2122640 at bugs.launchpad.net  Wed Oct  1 15:19:12 2025
From: 2122640 at bugs.launchpad.net (Ken VanDine)
Date: Wed, 01 Oct 2025 15:19:12 -0000
Subject: [Bug 2122640] Re: When switching between the audio profiles of a
 bluetooth device, a sound glitch can be heard on another device
References: <175766059776.3883154.4764375481303445809.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175933195389.1820313.12235240131149317521.launchpad@juju-98d295-prod-launchpad-4>

** Changed in: wireplumber (Ubuntu)
       Status: New => Invalid

** Changed in: wireplumber (Ubuntu Noble)
       Status: New => In Progress

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

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

Title:
  When switching between the audio profiles of a bluetooth device, a
  sound glitch can be heard on another device

Status in wireplumber package in Ubuntu:
  Invalid
Status in wireplumber source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [ Impact ]

   * When switching between different bluetooth profiles of the same
  device (ex: headphones / handsfree), the sound sometimes goes out from
  the default sound output (USB, HDMI...) for half a second, roughly.

   * After Wireplumber 0.5.6 and this fix:
  https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/655,
  the problem goes away. Plucky and Questing are fine.

   * Noble uses Wireplumber 0.4.17 and suffers from this bug.

  [ Fix ]

   * Upstream wireplumber 0.5.x got a huge refacto compared to what's in
  Noble. The fix I mentioned above does not apply, at all, given the
  architecture changed significantly.

  * I rewrote a patch, taking ideas from the original patch.

  * The idea is to detect these transition of bluetooth devices and,
  when they happen, prevent non-bluetooth devices to be linked with apps
  for a few (2) seconds.

  [ Test Plan ]

   1. Connect at least 3 devices to the system: 2 bluetooth devices
  (with several profiles each) one wired device

  2. Play at least 2 audio streams from different apps. Ex: using
  Youtube from both chromium and firefox.

  3. Switch between devices, switch between profiles. For each switch,
  the audio must transition to the right device without hearing a glitch
  anymore. With all devices and profiles, the transition must be quick.
  One should be able to click somewhere else on the Youtube video
  without causing a lag (it will trigger a transition).

  [ Where problems could occur ]

  Given the nature of the fix, 2 problems could occur

  1. Some unexpected transitions could now take 2 second instead of
  being instant. I tried to cover all the edge case in my patch, and in
  the test cases, to address that.

  2. Some transitions could not happen at all, causing the sound to be
  buffering. Again, the test plan covers that.

  If I forgot about some edge cases in the test plan, I will be happy to
  add some.

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



From 2122640 at bugs.launchpad.net  Wed Oct  1 16:03:59 2025
From: 2122640 at bugs.launchpad.net (Julian Andres Klode)
Date: Wed, 01 Oct 2025 16:03:59 -0000
Subject: [Bug 2122640] Re: When switching between the audio profiles of a
 bluetooth device, a sound glitch can be heard on another device
References: <175766059776.3883154.4764375481303445809.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175933463942.1886221.11194581347463800411.malone@juju-98d295-prod-launchpad-4>

I'm not happy this is not a clean backport because we don't have any
experience with it so we should have a wider call for testing perhaps on
Discourse or something.

But ultimately I understand that if say you are say watching a video and
switch profiles and sound comes out your laptop speaker for half a
second that's not a good thing when you're in a train or office or
something.

The test plan looks good to me, I'm happy it has two BT devices. Ensure
that you do a whole bunch of fast switches too, and slow switches. i.e.
if I take my keyboard and switch in 100ms intervals between profiles
this should not cause a hang or other bad behavior.

** Changed in: wireplumber (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  When switching between the audio profiles of a bluetooth device, a
  sound glitch can be heard on another device

Status in wireplumber package in Ubuntu:
  Invalid
Status in wireplumber source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [ Impact ]

   * When switching between different bluetooth profiles of the same
  device (ex: headphones / handsfree), the sound sometimes goes out from
  the default sound output (USB, HDMI...) for half a second, roughly.

   * After Wireplumber 0.5.6 and this fix:
  https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/655,
  the problem goes away. Plucky and Questing are fine.

   * Noble uses Wireplumber 0.4.17 and suffers from this bug.

  [ Fix ]

   * Upstream wireplumber 0.5.x got a huge refacto compared to what's in
  Noble. The fix I mentioned above does not apply, at all, given the
  architecture changed significantly.

  * I rewrote a patch, taking ideas from the original patch.

  * The idea is to detect these transition of bluetooth devices and,
  when they happen, prevent non-bluetooth devices to be linked with apps
  for a few (2) seconds.

  [ Test Plan ]

   1. Connect at least 3 devices to the system: 2 bluetooth devices
  (with several profiles each) one wired device

  2. Play at least 2 audio streams from different apps. Ex: using
  Youtube from both chromium and firefox.

  3. Switch between devices, switch between profiles. For each switch,
  the audio must transition to the right device without hearing a glitch
  anymore. With all devices and profiles, the transition must be quick.
  One should be able to click somewhere else on the Youtube video
  without causing a lag (it will trigger a transition).

  [ Where problems could occur ]

  Given the nature of the fix, 2 problems could occur

  1. Some unexpected transitions could now take 2 second instead of
  being instant. I tried to cover all the edge case in my patch, and in
  the test cases, to address that.

  2. Some transitions could not happen at all, causing the sound to be
  buffering. Again, the test plan covers that.

  If I forgot about some edge cases in the test plan, I will be happy to
  add some.

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



From 2122640 at bugs.launchpad.net  Wed Oct  1 16:04:16 2025
From: 2122640 at bugs.launchpad.net (Julian Andres Klode)
Date: Wed, 01 Oct 2025 16:04:16 -0000
Subject: [Bug 2122640] Please test proposed package
References: <175766059776.3883154.4764375481303445809.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175933465634.3856436.4885297063692932839.malone@juju-98d295-prod-launchpad-2>

Hello Antoine, or anyone else affected,

Accepted wireplumber into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/wireplumber/0.4.17-1ubuntu4.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2122640

Title:
  When switching between the audio profiles of a bluetooth device, a
  sound glitch can be heard on another device

Status in wireplumber package in Ubuntu:
  Invalid
Status in wireplumber source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [ Impact ]

   * When switching between different bluetooth profiles of the same
  device (ex: headphones / handsfree), the sound sometimes goes out from
  the default sound output (USB, HDMI...) for half a second, roughly.

   * After Wireplumber 0.5.6 and this fix:
  https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/655,
  the problem goes away. Plucky and Questing are fine.

   * Noble uses Wireplumber 0.4.17 and suffers from this bug.

  [ Fix ]

   * Upstream wireplumber 0.5.x got a huge refacto compared to what's in
  Noble. The fix I mentioned above does not apply, at all, given the
  architecture changed significantly.

  * I rewrote a patch, taking ideas from the original patch.

  * The idea is to detect these transition of bluetooth devices and,
  when they happen, prevent non-bluetooth devices to be linked with apps
  for a few (2) seconds.

  [ Test Plan ]

   1. Connect at least 3 devices to the system: 2 bluetooth devices
  (with several profiles each) one wired device

  2. Play at least 2 audio streams from different apps. Ex: using
  Youtube from both chromium and firefox.

  3. Switch between devices, switch between profiles. For each switch,
  the audio must transition to the right device without hearing a glitch
  anymore. With all devices and profiles, the transition must be quick.
  One should be able to click somewhere else on the Youtube video
  without causing a lag (it will trigger a transition).

  [ Where problems could occur ]

  Given the nature of the fix, 2 problems could occur

  1. Some unexpected transitions could now take 2 second instead of
  being instant. I tried to cover all the edge case in my patch, and in
  the test cases, to address that.

  2. Some transitions could not happen at all, causing the sound to be
  buffering. Again, the test plan covers that.

  If I forgot about some edge cases in the test plan, I will be happy to
  add some.

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



From 2125628 at bugs.launchpad.net  Wed Oct  1 16:40:21 2025
From: 2125628 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 01 Oct 2025 16:40:21 -0000
Subject: [Bug 2125628] Re: u-boot amd64 fails to build on questing due to
 missing gcc-14-mipsel-linux-gnu
References: <175874832515.1882896.13600548544551884635.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175933682502.3990279.4093267265247856508.malone@scripts.lp.internal>

This bug was fixed in the package u-boot - 2025.01-3ubuntu4

---------------
u-boot (2025.01-3ubuntu4) questing; urgency=medium

  [ Ravi Kant Sharma ]
  * d/targets.mk: Remove MIPS builds to fix FTBFS in questing (LP: #2125628)

u-boot (2025.01-3ubuntu3) questing; urgency=medium

  * d/p/ubuntu-hardening-limit-keynames-to-keydir.patch: Fix NULL dereference
    in lib/rsa/rsa-sign.c when calling mkimage with -G (LP: #2046462)

 -- Dave Jones <dave.jones at canonical.com>  Tue, 30 Sep 2025 11:18:03
+0100

** Changed in: u-boot (Ubuntu)
       Status: Triaged => Fix Released

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

Title:
  u-boot amd64 fails to build on questing due to missing gcc-14-mipsel-
  linux-gnu

Status in u-boot package in Ubuntu:
  Fix Released

Bug description:
  u-boot is currently ftbfs [1] on questing due to gcc-14-mipsel-linux-
  gnu not being available (from gcc-14-cross-mipsen, which itself is
  waiting on other packages)

  [1]: https://launchpadlibrarian.net/818383253/buildlog_ubuntu-
  questing-amd64.u-boot_2025.01-3ubuntu2_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2125628/+subscriptions



From 2121948 at bugs.launchpad.net  Wed Oct  1 16:38:06 2025
From: 2121948 at bugs.launchpad.net (You-Sheng Yang)
Date: Wed, 01 Oct 2025 16:38:06 -0000
Subject: [Bug 2121948] Re: [SRU] Support suspend/resume for IMX471 camera
 sensor
References: <175690774470.3522322.3912132826639117162.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175933668640.3910958.13836137474736162982.malone@juju-98d295-prod-launchpad-2>

Verified linux-oem-6.14/6.14.0-1013.13 from ppa:canonical-kernel-
team/proposed2:

$ sudo media-ctl -p
......
- entity 233: imx471 0-0010 (1 pad, 1 link, 0 routes)
              type V4L2 subdev subtype Sensor flags 0
              device node name /dev/v4l-subdev4
        pad0: Source
                [stream:0 fmt:SRGGB10_1X10/1928x1088 field:none]
                -> "Intel IPU7 CSI2 0":0 [ENABLED,IMMUTABLE]


** Tags removed: verification-needed verification-needed-noble-linux-oem-6.14
** Tags added: verification-done verification-done-noble-linux-oem-6.14

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

Title:
  [SRU] Support suspend/resume for IMX471 camera sensor

Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in linux-oem-6.14 package in Ubuntu:
  Invalid
Status in linux-oem-6.17 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Noble:
  Invalid
Status in linux-oem-6.14 source package in Noble:
  Fix Committed
Status in linux-oem-6.17 source package in Noble:
  In Progress
Status in ipu6-drivers source package in Plucky:
  Fix Committed
Status in linux-oem-6.14 source package in Plucky:
  Invalid
Status in linux-oem-6.17 source package in Plucky:
  Invalid
Status in ipu6-drivers source package in Questing:
  Fix Released
Status in linux-oem-6.14 source package in Questing:
  Invalid
Status in linux-oem-6.17 source package in Questing:
  Invalid

Bug description:
  [SRU Justification]

  [ Impact ]

  Sony imx471 is not explicitly powered on before trying to identify the module, leaving following error messages in kernel dmesg buffer:
  ```
  kernel: imx471 i2c-SONY471A:00: failed to find sensor: -5
  kernel: imx471 i2c-SONY471A:00: probe with driver imx471 failed with error -5
  ```

  Proposed fix in
  https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.

  [ Test Plan ]

  1. Install the dkms from -proposed pocket. The corresponding binary kernel module should be built automatically; if not, run:
  ```
  $ sudo dkms install --force ipu6-drivers/0~git202506270118.9bff7368 -k $(uname -r)
  ```

  2. Reboot to the same kernel to reload the drivers.

  3. Make sure the device is probed and up running:
  ```
  $ media-ctl -p
  Media controller API version 6.14.8

  Media device information
  ------------------------
  driver          intel-ipu7
  model           ipu7
  serial          
  bus info        PCI:intel-ipu7
  hw revision     0x17aa233b
  driver version  6.14.8
  ...
  ```

  4. Use https://webcamtests.com to verify the camera is really capable
  of streaming.

  [ Where problems could occur ]

  This fills the probe procedure as other similar camera sensors do. No
  known problem so far.

  [ Other Info ]

  This is a follow-up for bug 2107320 that supports IMX471 in linux-
  oem-6.11 and on. Nominate for Plucky, Questing for ipu6-drivers, which
  will be compiled within linux-oem-6.11 and on.

  ========== original bug report ==========

  This is a follow-up for bug 2107320, support Sony IMX471 camera sensor
  for Intel IPU7 platforms.

  Proposed fix in https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.
  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu     1575 F.... pipewire
                        ubuntu     1579 F.... wireplumber
   /dev/snd/seq:        ubuntu     1575 F.... pipewire
  CRDA: N/A
  CasperMD5CheckMismatches: ./casper/initrd ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for Ubuntu 24.04 for Lenovo
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-noble-oem-24.04c-20250822-50
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2025-08-29 (12 days ago)
  InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20250821)
  IwConfig:
   lo        no wireless extensions.

   wlp0s20f3  no wireless extensions.

   enx607d099eaa26  no wireless extensions.
  MachineType: LENOVO 21Q7ZCM3US
  Package: ipu6-drivers
  ProcFB: 0 xedrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-9011-oem root=UUID=0f9adf29-e579-4dc5-82a4-a98b51147867 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.14.0-9011.11+exp.19-oem 6.14.8
  RelatedPackageVersions:
   linux-restricted-modules-6.14.0-9011-oem N/A
   linux-backports-modules-6.14.0-9011-oem  N/A
   linux-firmware                           20240318.git3b128b60-0ubuntu2.17
  Tags: noble
  Uname: Linux 6.14.0-9011-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/03/2025
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N4CET39W.T02.HotKey (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21Q7ZCM3US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76576 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: dmi:bvnLENOVO:bvrN4CET39W.T02.HotKey(1.15):bd09/03/2025:br1.15:efr1.11:svnLENOVO:pn21Q7ZCM3US:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7ZCM3US:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:
  dmi.product.family: ThinkPad X9-15 Gen 1
  dmi.product.name: 21Q7ZCM3US
  dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1
  dmi.product.version: ThinkPad X9-15 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2121948/+subscriptions



From 2121948 at bugs.launchpad.net  Wed Oct  1 16:39:39 2025
From: 2121948 at bugs.launchpad.net (You-Sheng Yang)
Date: Wed, 01 Oct 2025 16:39:39 -0000
Subject: [Bug 2121948] Re: [SRU] Support suspend/resume for IMX471 camera
 sensor
References: <175690774470.3522322.3912132826639117162.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175933677914.180395.6788881526805010296.malone@juju-98d295-prod-launchpad-7>

Verified ipu6-drivers/0~git202411190607.0ad49882-0ubuntu5~25.04.2 on
Aladdin-SVT-C1-202509-37885

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

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

Title:
  [SRU] Support suspend/resume for IMX471 camera sensor

Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in linux-oem-6.14 package in Ubuntu:
  Invalid
Status in linux-oem-6.17 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Noble:
  Invalid
Status in linux-oem-6.14 source package in Noble:
  Fix Committed
Status in linux-oem-6.17 source package in Noble:
  In Progress
Status in ipu6-drivers source package in Plucky:
  Fix Committed
Status in linux-oem-6.14 source package in Plucky:
  Invalid
Status in linux-oem-6.17 source package in Plucky:
  Invalid
Status in ipu6-drivers source package in Questing:
  Fix Released
Status in linux-oem-6.14 source package in Questing:
  Invalid
Status in linux-oem-6.17 source package in Questing:
  Invalid

Bug description:
  [SRU Justification]

  [ Impact ]

  Sony imx471 is not explicitly powered on before trying to identify the module, leaving following error messages in kernel dmesg buffer:
  ```
  kernel: imx471 i2c-SONY471A:00: failed to find sensor: -5
  kernel: imx471 i2c-SONY471A:00: probe with driver imx471 failed with error -5
  ```

  Proposed fix in
  https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.

  [ Test Plan ]

  1. Install the dkms from -proposed pocket. The corresponding binary kernel module should be built automatically; if not, run:
  ```
  $ sudo dkms install --force ipu6-drivers/0~git202506270118.9bff7368 -k $(uname -r)
  ```

  2. Reboot to the same kernel to reload the drivers.

  3. Make sure the device is probed and up running:
  ```
  $ media-ctl -p
  Media controller API version 6.14.8

  Media device information
  ------------------------
  driver          intel-ipu7
  model           ipu7
  serial          
  bus info        PCI:intel-ipu7
  hw revision     0x17aa233b
  driver version  6.14.8
  ...
  ```

  4. Use https://webcamtests.com to verify the camera is really capable
  of streaming.

  [ Where problems could occur ]

  This fills the probe procedure as other similar camera sensors do. No
  known problem so far.

  [ Other Info ]

  This is a follow-up for bug 2107320 that supports IMX471 in linux-
  oem-6.11 and on. Nominate for Plucky, Questing for ipu6-drivers, which
  will be compiled within linux-oem-6.11 and on.

  ========== original bug report ==========

  This is a follow-up for bug 2107320, support Sony IMX471 camera sensor
  for Intel IPU7 platforms.

  Proposed fix in https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.
  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu     1575 F.... pipewire
                        ubuntu     1579 F.... wireplumber
   /dev/snd/seq:        ubuntu     1575 F.... pipewire
  CRDA: N/A
  CasperMD5CheckMismatches: ./casper/initrd ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for Ubuntu 24.04 for Lenovo
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-noble-oem-24.04c-20250822-50
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2025-08-29 (12 days ago)
  InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20250821)
  IwConfig:
   lo        no wireless extensions.

   wlp0s20f3  no wireless extensions.

   enx607d099eaa26  no wireless extensions.
  MachineType: LENOVO 21Q7ZCM3US
  Package: ipu6-drivers
  ProcFB: 0 xedrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-9011-oem root=UUID=0f9adf29-e579-4dc5-82a4-a98b51147867 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.14.0-9011.11+exp.19-oem 6.14.8
  RelatedPackageVersions:
   linux-restricted-modules-6.14.0-9011-oem N/A
   linux-backports-modules-6.14.0-9011-oem  N/A
   linux-firmware                           20240318.git3b128b60-0ubuntu2.17
  Tags: noble
  Uname: Linux 6.14.0-9011-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/03/2025
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N4CET39W.T02.HotKey (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21Q7ZCM3US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76576 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: dmi:bvnLENOVO:bvrN4CET39W.T02.HotKey(1.15):bd09/03/2025:br1.15:efr1.11:svnLENOVO:pn21Q7ZCM3US:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7ZCM3US:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:
  dmi.product.family: ThinkPad X9-15 Gen 1
  dmi.product.name: 21Q7ZCM3US
  dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1
  dmi.product.version: ThinkPad X9-15 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2121948/+subscriptions



From 2126596 at bugs.launchpad.net  Wed Oct  1 19:37:36 2025
From: 2126596 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 01 Oct 2025 19:37:36 -0000
Subject: [Bug 2126596] [NEW] gvfs 1.57.2-2ubuntu5 autopkgtests failing with
 SyntaxWarning
References: <175934729636.3257950.7089237589155834792.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175934745661.470474.5254570658855816637.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Ravi Kant Sharma (ravi-sharma):

https://autopkgtest.ubuntu.com/results/autopkgtest-
questing/questing/amd64/g/gvfs/20251001_144858_724dc@/log.gz

 97s test_media_player (__main__.Drive.test_media_player)
 99s drive mount: media player ... FAIL
 99s <unknown>:2: SyntaxWarning: invalid escape sequence '\s'
 99s <unknown>:1: SyntaxWarning: invalid escape sequence '\s'
 99s 
 99s ----- dbus stdout -----
 99s 
 99s ----- dbus stderr -----
 99s 
 99s

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

-- 
gvfs 1.57.2-2ubuntu5 autopkgtests failing with SyntaxWarning
https://bugs.launchpad.net/bugs/2126596
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2126596 at bugs.launchpad.net  Wed Oct  1 19:37:18 2025
From: 2126596 at bugs.launchpad.net (Ravi Kant Sharma)
Date: Wed, 01 Oct 2025 19:37:18 -0000
Subject: [Bug 2126596] Re: gvfs 1.57.2-2ubuntu5 autopkgtests failing with
 SyntaxWarning
References: <175934729636.3257950.7089237589155834792.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175934743862.3262724.9727606469716295560.malone@juju-98d295-prod-launchpad-3>

The patch fixes is the failure.

** Patch added: "fix-lp2126596.patch"
   https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2126596/+attachment/5913743/+files/fix-lp2126596.patch

** Tags added: update-excuse

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

Title:
  gvfs 1.57.2-2ubuntu5 autopkgtests failing with SyntaxWarning

Status in gvfs package in Ubuntu:
  New

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  questing/questing/amd64/g/gvfs/20251001_144858_724dc@/log.gz

   97s test_media_player (__main__.Drive.test_media_player)
   99s drive mount: media player ... FAIL
   99s <unknown>:2: SyntaxWarning: invalid escape sequence '\s'
   99s <unknown>:1: SyntaxWarning: invalid escape sequence '\s'
   99s 
   99s ----- dbus stdout -----
   99s 
   99s ----- dbus stderr -----
   99s 
   99s

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



From 2124947 at bugs.launchpad.net  Wed Oct  1 22:48:54 2025
From: 2124947 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 01 Oct 2025 22:48:54 -0000
Subject: [Bug 2124947] [NEW] editorconfig-core ftbfs on arm in questing
 archive rebuild
References: <175812194061.1948777.8694742432377201955.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175935893514.314205.4178209867191146072.launchpad@juju-98d295-prod-launchpad-2>

You have been subscribed to a public bug by Simon Poirier (simpoir):

The package fails to build in the recent archive rebuild
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250910-questing-questing.html

> error: Could not create output directory /<<PKGBUILDDIR>>/obj-
aarch64-linux-gnu/doc/man

** Affects: editorconfig-core (Ubuntu)
     Importance: Undecided
     Assignee: Simon Poirier (simpoir)
         Status: In Progress


** Tags: dcr-incoming ftbfs
-- 
editorconfig-core ftbfs on arm in questing archive rebuild
https://bugs.launchpad.net/bugs/2124947
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2104094 at bugs.launchpad.net  Thu Oct  2 00:37:01 2025
From: 2104094 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 02 Oct 2025 00:37:01 -0000
Subject: [Bug 2104094] [NEW] [SRU] NV-CONTROL version is listed as Unknown
 using 570-open driver
References: <174287368699.681557.15942246773009453043.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175936542170.2714620.4069185454555884576.launchpad@juju-98d295-prod-launchpad-4>

You have been subscribed to a public bug by Yao Wei (medicalwei):

[ Impact ]

 * NV-CONTROL version shows "Unknown" in nvidia-settings GUI

 * This update fixes NV-CONTROL version display when using NVIDIA
570-open driver

[ Test Plan ]

 * Install nvidia-driver-570-open, then reboot

 * Check nvidia-settings, NV-CONTROL version should show "Unknown"

 * Update nvidia-settings package to -proposed, it should show the
correct version (1.29)

[ Where problems could occur ]

 * If nvidia-settings breaks completely, some NVIDIA-specific features
might not be able to configure.

=== Original report ===

[Summary]

NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

[Steps to reproduce]

Boot to OS.

Install 570-open NVIDIA driver.

Launch the NVIDIA X Server Settings in Show Apps.

[Expected result]

NV-CONTROL version should display normally (1.29) in NVIDIA X Server
Settings.

[Actual Result]

NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

Note that this issue does not apply to NVIDIA drivers for 560 and below.

** Affects: oem-priority
     Importance: Undecided
         Status: New

** Affects: nvidia-settings (Ubuntu)
     Importance: Undecided
     Assignee: Yao Wei (medicalwei)
         Status: In Progress


** Tags: jira-cpl-152 oem-priority
-- 
[SRU] NV-CONTROL version is listed as Unknown using 570-open driver
https://bugs.launchpad.net/bugs/2104094
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2104094 at bugs.launchpad.net  Thu Oct  2 00:36:35 2025
From: 2104094 at bugs.launchpad.net (Yao Wei)
Date: Thu, 02 Oct 2025 00:36:35 -0000
Subject: [Bug 2104094] Re: [SRU] NV-CONTROL version is listed as Unknown using
 570-open driver
References: <174287368699.681557.15942246773009453043.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175936539598.943371.9779454432386240548.malone@juju-98d295-prod-launchpad-7>

** Patch added: "debdiff for questing"
   https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5913831/+files/nvidia-settings_510.47.03-0ubuntu5.debdiff

** Changed in: nvidia-settings (Ubuntu)
       Status: Incomplete => In Progress

** Description changed:

  [ Impact ]
  
-  * NV-CONTROL version shows "Unknown" in nvidia-settings GUI
+  * NV-CONTROL version shows "Unknown" in nvidia-settings GUI
  
-  * This update fixes NV-CONTROL version display when using NVIDIA
+  * This update fixes NV-CONTROL version display when using NVIDIA
  570-open driver
  
  [ Test Plan ]
  
-  * Install nvidia-driver-570-open, then reboot
+  * On machines with PRIME config (e.g. laptops with Intel GPU and NVIDIA
+ GPU, where Intel GPU is used for display)
  
-  * Check nvidia-settings, NV-CONTROL version should show "Unknown"
+  * Check nvidia-settings, NV-CONTROL version should show "Unknown"
  
-  * Update nvidia-settings package to -proposed, it should show the
+  * Update nvidia-settings package to -proposed, it should show the
  correct version (1.29)
  
  [ Where problems could occur ]
  
-  * If nvidia-settings breaks completely, some NVIDIA-specific features
+  * If nvidia-settings breaks completely, some NVIDIA-specific features
  might not be able to configure.
  
  === Original report ===
  
  [Summary]
  
  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.
  
  [Steps to reproduce]
  
  Boot to OS.
  
  Install 570-open NVIDIA driver.
  
  Launch the NVIDIA X Server Settings in Show Apps.
  
  [Expected result]
  
  NV-CONTROL version should display normally (1.29) in NVIDIA X Server
  Settings.
  
  [Actual Result]
  
  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.
  
  Note that this issue does not apply to NVIDIA drivers for 560 and below.

** Description changed:

  [ Impact ]
  
   * NV-CONTROL version shows "Unknown" in nvidia-settings GUI
  
   * This update fixes NV-CONTROL version display when using NVIDIA
  570-open driver
  
  [ Test Plan ]
  
-  * On machines with PRIME config (e.g. laptops with Intel GPU and NVIDIA
- GPU, where Intel GPU is used for display)
+  * Find machines with PRIME config (e.g. laptops with Intel GPU and
+ NVIDIA GPU, where Intel GPU is used for display)
  
   * Check nvidia-settings, NV-CONTROL version should show "Unknown"
  
   * Update nvidia-settings package to -proposed, it should show the
  correct version (1.29)
  
  [ Where problems could occur ]
  
   * If nvidia-settings breaks completely, some NVIDIA-specific features
  might not be able to configure.
  
  === Original report ===
  
  [Summary]
  
  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.
  
  [Steps to reproduce]
  
  Boot to OS.
  
  Install 570-open NVIDIA driver.
  
  Launch the NVIDIA X Server Settings in Show Apps.
  
  [Expected result]
  
  NV-CONTROL version should display normally (1.29) in NVIDIA X Server
  Settings.
  
  [Actual Result]
  
  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.
  
  Note that this issue does not apply to NVIDIA drivers for 560 and below.

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

Title:
  [SRU] NV-CONTROL version is listed as Unknown using 570-open driver

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * NV-CONTROL version shows "Unknown" in nvidia-settings GUI

   * This update fixes NV-CONTROL version display when using NVIDIA
  570-open driver

  [ Test Plan ]

   * Find machines with PRIME config (e.g. laptops with Intel GPU and
  NVIDIA GPU, where Intel GPU is used for display)

   * Check nvidia-settings, NV-CONTROL version should show "Unknown"

   * Update nvidia-settings package to -proposed, it should show the
  correct version (1.29)

  [ Where problems could occur ]

   * If nvidia-settings breaks completely, some NVIDIA-specific features
  might not be able to configure.

  === Original report ===

  [Summary]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  [Steps to reproduce]

  Boot to OS.

  Install 570-open NVIDIA driver.

  Launch the NVIDIA X Server Settings in Show Apps.

  [Expected result]

  NV-CONTROL version should display normally (1.29) in NVIDIA X Server
  Settings.

  [Actual Result]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  Note that this issue does not apply to NVIDIA drivers for 560 and
  below.

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



From 2104094 at bugs.launchpad.net  Thu Oct  2 00:39:42 2025
From: 2104094 at bugs.launchpad.net (Yao Wei)
Date: Thu, 02 Oct 2025 00:39:42 -0000
Subject: [Bug 2104094] Re: [SRU] NV-CONTROL version is listed as Unknown using
 570-open driver
References: <174287368699.681557.15942246773009453043.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175936558254.941595.1451084065700745304.malone@juju-98d295-prod-launchpad-7>

The above debdiff is a patch excerpted from nvidia-settings 580.65.06,
which I've validated on noble that it has fixed the issue.

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

Title:
  [SRU] NV-CONTROL version is listed as Unknown using 570-open driver

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * NV-CONTROL version shows "Unknown" in nvidia-settings GUI

   * This update fixes NV-CONTROL version display when using NVIDIA
  570-open driver

  [ Test Plan ]

   * Find machines with PRIME config (e.g. laptops with Intel GPU and
  NVIDIA GPU, where Intel GPU is used for display)

   * Check nvidia-settings, NV-CONTROL version should show "Unknown"

   * Update nvidia-settings package to -proposed, it should show the
  correct version (1.29)

  [ Where problems could occur ]

   * If nvidia-settings breaks completely, some NVIDIA-specific features
  might not be able to configure.

  === Original report ===

  [Summary]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  [Steps to reproduce]

  Boot to OS.

  Install 570-open NVIDIA driver.

  Launch the NVIDIA X Server Settings in Show Apps.

  [Expected result]

  NV-CONTROL version should display normally (1.29) in NVIDIA X Server
  Settings.

  [Actual Result]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  Note that this issue does not apply to NVIDIA drivers for 560 and
  below.

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



From 2104094 at bugs.launchpad.net  Thu Oct  2 01:01:43 2025
From: 2104094 at bugs.launchpad.net (Yao Wei)
Date: Thu, 02 Oct 2025 01:01:43 -0000
Subject: [Bug 2104094] Re: [SRU] NV-CONTROL version is listed as Unknown using
 570-open driver
References: <174287368699.681557.15942246773009453043.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175936690446.519536.15141253500423886333.launchpad@juju-98d295-prod-launchpad-2>

** Patch removed: "nvidia-settings_510.47.03-0ubuntu4.24.04.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5868792/+files/nvidia-settings_510.47.03-0ubuntu4.24.04.1.debdiff

** Patch removed: "nvidia-settings_510.47.03-0ubuntu4.24.10.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5868793/+files/nvidia-settings_510.47.03-0ubuntu4.24.10.1.debdiff

** Patch removed: "nvidia-settings_510.47.03-0ubuntu4.25.04.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5868794/+files/nvidia-settings_510.47.03-0ubuntu4.25.04.1.debdiff

** Patch removed: "debdiff for noble"
   https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5913830/+files/nvidia-settings_510.47.03-0ubuntu4.1.debdiff

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

Title:
  [SRU] NV-CONTROL version is listed as Unknown using 570-open driver

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * NV-CONTROL version shows "Unknown" in nvidia-settings GUI

   * This update fixes NV-CONTROL version display when using NVIDIA
  570-open driver

  [ Test Plan ]

   * Find machines with PRIME config (e.g. laptops with Intel GPU and
  NVIDIA GPU, where Intel GPU is used for display)

   * Check nvidia-settings, NV-CONTROL version should show "Unknown"

   * Update nvidia-settings package to -proposed, it should show the
  correct version (1.29)

  [ Where problems could occur ]

   * If nvidia-settings breaks completely, some NVIDIA-specific features
  might not be able to configure.

  === Original report ===

  [Summary]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  [Steps to reproduce]

  Boot to OS.

  Install 570-open NVIDIA driver.

  Launch the NVIDIA X Server Settings in Show Apps.

  [Expected result]

  NV-CONTROL version should display normally (1.29) in NVIDIA X Server
  Settings.

  [Actual Result]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  Note that this issue does not apply to NVIDIA drivers for 560 and
  below.

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



From 2104094 at bugs.launchpad.net  Thu Oct  2 01:43:58 2025
From: 2104094 at bugs.launchpad.net (Yao Wei)
Date: Thu, 02 Oct 2025 01:43:58 -0000
Subject: [Bug 2104094] Re: [SRU] NV-CONTROL version is listed as Unknown using
 570-open driver
References: <174287368699.681557.15942246773009453043.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175936943810.572877.5891701225802277515.malone@juju-98d295-prod-launchpad-2>

** Patch added: "nvidia-settings_510.47.03-0ubuntu1.22.04.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5913839/+files/nvidia-settings_510.47.03-0ubuntu1.22.04.1.debdiff

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

Title:
  [SRU] NV-CONTROL version is listed as Unknown using 570-open driver

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * NV-CONTROL version shows "Unknown" in nvidia-settings GUI

   * This update fixes NV-CONTROL version display when using NVIDIA
  570-open driver

  [ Test Plan ]

   * Find machines with PRIME config (e.g. laptops with Intel GPU and
  NVIDIA GPU, where Intel GPU is used for display)

   * Check nvidia-settings, NV-CONTROL version should show "Unknown"

   * Update nvidia-settings package to -proposed, it should show the
  correct version (1.29)

  [ Where problems could occur ]

   * If nvidia-settings breaks completely, some NVIDIA-specific features
  might not be able to configure.

  === Original report ===

  [Summary]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  [Steps to reproduce]

  Boot to OS.

  Install 570-open NVIDIA driver.

  Launch the NVIDIA X Server Settings in Show Apps.

  [Expected result]

  NV-CONTROL version should display normally (1.29) in NVIDIA X Server
  Settings.

  [Actual Result]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  Note that this issue does not apply to NVIDIA drivers for 560 and
  below.

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



From 2104094 at bugs.launchpad.net  Thu Oct  2 01:45:00 2025
From: 2104094 at bugs.launchpad.net (Yao Wei)
Date: Thu, 02 Oct 2025 01:45:00 -0000
Subject: [Bug 2104094] Re: [SRU] NV-CONTROL version is listed as Unknown using
 570-open driver
References: <174287368699.681557.15942246773009453043.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175936950116.1043976.14370258124621233549.malone@juju-98d295-prod-launchpad-7>

** Patch added: "nvidia-settings_510.47.03-0ubuntu4.24.04.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5913840/+files/nvidia-settings_510.47.03-0ubuntu4.24.04.1.debdiff

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

Title:
  [SRU] NV-CONTROL version is listed as Unknown using 570-open driver

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * NV-CONTROL version shows "Unknown" in nvidia-settings GUI

   * This update fixes NV-CONTROL version display when using NVIDIA
  570-open driver

  [ Test Plan ]

   * Find machines with PRIME config (e.g. laptops with Intel GPU and
  NVIDIA GPU, where Intel GPU is used for display)

   * Check nvidia-settings, NV-CONTROL version should show "Unknown"

   * Update nvidia-settings package to -proposed, it should show the
  correct version (1.29)

  [ Where problems could occur ]

   * If nvidia-settings breaks completely, some NVIDIA-specific features
  might not be able to configure.

  === Original report ===

  [Summary]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  [Steps to reproduce]

  Boot to OS.

  Install 570-open NVIDIA driver.

  Launch the NVIDIA X Server Settings in Show Apps.

  [Expected result]

  NV-CONTROL version should display normally (1.29) in NVIDIA X Server
  Settings.

  [Actual Result]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  Note that this issue does not apply to NVIDIA drivers for 560 and
  below.

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



From 2104094 at bugs.launchpad.net  Thu Oct  2 01:45:36 2025
From: 2104094 at bugs.launchpad.net (Yao Wei)
Date: Thu, 02 Oct 2025 01:45:36 -0000
Subject: [Bug 2104094] Re: [SRU] NV-CONTROL version is listed as Unknown using
 570-open driver
References: <174287368699.681557.15942246773009453043.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175936953628.576894.11987841451453877968.malone@juju-98d295-prod-launchpad-2>

** Patch added: "nvidia-settings_510.47.03-0ubuntu4.25.04.1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2104094/+attachment/5913841/+files/nvidia-settings_510.47.03-0ubuntu4.25.04.1.debdiff

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

Title:
  [SRU] NV-CONTROL version is listed as Unknown using 570-open driver

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * NV-CONTROL version shows "Unknown" in nvidia-settings GUI

   * This update fixes NV-CONTROL version display when using NVIDIA
  570-open driver

  [ Test Plan ]

   * Find machines with PRIME config (e.g. laptops with Intel GPU and
  NVIDIA GPU, where Intel GPU is used for display)

   * Check nvidia-settings, NV-CONTROL version should show "Unknown"

   * Update nvidia-settings package to -proposed, it should show the
  correct version (1.29)

  [ Where problems could occur ]

   * If nvidia-settings breaks completely, some NVIDIA-specific features
  might not be able to configure.

  === Original report ===

  [Summary]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  [Steps to reproduce]

  Boot to OS.

  Install 570-open NVIDIA driver.

  Launch the NVIDIA X Server Settings in Show Apps.

  [Expected result]

  NV-CONTROL version should display normally (1.29) in NVIDIA X Server
  Settings.

  [Actual Result]

  NV-CONTROL version shows "Unknown" in NVIDIA X Server Settings.

  Note that this issue does not apply to NVIDIA drivers for 560 and
  below.

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



From 2122576 at bugs.launchpad.net  Thu Oct  2 06:21:36 2025
From: 2122576 at bugs.launchpad.net (Kai-Chuan Hsieh)
Date: Thu, 02 Oct 2025 06:21:36 -0000
Subject: [Bug 2122576] Re: Add support Intel PTL platform and ITMT3.0 policy
References: <175758076411.1792167.10087975254811915865.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175938609691.1465646.7705060702440450522.malone@juju-98d295-prod-launchpad-7>

@juliank

Hello,

thanks for your feedback. I have updated the description and debdiff,
could you help to review if it is ok.


Thanks,


** Description changed:

  [ Impact ]
  
   * The thermald will not be active on Intel PTL platform
  
   * The thermald can't enable ITMT3 even though the processor can support
  it.
  
  [ Test Plan ]
  
   * On Intel PTL platform with ITMT3.0 policy configured
  
   * Boot into Ubuntu
  
   * Stop the default thermald by $ sudo systemctl stop thermald
  
   * run the thermlad with extra parameter $ sudo thermald --systemd
  --dbus-enable --adaptive --log-level=info
  
   * check the journalctl log to confirm that thermald apply the policy
  successfully
  
  1. Make sure to see ITMT3.0 policy defined in the APAT table
  [1754988644][INFO]..apat dump begin..
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance
  
  2. Check that ITMT3 policy is applied
  [1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance
  
  [ Where problems could occur ]
  
   * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.
  
   *
  https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  enhance the support for the ITMT3.0 policy. No code logic change for
  ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
  change the thermal behavior.
  
  [ Other Info ]
  
   * ITMT stands for Intel Turbo Boost Max Technology, a feature that
  identifies the best-performing cores on a processor and directs
  workloads to them for increased single-threaded performance. This
  technology assigns a higher priority to the fastest cores, ensuring that
  demanding tasks get the maximum possible speed on those select cores,
  while other cores handle less intensive work or remain idle. The
  advantage of ITMT3 can be found in The advantage of ITMT3 can be found
  in https://edc.intel.com/content/www/us/en/design/ipla/software-
  development-platforms/client/platforms/alder-lake-desktop/12th-
  generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
  turbo-boost-max-technology-3-0/.
  
   * Upstream commits:
     https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  
   * extra commit for noble to add PTL support.
     https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
     these two I combine them into one patch
     https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
     https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659
+ 
+  * According to Dell architect, there is no certified Dell platform has
+ ITMI3 configured, it will only be available on the coming PTL platform.

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

Title:
  Add support Intel PTL platform and ITMT3.0 policy

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * The thermald will not be active on Intel PTL platform.

   * The thermald still use passive policy on board with ITMI3
  configured.

  [ Test Plan ]

   * On Intel PTL platform with ITMT3.0 policy configured

   * Boot into Ubuntu

   * Stop the default thermald by $ sudo systemctl stop thermald

   * run the thermlad with extra parameter $ sudo thermald --systemd
  --dbus-enable --adaptive --log-level=info

   * check the journalctl log to confirm that thermald apply the policy
  successfully

  1. Make sure to see ITMT3.0 policy defined in the APAT table
  [1754988644][INFO]..apat dump begin..
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance

  2. Check that ITMT3 policy is applied
  [1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance

  [ Where problems could occur ]

   * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.

   *
  https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  enhance the support for the ITMT3.0 policy. No code logic change for
  ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
  change the thermal behavior.

  [ Other Info ]

   * ITMT stands for Intel Turbo Boost Max Technology, a feature that
  identifies the best-performing cores on a processor and directs
  workloads to them for increased single-threaded performance. This
  technology assigns a higher priority to the fastest cores, ensuring
  that demanding tasks get the maximum possible speed on those select
  cores, while other cores handle less intensive work or remain idle.
  The advantage of ITMT3 can be found in The advantage of ITMT3 can be
  found in https://edc.intel.com/content/www/us/en/design/ipla/software-
  development-platforms/client/platforms/alder-lake-desktop/12th-
  generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
  turbo-boost-max-technology-3-0/.

   * Upstream commits:
     https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28

   * extra commit for noble to add PTL support.
     https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
     these two I combine them into one patch
     https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
     https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659

   * According to Dell architect yijun.shen at dell.com, there is no
  certified Dell platform has ITMI3 configured, it will only be
  available on the coming PTL platform.

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



From 2122576 at bugs.launchpad.net  Thu Oct  2 06:27:44 2025
From: 2122576 at bugs.launchpad.net (Kai-Chuan Hsieh)
Date: Thu, 02 Oct 2025 06:27:44 -0000
Subject: [Bug 2122576] Re: Add support Intel PTL platform and ITMT3.0 policy
References: <175758076411.1792167.10087975254811915865.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175938646493.3240754.50661662161460988.launchpad@juju-98d295-prod-launchpad-4>

** Description changed:

  [ Impact ]
  
   * The thermald will not be active on Intel PTL platform
  
   * The thermald can't enable ITMT3 even though the processor can support
  it.
  
  [ Test Plan ]
  
   * On Intel PTL platform with ITMT3.0 policy configured
  
   * Boot into Ubuntu
  
   * Stop the default thermald by $ sudo systemctl stop thermald
  
   * run the thermlad with extra parameter $ sudo thermald --systemd
  --dbus-enable --adaptive --log-level=info
  
   * check the journalctl log to confirm that thermald apply the policy
  successfully
  
  1. Make sure to see ITMT3.0 policy defined in the APAT table
  [1754988644][INFO]..apat dump begin..
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance
  
  2. Check that ITMT3 policy is applied
  [1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance
  
  [ Where problems could occur ]
  
   * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.
  
   *
  https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  enhance the support for the ITMT3.0 policy. No code logic change for
  ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
  change the thermal behavior.
  
  [ Other Info ]
  
   * ITMT stands for Intel Turbo Boost Max Technology, a feature that
  identifies the best-performing cores on a processor and directs
  workloads to them for increased single-threaded performance. This
  technology assigns a higher priority to the fastest cores, ensuring that
  demanding tasks get the maximum possible speed on those select cores,
  while other cores handle less intensive work or remain idle. The
  advantage of ITMT3 can be found in The advantage of ITMT3 can be found
  in https://edc.intel.com/content/www/us/en/design/ipla/software-
  development-platforms/client/platforms/alder-lake-desktop/12th-
  generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
  turbo-boost-max-technology-3-0/.
  
   * Upstream commits:
     https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  
   * extra commit for noble to add PTL support.
     https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
     these two I combine them into one patch
     https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
     https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659
  
-  * According to Dell architect, there is no certified Dell platform has
- ITMI3 configured, it will only be available on the coming PTL platform.
+  * According to Dell architect yijun.shen at dell.com, there is no
+ certified Dell platform has ITMI3 configured, it will only be available
+ on the coming PTL platform.

** Description changed:

  [ Impact ]
  
-  * The thermald will not be active on Intel PTL platform
+  * The thermald will not be active on Intel PTL platform.
  
-  * The thermald can't enable ITMT3 even though the processor can support
- it.
+  * The thermald still use passive policy on board with ITMI3 configured.
  
  [ Test Plan ]
  
   * On Intel PTL platform with ITMT3.0 policy configured
  
   * Boot into Ubuntu
  
   * Stop the default thermald by $ sudo systemctl stop thermald
  
   * run the thermlad with extra parameter $ sudo thermald --systemd
  --dbus-enable --adaptive --log-level=info
  
   * check the journalctl log to confirm that thermald apply the policy
  successfully
  
  1. Make sure to see ITMT3.0 policy defined in the APAT table
  [1754988644][INFO]..apat dump begin..
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance
  
  2. Check that ITMT3 policy is applied
  [1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance
  
  [ Where problems could occur ]
  
   * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.
  
   *
  https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  enhance the support for the ITMT3.0 policy. No code logic change for
  ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
  change the thermal behavior.
  
  [ Other Info ]
  
   * ITMT stands for Intel Turbo Boost Max Technology, a feature that
  identifies the best-performing cores on a processor and directs
  workloads to them for increased single-threaded performance. This
  technology assigns a higher priority to the fastest cores, ensuring that
  demanding tasks get the maximum possible speed on those select cores,
  while other cores handle less intensive work or remain idle. The
  advantage of ITMT3 can be found in The advantage of ITMT3 can be found
  in https://edc.intel.com/content/www/us/en/design/ipla/software-
  development-platforms/client/platforms/alder-lake-desktop/12th-
  generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
  turbo-boost-max-technology-3-0/.
  
   * Upstream commits:
     https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  
   * extra commit for noble to add PTL support.
     https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
     these two I combine them into one patch
     https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
     https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659
  
   * According to Dell architect yijun.shen at dell.com, there is no
  certified Dell platform has ITMI3 configured, it will only be available
  on the coming PTL platform.

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

Title:
  Add support Intel PTL platform and ITMT3.0 policy

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * The thermald will not be active on Intel PTL platform.

   * The thermald still use passive policy on board with ITMI3
  configured.

  [ Test Plan ]

   * On Intel PTL platform with ITMT3.0 policy configured

   * Boot into Ubuntu

   * Stop the default thermald by $ sudo systemctl stop thermald

   * run the thermlad with extra parameter $ sudo thermald --systemd
  --dbus-enable --adaptive --log-level=info

   * check the journalctl log to confirm that thermald apply the policy
  successfully

  1. Make sure to see ITMT3.0 policy defined in the APAT table
  [1754988644][INFO]..apat dump begin..
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance

  2. Check that ITMT3 policy is applied
  [1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance

  [ Where problems could occur ]

   * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.

   *
  https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  enhance the support for the ITMT3.0 policy. No code logic change for
  ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
  change the thermal behavior.

  [ Other Info ]

   * ITMT stands for Intel Turbo Boost Max Technology, a feature that
  identifies the best-performing cores on a processor and directs
  workloads to them for increased single-threaded performance. This
  technology assigns a higher priority to the fastest cores, ensuring
  that demanding tasks get the maximum possible speed on those select
  cores, while other cores handle less intensive work or remain idle.
  The advantage of ITMT3 can be found in The advantage of ITMT3 can be
  found in https://edc.intel.com/content/www/us/en/design/ipla/software-
  development-platforms/client/platforms/alder-lake-desktop/12th-
  generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
  turbo-boost-max-technology-3-0/.

   * Upstream commits:
     https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28

   * extra commit for noble to add PTL support.
     https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
     these two I combine them into one patch
     https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
     https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659

   * According to Dell architect yijun.shen at dell.com, there is no
  certified Dell platform has ITMI3 configured, it will only be
  available on the coming PTL platform.

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



From 2121948 at bugs.launchpad.net  Thu Oct  2 07:14:24 2025
From: 2121948 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 02 Oct 2025 07:14:24 -0000
Subject: [Bug 2121948] Re: [SRU] Support suspend/resume for IMX471 camera
 sensor
References: <175690774470.3522322.3912132826639117162.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175938927143.399253.9087524084068469223.malone@scripts.lp.internal>

This bug was fixed in the package linux-oem-6.14 - 6.14.0-1013.13

---------------
linux-oem-6.14 (6.14.0-1013.13) noble; urgency=medium

  * noble/linux-oem-6.14: 6.14.0-1013.13 -proposed tracker (LP:
#2124041)

  *  system hang observed when running compute over s0i3 (LP: #2125019)
    - SAUCE: drm/amdkfd: Move the process suspend and resume out of full
      access
    - SAUCE: drm/amdgpu/kfd: Add shared SDMA reset functionality with callback
      support
    - SAUCE: drm/amdkfd: add proper handling for S0ix
    - SAUCE: drm/amdgpu: suspend KFD and KGD user queues for S0ix

  * Support Samsung S5K3J1 sensor for Intel MIPI camera (LP: #2121852) //
    [SRU] Support suspend/resume for IMX471 camera sensor (LP: #2121948)
    - [Packaging] debian.oem/dkms-versions -- update ipu6

  * Support Samsung S5K3J1 sensor for Intel MIPI camera (LP: #2121852)
    - SAUCE: media: ipu-bridge: Support s5k3j1 sensor

  * [SRU] Add support of cs42l43 and cs35l56 on ThinkPad P1 and P16
    (LP: #2122379)
    - ASoC: Intel: soc-acpi: arl: Correct order of cs42l43 matches
    - ASoC: Intel: sof_sdw: Add quirks for Lenovo P1 and P16

  * Enable  Wi-Fi 7 MLO on MTK MT7925 (2.4/5 GHz) (LP: #2121342)
    - wifi: mt76: mt7925: introduce MLO capability control

  * r8169 can not wake on LAN via SFP moudule (LP: #2123901)
    - SAUCE: r8169: set EEE speed down ratio to 1

  * A few HP laptops are failing to respond during test runs after upgrading
    to the 6.14.0-1012-oem kernel. (LP: #2122397)
    - wifi: ath12k: eliminate redundant debug mask check in ath12k_dbg()
    - wifi: ath12k: introduce ath12k_generic_dbg()
    - wifi: ath12k: remove redundant vif settings during link interface
      creation
    - wifi: ath12k: remove redundant logic for initializing arvif
    - wifi: ath12k: relocate a few functions in mac.c
    - wifi: ath12k: allocate new links in change_vif_links()
    - wifi: ath12k: handle link removal in change_vif_links()

  [ Ubuntu: 6.14.0-33.33 ]

  * plucky/linux: 6.14.0-33.33 -proposed tracker (LP: #2124042)
  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
  * CVE-2025-38477
    - net/sched: sch_qfq: Fix race condition on qfq_aggregate
    - net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in
      qfq_delete_class
  * CVE-2025-38500
    - xfrm: interface: fix use-after-free after changing collect_md xfrm
      interface
  * CVE-2025-38617
    - net/packet: fix a race in packet_set_ring() and packet_notifier()
  * CVE-2025-38618
    - vsock: Do not allow binding to VMADDR_PORT_ANY

 -- Kuan-Ying Lee <kuan-ying.lee at canonical.com>  Wed, 24 Sep 2025
14:40:27 +0800

** Changed in: linux-oem-6.14 (Ubuntu Noble)
       Status: Fix Committed => Fix Released

** CVE added: https://cve.org/CVERecord?id=CVE-2025-38477

** CVE added: https://cve.org/CVERecord?id=CVE-2025-38500

** CVE added: https://cve.org/CVERecord?id=CVE-2025-38617

** CVE added: https://cve.org/CVERecord?id=CVE-2025-38618

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

Title:
  [SRU] Support suspend/resume for IMX471 camera sensor

Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in linux-oem-6.14 package in Ubuntu:
  Invalid
Status in linux-oem-6.17 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Noble:
  Invalid
Status in linux-oem-6.14 source package in Noble:
  Fix Released
Status in linux-oem-6.17 source package in Noble:
  In Progress
Status in ipu6-drivers source package in Plucky:
  Fix Committed
Status in linux-oem-6.14 source package in Plucky:
  Invalid
Status in linux-oem-6.17 source package in Plucky:
  Invalid
Status in ipu6-drivers source package in Questing:
  Fix Released
Status in linux-oem-6.14 source package in Questing:
  Invalid
Status in linux-oem-6.17 source package in Questing:
  Invalid

Bug description:
  [SRU Justification]

  [ Impact ]

  Sony imx471 is not explicitly powered on before trying to identify the module, leaving following error messages in kernel dmesg buffer:
  ```
  kernel: imx471 i2c-SONY471A:00: failed to find sensor: -5
  kernel: imx471 i2c-SONY471A:00: probe with driver imx471 failed with error -5
  ```

  Proposed fix in
  https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.

  [ Test Plan ]

  1. Install the dkms from -proposed pocket. The corresponding binary kernel module should be built automatically; if not, run:
  ```
  $ sudo dkms install --force ipu6-drivers/0~git202506270118.9bff7368 -k $(uname -r)
  ```

  2. Reboot to the same kernel to reload the drivers.

  3. Make sure the device is probed and up running:
  ```
  $ media-ctl -p
  Media controller API version 6.14.8

  Media device information
  ------------------------
  driver          intel-ipu7
  model           ipu7
  serial          
  bus info        PCI:intel-ipu7
  hw revision     0x17aa233b
  driver version  6.14.8
  ...
  ```

  4. Use https://webcamtests.com to verify the camera is really capable
  of streaming.

  [ Where problems could occur ]

  This fills the probe procedure as other similar camera sensors do. No
  known problem so far.

  [ Other Info ]

  This is a follow-up for bug 2107320 that supports IMX471 in linux-
  oem-6.11 and on. Nominate for Plucky, Questing for ipu6-drivers, which
  will be compiled within linux-oem-6.11 and on.

  ========== original bug report ==========

  This is a follow-up for bug 2107320, support Sony IMX471 camera sensor
  for Intel IPU7 platforms.

  Proposed fix in https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.
  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu     1575 F.... pipewire
                        ubuntu     1579 F.... wireplumber
   /dev/snd/seq:        ubuntu     1575 F.... pipewire
  CRDA: N/A
  CasperMD5CheckMismatches: ./casper/initrd ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for Ubuntu 24.04 for Lenovo
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-noble-oem-24.04c-20250822-50
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2025-08-29 (12 days ago)
  InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20250821)
  IwConfig:
   lo        no wireless extensions.

   wlp0s20f3  no wireless extensions.

   enx607d099eaa26  no wireless extensions.
  MachineType: LENOVO 21Q7ZCM3US
  Package: ipu6-drivers
  ProcFB: 0 xedrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-9011-oem root=UUID=0f9adf29-e579-4dc5-82a4-a98b51147867 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.14.0-9011.11+exp.19-oem 6.14.8
  RelatedPackageVersions:
   linux-restricted-modules-6.14.0-9011-oem N/A
   linux-backports-modules-6.14.0-9011-oem  N/A
   linux-firmware                           20240318.git3b128b60-0ubuntu2.17
  Tags: noble
  Uname: Linux 6.14.0-9011-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/03/2025
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N4CET39W.T02.HotKey (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21Q7ZCM3US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76576 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: dmi:bvnLENOVO:bvrN4CET39W.T02.HotKey(1.15):bd09/03/2025:br1.15:efr1.11:svnLENOVO:pn21Q7ZCM3US:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7ZCM3US:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:
  dmi.product.family: ThinkPad X9-15 Gen 1
  dmi.product.name: 21Q7ZCM3US
  dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1
  dmi.product.version: ThinkPad X9-15 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2121948/+subscriptions



From 2126596 at bugs.launchpad.net  Thu Oct  2 10:26:33 2025
From: 2126596 at bugs.launchpad.net (Sebastien Bacher)
Date: Thu, 02 Oct 2025 10:26:33 -0000
Subject: [Bug 2126596] Re: gvfs 1.57.2-2ubuntu5 autopkgtests failing with
 SyntaxWarning
References: <175934729636.3257950.7089237589155834792.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175940079384.1372418.793419962966972226.malone@juju-98d295-prod-launchpad-2>

Thanks Ravi, I think the warning is a red herring though, it just
happens to print stdout/stderr only on failure. Those warnings are also
here on success run

Doing some local testing in an autopkgtest and printing the output "out
= self.get_monitor_output()" in test_media_player(()

in a success

Drive connected:    'Linux scsi_debug'
  Drive(0): Linux scsi_debug
    Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
    ids:
     unix-device: '/dev/sda'
    themed icons:  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]
    symbolic themed icons:  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]
    is_removable=0
    is_media_removable=0
    has_media=1
    is_media_check_automatic=1
    can_poll_for_media=0
    can_eject=0
    can_start=0
    can_stop=0
    start_stop_type=shutdown
    sort_key=01hotplug/1759397355041609
    Volume(0): bogus-cd
      Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
      ids:
       class: 'device'
       unix-device: '/dev/sda'
       uuid: '2013-01-10-07-29-25-00'
       label: 'bogus-cd'
      uuid=2013-01-10-07-29-25-00
      themed icons:  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]
      symbolic themed icons:  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]
      can_mount=1
      can_eject=0
      should_automount=0
      sort_key=gvfs.time_detected_usec.1759397355112198

Volume added:       'bogus-cd'
  Volume(0): bogus-cd
    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
    ids:
     class: 'device'
     unix-device: '/dev/sda'
     uuid: '2013-01-10-07-29-25-00'
     label: 'bogus-cd'
    uuid=2013-01-10-07-29-25-00
    themed icons:  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]
    symbolic themed icons:  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]
    can_mount=1
    can_eject=0
    should_automount=0
    sort_key=gvfs.time_detected_usec.1759397355112198


but when failing

drive mount: media player ... --------------------------------------------------
Volume changed:     'bogus-cd'
  Volume(0): bogus-cd
    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
    ids:
     class: 'device'
     unix-device: '/dev/sda'
     uuid: '2013-01-10-07-29-25-00'
     label: 'bogus-cd'
    uuid=2013-01-10-07-29-25-00
    themed icons:  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]
    symbolic themed icons:  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]
    can_mount=1
    can_eject=0
    should_automount=0
    sort_key=gvfs.time_detected_usec.1759397388885963

Drive disconnected: 'Linux scsi_debug'
  Drive(0): Linux scsi_debug
    Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
    ids:
     unix-device: '/dev/sda'
    themed icons:  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]
    symbolic themed icons:  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]
    is_removable=0
    is_media_removable=0
    has_media=1
    is_media_check_automatic=1
    can_poll_for_media=0
    can_eject=0
    can_start=0
    can_stop=0
    start_stop_type=shutdown
    sort_key=01hotplug/1759397388678091
    Volume(0): bogus-cd
      Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
      ids:
       class: 'device'
       unix-device: '/dev/sda'
       uuid: '2013-01-10-07-29-25-00'
       label: 'bogus-cd'
      uuid=2013-01-10-07-29-25-00
      themed icons:  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]
      symbolic themed icons:  [drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  [drive-symbolic]  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]
      can_mount=1
      can_eject=0
      should_automount=0
      sort_key=gvfs.time_detected_usec.1759397388885963


the same device is first set up in test_cdrom_api() so it looks like
sometime the volume is removed between the previous test and this one
and sometime not, which then leads to a "changed" event rather than an
"added" one.

A real fix would be to ensure that volume is removed/unsure why it is
sometime and sometime not. Adding a sleep() before "dev =
self.create_host(PTYPE_DISK)" doesn't workaround it.

A potential workaround could be to use a different device name/image for
the cdrom and media cases avoiding relying on the volume to go away in
between tests?

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

Title:
  gvfs 1.57.2-2ubuntu5 autopkgtests failing with SyntaxWarning

Status in gvfs package in Ubuntu:
  New

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  questing/questing/amd64/g/gvfs/20251001_144858_724dc@/log.gz

   97s test_media_player (__main__.Drive.test_media_player)
   99s drive mount: media player ... FAIL
   99s <unknown>:2: SyntaxWarning: invalid escape sequence '\s'
   99s <unknown>:1: SyntaxWarning: invalid escape sequence '\s'
   99s 
   99s ----- dbus stdout -----
   99s 
   99s ----- dbus stderr -----
   99s 
   99s

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



From 2121948 at bugs.launchpad.net  Thu Oct  2 13:38:25 2025
From: 2121948 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 02 Oct 2025 13:38:25 -0000
Subject: [Bug 2121948] Re: [SRU] Support suspend/resume for IMX471 camera
 sensor
References: <175690774470.3522322.3912132826639117162.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175941230783.228540.15580484208173062251.malone@scripts.lp.internal>

This bug was fixed in the package ipu6-drivers -
0~git202411190607.0ad49882-0ubuntu5~25.04.2

---------------
ipu6-drivers (0~git202411190607.0ad49882-0ubuntu5~25.04.2) plucky; urgency=medium

  * Support suspend/resume for IMX471 camera sensor (LP: #2121948)
    - add d/p/Add-IMX471-power-management-for-correct-behaviors.patch

 -- You-Sheng Yang <vicamo at gmail.com>  Thu, 04 Sep 2025 18:53:12 +0800

** Changed in: ipu6-drivers (Ubuntu Plucky)
       Status: Fix Committed => Fix Released

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

Title:
  [SRU] Support suspend/resume for IMX471 camera sensor

Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in linux-oem-6.14 package in Ubuntu:
  Invalid
Status in linux-oem-6.17 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Noble:
  Invalid
Status in linux-oem-6.14 source package in Noble:
  Fix Released
Status in linux-oem-6.17 source package in Noble:
  In Progress
Status in ipu6-drivers source package in Plucky:
  Fix Released
Status in linux-oem-6.14 source package in Plucky:
  Invalid
Status in linux-oem-6.17 source package in Plucky:
  Invalid
Status in ipu6-drivers source package in Questing:
  Fix Released
Status in linux-oem-6.14 source package in Questing:
  Invalid
Status in linux-oem-6.17 source package in Questing:
  Invalid

Bug description:
  [SRU Justification]

  [ Impact ]

  Sony imx471 is not explicitly powered on before trying to identify the module, leaving following error messages in kernel dmesg buffer:
  ```
  kernel: imx471 i2c-SONY471A:00: failed to find sensor: -5
  kernel: imx471 i2c-SONY471A:00: probe with driver imx471 failed with error -5
  ```

  Proposed fix in
  https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.

  [ Test Plan ]

  1. Install the dkms from -proposed pocket. The corresponding binary kernel module should be built automatically; if not, run:
  ```
  $ sudo dkms install --force ipu6-drivers/0~git202506270118.9bff7368 -k $(uname -r)
  ```

  2. Reboot to the same kernel to reload the drivers.

  3. Make sure the device is probed and up running:
  ```
  $ media-ctl -p
  Media controller API version 6.14.8

  Media device information
  ------------------------
  driver          intel-ipu7
  model           ipu7
  serial          
  bus info        PCI:intel-ipu7
  hw revision     0x17aa233b
  driver version  6.14.8
  ...
  ```

  4. Use https://webcamtests.com to verify the camera is really capable
  of streaming.

  [ Where problems could occur ]

  This fills the probe procedure as other similar camera sensors do. No
  known problem so far.

  [ Other Info ]

  This is a follow-up for bug 2107320 that supports IMX471 in linux-
  oem-6.11 and on. Nominate for Plucky, Questing for ipu6-drivers, which
  will be compiled within linux-oem-6.11 and on.

  ========== original bug report ==========

  This is a follow-up for bug 2107320, support Sony IMX471 camera sensor
  for Intel IPU7 platforms.

  Proposed fix in https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.
  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu     1575 F.... pipewire
                        ubuntu     1579 F.... wireplumber
   /dev/snd/seq:        ubuntu     1575 F.... pipewire
  CRDA: N/A
  CasperMD5CheckMismatches: ./casper/initrd ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for Ubuntu 24.04 for Lenovo
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-noble-oem-24.04c-20250822-50
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2025-08-29 (12 days ago)
  InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20250821)
  IwConfig:
   lo        no wireless extensions.

   wlp0s20f3  no wireless extensions.

   enx607d099eaa26  no wireless extensions.
  MachineType: LENOVO 21Q7ZCM3US
  Package: ipu6-drivers
  ProcFB: 0 xedrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-9011-oem root=UUID=0f9adf29-e579-4dc5-82a4-a98b51147867 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.14.0-9011.11+exp.19-oem 6.14.8
  RelatedPackageVersions:
   linux-restricted-modules-6.14.0-9011-oem N/A
   linux-backports-modules-6.14.0-9011-oem  N/A
   linux-firmware                           20240318.git3b128b60-0ubuntu2.17
  Tags: noble
  Uname: Linux 6.14.0-9011-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/03/2025
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N4CET39W.T02.HotKey (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21Q7ZCM3US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76576 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: dmi:bvnLENOVO:bvrN4CET39W.T02.HotKey(1.15):bd09/03/2025:br1.15:efr1.11:svnLENOVO:pn21Q7ZCM3US:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7ZCM3US:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:
  dmi.product.family: ThinkPad X9-15 Gen 1
  dmi.product.name: 21Q7ZCM3US
  dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1
  dmi.product.version: ThinkPad X9-15 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2121948/+subscriptions



From 2121948 at bugs.launchpad.net  Thu Oct  2 13:38:29 2025
From: 2121948 at bugs.launchpad.net (Andreas Hasenack)
Date: Thu, 02 Oct 2025 13:38:29 -0000
Subject: [Bug 2121948] Update Released
References: <175690774470.3522322.3912132826639117162.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175941230969.770485.11207290460556123443.malone@juju-98d295-prod-launchpad-3>

The verification of the Stable Release Update for ipu6-drivers 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2121948

Title:
  [SRU] Support suspend/resume for IMX471 camera sensor

Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in linux-oem-6.14 package in Ubuntu:
  Invalid
Status in linux-oem-6.17 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Noble:
  Invalid
Status in linux-oem-6.14 source package in Noble:
  Fix Released
Status in linux-oem-6.17 source package in Noble:
  In Progress
Status in ipu6-drivers source package in Plucky:
  Fix Released
Status in linux-oem-6.14 source package in Plucky:
  Invalid
Status in linux-oem-6.17 source package in Plucky:
  Invalid
Status in ipu6-drivers source package in Questing:
  Fix Released
Status in linux-oem-6.14 source package in Questing:
  Invalid
Status in linux-oem-6.17 source package in Questing:
  Invalid

Bug description:
  [SRU Justification]

  [ Impact ]

  Sony imx471 is not explicitly powered on before trying to identify the module, leaving following error messages in kernel dmesg buffer:
  ```
  kernel: imx471 i2c-SONY471A:00: failed to find sensor: -5
  kernel: imx471 i2c-SONY471A:00: probe with driver imx471 failed with error -5
  ```

  Proposed fix in
  https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.

  [ Test Plan ]

  1. Install the dkms from -proposed pocket. The corresponding binary kernel module should be built automatically; if not, run:
  ```
  $ sudo dkms install --force ipu6-drivers/0~git202506270118.9bff7368 -k $(uname -r)
  ```

  2. Reboot to the same kernel to reload the drivers.

  3. Make sure the device is probed and up running:
  ```
  $ media-ctl -p
  Media controller API version 6.14.8

  Media device information
  ------------------------
  driver          intel-ipu7
  model           ipu7
  serial          
  bus info        PCI:intel-ipu7
  hw revision     0x17aa233b
  driver version  6.14.8
  ...
  ```

  4. Use https://webcamtests.com to verify the camera is really capable
  of streaming.

  [ Where problems could occur ]

  This fills the probe procedure as other similar camera sensors do. No
  known problem so far.

  [ Other Info ]

  This is a follow-up for bug 2107320 that supports IMX471 in linux-
  oem-6.11 and on. Nominate for Plucky, Questing for ipu6-drivers, which
  will be compiled within linux-oem-6.11 and on.

  ========== original bug report ==========

  This is a follow-up for bug 2107320, support Sony IMX471 camera sensor
  for Intel IPU7 platforms.

  Proposed fix in https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.
  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu     1575 F.... pipewire
                        ubuntu     1579 F.... wireplumber
   /dev/snd/seq:        ubuntu     1575 F.... pipewire
  CRDA: N/A
  CasperMD5CheckMismatches: ./casper/initrd ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for Ubuntu 24.04 for Lenovo
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-noble-oem-24.04c-20250822-50
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2025-08-29 (12 days ago)
  InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20250821)
  IwConfig:
   lo        no wireless extensions.

   wlp0s20f3  no wireless extensions.

   enx607d099eaa26  no wireless extensions.
  MachineType: LENOVO 21Q7ZCM3US
  Package: ipu6-drivers
  ProcFB: 0 xedrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-9011-oem root=UUID=0f9adf29-e579-4dc5-82a4-a98b51147867 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.14.0-9011.11+exp.19-oem 6.14.8
  RelatedPackageVersions:
   linux-restricted-modules-6.14.0-9011-oem N/A
   linux-backports-modules-6.14.0-9011-oem  N/A
   linux-firmware                           20240318.git3b128b60-0ubuntu2.17
  Tags: noble
  Uname: Linux 6.14.0-9011-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/03/2025
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N4CET39W.T02.HotKey (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21Q7ZCM3US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76576 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: dmi:bvnLENOVO:bvrN4CET39W.T02.HotKey(1.15):bd09/03/2025:br1.15:efr1.11:svnLENOVO:pn21Q7ZCM3US:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7ZCM3US:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:
  dmi.product.family: ThinkPad X9-15 Gen 1
  dmi.product.name: 21Q7ZCM3US
  dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1
  dmi.product.version: ThinkPad X9-15 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2121948/+subscriptions



From 2124947 at bugs.launchpad.net  Thu Oct  2 14:18:08 2025
From: 2124947 at bugs.launchpad.net (Simon Poirier)
Date: Thu, 02 Oct 2025 14:18:08 -0000
Subject: [Bug 2124947] Re: editorconfig-core ftbfs on arm in questing archive
 rebuild
References: <175812194061.1948777.8694742432377201955.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175941468859.836170.8755809589509623697.launchpad@juju-98d295-prod-launchpad-3>

** Bug watch added: Debian Bug tracker #1062397
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062397

** Also affects: editorconfig-core (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062397
   Importance: Unknown
       Status: Unknown

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

Title:
  editorconfig-core ftbfs on arm in questing archive rebuild

Status in editorconfig-core package in Ubuntu:
  In Progress
Status in editorconfig-core package in Debian:
  Unknown

Bug description:
  The package fails to build in the recent archive rebuild
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250910-questing-questing.html

  > error: Could not create output directory /<<PKGBUILDDIR>>/obj-
  aarch64-linux-gnu/doc/man

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/editorconfig-core/+bug/2124947/+subscriptions



From 2124947 at bugs.launchpad.net  Thu Oct  2 15:09:50 2025
From: 2124947 at bugs.launchpad.net (Simon Chopin)
Date: Thu, 02 Oct 2025 15:09:50 -0000
Subject: [Bug 2124947] Re: editorconfig-core ftbfs on arm in questing archive
 rebuild
References: <175812194061.1948777.8694742432377201955.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175941779091.2313257.3039697165281686217.malone@juju-98d295-prod-launchpad-7>

The initial fix by simpoir was... incomplete.

I've uploaded a new fix that simply disables all parallelism at the dh
level (and tried a couple of PPA builds in a row)

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

Title:
  editorconfig-core ftbfs on arm in questing archive rebuild

Status in editorconfig-core package in Ubuntu:
  In Progress
Status in editorconfig-core package in Debian:
  Unknown

Bug description:
  The package fails to build in the recent archive rebuild
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250910-questing-questing.html

  > error: Could not create output directory /<<PKGBUILDDIR>>/obj-
  aarch64-linux-gnu/doc/man

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/editorconfig-core/+bug/2124947/+subscriptions



From 2122484 at bugs.launchpad.net  Thu Oct  2 15:19:45 2025
From: 2122484 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 02 Oct 2025 15:19:45 -0000
Subject: [Bug 2122484] Re: Regression in wget 1.25.0,
 incorrectly logging to stderr in quiet mode
References: <175749127228.3538865.4257214592598741745.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175941838638.4111809.16845715103187742021.launchpad@juju-98d295-prod-launchpad-4>

** Description changed:

  There is a change in behavior in wget 1.25, causing it to output
  "Prepended http:// to" on stderr when called using just an address or
- DNS name, even when called with `-q` for quiet mode.
+ DNS name, even when called with `-q` for quiet mode. This blocks the
+ autopkgtest of ovn.
  
  While I'm sure there are good intentions behind this change with
  security in mind, it has real world effects on breaking in the wild
  system test suites.
  
  The offending change has since the release of 1.25.0 been fixed in [0].
  
  0:
  https://cgit.git.savannah.gnu.org/cgit/wget.git/commit/?id=d98df662121977f3d3ba69d0cfbd4d3322714f2d

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

Title:
  Regression in wget 1.25.0, incorrectly logging to stderr in quiet mode

Status in ovn package in Ubuntu:
  New
Status in wget package in Ubuntu:
  New

Bug description:
  There is a change in behavior in wget 1.25, causing it to output
  "Prepended http:// to" on stderr when called using just an address or
  DNS name, even when called with `-q` for quiet mode. This blocks the
  autopkgtest of ovn.

  While I'm sure there are good intentions behind this change with
  security in mind, it has real world effects on breaking in the wild
  system test suites.

  The offending change has since the release of 1.25.0 been fixed in
  [0].

  0:
  https://cgit.git.savannah.gnu.org/cgit/wget.git/commit/?id=d98df662121977f3d3ba69d0cfbd4d3322714f2d

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



From 2122484 at bugs.launchpad.net  Thu Oct  2 15:35:24 2025
From: 2122484 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 02 Oct 2025 15:35:24 -0000
Subject: [Bug 2122484] Re: Regression in wget 1.25.0,
 incorrectly logging to stderr in quiet mode
References: <175749127228.3538865.4257214592598741745.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175941932441.968837.8649954236614219835.malone@juju-98d295-prod-launchpad-3>

Sponsored wget.

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

** Changed in: wget (Ubuntu)
       Status: New => Fix Committed

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

Title:
  Regression in wget 1.25.0, incorrectly logging to stderr in quiet mode

Status in ovn package in Ubuntu:
  New
Status in wget package in Ubuntu:
  Fix Committed

Bug description:
  There is a change in behavior in wget 1.25, causing it to output
  "Prepended http:// to" on stderr when called using just an address or
  DNS name, even when called with `-q` for quiet mode. This blocks the
  autopkgtest of ovn.

  While I'm sure there are good intentions behind this change with
  security in mind, it has real world effects on breaking in the wild
  system test suites.

  The offending change has since the release of 1.25.0 been fixed in
  [0].

  0:
  https://cgit.git.savannah.gnu.org/cgit/wget.git/commit/?id=d98df662121977f3d3ba69d0cfbd4d3322714f2d

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



From 2117389 at bugs.launchpad.net  Thu Oct  2 17:05:04 2025
From: 2117389 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 02 Oct 2025 17:05:04 -0000
Subject: [Bug 2117389] Re: [SRU] evdi-dkms=1.14.2 not working with kernel >=
 6.12
References: <175309661179.3246098.2903563503180141121.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175942470505.2514142.18326714968612541494.malone@juju-98d295-prod-launchpad-7>

Please extend the test plan to test with the stock noble kernel version
and with a kernel >= v6.12.

This upstream patch
https://github.com/DisplayLink/evdi/commit/a2971b023709ea7335964abe5ddab93b6e70b74f
is part of the 1.14.8 release and plucky has this version. So I
sponsored the linked merged.

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

Title:
  [SRU] evdi-dkms=1.14.2 not working with kernel >= 6.12

Status in evdi package in Ubuntu:
  Fix Released
Status in evdi source package in Noble:
  In Progress
Status in evdi source package in Plucky:
  Fix Released
Status in evdi source package in Questing:
  Fix Released

Bug description:
  [ SRU Justification ]

  [ Impact ]

  Noble EVDI driver is unable to open DRM device when compiled and
  loaded into kernels with version >= v6.12.

  ------------[ cut here ]------------
  WARNING: CPU: 16 PID: 426 at drivers/gpu/drm/drm_file.c:317 drm_open_helper+0x11f/0x140
  Modules linked in: snd_soc_dmic binfmt_misc sch_fq_codel v4l2loopback(O) msr evdi(OE) snd_sof_pci_intel_mtl snd_sof_intel_hda_generic soundwire_intel soundwire_cadence intel_ipu6_psys(O) snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda snd_hda_codec_hdmi snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks intel_ipu6_isys soundwire_generic_allocation intel_uncore_frequency snd_soc_acpi videobuf2_dma_sg intel_uncore_frequency_common soundwire_bus videobuf2_memops x86_pkg_temp_thermal videobuf2_v4l2 spi_nor snd_soc_sdca videobuf2_common iwlmvm(+) intel_powerclamp mtd intel_rapl_msr i2c_usbio(O) mei_gsc_proxy gpio_usbio(O) snd_soc_core snd_compress mac80211 ac97_bus xe snd_pcm_dmaengine coretemp libarc4 polyval_clmulni polyval_generic snd_ctl_led snd_hda_intel ghash_clmulni_intel sha256_ssse3 snd_intel_dspcfg sha1_ssse3 processor_thermal_device_pci snd_intel_sdw_acpi aesni_intel processor_thermal_device
   processor_thermal_wt_hint crypto_simd processor_thermal_rfim snd_hda_codec btusb cryptd processor_thermal_rapl hid_sensor_custom_intel_hinge snd_hda_core hid_sensor_accel_3d ov08x40(O) intel_pmc_core btrtl gpu_sched think_lmi(+) intel_rapl_common intel_skl_int3472_tps68470 rapl iwlwifi intel_cstate snd_hwdep hid_sensor_trigger v4l2_fwnode drm_gpuvm tps68470_regulator btintel processor_thermal_wt_req i2c_i801 clk_tps68470 drm_ttm_helper pmt_telemetry v4l2_async industrialio_triggered_buffer btbcm processor_thermal_power_floor joydev thinkpad_acpi intel_skl_int3472_discrete kfifo_buf input_leds processor_thermal_mbox int3403_thermal firmware_attributes_class drm_exec spi_intel_pci pmt_class i2c_smbus wmi_bmof snd_pcm videodev mei_me btmtk intel_ipu6 int3400_thermal hid_sensor_iio_common drm_suballoc_helper bluetooth usbio(O) spi_intel cfg80211 industrialio intel_vpu mei snd_timer i2c_mux ipu_bridge igen6_edac soc_button_array nvram int340x_thermal_zone mc acpi_tad intel_skl_int3472_common acpi_thermal_rel
   intel_hid acpi_pad intel_vsec mac_hid serio_raw i915 drm_buddy ttm drm_display_helper cec rc_core i2c_algo_bit parport_pc ppdev lp parport nvme_fabrics efi_pstore nvme_keyring nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 hid_sensor_custom linear hid_sensor_hub intel_ishtp_hid hid_multitouch hid_generic nvme snd psmouse thunderbolt intel_ish_ipc soundcore ucsi_acpi intel_lpss_pci nvme_core video intel_lpss typec_ucsi intel_ishtp idma64 i2c_hid_acpi nvme_auth typec i2c_hid sparse_keymap hid platform_profile wmi pinctrl_meteorlake
  CPU: 16 UID: 0 PID: 426 Comm: plymouthd Tainted: G           OE      6.14.0-1009-oem #9-Ubuntu
  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
  Hardware name: LENOVO 21KCSIT080/21KCSIT080, BIOS N3YET69W (1.34 ) 08/06/2024
  RIP: 0010:drm_open_helper+0x11f/0x140
  Code: f6 31 ff 45 31 c0 45 31 c9 c3 cc cc cc cc 48 89 df e8 95 98 fe ff 85 c0 74 8d 48 89 df 89 45 e4 e8 46 fa ff ff 8b 45 e4 eb c7 <0f> 0b b8 ea ff ff ff eb be b8 ea ff ff ff eb b7 b8 f0 ff ff ff eb
  RSP: 0018:ffffa693c0d878d8 EFLAGS: 00010246
  RAX: ffffffffc1f1a6c0 RBX: ffff9a5e54cf4388 RCX: 0000000000000000
  RDX: 0000000000000000 RSI: ffff9a5e54cf4388 RDI: ffff9a5e5718cd80
  RBP: ffffa693c0d878f8 R08: 0000000000000000 R09: 0000000000000000
  R10: 0000000000000000 R11: 0000000000000000 R12: ffff9a5e5718cd80
  R13: ffff9a5e6d6d2800 R14: 00000000ffffffed R15: ffffffffc1f1a6c0
  FS:  00007a3e911c1000(0000) GS:ffff9a6580000000(0000) knlGS:0000000000000000
  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
  CR2: 000063a3b6d45000 CR3: 000000011393f005 CR4: 0000000000f70ef0
  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
  DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400
  PKRU: 55555554
  Call Trace:
   <TASK>
   ? drm_minor_acquire+0x9f/0x150
   drm_open+0x73/0x120
   drm_stub_open+0x9b/0xe0
   chrdev_open+0xb8/0x230
   ? __pfx_chrdev_open+0x10/0x10
   do_dentry_open+0x174/0x5b0
   vfs_open+0x2a/0x100
   do_open+0x2b7/0x430
   path_openat+0x134/0x2d0
   ? crng_fast_key_erasure+0xd5/0x120
   do_filp_open+0xd4/0x1a0
   do_sys_openat2+0xb3/0xe0
   __x64_sys_openat+0x55/0xa0
   x64_sys_call+0x1c49/0x2650
   do_syscall_64+0x7e/0x170
   ? netlink_recvmsg+0x282/0x360
   ? sock_recvmsg+0xde/0xf0
   ? __sys_recvfrom+0xcc/0x160
   ? arch_exit_to_user_mode_prepare.isra.0+0x22/0xd0
   ? syscall_exit_to_user_mode+0x38/0x1d0
   ? do_syscall_64+0x8a/0x170
   ? arch_exit_to_user_mode_prepare.isra.0+0x22/0xd0
   ? syscall_exit_to_user_mode+0x38/0x1d0
   ? do_syscall_64+0x8a/0x170
   ? irqentry_exit+0x43/0x50
   ? exc_page_fault+0x96/0x1e0
   entry_SYSCALL_64_after_hwframe+0x76/0x7e
  RIP: 0033:0x7a3e9146f175
  Code: 83 e2 40 75 50 89 f0 f7 d0 a9 00 00 41 00 74 45 80 3d de fe 0e 00 00 74 60 89 da 4c 89 e6 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 7f 00 00 00 48 8b 55 b8 64 48 2b 14 25 28
  RSP: 002b:00007ffca923d9d0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
  RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007a3e9146f175
  RDX: 0000000000000002 RSI: 000063a3b6d44440 RDI: 00000000ffffff9c
  RBP: 00007ffca923da40 R08: 000000063a3b6d44 R09: 0000000000000007
  R10: 0000000000000000 R11: 0000000000000202 R12: 000063a3b6d44440
  R13: 00007a3e911c0f88 R14: 00007a3e9158db00 R15: 000000000000000b
   </TASK>
  ---[ end trace 0000000000000000 ]---

  [ Test Plan ]

  1. Install evdi-dkms from noble-proposed pocket. The dkms module
  should be built automatically by default; if not, execute:

     $ sudo dkms install evdi/1.14.2+dfsg -k $(uname -r)
     $ dkms status
     evdi/1.14.2+dfsg, ..., x86_64: installed

  2. Reboot into the same kernel
  3. Attach DisplayLink device after logging in GUI.
  4. An external monitor should light up and become joined in a few seconds.

  [ Where problems could occur ]

  The module only works with kernel < v6.16 so far, and we may need
  another update for hwe-6.17.

  [ Other Info ]

  The proposed fix has been available in evdi/plucky and evdi/questing.
  Nominate only for Noble.

  ========= original bug report ==========

  We have found an issue between evdi-dkms=1.14.2 and linux-kernel v6.14 on Ubuntu 24.04.2. kernels <=6.11 are unaffected.
  Luckily it is fixed in evdi-dkms=1.14.8 that is available in Ubuntu 25.04 that contains a fix:
    https://github.com/DisplayLink/evdi/commit/a2971b023709ea7335964abe5ddab93b6e70b74f

  Can evdi-dkms in Ubuntu 24.04 be updated?

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



From 2125448 at bugs.launchpad.net  Thu Oct  2 18:00:20 2025
From: 2125448 at bugs.launchpad.net (Jorge Merlino)
Date: Thu, 02 Oct 2025 18:00:20 -0000
Subject: [Bug 2125448] Re: Burst parameter of tc police only allows 4GB while
 the kernel can support much more
References: <175857809490.3129996.13210339429758148161.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175942802085.2138281.2902076526454474556.malone@juju-98d295-prod-launchpad-2>

Patch for Plucky

** Patch added: "lp2125448_plucky.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2125448/+attachment/5914255/+files/lp2125448_plucky.debdiff

** Changed in: iproute2 (Ubuntu Plucky)
     Assignee: (unassigned) => Jorge Merlino (jorge-merlino)

** Changed in: iproute2 (Ubuntu Plucky)
       Status: New => In Progress

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

Title:
  Burst parameter of tc police only allows 4GB while the kernel can
  support much more

Status in iproute2 package in Ubuntu:
  In Progress
Status in iproute2 source package in Jammy:
  New
Status in iproute2 source package in Noble:
  New
Status in iproute2 source package in Plucky:
  In Progress
Status in iproute2 source package in Questing:
  In Progress

Bug description:
  [Impact]
  The tc police burst option limits the size of the burst up to 4 GiB, i.e., UINT_MAX for a 32 bit unsigned int. However, the underlying implementation of burst is computed as "time at the specified rate", and for higher rates, a burst size exceeding 4 GiB is feasible without modification to the kernel.
  Conversely, there can be bursts smaller that 4 GiB that overflow the burst time calculation and that was not detected.

  [Test Plan]
  All the following commands must be run as root. We are assuming the tested interface is eth0.

  Add fq_codel queuing discipline

  # tc qdisc add dev eth0 root fq_codel

  Check the assigned discipline number

  # tc -s qdisc show dev eth0
  qdisc fq_codel nnnn: root refcnt 13 limit ...

  Note the 4 digits nnnn number. It should be substituted for the nnnn
  number in the rest of the following commands.

  1) Tests before the patch is applied

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate and see
  that it fails:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-exceed reclassify
  Error: argument "4294967296" is wrong: buffer

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-
  exceed reclassify

  Check if it was set correctly:

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 1Mbit burst 15261b mtu 64Kb [001d1bf8] peakrate 10Gbit action reclassify overhead 0b

  We can see a result with the overflowed buffer (burst is 15261b)

  2) Tests after the patch is applied:

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-
  exceed reclassify

  We can check that it was set correctly (burst is 4Gb):

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 10Gbit burst 4Gb mtu 64Kb [03333334] peakrate 10Gbit action reclassify overhead 0b

  Remove the filter:

  # tc filter del dev eth0 protocol ip prio 1 parent nnnn:

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-exceed reclassify
  POLICE: burst out of range

  We see that it is out of range

  [Where problems could occur]
  Externally the only difference with the installed patch is that some commands that will previously overflow without errors will now fail. That might break some scripts but it can be argued that they were already broken before.

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



From 2121842 at bugs.launchpad.net  Thu Oct  2 18:58:28 2025
From: 2121842 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 02 Oct 2025 18:58:28 -0000
Subject: [Bug 2121842] Re: [SRU] [FFE] add Intel mbim service to send AT
 command on Dell DW5933e
References: <175678485878.2154842.16197342457815429794.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175943150851.1316020.11406018898393024332.malone@juju-98d295-prod-launchpad-3>

Sponsored libmbim 1.32.0-1ubuntu1 to questing with two changes:

* added a ~ to the version for the added symbols to fix symbols-file-contains-current-version-with-debian-revision
* Added an Origin line to the patch that points to the upstream merge request

Please update the patches for plucky and noble (with those changes).
Then please re-subscribe ubuntu-sponsors.

** Changed in: libmbim (Ubuntu)
       Status: Triaged => Fix Committed

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

Title:
  [SRU] [FFE] add Intel mbim service to send AT command on Dell DW5933e

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Committed
Status in libmbim source package in Noble:
  New
Status in libmbim source package in Plucky:
  New

Bug description:
  [ User impact ]

   * Currently we are not able use AT command to communicate with WWAN
  module DW5933e. This SRU will add a service to make mbimcli able to
  send AT command to the WWAN module.

  [ Test Plan ]

   * On the platform with Dell WWAN module DW5933e:
   * Open terminal Ctrl + Alt + t
   * Use command "sudo mbimcli -d /dev/wwan0mbim0 -p --intel-at-tunnel-set-at-command=at+productinfo=1"
   * it will get output:

     SW VERSION: RMM-G1.99.00.075_0075

     OK

  [ Where problems could occur ]

   * It adds new mbim service for supporting DW5933e module, there is no
  existing service modification.

  [ Other Info ]

   * upstream patch from https://gitlab.freedesktop.org/mobile-
  broadband/libmbim/-/merge_requests/235

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



From 2114261 at bugs.launchpad.net  Fri Oct  3 01:24:10 2025
From: 2114261 at bugs.launchpad.net (You-Sheng Yang)
Date: Fri, 03 Oct 2025 01:24:10 -0000
Subject: [Bug 2114261] Re: [SRU] Failed to build against linux-6.16
References: <174981020912.3028557.31818042851637468.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175945465075.871884.6063280427071077761.malone@juju-98d295-prod-launchpad-4>

This happens only when compiled against Linux kernel >= v6.15-rc1, and
we will never have a kernel > v6.14 for Plucky.

** Also affects: broadcom-sta (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Changed in: broadcom-sta (Ubuntu Plucky)
       Status: New => Won't Fix

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

Title:
  [SRU] Failed to build against linux-6.16

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.16-rc1.

  [ Test Plan ]

  0. Install mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or experimental oem-6.16 kernels from https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/oem-kernel-next
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.16. Nominate Noble for fixing.

  ========== original bug report ==========

  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  src/wl/sys/wl_linux.c: In function 'wl_timer':
  src/wl/sys/wl_linux.c:2381:17: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Wimplicit-function-declaration]
   2381 |                 from_timer(t, tl, timer);
        |                 ^~~~~~~~~~
        |                 mod_timer
  src/wl/sys/wl_linux.c:2381:35: error: 'timer' undeclared (first use in this function); did you mean 'ktimerd'?
   2381 |                 from_timer(t, tl, timer);
        |                                   ^~~~~
        |                                   ktimerd
  src/wl/sys/wl_linux.c:2381:35: note: each undeclared identifier is reported only once for each function it appears in
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: src/wl/sys/wl_linux.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2114261/+subscriptions



From 2111898 at bugs.launchpad.net  Fri Oct  3 01:23:21 2025
From: 2111898 at bugs.launchpad.net (You-Sheng Yang)
Date: Fri, 03 Oct 2025 01:23:21 -0000
Subject: [Bug 2111898] Re: [SRU] Failed to build against linux-6.15
References: <174842157474.914775.12489393328967854313.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175945460112.872196.13587257037376762111.malone@juju-98d295-prod-launchpad-4>

This happens only when compiled against Linux kernel >= v6.15-rc1, and
we will never have a kernel > v6.14 for Plucky.

** Also affects: broadcom-sta (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Changed in: broadcom-sta (Ubuntu Plucky)
       Status: New => Won't Fix

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

Title:
  [SRU] Failed to build against linux-6.15

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.15-rc1.

  [ Test Plan ]

  0. Install mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.15. Nominate Noble.

  ========== original bug report ==========

  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS
  support")， which results in following errors:

  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1

  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!

  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):

  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1

  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):

  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2111898/+subscriptions



From 2121092 at bugs.launchpad.net  Fri Oct  3 01:54:46 2025
From: 2121092 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 03 Oct 2025 01:54:46 -0000
Subject: [Bug 2121092] Re: python-dbusmock autopkgtest failures
References: <175572003993.804696.14328502810198976984.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175945648693.3325812.2942157616247257449.malone@juju-98d295-prod-launchpad-7>

Changelog since 0.36-1 (questing):
----
python-dbusmock (0.37.0-1) unstable; urgency=medium

  * New upstream release:
    - templates: Drop iio-sensors-proxy (See
      https://github.com/martinpitt/python-dbusmock/issues/241)
    - DBusTestCase: Drop obsolete {start,stop}_dbus() methods
    - Fix dbus-daemon startup race condition (Closes: #1109272)

 -- Martin Pitt <mpitt at debian.org>  Sun, 14 Sep 2025 11:27:52 +0200

python-dbusmock (0.36.0-2) unstable; urgency=medium

  * autopkgtest: Disable notify-send AppArmor profile
    apparmor 5.0.0~alpha1-0ubuntu2 in Ubuntu questing introduces an AppArmor
    profile for notify-send. This prevents notify-send from talking to the
    mock D-Bus and fails the notification-daemon tests. Avoid that by
    disabling that AA profile for the test. (LP: #2121092)

 -- Martin Pitt <mpitt at debian.org>  Sun, 24 Aug 2025 14:49:57 +0000

---

The changelog contains only bugfixes and the package is not seeded.
Requesting sync.


** Bug watch added: github.com/martinpitt/python-dbusmock/issues #241
   https://github.com/martinpitt/python-dbusmock/issues/241

** Changed in: python-dbusmock (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  python-dbusmock autopkgtest failures

Status in python-dbusmock package in Ubuntu:
  Fix Released

Bug description:
  python-dbusmock's autopkgtests began failing earlier this month in
  questing:

  https://autopkgtest.ubuntu.com/packages/python-dbusmock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-dbusmock/+bug/2121092/+subscriptions



From 2121092 at bugs.launchpad.net  Fri Oct  3 01:57:03 2025
From: 2121092 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 03 Oct 2025 01:57:03 -0000
Subject: [Bug 2121092] Re: python-dbusmock autopkgtest failures
References: <175572003993.804696.14328502810198976984.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175945662361.1949054.1407828522418440313.malone@juju-98d295-prod-launchpad-3>

This bug was fixed in the package python-dbusmock - 0.37.0-1

---------------
python-dbusmock (0.37.0-1) unstable; urgency=medium

  * New upstream release:
    - templates: Drop iio-sensors-proxy (See
      https://github.com/martinpitt/python-dbusmock/issues/241)
    - DBusTestCase: Drop obsolete {start,stop}_dbus() methods
    - Fix dbus-daemon startup race condition (Closes: #1109272)

 -- Martin Pitt <mpitt at debian.org>  Sun, 14 Sep 2025 11:27:52 +0200

python-dbusmock (0.36.0-2) unstable; urgency=medium

  * autopkgtest: Disable notify-send AppArmor profile
    apparmor 5.0.0~alpha1-0ubuntu2 in Ubuntu questing introduces an AppArmor
    profile for notify-send. This prevents notify-send from talking to the
    mock D-Bus and fails the notification-daemon tests. Avoid that by
    disabling that AA profile for the test. (LP: #2121092)

 -- Martin Pitt <mpitt at debian.org>  Sun, 24 Aug 2025 14:49:57 +0000

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

Title:
  python-dbusmock autopkgtest failures

Status in python-dbusmock package in Ubuntu:
  Fix Released

Bug description:
  python-dbusmock's autopkgtests began failing earlier this month in
  questing:

  https://autopkgtest.ubuntu.com/packages/python-dbusmock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-dbusmock/+bug/2121092/+subscriptions



From 2114261 at bugs.launchpad.net  Fri Oct  3 02:04:45 2025
From: 2114261 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 03 Oct 2025 02:04:45 -0000
Subject: [Bug 2114261] Re: [SRU] Failed to build against linux-6.16
References: <174981020912.3028557.31818042851637468.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175945708630.932377.4787675387501016451.launchpad@juju-98d295-prod-launchpad-4>

** Description changed:

  [SRU Justification]
  
  [ Impact ]
  
  Failed to build against kernel v6.16-rc1.
  
  [ Test Plan ]
  
  0. Install mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or experimental oem-6.16 kernels from https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/oem-kernel-next
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:
  
-    $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
+    $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
  
  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.
  
  [ Where problems could occur ]
  
  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.
  
  [ Other Info ]
  
  This affects series with kernels >= 6.16. Nominate Noble for fixing.
+ 
+ Kernels >= 6.16 will not be introduced in Plucky.
  
  ========== original bug report ==========
  
  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):
  
  src/wl/sys/wl_linux.c: In function 'wl_timer':
  src/wl/sys/wl_linux.c:2381:17: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Wimplicit-function-declaration]
   2381 |                 from_timer(t, tl, timer);
        |                 ^~~~~~~~~~
        |                 mod_timer
  src/wl/sys/wl_linux.c:2381:35: error: 'timer' undeclared (first use in this function); did you mean 'ktimerd'?
   2381 |                 from_timer(t, tl, timer);
        |                                   ^~~~~
        |                                   ktimerd
  src/wl/sys/wl_linux.c:2381:35: note: each undeclared identifier is reported only once for each function it appears in
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: src/wl/sys/wl_linux.o] Error 1

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

Title:
  [SRU] Failed to build against linux-6.16

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.16-rc1.

  [ Test Plan ]

  0. Install mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or experimental oem-6.16 kernels from https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/oem-kernel-next
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.16. Nominate Noble for fixing.

  Kernels >= 6.16 will not be introduced in Plucky.

  ========== original bug report ==========

  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  src/wl/sys/wl_linux.c: In function 'wl_timer':
  src/wl/sys/wl_linux.c:2381:17: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Wimplicit-function-declaration]
   2381 |                 from_timer(t, tl, timer);
        |                 ^~~~~~~~~~
        |                 mod_timer
  src/wl/sys/wl_linux.c:2381:35: error: 'timer' undeclared (first use in this function); did you mean 'ktimerd'?
   2381 |                 from_timer(t, tl, timer);
        |                                   ^~~~~
        |                                   ktimerd
  src/wl/sys/wl_linux.c:2381:35: note: each undeclared identifier is reported only once for each function it appears in
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: src/wl/sys/wl_linux.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2114261/+subscriptions



From 2121092 at bugs.launchpad.net  Fri Oct  3 02:09:25 2025
From: 2121092 at bugs.launchpad.net (=?utf-8?q?Jeremy_B=C3=ADcha?=)
Date: Fri, 03 Oct 2025 02:09:25 -0000
Subject: [Bug 2121092] Re: python-dbusmock autopkgtest failures
References: <175572003993.804696.14328502810198976984.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175945736565.3345785.15652142622850593514.malone@juju-98d295-prod-launchpad-7>

Sorry, I didn't see the replies here until now.

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

Title:
  python-dbusmock autopkgtest failures

Status in python-dbusmock package in Ubuntu:
  Fix Released

Bug description:
  python-dbusmock's autopkgtests began failing earlier this month in
  questing:

  https://autopkgtest.ubuntu.com/packages/python-dbusmock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-dbusmock/+bug/2121092/+subscriptions



From 2111898 at bugs.launchpad.net  Fri Oct  3 02:05:41 2025
From: 2111898 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 03 Oct 2025 02:05:41 -0000
Subject: [Bug 2111898] Re: [SRU] Failed to build against linux-6.15
References: <174842157474.914775.12489393328967854313.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175945714259.2869643.11701073953605196334.launchpad@juju-98d295-prod-launchpad-2>

** Description changed:

  [SRU Justification]
  
  [ Impact ]
  
  Failed to build against kernel v6.15-rc1.
  
  [ Test Plan ]
  
  0. Install mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:
  
-    $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
+    $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
  
  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.
  
  [ Where problems could occur ]
  
  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.
  
  [ Other Info ]
  
  This affects series with kernels >= 6.15. Nominate Noble.
+ Kernels >= 6.15 will not be introduced in Plucky. 
+ 
  
  ========== original bug report ==========
  
  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS support")，
  which results in following errors:
  
  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1
  
  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!
  
  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):
  
  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1
  
  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):
  
  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

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

Title:
  [SRU] Failed to build against linux-6.15

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.15-rc1.

  [ Test Plan ]

  0. Install mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.15. Nominate Noble.
  Kernels >= 6.15 will not be introduced in Plucky. 

  
  ========== original bug report ==========

  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS
  support")， which results in following errors:

  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1

  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!

  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):

  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1

  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):

  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2111898/+subscriptions



From 2122551 at bugs.launchpad.net  Fri Oct  3 04:06:04 2025
From: 2122551 at bugs.launchpad.net (Quang Ngo)
Date: Fri, 03 Oct 2025 04:06:04 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175946436469.2145923.1773896175453868456.malone@juju-98d295-prod-launchpad-3>

** Patch removed: "lp2122551_plucky.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5909734/+files/lp2122551_plucky.patch

** Patch removed: "lp2122551_noble.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5909735/+files/lp2122551_noble.patch

** Patch removed: "lp2122551_uca_epoxy.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5909736/+files/lp2122551_uca_epoxy.patch

** Patch added: "lp2122551_plucky.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5914485/+files/lp2122551_plucky.patch

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  New
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  New

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2122551 at bugs.launchpad.net  Fri Oct  3 04:11:36 2025
From: 2122551 at bugs.launchpad.net (Quang Ngo)
Date: Fri, 03 Oct 2025 04:11:36 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175946469619.2157242.9767635795070992008.malone@juju-98d295-prod-launchpad-3>

** Patch added: "lp2122551_noble.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5914486/+files/lp2122551_noble.patch

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  New
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  New

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2122551 at bugs.launchpad.net  Fri Oct  3 04:11:53 2025
From: 2122551 at bugs.launchpad.net (Quang Ngo)
Date: Fri, 03 Oct 2025 04:11:53 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175946471352.3542403.18089131686960446651.malone@juju-98d295-prod-launchpad-7>

** Patch added: "lp2122551_uca_epoxy.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5914487/+files/lp2122551_uca_epoxy.patch

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  New
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  New

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2111898 at bugs.launchpad.net  Fri Oct  3 04:33:56 2025
From: 2111898 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 03 Oct 2025 04:33:56 -0000
Subject: [Bug 2111898] Re: [SRU] Failed to build against linux-6.15
References: <174842157474.914775.12489393328967854313.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175946603718.2200907.12174773450673044198.launchpad@juju-98d295-prod-launchpad-3>

** Also affects: broadcom-sta (Ubuntu Questing)
   Importance: Undecided
       Status: Fix Released

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

Title:
  [SRU] Failed to build against linux-6.15

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.15-rc1.

  [ Test Plan ]

  0. Install mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.15. Nominate Noble.
  Kernels >= 6.15 will not be introduced in Plucky. 

  
  ========== original bug report ==========

  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS
  support")， which results in following errors:

  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1

  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!

  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):

  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1

  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):

  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2111898/+subscriptions



From 2114261 at bugs.launchpad.net  Fri Oct  3 11:01:43 2025
From: 2114261 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 03 Oct 2025 11:01:43 -0000
Subject: [Bug 2114261] Proposed package upload rejected
References: <174981020912.3028557.31818042851637468.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175948930347.3699539.9407709660850962201.malone@juju-98d295-prod-launchpad-2>

An upload of broadcom-sta to noble-proposed has been rejected from the
upload queue for the following reason: "6.15/6.16 kernels won't be in
noble, please merge these bugs with the 6.17 one to have only one
verification step with in-archive packages".

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

Title:
  [SRU] Failed to build against linux-6.16

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.16-rc1.

  [ Test Plan ]

  0. Install mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or experimental oem-6.16 kernels from https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/oem-kernel-next
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.16. Nominate Noble for fixing.

  Kernels >= 6.16 will not be introduced in Plucky.

  ========== original bug report ==========

  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  src/wl/sys/wl_linux.c: In function 'wl_timer':
  src/wl/sys/wl_linux.c:2381:17: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Wimplicit-function-declaration]
   2381 |                 from_timer(t, tl, timer);
        |                 ^~~~~~~~~~
        |                 mod_timer
  src/wl/sys/wl_linux.c:2381:35: error: 'timer' undeclared (first use in this function); did you mean 'ktimerd'?
   2381 |                 from_timer(t, tl, timer);
        |                                   ^~~~~
        |                                   ktimerd
  src/wl/sys/wl_linux.c:2381:35: note: each undeclared identifier is reported only once for each function it appears in
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: src/wl/sys/wl_linux.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2114261/+subscriptions



From 2111898 at bugs.launchpad.net  Fri Oct  3 11:01:41 2025
From: 2111898 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 03 Oct 2025 11:01:41 -0000
Subject: [Bug 2111898] Proposed package upload rejected
References: <174842157474.914775.12489393328967854313.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175948930154.3697460.7527243776115569377.malone@juju-98d295-prod-launchpad-2>

An upload of broadcom-sta to noble-proposed has been rejected from the
upload queue for the following reason: "6.15/6.16 kernels won't be in
noble, please merge these bugs with the 6.17 one to have only one
verification step with in-archive packages".

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

Title:
  [SRU] Failed to build against linux-6.15

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.15-rc1.

  [ Test Plan ]

  0. Install mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.15. Nominate Noble.
  Kernels >= 6.15 will not be introduced in Plucky. 

  
  ========== original bug report ==========

  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS
  support")， which results in following errors:

  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1

  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!

  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):

  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1

  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):

  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2111898/+subscriptions



From 2125448 at bugs.launchpad.net  Fri Oct  3 13:32:25 2025
From: 2125448 at bugs.launchpad.net (Jorge Merlino)
Date: Fri, 03 Oct 2025 13:32:25 -0000
Subject: [Bug 2125448] Re: Burst parameter of tc police only allows 4GB while
 the kernel can support much more
References: <175857809490.3129996.13210339429758148161.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175949834539.2007222.16183564023911032777.malone@juju-98d295-prod-launchpad-4>

Patch for Noble

** Patch added: "lp2125448_noble.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2125448/+attachment/5914703/+files/lp2125448_noble.debdiff

** Changed in: iproute2 (Ubuntu Noble)
     Assignee: (unassigned) => Jorge Merlino (jorge-merlino)

** Changed in: iproute2 (Ubuntu Noble)
       Status: New => In Progress

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

Title:
  Burst parameter of tc police only allows 4GB while the kernel can
  support much more

Status in iproute2 package in Ubuntu:
  In Progress
Status in iproute2 source package in Jammy:
  New
Status in iproute2 source package in Noble:
  In Progress
Status in iproute2 source package in Plucky:
  In Progress
Status in iproute2 source package in Questing:
  In Progress

Bug description:
  [Impact]
  The tc police burst option limits the size of the burst up to 4 GiB, i.e., UINT_MAX for a 32 bit unsigned int. However, the underlying implementation of burst is computed as "time at the specified rate", and for higher rates, a burst size exceeding 4 GiB is feasible without modification to the kernel.
  Conversely, there can be bursts smaller that 4 GiB that overflow the burst time calculation and that was not detected.

  [Test Plan]
  All the following commands must be run as root. We are assuming the tested interface is eth0.

  Add fq_codel queuing discipline

  # tc qdisc add dev eth0 root fq_codel

  Check the assigned discipline number

  # tc -s qdisc show dev eth0
  qdisc fq_codel nnnn: root refcnt 13 limit ...

  Note the 4 digits nnnn number. It should be substituted for the nnnn
  number in the rest of the following commands.

  1) Tests before the patch is applied

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate and see
  that it fails:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-exceed reclassify
  Error: argument "4294967296" is wrong: buffer

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-
  exceed reclassify

  Check if it was set correctly:

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 1Mbit burst 15261b mtu 64Kb [001d1bf8] peakrate 10Gbit action reclassify overhead 0b

  We can see a result with the overflowed buffer (burst is 15261b)

  2) Tests after the patch is applied:

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-
  exceed reclassify

  We can check that it was set correctly (burst is 4Gb):

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 10Gbit burst 4Gb mtu 64Kb [03333334] peakrate 10Gbit action reclassify overhead 0b

  Remove the filter:

  # tc filter del dev eth0 protocol ip prio 1 parent nnnn:

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-exceed reclassify
  POLICE: burst out of range

  We see that it is out of range

  [Where problems could occur]
  Externally the only difference with the installed patch is that some commands that will previously overflow without errors will now fail. That might break some scripts but it can be argued that they were already broken before.

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



From 2121092 at bugs.launchpad.net  Fri Oct  3 14:54:10 2025
From: 2121092 at bugs.launchpad.net (=?utf-8?q?Jeremy_B=C3=ADcha?=)
Date: Fri, 03 Oct 2025 14:54:10 -0000
Subject: [Bug 2121092] Re: python-dbusmock autopkgtest failures
References: <175572003993.804696.14328502810198976984.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175950325037.2146001.6206759256201317044.malone@juju-98d295-prod-launchpad-4>

The autopkgtests are passing now, except on armhf:

apparmor_parser: Unable to remove "notify-send".  apparmor_parser:
Access denied. You need policy admin privileges to manage profiles.

https://autopkgtest.ubuntu.com/packages/python-dbusmock/questing/armhf

python-dbusmock is not seeded in Ubuntu so there are still a few days to
fix this issue before Ubuntu 25.10 is released next week.

** Changed in: python-dbusmock (Ubuntu)
       Status: Fix Released => Triaged

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

Title:
  python-dbusmock autopkgtest failures

Status in python-dbusmock package in Ubuntu:
  Triaged

Bug description:
  python-dbusmock's autopkgtests began failing earlier this month in
  questing:

  https://autopkgtest.ubuntu.com/packages/python-dbusmock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-dbusmock/+bug/2121092/+subscriptions



From 2125448 at bugs.launchpad.net  Fri Oct  3 15:01:55 2025
From: 2125448 at bugs.launchpad.net (Jorge Merlino)
Date: Fri, 03 Oct 2025 15:01:55 -0000
Subject: [Bug 2125448] Re: Burst parameter of tc police only allows 4GB while
 the kernel can support much more
References: <175857809490.3129996.13210339429758148161.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175950371604.2156225.17983555009963295328.malone@juju-98d295-prod-launchpad-4>

Patch for Jammy

** Patch added: "lp2125448_jammy.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2125448/+attachment/5914735/+files/lp2125448_jammy.debdiff

** Changed in: iproute2 (Ubuntu Jammy)
       Status: New => In Progress

** Changed in: iproute2 (Ubuntu Jammy)
     Assignee: (unassigned) => Jorge Merlino (jorge-merlino)

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

Title:
  Burst parameter of tc police only allows 4GB while the kernel can
  support much more

Status in iproute2 package in Ubuntu:
  In Progress
Status in iproute2 source package in Jammy:
  In Progress
Status in iproute2 source package in Noble:
  In Progress
Status in iproute2 source package in Plucky:
  In Progress
Status in iproute2 source package in Questing:
  In Progress

Bug description:
  [Impact]
  The tc police burst option limits the size of the burst up to 4 GiB, i.e., UINT_MAX for a 32 bit unsigned int. However, the underlying implementation of burst is computed as "time at the specified rate", and for higher rates, a burst size exceeding 4 GiB is feasible without modification to the kernel.
  Conversely, there can be bursts smaller that 4 GiB that overflow the burst time calculation and that was not detected.

  [Test Plan]
  All the following commands must be run as root. We are assuming the tested interface is eth0.

  Add fq_codel queuing discipline

  # tc qdisc add dev eth0 root fq_codel

  Check the assigned discipline number

  # tc -s qdisc show dev eth0
  qdisc fq_codel nnnn: root refcnt 13 limit ...

  Note the 4 digits nnnn number. It should be substituted for the nnnn
  number in the rest of the following commands.

  1) Tests before the patch is applied

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate and see
  that it fails:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-exceed reclassify
  Error: argument "4294967296" is wrong: buffer

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-
  exceed reclassify

  Check if it was set correctly:

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 1Mbit burst 15261b mtu 64Kb [001d1bf8] peakrate 10Gbit action reclassify overhead 0b

  We can see a result with the overflowed buffer (burst is 15261b)

  2) Tests after the patch is applied:

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-
  exceed reclassify

  We can check that it was set correctly (burst is 4Gb):

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 10Gbit burst 4Gb mtu 64Kb [03333334] peakrate 10Gbit action reclassify overhead 0b

  Remove the filter:

  # tc filter del dev eth0 protocol ip prio 1 parent nnnn:

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-exceed reclassify
  POLICE: burst out of range

  We see that it is out of range

  [Where problems could occur]
  Externally the only difference with the installed patch is that some commands that will previously overflow without errors will now fail. That might break some scripts but it can be argued that they were already broken before.

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



From 2114261 at bugs.launchpad.net  Fri Oct  3 15:10:48 2025
From: 2114261 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 03 Oct 2025 15:10:48 -0000
Subject: [Bug 2114261] Re: [SRU] Failed to build against linux-6.16
References: <174981020912.3028557.31818042851637468.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175950424816.4100961.2122523874637290028.malone@juju-98d295-prod-launchpad-2>

amend the test case to test with 6.8 GA kernel and oem-6.17, which is
available on noble-proposed

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

Title:
  [SRU] Failed to build against linux >= 6.16

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.16-rc1.

  [ Test Plan ]

  0. Install kernels >= v6.16.
     - mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or,
     - linux-oem-6.17/noble
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.16. Nominate Noble for fixing.

  Kernels >= 6.16 will not be introduced in Plucky.

  ========== original bug report ==========

  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  src/wl/sys/wl_linux.c: In function 'wl_timer':
  src/wl/sys/wl_linux.c:2381:17: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Wimplicit-function-declaration]
   2381 |                 from_timer(t, tl, timer);
        |                 ^~~~~~~~~~
        |                 mod_timer
  src/wl/sys/wl_linux.c:2381:35: error: 'timer' undeclared (first use in this function); did you mean 'ktimerd'?
   2381 |                 from_timer(t, tl, timer);
        |                                   ^~~~~
        |                                   ktimerd
  src/wl/sys/wl_linux.c:2381:35: note: each undeclared identifier is reported only once for each function it appears in
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: src/wl/sys/wl_linux.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2114261/+subscriptions



From 2114261 at bugs.launchpad.net  Fri Oct  3 15:12:43 2025
From: 2114261 at bugs.launchpad.net (You-Sheng Yang)
Date: Fri, 03 Oct 2025 15:12:43 -0000
Subject: [Bug 2114261] Re: [SRU] Failed to build against linux >= 6.16
References: <174981020912.3028557.31818042851637468.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175950436381.3242137.234451448664189282.launchpad@juju-98d295-prod-launchpad-3>

** Summary changed:

- [SRU] Failed to build against linux-6.16
+ [SRU] Failed to build against linux >= 6.16

** Description changed:

  [SRU Justification]
  
  [ Impact ]
  
  Failed to build against kernel v6.16-rc1.
  
  [ Test Plan ]
  
- 0. Install mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or experimental oem-6.16 kernels from https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/oem-kernel-next
+ 0. Install kernels >= v6.16.
+    - mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or,
+    - linux-oem-6.17/noble
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:
  
     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
  
  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.
  
  [ Where problems could occur ]
  
  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.
  
  [ Other Info ]
  
  This affects series with kernels >= 6.16. Nominate Noble for fixing.
  
  Kernels >= 6.16 will not be introduced in Plucky.
  
  ========== original bug report ==========
  
  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):
  
  src/wl/sys/wl_linux.c: In function 'wl_timer':
  src/wl/sys/wl_linux.c:2381:17: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Wimplicit-function-declaration]
   2381 |                 from_timer(t, tl, timer);
        |                 ^~~~~~~~~~
        |                 mod_timer
  src/wl/sys/wl_linux.c:2381:35: error: 'timer' undeclared (first use in this function); did you mean 'ktimerd'?
   2381 |                 from_timer(t, tl, timer);
        |                                   ^~~~~
        |                                   ktimerd
  src/wl/sys/wl_linux.c:2381:35: note: each undeclared identifier is reported only once for each function it appears in
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: src/wl/sys/wl_linux.o] Error 1

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

Title:
  [SRU] Failed to build against linux >= 6.16

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.16-rc1.

  [ Test Plan ]

  0. Install kernels >= v6.16.
     - mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or,
     - linux-oem-6.17/noble
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.16. Nominate Noble for fixing.

  Kernels >= 6.16 will not be introduced in Plucky.

  ========== original bug report ==========

  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  src/wl/sys/wl_linux.c: In function 'wl_timer':
  src/wl/sys/wl_linux.c:2381:17: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Wimplicit-function-declaration]
   2381 |                 from_timer(t, tl, timer);
        |                 ^~~~~~~~~~
        |                 mod_timer
  src/wl/sys/wl_linux.c:2381:35: error: 'timer' undeclared (first use in this function); did you mean 'ktimerd'?
   2381 |                 from_timer(t, tl, timer);
        |                                   ^~~~~
        |                                   ktimerd
  src/wl/sys/wl_linux.c:2381:35: note: each undeclared identifier is reported only once for each function it appears in
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: src/wl/sys/wl_linux.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2114261/+subscriptions



From 2111898 at bugs.launchpad.net  Fri Oct  3 15:10:50 2025
From: 2111898 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 03 Oct 2025 15:10:50 -0000
Subject: [Bug 2111898] Re: [SRU] Failed to build against linux-6.15
References: <174842157474.914775.12489393328967854313.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175950425054.3246668.18198127307522925147.malone@juju-98d295-prod-launchpad-3>

amend the test case to test with 6.8 GA kernel and oem-6.17, which is
available on noble-proposed

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

Title:
  [SRU] Failed to build against linux >= 6.15

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.15-rc1.

  [ Test Plan ]

  0. Install kernels >= v6.15
     - mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline, or
     - linux-oem-6.17/noble
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.15. Nominate Noble.
  Kernels >= 6.15 will not be introduced in Plucky.

  ========== original bug report ==========

  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS
  support")， which results in following errors:

  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1

  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!

  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):

  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1

  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):

  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2111898/+subscriptions



From 2111898 at bugs.launchpad.net  Fri Oct  3 15:12:34 2025
From: 2111898 at bugs.launchpad.net (You-Sheng Yang)
Date: Fri, 03 Oct 2025 15:12:34 -0000
Subject: [Bug 2111898] Re: [SRU] Failed to build against linux >= 6.15
References: <174842157474.914775.12489393328967854313.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175950435514.2174362.14187836669493293653.launchpad@juju-98d295-prod-launchpad-4>

** Summary changed:

- [SRU] Failed to build against linux-6.15
+ [SRU] Failed to build against linux >= 6.15

** Description changed:

  [SRU Justification]
  
  [ Impact ]
  
  Failed to build against kernel v6.15-rc1.
  
  [ Test Plan ]
  
- 0. Install mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline
+ 0. Install kernels >= v6.15
+    - mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline, or
+    - linux-oem-6.17/noble
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:
  
     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
  
  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.
  
  [ Where problems could occur ]
  
  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.
  
  [ Other Info ]
  
  This affects series with kernels >= 6.15. Nominate Noble.
- Kernels >= 6.15 will not be introduced in Plucky. 
- 
+ Kernels >= 6.15 will not be introduced in Plucky.
  
  ========== original bug report ==========
  
  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS support")，
  which results in following errors:
  
  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1
  
  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!
  
  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):
  
  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1
  
  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):
  
  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

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

Title:
  [SRU] Failed to build against linux >= 6.15

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.15-rc1.

  [ Test Plan ]

  0. Install kernels >= v6.15
     - mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline, or
     - linux-oem-6.17/noble
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.15. Nominate Noble.
  Kernels >= 6.15 will not be introduced in Plucky.

  ========== original bug report ==========

  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS
  support")， which results in following errors:

  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1

  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!

  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):

  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1

  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):

  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2111898/+subscriptions



From 2121607 at bugs.launchpad.net  Fri Oct  3 15:44:31 2025
From: 2121607 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 03 Oct 2025 15:44:31 -0000
Subject: [Bug 2121607] [NEW] [SRU] Nova-api showing latency after upgrading to
 Caracal
References: <175639705793.728435.16126226382096763223.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175950627299.448755.10025096361558016131.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Zachary Raines (raineszm):

[ Impact ]

* A resource leak bug in 21.2.0 of python-attrs (<https://github.com/python-attrs/attrs/issues/826>)
 caused performance issues when an application created many classes with the same name.

* This caused a performance regression in nova through its dependency on python-jsonschema
  * The latency of API calls to nova increases over time

[ Test Plan ]

 To reproduce the issue and confirm the fix:

* Create a minimal openstack deployment, using e.g. devstack
(<https://docs.openstack.org/devstack/latest/>).

* Run a script which makes many calls to the nova API

 ---Script to call API---
 #!/bin/bash
 # --- Get a fresh token (requires openrc sourced first) ---
 get_token() {
     openstack token issue -f value -c id
 }

 OS_TOKEN=$(get_token)
 echo "Using token: $OS_TOKEN"

 # --- Send requests at 10 per second ---
 COUNT=0
 while true; do
     COUNT=$((COUNT + 1))
     STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
         -H "X-Auth-Token: $OS_TOKEN" \
         -H "Accept: application/json" \
         "$NOVA_URL/servers/detail")

     echo "$(date +'%F %T') [$COUNT] HTTP $STATUS"

     if [ "$STATUS" = "401" ]; then
         echo "[$(date)] Got 401 → refreshing token..."
         OS_TOKEN=$(get_token)
         continue # retry next loop with fresh token
     fi
     # sleep 0.1 # 0.1 sec → 10 per second
 done
 ---/Script to call API---

* Simultaneously monitor the response time of API calls using the
openstack CLI

 ---Script to monitor response time---
 #!/bin/bash

 # --- Again openrc must be sourced first ---
 os_quota() {
     openstack quota list --compute --timing --format=json
 }

 headers() {
     os_quota | grep -o -P '/(\w|\d){32}(/d)?' | tr '\n' ','
 }

 time_api() {
     os_quota |
         awk 'BEGIN { FS=","; ORS=","} /quota/ {print $2} END { printf "\n" }'
 }

 OUTPUT="api_calls_$(date +%Y-%m-%dT%H_%M_%S)"

 echo -n "# time," >>"$OUTPUT"
 headers >>"$OUTPUT"
 echo >>"$OUTPUT"

 i=0
 while true; do
     echo -n "$(date +'%F %T')," >>"$OUTPUT"
     time_api >>"$OUTPUT"
     echo -n "."
     if ((i > 80)); then
         i=0
         echo
     fi
     sleep 5
 done

---/Script to monitor response time---

* Observe that the response time increases over time with python-attrs 21.2.0
  * I did this over a period of about 20 hrs.

* Log in to the server hosting the nova API and upgrade python-attrs to
21.4.0

* Repeat the above steps and observe that the response time remains
stable over time.

[ Where problems could occur ]

* Other packages depend on python-attrs as a library and so could be
affected.

* From 21.2.0 to 21.4.0 there was one backward incompatible change change of which could potentailly cause issues:
  * <https://github.com/python-attrs/attrs/blob/21.4.0/CHANGELOG.rst>
    """
    When using @define, converters are now run by default when setting an attribute on an instance -- additionally to validators. I.e. the new default is on_setattr=[attrs.setters.convert, attrs.setters.validate].

    This is unfortunately a breaking change, but it was an oversight, impossible to raise a DeprecationWarning about, and it's better to fix it now while the APIs are very fresh with few users.
    """
  * Since there are no version pins of python-attrs excluding this version it is unlikely to break other packages.
  * It is possible that some users could be using the python3-attr package in their own code, but it is much more likely that
    for user code, attr would be installed via pip, either directly or within a virtualenv.

* The version in noble is 23.2.0 which already includes all these
changes and there doesn't seem to be any associated issues.

[ Other Info ]

* This SRU proposal bumps to 21.4.0 instead of 21.3.0 because 21.4.0 is a bug fix
  release for a regression in 21.3.0.

* This is the first ubuntu specific modification to this package, but it
is a fairly minor one and doesn't need to be carried forward to any
other series.

* A possible lighter weight alternative is to simply cherry pick the
bugfix commit <https://github.com/python-
attrs/attrs/commit/38580632ceac1cd6e477db71e1d190a4130beed4>

** Affects: nova
     Importance: Undecided
         Status: Confirmed

** Affects: python-attrs (Ubuntu)
     Importance: Undecided
         Status: In Progress

** Affects: python-attrs (Ubuntu Jammy)
     Importance: Undecided
         Status: In Progress


** Tags: se-sponsors
-- 
[SRU] Nova-api showing latency after upgrading to Caracal
https://bugs.launchpad.net/bugs/2121607
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2125448 at bugs.launchpad.net  Sun Oct  5 02:43:32 2025
From: 2125448 at bugs.launchpad.net (Matthew Ruffell)
Date: Sun, 05 Oct 2025 02:43:32 -0000
Subject: [Bug 2125448] Re: Burst parameter of tc police only allows 4GB while
 the kernel can support much more
References: <175857809490.3129996.13210339429758148161.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175963221232.875158.2902489273432257156.malone@juju-98d295-prod-launchpad-4>

Hi Jorge,

A few nitpicks, that I don't really think are that important, but are
for next time:

I would prefer if the non-git dep3 tags like Bug, Bug-Ubuntu, and Origin
go after Subject, and are the last tags. After the Signed-off-lines. Its
just a Ubuntu convention.

I understand why you chose the patch names you did, doing 2001, 2002,
etc, to match the existing patches. That is perfectly okay, but the
primary convention to use is lp2125448-1-subject, lp2125448-2-subject,
and so on.

Since this needs to land in -devel, you can either:
1) See if the commits have been tagged upstream and encourage the debian maintainers to package the new release, and get it synced to -devel when RR opens later this month.
2) Find a coredev to sponsor your debdiff to RR. Try Server Team, or Foundation Team.

Questing is closed now, and will need to be done as a SRU.

Thanks,
Matthew

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

Title:
  Burst parameter of tc police only allows 4GB while the kernel can
  support much more

Status in iproute2 package in Ubuntu:
  In Progress
Status in iproute2 source package in Jammy:
  In Progress
Status in iproute2 source package in Noble:
  In Progress
Status in iproute2 source package in Plucky:
  In Progress
Status in iproute2 source package in Questing:
  In Progress

Bug description:
  [Impact]
  The tc police burst option limits the size of the burst up to 4 GiB, i.e., UINT_MAX for a 32 bit unsigned int. However, the underlying implementation of burst is computed as "time at the specified rate", and for higher rates, a burst size exceeding 4 GiB is feasible without modification to the kernel.
  Conversely, there can be bursts smaller that 4 GiB that overflow the burst time calculation and that was not detected.

  [Test Plan]
  All the following commands must be run as root. We are assuming the tested interface is eth0.

  Add fq_codel queuing discipline

  # tc qdisc add dev eth0 root fq_codel

  Check the assigned discipline number

  # tc -s qdisc show dev eth0
  qdisc fq_codel nnnn: root refcnt 13 limit ...

  Note the 4 digits nnnn number. It should be substituted for the nnnn
  number in the rest of the following commands.

  1) Tests before the patch is applied

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate and see
  that it fails:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-exceed reclassify
  Error: argument "4294967296" is wrong: buffer

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-
  exceed reclassify

  Check if it was set correctly:

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 1Mbit burst 15261b mtu 64Kb [001d1bf8] peakrate 10Gbit action reclassify overhead 0b

  We can see a result with the overflowed buffer (burst is 15261b)

  2) Tests after the patch is applied:

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-
  exceed reclassify

  We can check that it was set correctly (burst is 4Gb):

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 10Gbit burst 4Gb mtu 64Kb [03333334] peakrate 10Gbit action reclassify overhead 0b

  Remove the filter:

  # tc filter del dev eth0 protocol ip prio 1 parent nnnn:

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-exceed reclassify
  POLICE: burst out of range

  We see that it is out of range

  [Where problems could occur]
  Externally the only difference with the installed patch is that some commands that will previously overflow without errors will now fail. That might break some scripts but it can be argued that they were already broken before.

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



From 2121607 at bugs.launchpad.net  Mon Oct  6 11:38:29 2025
From: 2121607 at bugs.launchpad.net (Edward Hope-Morley)
Date: Mon, 06 Oct 2025 11:38:29 -0000
Subject: [Bug 2121607] Re: [SRU] Nova-api showing latency after upgrading to
 Caracal
References: <175639705793.728435.16126226382096763223.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175975070964.3580558.12712948703296078692.launchpad@juju-98d295-prod-launchpad-4>

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/yoga
   Importance: Undecided
       Status: New

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

Title:
  [SRU] Nova-api showing latency after upgrading to Caracal

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive yoga series:
  New
Status in OpenStack Compute (nova):
  Confirmed
Status in python-attrs package in Ubuntu:
  In Progress
Status in python-attrs source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  * A resource leak bug in 21.2.0 of python-attrs (<https://github.com/python-attrs/attrs/issues/826>)
   caused performance issues when an application created many classes with the same name.

  * This caused a performance regression in nova through its dependency on python-jsonschema
    * The latency of API calls to nova increases over time

  [ Test Plan ]

   To reproduce the issue and confirm the fix:

  * Create a minimal openstack deployment, using e.g. devstack
  (<https://docs.openstack.org/devstack/latest/>).

  * Run a script which makes many calls to the nova API

   ---Script to call API---
   #!/bin/bash
   # --- Get a fresh token (requires openrc sourced first) ---
   get_token() {
       openstack token issue -f value -c id
   }

   OS_TOKEN=$(get_token)
   echo "Using token: $OS_TOKEN"

   # --- Send requests at 10 per second ---
   COUNT=0
   while true; do
       COUNT=$((COUNT + 1))
       STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
           -H "X-Auth-Token: $OS_TOKEN" \
           -H "Accept: application/json" \
           "$NOVA_URL/servers/detail")

       echo "$(date +'%F %T') [$COUNT] HTTP $STATUS"

       if [ "$STATUS" = "401" ]; then
           echo "[$(date)] Got 401 → refreshing token..."
           OS_TOKEN=$(get_token)
           continue # retry next loop with fresh token
       fi
       # sleep 0.1 # 0.1 sec → 10 per second
   done
   ---/Script to call API---

  * Simultaneously monitor the response time of API calls using the
  openstack CLI

   ---Script to monitor response time---
   #!/bin/bash

   # --- Again openrc must be sourced first ---
   os_quota() {
       openstack quota list --compute --timing --format=json
   }

   headers() {
       os_quota | grep -o -P '/(\w|\d){32}(/d)?' | tr '\n' ','
   }

   time_api() {
       os_quota |
           awk 'BEGIN { FS=","; ORS=","} /quota/ {print $2} END { printf "\n" }'
   }

   OUTPUT="api_calls_$(date +%Y-%m-%dT%H_%M_%S)"

   echo -n "# time," >>"$OUTPUT"
   headers >>"$OUTPUT"
   echo >>"$OUTPUT"

   i=0
   while true; do
       echo -n "$(date +'%F %T')," >>"$OUTPUT"
       time_api >>"$OUTPUT"
       echo -n "."
       if ((i > 80)); then
           i=0
           echo
       fi
       sleep 5
   done

  ---/Script to monitor response time---

  * Observe that the response time increases over time with python-attrs 21.2.0
    * I did this over a period of about 20 hrs.

  * Log in to the server hosting the nova API and upgrade python-attrs
  to 21.4.0

  * Repeat the above steps and observe that the response time remains
  stable over time.

  [ Where problems could occur ]

  * Other packages depend on python-attrs as a library and so could be
  affected.

  * From 21.2.0 to 21.4.0 there was one backward incompatible change change of which could potentailly cause issues:
    * <https://github.com/python-attrs/attrs/blob/21.4.0/CHANGELOG.rst>
      """
      When using @define, converters are now run by default when setting an attribute on an instance -- additionally to validators. I.e. the new default is on_setattr=[attrs.setters.convert, attrs.setters.validate].

      This is unfortunately a breaking change, but it was an oversight, impossible to raise a DeprecationWarning about, and it's better to fix it now while the APIs are very fresh with few users.
      """
    * Since there are no version pins of python-attrs excluding this version it is unlikely to break other packages.
    * It is possible that some users could be using the python3-attr package in their own code, but it is much more likely that
      for user code, attr would be installed via pip, either directly or within a virtualenv.

  * The version in noble is 23.2.0 which already includes all these
  changes and there doesn't seem to be any associated issues.

  [ Other Info ]

  * This SRU proposal bumps to 21.4.0 instead of 21.3.0 because 21.4.0 is a bug fix
    release for a regression in 21.3.0.

  * This is the first ubuntu specific modification to this package, but
  it is a fairly minor one and doesn't need to be carried forward to any
  other series.

  * A possible lighter weight alternative is to simply cherry pick the
  bugfix commit <https://github.com/python-
  attrs/attrs/commit/38580632ceac1cd6e477db71e1d190a4130beed4>

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2121607/+subscriptions



From 2121607 at bugs.launchpad.net  Mon Oct  6 11:52:47 2025
From: 2121607 at bugs.launchpad.net (Edward Hope-Morley)
Date: Mon, 06 Oct 2025 11:52:47 -0000
Subject: [Bug 2121607] Re: [SRU] Nova-api showing latency after upgrading to
 Caracal
References: <175639705793.728435.16126226382096763223.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175975156805.1813497.17098738271033988615.launchpad@juju-98d295-prod-launchpad-7>

** No longer affects: cloud-archive

** No longer affects: cloud-archive/yoga

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

Title:
  [SRU] Nova-api showing latency after upgrading to Caracal

Status in OpenStack Compute (nova):
  Confirmed
Status in python-attrs package in Ubuntu:
  In Progress
Status in python-attrs source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  * A resource leak bug in 21.2.0 of python-attrs (<https://github.com/python-attrs/attrs/issues/826>)
   caused performance issues when an application created many classes with the same name.

  * This caused a performance regression in nova through its dependency on python-jsonschema
    * The latency of API calls to nova increases over time

  [ Test Plan ]

   To reproduce the issue and confirm the fix:

  * Create a minimal openstack deployment, using e.g. devstack
  (<https://docs.openstack.org/devstack/latest/>).

  * Run a script which makes many calls to the nova API

   ---Script to call API---
   #!/bin/bash
   # --- Get a fresh token (requires openrc sourced first) ---
   get_token() {
       openstack token issue -f value -c id
   }

   OS_TOKEN=$(get_token)
   echo "Using token: $OS_TOKEN"

   # --- Send requests at 10 per second ---
   COUNT=0
   while true; do
       COUNT=$((COUNT + 1))
       STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
           -H "X-Auth-Token: $OS_TOKEN" \
           -H "Accept: application/json" \
           "$NOVA_URL/servers/detail")

       echo "$(date +'%F %T') [$COUNT] HTTP $STATUS"

       if [ "$STATUS" = "401" ]; then
           echo "[$(date)] Got 401 → refreshing token..."
           OS_TOKEN=$(get_token)
           continue # retry next loop with fresh token
       fi
       # sleep 0.1 # 0.1 sec → 10 per second
   done
   ---/Script to call API---

  * Simultaneously monitor the response time of API calls using the
  openstack CLI

   ---Script to monitor response time---
   #!/bin/bash

   # --- Again openrc must be sourced first ---
   os_quota() {
       openstack quota list --compute --timing --format=json
   }

   headers() {
       os_quota | grep -o -P '/(\w|\d){32}(/d)?' | tr '\n' ','
   }

   time_api() {
       os_quota |
           awk 'BEGIN { FS=","; ORS=","} /quota/ {print $2} END { printf "\n" }'
   }

   OUTPUT="api_calls_$(date +%Y-%m-%dT%H_%M_%S)"

   echo -n "# time," >>"$OUTPUT"
   headers >>"$OUTPUT"
   echo >>"$OUTPUT"

   i=0
   while true; do
       echo -n "$(date +'%F %T')," >>"$OUTPUT"
       time_api >>"$OUTPUT"
       echo -n "."
       if ((i > 80)); then
           i=0
           echo
       fi
       sleep 5
   done

  ---/Script to monitor response time---

  * Observe that the response time increases over time with python-attrs 21.2.0
    * I did this over a period of about 20 hrs.

  * Log in to the server hosting the nova API and upgrade python-attrs
  to 21.4.0

  * Repeat the above steps and observe that the response time remains
  stable over time.

  [ Where problems could occur ]

  * Other packages depend on python-attrs as a library and so could be
  affected.

  * From 21.2.0 to 21.4.0 there was one backward incompatible change change of which could potentailly cause issues:
    * <https://github.com/python-attrs/attrs/blob/21.4.0/CHANGELOG.rst>
      """
      When using @define, converters are now run by default when setting an attribute on an instance -- additionally to validators. I.e. the new default is on_setattr=[attrs.setters.convert, attrs.setters.validate].

      This is unfortunately a breaking change, but it was an oversight, impossible to raise a DeprecationWarning about, and it's better to fix it now while the APIs are very fresh with few users.
      """
    * Since there are no version pins of python-attrs excluding this version it is unlikely to break other packages.
    * It is possible that some users could be using the python3-attr package in their own code, but it is much more likely that
      for user code, attr would be installed via pip, either directly or within a virtualenv.

  * The version in noble is 23.2.0 which already includes all these
  changes and there doesn't seem to be any associated issues.

  [ Other Info ]

  * This SRU proposal bumps to 21.4.0 instead of 21.3.0 because 21.4.0 is a bug fix
    release for a regression in 21.3.0.

  * This is the first ubuntu specific modification to this package, but
  it is a fairly minor one and doesn't need to be carried forward to any
  other series.

  * A possible lighter weight alternative is to simply cherry pick the
  bugfix commit <https://github.com/python-
  attrs/attrs/commit/38580632ceac1cd6e477db71e1d190a4130beed4>

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



From 2121607 at bugs.launchpad.net  Mon Oct  6 15:05:05 2025
From: 2121607 at bugs.launchpad.net (Edward Hope-Morley)
Date: Mon, 06 Oct 2025 15:05:05 -0000
Subject: [Bug 2121607] Re: [SRU] Nova-api showing latency after upgrading to
 Caracal
References: <175639705793.728435.16126226382096763223.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175976310557.1632550.15446126009635180036.malone@juju-98d295-prod-launchpad-2>

Hi Zach, thank you for this request. Having reviewed it I think it is
going to make for a challenging SRU due to the size and complexity of
the patch (and the fact that it is point release rather than a single
fix). I wonder if it is possible to isolate a single fix that would
resolve the issue you see so that we can SRU that instead? As an
alternative I have been discussing other ways that we might be able to
get this done and wanted to propose the solution of backporting the
version in Noble (currently 23.2.0-2) to the Carcal Ubuntu Cloud Archive
that way we would have the same version in Noble made available to users
of Jammy running OpenStack Caracal and avoid having to change the
version in Jammy itself. The process of doing the backport is fairly
simple (i can show you how) but it is going to require thorough testing
to ensure (a) no regressions are introduced and (b) the desired
performance is achieved. Can you please let me know your thoughts?

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

Title:
  [SRU] Nova-api showing latency after upgrading to Caracal

Status in OpenStack Compute (nova):
  Confirmed
Status in python-attrs package in Ubuntu:
  In Progress
Status in python-attrs source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  * A resource leak bug in 21.2.0 of python-attrs (<https://github.com/python-attrs/attrs/issues/826>)
   caused performance issues when an application created many classes with the same name.

  * This caused a performance regression in nova through its dependency on python-jsonschema
    * The latency of API calls to nova increases over time

  [ Test Plan ]

   To reproduce the issue and confirm the fix:

  * Create a minimal openstack deployment, using e.g. devstack
  (<https://docs.openstack.org/devstack/latest/>).

  * Run a script which makes many calls to the nova API

   ---Script to call API---
   #!/bin/bash
   # --- Get a fresh token (requires openrc sourced first) ---
   get_token() {
       openstack token issue -f value -c id
   }

   OS_TOKEN=$(get_token)
   echo "Using token: $OS_TOKEN"

   # --- Send requests at 10 per second ---
   COUNT=0
   while true; do
       COUNT=$((COUNT + 1))
       STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
           -H "X-Auth-Token: $OS_TOKEN" \
           -H "Accept: application/json" \
           "$NOVA_URL/servers/detail")

       echo "$(date +'%F %T') [$COUNT] HTTP $STATUS"

       if [ "$STATUS" = "401" ]; then
           echo "[$(date)] Got 401 → refreshing token..."
           OS_TOKEN=$(get_token)
           continue # retry next loop with fresh token
       fi
       # sleep 0.1 # 0.1 sec → 10 per second
   done
   ---/Script to call API---

  * Simultaneously monitor the response time of API calls using the
  openstack CLI

   ---Script to monitor response time---
   #!/bin/bash

   # --- Again openrc must be sourced first ---
   os_quota() {
       openstack quota list --compute --timing --format=json
   }

   headers() {
       os_quota | grep -o -P '/(\w|\d){32}(/d)?' | tr '\n' ','
   }

   time_api() {
       os_quota |
           awk 'BEGIN { FS=","; ORS=","} /quota/ {print $2} END { printf "\n" }'
   }

   OUTPUT="api_calls_$(date +%Y-%m-%dT%H_%M_%S)"

   echo -n "# time," >>"$OUTPUT"
   headers >>"$OUTPUT"
   echo >>"$OUTPUT"

   i=0
   while true; do
       echo -n "$(date +'%F %T')," >>"$OUTPUT"
       time_api >>"$OUTPUT"
       echo -n "."
       if ((i > 80)); then
           i=0
           echo
       fi
       sleep 5
   done

  ---/Script to monitor response time---

  * Observe that the response time increases over time with python-attrs 21.2.0
    * I did this over a period of about 20 hrs.

  * Log in to the server hosting the nova API and upgrade python-attrs
  to 21.4.0

  * Repeat the above steps and observe that the response time remains
  stable over time.

  [ Where problems could occur ]

  * Other packages depend on python-attrs as a library and so could be
  affected.

  * From 21.2.0 to 21.4.0 there was one backward incompatible change change of which could potentailly cause issues:
    * <https://github.com/python-attrs/attrs/blob/21.4.0/CHANGELOG.rst>
      """
      When using @define, converters are now run by default when setting an attribute on an instance -- additionally to validators. I.e. the new default is on_setattr=[attrs.setters.convert, attrs.setters.validate].

      This is unfortunately a breaking change, but it was an oversight, impossible to raise a DeprecationWarning about, and it's better to fix it now while the APIs are very fresh with few users.
      """
    * Since there are no version pins of python-attrs excluding this version it is unlikely to break other packages.
    * It is possible that some users could be using the python3-attr package in their own code, but it is much more likely that
      for user code, attr would be installed via pip, either directly or within a virtualenv.

  * The version in noble is 23.2.0 which already includes all these
  changes and there doesn't seem to be any associated issues.

  [ Other Info ]

  * This SRU proposal bumps to 21.4.0 instead of 21.3.0 because 21.4.0 is a bug fix
    release for a regression in 21.3.0.

  * This is the first ubuntu specific modification to this package, but
  it is a fairly minor one and doesn't need to be carried forward to any
  other series.

  * A possible lighter weight alternative is to simply cherry pick the
  bugfix commit <https://github.com/python-
  attrs/attrs/commit/38580632ceac1cd6e477db71e1d190a4130beed4>

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



From 2121607 at bugs.launchpad.net  Mon Oct  6 15:08:54 2025
From: 2121607 at bugs.launchpad.net (Zachary Raines)
Date: Mon, 06 Oct 2025 15:08:54 -0000
Subject: [Bug 2121607] Re: [SRU] Nova-api showing latency after upgrading to
 Caracal
References: <175639705793.728435.16126226382096763223.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175976333436.1205983.5096147015644188407.malone@juju-98d295-prod-launchpad-3>

Thanks for taking a look! If the complexity of bumping the point release
is too high, it shouldn't be any trouble to do a cherry-pick of the fix
from upstream, since its just a single commit.

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

Title:
  [SRU] Nova-api showing latency after upgrading to Caracal

Status in OpenStack Compute (nova):
  Confirmed
Status in python-attrs package in Ubuntu:
  In Progress
Status in python-attrs source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  * A resource leak bug in 21.2.0 of python-attrs (<https://github.com/python-attrs/attrs/issues/826>)
   caused performance issues when an application created many classes with the same name.

  * This caused a performance regression in nova through its dependency on python-jsonschema
    * The latency of API calls to nova increases over time

  [ Test Plan ]

   To reproduce the issue and confirm the fix:

  * Create a minimal openstack deployment, using e.g. devstack
  (<https://docs.openstack.org/devstack/latest/>).

  * Run a script which makes many calls to the nova API

   ---Script to call API---
   #!/bin/bash
   # --- Get a fresh token (requires openrc sourced first) ---
   get_token() {
       openstack token issue -f value -c id
   }

   OS_TOKEN=$(get_token)
   echo "Using token: $OS_TOKEN"

   # --- Send requests at 10 per second ---
   COUNT=0
   while true; do
       COUNT=$((COUNT + 1))
       STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
           -H "X-Auth-Token: $OS_TOKEN" \
           -H "Accept: application/json" \
           "$NOVA_URL/servers/detail")

       echo "$(date +'%F %T') [$COUNT] HTTP $STATUS"

       if [ "$STATUS" = "401" ]; then
           echo "[$(date)] Got 401 → refreshing token..."
           OS_TOKEN=$(get_token)
           continue # retry next loop with fresh token
       fi
       # sleep 0.1 # 0.1 sec → 10 per second
   done
   ---/Script to call API---

  * Simultaneously monitor the response time of API calls using the
  openstack CLI

   ---Script to monitor response time---
   #!/bin/bash

   # --- Again openrc must be sourced first ---
   os_quota() {
       openstack quota list --compute --timing --format=json
   }

   headers() {
       os_quota | grep -o -P '/(\w|\d){32}(/d)?' | tr '\n' ','
   }

   time_api() {
       os_quota |
           awk 'BEGIN { FS=","; ORS=","} /quota/ {print $2} END { printf "\n" }'
   }

   OUTPUT="api_calls_$(date +%Y-%m-%dT%H_%M_%S)"

   echo -n "# time," >>"$OUTPUT"
   headers >>"$OUTPUT"
   echo >>"$OUTPUT"

   i=0
   while true; do
       echo -n "$(date +'%F %T')," >>"$OUTPUT"
       time_api >>"$OUTPUT"
       echo -n "."
       if ((i > 80)); then
           i=0
           echo
       fi
       sleep 5
   done

  ---/Script to monitor response time---

  * Observe that the response time increases over time with python-attrs 21.2.0
    * I did this over a period of about 20 hrs.

  * Log in to the server hosting the nova API and upgrade python-attrs
  to 21.4.0

  * Repeat the above steps and observe that the response time remains
  stable over time.

  [ Where problems could occur ]

  * Other packages depend on python-attrs as a library and so could be
  affected.

  * From 21.2.0 to 21.4.0 there was one backward incompatible change change of which could potentailly cause issues:
    * <https://github.com/python-attrs/attrs/blob/21.4.0/CHANGELOG.rst>
      """
      When using @define, converters are now run by default when setting an attribute on an instance -- additionally to validators. I.e. the new default is on_setattr=[attrs.setters.convert, attrs.setters.validate].

      This is unfortunately a breaking change, but it was an oversight, impossible to raise a DeprecationWarning about, and it's better to fix it now while the APIs are very fresh with few users.
      """
    * Since there are no version pins of python-attrs excluding this version it is unlikely to break other packages.
    * It is possible that some users could be using the python3-attr package in their own code, but it is much more likely that
      for user code, attr would be installed via pip, either directly or within a virtualenv.

  * The version in noble is 23.2.0 which already includes all these
  changes and there doesn't seem to be any associated issues.

  [ Other Info ]

  * This SRU proposal bumps to 21.4.0 instead of 21.3.0 because 21.4.0 is a bug fix
    release for a regression in 21.3.0.

  * This is the first ubuntu specific modification to this package, but
  it is a fairly minor one and doesn't need to be carried forward to any
  other series.

  * A possible lighter weight alternative is to simply cherry pick the
  bugfix commit <https://github.com/python-
  attrs/attrs/commit/38580632ceac1cd6e477db71e1d190a4130beed4>

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



From 2121607 at bugs.launchpad.net  Mon Oct  6 15:39:41 2025
From: 2121607 at bugs.launchpad.net (Zachary Raines)
Date: Mon, 06 Oct 2025 15:39:41 -0000
Subject: [Bug 2121607] Re: [SRU] Nova-api showing latency after upgrading to
 Caracal
References: <175639705793.728435.16126226382096763223.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175976518189.1690579.12131677865791539069.malone@juju-98d295-prod-launchpad-2>

** Patch added: "python-attrs_lp2121607_cherrypick.debdiff"
   https://bugs.launchpad.net/nova/+bug/2121607/+attachment/5915773/+files/python-attrs_lp2121607_cherrypick.debdiff

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

Title:
  [SRU] Nova-api showing latency after upgrading to Caracal

Status in OpenStack Compute (nova):
  Confirmed
Status in python-attrs package in Ubuntu:
  In Progress
Status in python-attrs source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  * A resource leak bug in 21.2.0 of python-attrs (<https://github.com/python-attrs/attrs/issues/826>)
   caused performance issues when an application created many classes with the same name.

  * This caused a performance regression in nova through its dependency on python-jsonschema
    * The latency of API calls to nova increases over time

  [ Test Plan ]

   To reproduce the issue and confirm the fix:

  * Create a minimal openstack deployment, using e.g. devstack
  (<https://docs.openstack.org/devstack/latest/>).

  * Run a script which makes many calls to the nova API

   ---Script to call API---
   #!/bin/bash
   # --- Get a fresh token (requires openrc sourced first) ---
   get_token() {
       openstack token issue -f value -c id
   }

   OS_TOKEN=$(get_token)
   echo "Using token: $OS_TOKEN"

   # --- Send requests at 10 per second ---
   COUNT=0
   while true; do
       COUNT=$((COUNT + 1))
       STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
           -H "X-Auth-Token: $OS_TOKEN" \
           -H "Accept: application/json" \
           "$NOVA_URL/servers/detail")

       echo "$(date +'%F %T') [$COUNT] HTTP $STATUS"

       if [ "$STATUS" = "401" ]; then
           echo "[$(date)] Got 401 → refreshing token..."
           OS_TOKEN=$(get_token)
           continue # retry next loop with fresh token
       fi
       # sleep 0.1 # 0.1 sec → 10 per second
   done
   ---/Script to call API---

  * Simultaneously monitor the response time of API calls using the
  openstack CLI

   ---Script to monitor response time---
   #!/bin/bash

   # --- Again openrc must be sourced first ---
   os_quota() {
       openstack quota list --compute --timing --format=json
   }

   headers() {
       os_quota | grep -o -P '/(\w|\d){32}(/d)?' | tr '\n' ','
   }

   time_api() {
       os_quota |
           awk 'BEGIN { FS=","; ORS=","} /quota/ {print $2} END { printf "\n" }'
   }

   OUTPUT="api_calls_$(date +%Y-%m-%dT%H_%M_%S)"

   echo -n "# time," >>"$OUTPUT"
   headers >>"$OUTPUT"
   echo >>"$OUTPUT"

   i=0
   while true; do
       echo -n "$(date +'%F %T')," >>"$OUTPUT"
       time_api >>"$OUTPUT"
       echo -n "."
       if ((i > 80)); then
           i=0
           echo
       fi
       sleep 5
   done

  ---/Script to monitor response time---

  * Observe that the response time increases over time with python-attrs 21.2.0
    * I did this over a period of about 20 hrs.

  * Log in to the server hosting the nova API and upgrade python-attrs
  to 21.4.0

  * Repeat the above steps and observe that the response time remains
  stable over time.

  [ Where problems could occur ]

  * Other packages depend on python-attrs as a library and so could be
  affected.

  * From 21.2.0 to 21.4.0 there was one backward incompatible change change of which could potentailly cause issues:
    * <https://github.com/python-attrs/attrs/blob/21.4.0/CHANGELOG.rst>
      """
      When using @define, converters are now run by default when setting an attribute on an instance -- additionally to validators. I.e. the new default is on_setattr=[attrs.setters.convert, attrs.setters.validate].

      This is unfortunately a breaking change, but it was an oversight, impossible to raise a DeprecationWarning about, and it's better to fix it now while the APIs are very fresh with few users.
      """
    * Since there are no version pins of python-attrs excluding this version it is unlikely to break other packages.
    * It is possible that some users could be using the python3-attr package in their own code, but it is much more likely that
      for user code, attr would be installed via pip, either directly or within a virtualenv.

  * The version in noble is 23.2.0 which already includes all these
  changes and there doesn't seem to be any associated issues.

  [ Other Info ]

  * This SRU proposal bumps to 21.4.0 instead of 21.3.0 because 21.4.0 is a bug fix
    release for a regression in 21.3.0.

  * This is the first ubuntu specific modification to this package, but
  it is a fairly minor one and doesn't need to be carried forward to any
  other series.

  * A possible lighter weight alternative is to simply cherry pick the
  bugfix commit <https://github.com/python-
  attrs/attrs/commit/38580632ceac1cd6e477db71e1d190a4130beed4>

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



From 2122556 at bugs.launchpad.net  Tue Oct  7 04:21:28 2025
From: 2122556 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 07 Oct 2025 04:21:28 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_=5BNEW=5D_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175981088882.3391882.13386634290291420469.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Dirk Su (dirksu):

[ Impact ]
Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

Restart pipewire can workaround the issue.
$ systemctl --user restart pipewire

[ Test Plan ]
Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

[ Where problems could occur ]
This SRU going to improve UCM handling and may affect the audio behavior.
The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

[ Other Info ]
* Apport information
 ProblemType: Bug
 ApportVersion: 2.28.1-0ubuntu3.8
 Architecture: amd64
 CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
 CasperMD5CheckResult: fail
 DistributionChannelDescriptor:
   # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
 DistroRelease: Ubuntu 24.04
 InstallationDate: Installed on 2025-09-05 (6 days ago)
 InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
 Package: pipewire 1.0.5-1ubuntu3.1
 PackageArchitecture: amd64
 ProcEnviron:
  LANG=en_US.UTF-8
  PATH=(custom, no user)
  SHELL=/bin/bash
  TERM=xterm-256color
  XDG_RUNTIME_DIR=<set>
 ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
 Tags: noble
 Uname: Linux 6.14.0-29-generic x86_64
 UpgradeStatus: No upgrade log present (probably fresh install)
 UserGroups: adm cdrom dip lxd sudo
 _MarkForUpload: True

* Related upstream patches
 - UCM updates
   - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
 - vendor suggested fix
   - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
   - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

** Affects: oem-priority
     Importance: Undecided
         Status: New

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

** Affects: pipewire (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: pipewire (Ubuntu Plucky)
     Importance: Undecided
         Status: New


** Tags: apport-collected dcr-incoming jira-cpl-206 noble oem-priority
-- 
3.5mm microphone recognized but can’t be used as audio input
https://bugs.launchpad.net/bugs/2122556
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2126737 at bugs.launchpad.net  Tue Oct  7 04:21:38 2025
From: 2126737 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 07 Oct 2025 04:21:38 -0000
Subject: [Bug 2126737] [NEW] [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175981089894.2529736.4869442412514531801.launchpad@juju-98d295-prod-launchpad-3>

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

[Impact]

This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
specifically to enable audio on a range of MediaTek Genio EVK platforms
based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

This is a crucial hardware enablement update necessary for out-of-the-
box audio functionality on these specific development and reference
boards. Without these profiles, audio playback, recording, and jack
detection are non-functional.

[Test Plan]

This update requires testing on the specific MediaTek EVK hardware for
which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
mt8395-evk).

To verify the fix:

1. On a target EVK, install the updated package.

2. Confirm that audio devices (speakers, microphone, headset) are
correctly detected in sound settings.

3. Test audio playback and recording through all available devices.

4. Verify that plugging in and unplugging a headset is correctly
detected and that audio routes appropriately.

[Where problems could occur]

Regressions are unlikely but possible on other, existing platforms if
the new configuration files cause parsing issues or introduce unexpected
conflicts. This would most likely manifest as a loss of audio
functionality (e.g., missing input/output devices) on previously working
hardware.

As a precaution, regression testing on a few non-MediaTek devices is
recommended to ensure no existing functionality is broken.

[Other Info]

This update cherry-picks a series of 9 upstream commits that add the
UCM2 profiles for the MediaTek EVK platforms.

Upstream commits:

* 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
* 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
* 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
* 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
* 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
* ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
* f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
* 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
* c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

**Affected Releases**

This bug has been filed against Noble Numbat (24.04 LTS) as the primary
target for the SRU.

Following the SRU policy, this fix also needs to be verified in the
development release. Could a bug triager please also mark this bug as
affecting **`Ubuntu (Development)`**?

** Affects: alsa-ucm-conf (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: genio mediatek noble patch sponsorship-needed
-- 
[SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK platforms
https://bugs.launchpad.net/bugs/2126737
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2126737 at bugs.launchpad.net  Tue Oct  7 04:21:39 2025
From: 2126737 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Tue, 07 Oct 2025 04:21:39 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175981089930.3392504.13777488377662900138.malone@juju-98d295-prod-launchpad-7>

The attachment "upstream-commits.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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2126737

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

  **Affected Releases**

  This bug has been filed against Noble Numbat (24.04 LTS) as the
  primary target for the SRU.

  Following the SRU policy, this fix also needs to be verified in the
  development release. Could a bug triager please also mark this bug as
  affecting **`Ubuntu (Development)`**?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2121543 at bugs.launchpad.net  Tue Oct  7 12:58:54 2025
From: 2121543 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 07 Oct 2025 12:58:54 -0000
Subject: [Bug 2121543] Re: [SRU] Poor performance of libnss-db on large db
 files
References: <175631388981.2420923.2641733358444941449.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175984193440.3677063.4286946151398907328.malone@juju-98d295-prod-launchpad-2>

Hi Ponnuvel, thank you for addressing my remarks from comment #2!

Unfortunately, Ubuntu 25.10 is in final freeze by now, so we'll need to
make this an SRU.

Could you please modify the bug description according to the
corresponding template?
https://documentation.ubuntu.com/sru/en/latest/reference/bug-template/
– we would need this anyway to get the change landed in 24.04 LTS
eventually.

Also I have one open question left:
In the patch you mention "Origin: upstream" without giving a specific reference. Was this patch discussed and/or discussed with the upstream community? Can you please point us to the original upstream changes?

I see you set "Forwarded: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1101371" – Should Debian be considered as the
upstream of libnss-db? It seems to be an orphaned package in Debian,
owned by the QA team and there has been no reaction so far on this
patch.

All of this unclarity about the upstream situation makes me a bit
hesitant to upload this patch into the Ubuntu packages. Would you be
able to point us to the upstream reference of this patch, or start a
discussion with upstream (not Debian, but the actual upstream libnss-db
project) about it, before introducing it in downstream distributions? It
seems to be a generally useful change that others might want to have,
too!

** Bug watch added: Debian Bug tracker #1101371
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101371

** Changed in: libnss-db (Ubuntu Questing)
       Status: In Progress => Incomplete

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

Title:
  [SRU] Poor performance of libnss-db on large db files

Status in libnss-db package in Ubuntu:
  Incomplete
Status in libnss-db source package in Noble:
  New
Status in libnss-db source package in Plucky:
  New
Status in libnss-db source package in Questing:
  Incomplete

Bug description:
  libdnss-db opens and closes the DB file each time. This is normally
  not an issue as the DB files are small.

  However, in a user environment, this takes considerably longer because
  the DB files have entries to the tune of 20k which severely impacts
  the performance of lookups.

  ----

  [ Impact ]

  The libnss-db library, which processes Berkeley DB files, closes
  and re-opens the DB file for each entry in the file that it currently scans.
  This results in very poor performance and noticiable botteneck on the
  application side. In a user environment that has 20k entries in the DB,
  this results in about 40 times worse performance (compared to keeping
  the file open).

  [ Test Plan ]

  The test plan sets up some DB files and queries them to see if the
  open(2) and close(2) calls are repeatedly called.

  1. update /etc/default/libnss-db
  DBS = passwd group shadow
  VAR_DB = /var/lib/misc
  ETC = ${VAR_DB}/etc
  AWK = awk
  MAKEDB = makedb --quiet
   
  2. update /etc/nsswitch.conf
  passwd:         files systemd db
  group:          files systemd db
  shadow:         files systemd db
   
  3. create required files
  mkdir -p /var/lib/misc/etc
  touch /var/lib/misc/etc/{passwd,group,shadow}
  cp /etc/login.defs /var/lib/misc/etc
   
  4. update /var/lib/misc/etc/login.defs so that UIDs are less likely to conflict
  UID_MIN                  5000
   
  5. create test users in berkelydb file
  cd /var/lib/misc
  for i in $(seq 0001 1000); do useradd -P /var/lib/misc test$i; done
  make
   
  6. verify users in berkeleydb is recognized
  id test1000
   
  7. verify that 'getent passwd' and 'getenv group' calls correctly retrieve the entr fom 
  verify that there's not as many open/close calls as there are entries in the DB files

  [ Where problems could occur ]

  To my understanding the historical reason for doing close-open for each line is to
  minimise possible resource usage and reduce the possibility of DB files getting stale
  if DB files get updated externally. Potential risks revolve around those two.

  In the former case, this could result in higher load on the system (modern hardware should be capable of handling that).
  In the latter case, lookups could fail and likely result in re-scans from the application.

  [ Other Info ]

  Debian bug and patch(not merged): https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1101371

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-db/+bug/2121543/+subscriptions



From 2114261 at bugs.launchpad.net  Tue Oct  7 13:25:11 2025
From: 2114261 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 07 Oct 2025 13:25:11 -0000
Subject: [Bug 2114261] Re: [SRU] Failed to build against linux >= 6.16
References: <174981020912.3028557.31818042851637468.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <175984351165.53199.9036634767995810237.malone@juju-98d295-prod-launchpad-7>

*** This bug is a duplicate of bug 2120508 ***
    https://bugs.launchpad.net/bugs/2120508

Closing this one as duplicate of bug #2120508 as per
https://bugs.launchpad.net/ubuntu/+source/broadcom-
sta/+bug/2120508/comments/6

** This bug has been marked a duplicate of bug 2120508
   [SRU] Kernel 6.17 support in broadcom-sta

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

Title:
  [SRU] Failed to build against linux >= 6.16

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.16-rc1.

  [ Test Plan ]

  0. Install kernels >= v6.16.
     - mainline v6.16-rcX kernels from https://kernel.ubuntu.com/mainline/ or,
     - linux-oem-6.17/noble
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.16. Nominate Noble for fixing.

  Kernels >= 6.16 will not be introduced in Plucky.

  ========== original bug report ==========

  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  src/wl/sys/wl_linux.c: In function 'wl_timer':
  src/wl/sys/wl_linux.c:2381:17: error: implicit declaration of function 'from_timer'; did you mean 'mod_timer'? [-Wimplicit-function-declaration]
   2381 |                 from_timer(t, tl, timer);
        |                 ^~~~~~~~~~
        |                 mod_timer
  src/wl/sys/wl_linux.c:2381:35: error: 'timer' undeclared (first use in this function); did you mean 'ktimerd'?
   2381 |                 from_timer(t, tl, timer);
        |                                   ^~~~~
        |                                   ktimerd
  src/wl/sys/wl_linux.c:2381:35: note: each undeclared identifier is reported only once for each function it appears in
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: src/wl/sys/wl_linux.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2114261/+subscriptions



From 2111898 at bugs.launchpad.net  Tue Oct  7 13:25:34 2025
From: 2111898 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 07 Oct 2025 13:25:34 -0000
Subject: [Bug 2111898] Re: [SRU] Failed to build against linux >= 6.15
References: <174842157474.914775.12489393328967854313.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175984353462.1845106.15527967123508836784.malone@juju-98d295-prod-launchpad-4>

*** This bug is a duplicate of bug 2120508 ***
    https://bugs.launchpad.net/bugs/2120508

Closing this one as duplicate of bug #2120508 as per
https://bugs.launchpad.net/ubuntu/+source/broadcom-
sta/+bug/2120508/comments/6

** This bug has been marked a duplicate of bug 2120508
   [SRU] Kernel 6.17 support in broadcom-sta

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

Title:
  [SRU] Failed to build against linux >= 6.15

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Won't Fix
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.15-rc1.

  [ Test Plan ]

  0. Install kernels >= v6.15
     - mainline v6.15-rcX kernels from https://kernel.ubuntu.com/mainline, or
     - linux-oem-6.17/noble
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.15. Nominate Noble.
  Kernels >= 6.15 will not be introduced in Plucky.

  ========== original bug report ==========

  1. EXTRA_*FLAGS has been deprecated for a while and is then removed in
  v6.15-rc1 commit e966ad0edd005 ("kbuild: remove EXTRA_*FLAGS
  support")， which results in following errors:

  # CC [M]  src/wl/sys/wl_linux.o
  src/shared/linux_osl.c:23:10: fatal error: typedefs.h: No such file or directory
     23 | #include <typedefs.h>
        |          ^~~~~~~~~~~~
  compilation terminated.
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/shared/linux_osl.o] Error 1

  ＃ LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  ERROR: modpost: "wlc_get" [wl.ko] undefined!
  ERROR: modpost: "wlc_module_register" [wl.ko] undefined!
  ERROR: modpost: "wf_channel2mhz" [wl.ko] undefined!
  ERROR: modpost: "wlc_isr" [wl.ko] undefined!
  ERROR: modpost: "wlc_set" [wl.ko] undefined!
  ERROR: modpost: "bcm_bprintf" [wl.ko] undefined!
  ERROR: modpost: "wlc_dpc" [wl.ko] undefined!
  ERROR: modpost: "wlc_chipmatch" [wl.ko] undefined!
  ERROR: modpost: "wlc_reset" [wl.ko] undefined!
  ERROR: modpost: "wlc_wlcif_stats_get" [wl.ko] undefined!

  2. `del_timer{,_sync}` have been redirected to `timer_delete{,_sync}`
  since v6.2-rc1 and they are now removed in v6.15-rc1 commit
  8fa7292fee5c5 ("treewide: Switch/rename to timer_delete[_sync]()"):

  # CC [M]  src/wl/sys/wl_linux.o
  src/wl/sys/wl_linux.c: In function ‘wl_del_timer’:
  src/wl/sys/wl_linux.c:2485:22: error: implicit declaration of function ‘del_timer’; did you mean ‘_wl_timer’? [-Wimplicit-function-declaration]
   2485 |                 if (!del_timer(&t->timer)) {
        |                      ^~~~~~~~~
        |                      _wl_timer
  make[4]: *** [/usr/src/linux-headers-6.15.0-9002-generic/scripts/Makefile.build:203: src/wl/sys/wl_linux.o] Error 1

  3. MODULE_DESCRIPTION is now a mandatory meta info for a module since
  v6.15-rc1 commit 6c6c1fc09de35 ("modpost: require a
  MODULE_DESCRIPTION()"):

  # LD [M]  wl.o
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
  Kernel architecture is X86_64
    MODPOST Module.symvers
  WARNING: modpost: missing MODULE_DESCRIPTION() in wl.o

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2111898/+subscriptions



From 2120508 at bugs.launchpad.net  Tue Oct  7 13:45:28 2025
From: 2120508 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 07 Oct 2025 13:45:28 -0000
Subject: [Bug 2120508] Re: [SRU] Kernel 6.17 support in broadcom-sta
References: <175504979388.1070318.10498456978486065255.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175984472821.95680.1146348688535725362.malone@juju-98d295-prod-launchpad-7>

Updated the test case for 6.8 GA and oem-6.17 from noble-proposed and
the UBSAN warning in dmesg.

Furthermore, I've re-uploaded the package and updated d/changelog to
have just a single SRU bug reference to this very bug, marking the
others as duplicates. As can be seen in
https://code.launchpad.net/~slyon/ubuntu/+source/broadcom-
sta/+git/broadcom-sta/+merge/493967

** Merge proposal linked:
   https://code.launchpad.net/~slyon/ubuntu/+source/broadcom-sta/+git/broadcom-sta/+merge/493967

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

Title:
  [SRU] Kernel 6.17 support in broadcom-sta

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Invalid
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.17-rc1.

  [ Test Plan ]

  0. Install oem-6.17 kernel from noble-proposed
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.
  5. There should not be any UBSAN warning in dmesg, e.g.:
  [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4

  Additionally, execute the same test (step 0-5) against the 6.8 kernel
  in Noble, to confirm it did not regress on the GA kernel.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.

  Kernel 6.17 will not be introduced in Plucky

  ========== original bug report ==========

  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions



From 2120508 at bugs.launchpad.net  Tue Oct  7 13:50:40 2025
From: 2120508 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 07 Oct 2025 13:50:40 -0000
Subject: [Bug 2120508] Re: [SRU] Kernel 6.17 support in broadcom-sta
References: <175504979388.1070318.10498456978486065255.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175984504108.3771506.14645226646815846890.launchpad@juju-98d295-prod-launchpad-2>

** Description changed:

  [SRU Justification]
  
  [ Impact ]
  
  Failed to build against kernel v6.17-rc1.
  
  [ Test Plan ]
  
  0. Install oem-6.17 kernel from noble-proposed
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:
  
     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
  
  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.
+ 5. There should not be any UBSAN warning in dmesg, e.g.:
+ [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
  
- Additionally, execute the same test (step 0-4) against the 6.8 kernel in
+ Additionally, execute the same test (step 0-5) against the 6.8 kernel in
  Noble, to confirm it did not regress on the GA kernel.
  
  [ Where problems could occur ]
  
  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.
  
  [ Other Info ]
  
  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.
  
  Kernel 6.17 will not be introduced in Plucky
  
  ========== original bug report ==========
  
  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

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

Title:
  [SRU] Kernel 6.17 support in broadcom-sta

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Invalid
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.17-rc1.

  [ Test Plan ]

  0. Install oem-6.17 kernel from noble-proposed
  1. Install broadcom-sta-dkms from noble -proposed pocket
  2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname
  -r)

  3. Reboot to load the kernel module
  4. The wl module should be loaded automatically and wireless lan should be usable as before.
  5. There should not be any UBSAN warning in dmesg, e.g.:
  [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4

  Additionally, execute the same test (step 0-5) against the 6.8 kernel
  in Noble, to confirm it did not regress on the GA kernel.

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.

  Kernel 6.17 will not be introduced in Plucky

  ========== original bug report ==========

  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions



From 2122556 at bugs.launchpad.net  Tue Oct  7 13:57:43 2025
From: 2122556 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 07 Oct 2025 13:57:43 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175984546398.3526186.6824694725953645616.malone@juju-98d295-prod-launchpad-3>

Both commits landed as part of the 1.3.81 upstream release. We have 1.4+
in Questing, so I'm marking devel as "Fix released"

[1] https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
[2] https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2122556 at bugs.launchpad.net  Tue Oct  7 14:06:03 2025
From: 2122556 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 07 Oct 2025 14:06:03 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175984596521.3885331.9357277519237487557.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~slyon/ubuntu/+source/pipewire/+git/pipewire/+merge/493968

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2122556 at bugs.launchpad.net  Tue Oct  7 14:10:22 2025
From: 2122556 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 07 Oct 2025 14:10:22 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175984622211.3802074.17176047211354586669.malone@juju-98d295-prod-launchpad-2>

I transformed pipewire_plucky.debdiff into (from comment #6) into an MP:
https://code.launchpad.net/~slyon/ubuntu/+source/pipewire/+git/pipewire/+merge/493968

It matches the corresponding upstream patch and the version number is
fine.

question: I'm just wondering if we need the other patch, too? As we
don't seem to have that on Plucky's 1.2 branch, yet?
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

Besides that, LGTM. Let me know if you want to have it uploaded as-is!

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2122556 at bugs.launchpad.net  Tue Oct  7 14:12:10 2025
From: 2122556 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 07 Oct 2025 14:12:10 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175984633098.137363.14928892554728605989.malone@juju-98d295-prod-launchpad-7>

For Noble: Backporting all of
https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
seems to be like a huge change, this is not usually something we want to
see in SRUs. Do we really need all of those patches in Noble, or would
you be able to isolate a minimal fix out of those?

If not, could you please provide some more explanation/stronger
rationale why we'd need to SRU all of MR#1800 and what could be the
side-effects for the SRU?

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2126596 at bugs.launchpad.net  Tue Oct  7 15:44:20 2025
From: 2126596 at bugs.launchpad.net (Simon Poirier)
Date: Tue, 07 Oct 2025 15:44:20 -0000
Subject: [Bug 2126596] Re: gvfs 1.57.2-2ubuntu5 autopkgtests failing with
 SyntaxWarning
References: <175934729636.3257950.7089237589155834792.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175985186015.2082865.14149663076525372104.malone@juju-98d295-prod-launchpad-4>

I'm with seb128 on this. It looks like a flaky test due to timing. I've
had successes with and without the patch.

the "Volume change" instead of "Volume added" in failed runs are a good
sign of this.


** Changed in: gvfs (Ubuntu)
       Status: New => In Progress

** Changed in: gvfs (Ubuntu)
     Assignee: (unassigned) => Simon Poirier (simpoir)

** Summary changed:

- gvfs 1.57.2-2ubuntu5 autopkgtests failing with SyntaxWarning
+ gvfs 1.57.2-2ubuntu5 autopkgtests failing on test_media_player

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

Title:
  gvfs 1.57.2-2ubuntu5 autopkgtests failing on test_media_player

Status in gvfs package in Ubuntu:
  In Progress

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  questing/questing/amd64/g/gvfs/20251001_144858_724dc@/log.gz

   97s test_media_player (__main__.Drive.test_media_player)
   99s drive mount: media player ... FAIL
   99s <unknown>:2: SyntaxWarning: invalid escape sequence '\s'
   99s <unknown>:1: SyntaxWarning: invalid escape sequence '\s'
   99s 
   99s ----- dbus stdout -----
   99s 
   99s ----- dbus stderr -----
   99s 
   99s

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



From 2126596 at bugs.launchpad.net  Tue Oct  7 23:41:02 2025
From: 2126596 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 07 Oct 2025 23:41:02 -0000
Subject: [Bug 2126596] Re: gvfs 1.57.2-2ubuntu5 autopkgtests failing on
 test_media_player
References: <175934729636.3257950.7089237589155834792.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175988046344.3885331.1566005547080052831.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~simpoir/ubuntu/+source/gvfs/+git/gvfs/+merge/494005

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

Title:
  gvfs 1.57.2-2ubuntu5 autopkgtests failing on test_media_player

Status in gvfs package in Ubuntu:
  In Progress

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  questing/questing/amd64/g/gvfs/20251001_144858_724dc@/log.gz

   97s test_media_player (__main__.Drive.test_media_player)
   99s drive mount: media player ... FAIL
   99s <unknown>:2: SyntaxWarning: invalid escape sequence '\s'
   99s <unknown>:1: SyntaxWarning: invalid escape sequence '\s'
   99s 
   99s ----- dbus stdout -----
   99s 
   99s ----- dbus stderr -----
   99s 
   99s

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



From 2126596 at bugs.launchpad.net  Tue Oct  7 23:43:34 2025
From: 2126596 at bugs.launchpad.net (Simon Poirier)
Date: Tue, 07 Oct 2025 23:43:34 -0000
Subject: [Bug 2126596] Re: gvfs 1.57.2-2ubuntu5 autopkgtests failing on
 test_media_player
References: <175934729636.3257950.7089237589155834792.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175988061493.331638.4564299806901382271.malone@juju-98d295-prod-launchpad-3>

Linked WIP branch addressing the amd64 failures.

Still looking at s390x and i386 tests, which are still hitting different
failures.

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

Title:
  gvfs 1.57.2-2ubuntu5 autopkgtests failing on test_media_player

Status in gvfs package in Ubuntu:
  In Progress

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  questing/questing/amd64/g/gvfs/20251001_144858_724dc@/log.gz

   97s test_media_player (__main__.Drive.test_media_player)
   99s drive mount: media player ... FAIL
   99s <unknown>:2: SyntaxWarning: invalid escape sequence '\s'
   99s <unknown>:1: SyntaxWarning: invalid escape sequence '\s'
   99s 
   99s ----- dbus stdout -----
   99s 
   99s ----- dbus stderr -----
   99s 
   99s

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



From 2122556 at bugs.launchpad.net  Wed Oct  8 01:50:37 2025
From: 2122556 at bugs.launchpad.net (Kai-Chuan Hsieh)
Date: Wed, 08 Oct 2025 01:50:37 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175988823792.2995288.8822163416140340425.malone@juju-98d295-prod-launchpad-4>

reply #9,

https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651
is required, since the mic will be muted after switch profile, and it is
in the upstream 1.0 branch, which the ubuntu noble based on.

reply #10,
The developer tries to add the UCM support for pulseaudio to pipewire once in 2023, however, it introduces a lot of side effect and regression, which impacts the 1.0 stable release, therefore, the upstream maintainer revert it. The https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800 is the final version being merged after 1.0 is branch out, and being merged into 1.2 and 1.4 branch to complete the UCM support.

To noble, the alsa-ucm-conf will keep updating for supporting the new
hardware, so that the pipewire needs to enhance its capability to handle
the latest ucm config, the philosophy is supporting the usefulness [1].

I agree that the impact is huge and the risk is high, is it possible to
leverage phased update to control the impact? We can keeps it zero until
it is passed on all machine in the certification pool.

[1]
https://documentation.ubuntu.com/sru/en/latest/explanation/principles/#maintain-
usefulness

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2120508 at bugs.launchpad.net  Wed Oct  8 02:16:20 2025
From: 2120508 at bugs.launchpad.net (You-Sheng Yang)
Date: Wed, 08 Oct 2025 02:16:20 -0000
Subject: [Bug 2120508] Re: [SRU] Kernel 6.17 support in broadcom-sta
References: <175504979388.1070318.10498456978486065255.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175988978061.698994.13159869714976126247.malone@juju-98d295-prod-launchpad-2>

Update SRU test plans to add tested kernel version info.

@slyon, @tjaalton, you're making bug tracking, patches/symptoms mapping
more difficult.

** Description changed:

  [SRU Justification]
  
  [ Impact ]
  
  Failed to build against kernel v6.17-rc1.
  
  [ Test Plan ]
  
- 0. Install oem-6.17 kernel from noble-proposed
- 1. Install broadcom-sta-dkms from noble -proposed pocket
- 2. The dkms should rebuild itself against the running kernel automatically; if not rebuild them manually with:
+ 1. Install kernels >= 6.17. For Noble, linux-oem-6.17 is available:
+    $ sudo apt-get install --no-install-recommends --yes \
+        linux-oem-6.17
+ 
+ 2. For Questing and Noble, install also stock kernel to ensure we don't break existing setup:
+    $ sudo apt-get install --no-install-recommends --yes \
+        linux-generic
+ 
+ 3. Install broadcom-sta-dkms from noble -proposed pocket. The dkms
+ should rebuild itself against the running kernel automatically; if not
+ rebuild them manually with:
  
     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
+    # With Questing
+    $ dkms status
+    broadcom-sta/6.30.223.271, 6.17.0-5-generic, x86_64: installed
+    # With Noble
+    $ dkms status
+    broadcom-sta/6.30.223.271, 6.17.0-1002-oem, x86_64: installed
+    broadcom-sta/6.30.223.271, 6.8.0-81-generic, x86_64: installed
  
- 3. Reboot to load the kernel module
- 4. The wl module should be loaded automatically and wireless lan should be usable as before.
- 5. There should not be any UBSAN warning in dmesg, e.g.:
- [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
- 
- Additionally, execute the same test (step 0-5) against the 6.8 kernel in
- Noble, to confirm it did not regress on the GA kernel.
+ 4. Reboot to load the kernel module
+ 5. The wl module should be loaded automatically and wireless lan should be usable as before.
+ 6. There should not be any UBSAN warning in dmesg, e.g.:
+    ```
+    [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
+    ```
  
  [ Where problems could occur ]
  
  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.
  
  [ Other Info ]
  
  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.
  
  Kernel 6.17 will not be introduced in Plucky
  
  ========== original bug report ==========
  
  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

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

Title:
  [SRU] Kernel 6.17 support in broadcom-sta

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Invalid
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.17-rc1.

  [ Test Plan ]

  1. Install kernels >= 6.17. For Noble, linux-oem-6.17 is available:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-oem-6.17

  2. For Questing and Noble, install also stock kernel to ensure we don't break existing setup:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-generic

  3. Install broadcom-sta-dkms from noble -proposed pocket. The dkms
  should rebuild itself against the running kernel automatically; if not
  rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
     # With Questing
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-5-generic, x86_64: installed
     # With Noble
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-1002-oem, x86_64: installed
     broadcom-sta/6.30.223.271, 6.8.0-81-generic, x86_64: installed

  4. Reboot to load the kernel module
  5. The wl module should be loaded automatically and wireless lan should be usable as before.
  6. There should not be any UBSAN warning in dmesg, e.g.:
     ```
     [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
     ```

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.

  Kernel 6.17 will not be introduced in Plucky

  ========== original bug report ==========

  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions



From 2122551 at bugs.launchpad.net  Wed Oct  8 03:35:46 2025
From: 2122551 at bugs.launchpad.net (Hemanth Nakkina)
Date: Wed, 08 Oct 2025 03:35:46 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <175989454622.672929.9606761846934752342.malone@juju-98d295-prod-launchpad-3>

Released in Questing as part of
https://code.launchpad.net/~mylesjp/ubuntu/+source/watcher/+git/watcher/+merge/493337

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

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  Fix Released
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  Fix Released

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2122556 at bugs.launchpad.net  Wed Oct  8 06:01:37 2025
From: 2122556 at bugs.launchpad.net (Charles)
Date: Wed, 08 Oct 2025 06:01:37 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175990329757.1566471.15413587359619156948.malone@juju-98d295-prod-launchpad-7>

I supported this SRU in private, but with the caveat that it will be up
to the SRU reviewer to judge the regression potential. I'm also on the
side of backporting to noble to enhance usefulness.

I'm not sure how common the affected hardware is though. It may be safer
to offer a PPA for the subset of affected devices than to roll the
changes out to everyone?

Pipewire+Wireplumber are not stable projects; it's a shame our policy is
to take point releases and then leave users with weird media bugs,
inevitably these issues will occur where we're stuck either way: leave
users in a broken state, or flog ourselves maintaining enormous
downstream backports. I don't have the experience in Ubuntu to
confidently pick an option here.

Ideally, we'd provide a rolling release of these system components to
our desktop users (perhaps in a snap), until the projects reach
something close to stability, but that is philosophical at this point,
just offering my opinion of why I initially supported the SRU.

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2122556 at bugs.launchpad.net  Wed Oct  8 07:37:56 2025
From: 2122556 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Wed, 08 Oct 2025 07:37:56 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175990907644.1072007.12929491207285875548.malone@juju-98d295-prod-launchpad-3>

re #9: Ok, could the patch for Plucky then please be updated to also
include commit d42bfa56b7c94afa113048529d430c811c8ba651 – ideally as a
merge-proposal (e.g. based upon
https://code.launchpad.net/~slyon/ubuntu/+source/pipewire/+git/pipewire/+merge/493968)?

re #10: Thanks for the explanation. I'm not part of the SRU team, so
cannot give an definitive answer here. I like the idea of adding "block-
proposed-noble" until it is verified on all machines in the
certification pool and then maybe additionally use an extended phasing
period, which is possible. But you should probably reach out to the SRU
team directly to clarify those topics.

You can reach the SRU team on Matrix (#sru:ubuntu.com) -
https://matrix.to/#/#sru:ubuntu.com

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2122556 at bugs.launchpad.net  Wed Oct  8 08:38:30 2025
From: 2122556 at bugs.launchpad.net (Dirk Su)
Date: Wed, 08 Oct 2025 08:38:30 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <175991271105.1284528.6883995952890199066.malone@juju-98d295-prod-launchpad-2>

reply #13: commit d42bfa56b7c94afa113048529d430c811c8ba651 been included
in upstream release 1.2.5. I think  plucky already include the patch.

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2114259 at bugs.launchpad.net  Wed Oct  8 09:09:35 2025
From: 2114259 at bugs.launchpad.net (You-Sheng Yang)
Date: Wed, 08 Oct 2025 09:09:35 -0000
Subject: [Bug 2114259] Re: Failed to build against linux-6.16
References: <174980980423.1737369.2832519615118497535.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175991457584.1868744.5886873706296371785.malone@juju-98d295-prod-launchpad-7>

Nominate for Noble for linux-oem-6.17/noble. Plucky doesn't have linux
kernel of v6.16+, so set INVALID.

** Also affects: v4l2loopback (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: v4l2loopback (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Changed in: v4l2loopback (Ubuntu Plucky)
       Status: New => Invalid

** Changed in: v4l2loopback (Ubuntu Noble)
       Status: New => In Progress

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

** Changed in: v4l2loopback (Ubuntu Noble)
     Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Failed to build against linux-6.16

Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in v4l2loopback source package in Noble:
  In Progress
Status in v4l2loopback source package in Plucky:
  Invalid
Status in v4l2loopback source package in Questing:
  Fix Released

Bug description:
  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  CC [M]  v4l2loopback.o
  v4l2loopback.c: In function 'v4l2_loopback_add':
  v4l2loopback.c:2910:9: error: implicit declaration of function 'setup_timer' [-Wimplicit-function-declaration]
   2910 |         setup_timer(&dev->sustain_timer, sustain_timer_clb, nr);
        |         ^~~~~~~~~~~
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: v4l2loopback.o] Error 1

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



From 2114259 at bugs.launchpad.net  Wed Oct  8 09:12:43 2025
From: 2114259 at bugs.launchpad.net (You-Sheng Yang)
Date: Wed, 08 Oct 2025 09:12:43 -0000
Subject: [Bug 2114259] Re: Failed to build against linux-6.16
References: <174980980423.1737369.2832519615118497535.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175991476364.1338920.13878611419138545105.malone@juju-98d295-prod-launchpad-2>

** Attachment added: "make.log.6.17.0-9003-oem"
   https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/2114259/+attachment/5916326/+files/make.log

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

Title:
  Failed to build against linux-6.16

Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in v4l2loopback source package in Noble:
  In Progress
Status in v4l2loopback source package in Plucky:
  Invalid
Status in v4l2loopback source package in Questing:
  Fix Released

Bug description:
  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  CC [M]  v4l2loopback.o
  v4l2loopback.c: In function 'v4l2_loopback_add':
  v4l2loopback.c:2910:9: error: implicit declaration of function 'setup_timer' [-Wimplicit-function-declaration]
   2910 |         setup_timer(&dev->sustain_timer, sustain_timer_clb, nr);
        |         ^~~~~~~~~~~
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: v4l2loopback.o] Error 1

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



From 2120508 at bugs.launchpad.net  Wed Oct  8 09:59:21 2025
From: 2120508 at bugs.launchpad.net (Timo Aaltonen)
Date: Wed, 08 Oct 2025 09:59:21 -0000
Subject: [Bug 2120508] Re: [SRU] Kernel 6.17 support in broadcom-sta
References: <175504979388.1070318.10498456978486065255.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <175991756206.1949990.17028683498982166099.malone@juju-98d295-prod-launchpad-7>

patch mapping should only matter for the devel package, where after a
rebase they should all hopefully get dropped anyway

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

Title:
  [SRU] Kernel 6.17 support in broadcom-sta

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  In Progress
Status in broadcom-sta source package in Plucky:
  Invalid
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.17-rc1.

  [ Test Plan ]

  1. Install kernels >= 6.17. For Noble, linux-oem-6.17 is available:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-oem-6.17

  2. For Questing and Noble, install also stock kernel to ensure we don't break existing setup:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-generic

  3. Install broadcom-sta-dkms from noble -proposed pocket. The dkms
  should rebuild itself against the running kernel automatically; if not
  rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
     # With Questing
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-5-generic, x86_64: installed
     # With Noble
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-1002-oem, x86_64: installed
     broadcom-sta/6.30.223.271, 6.8.0-81-generic, x86_64: installed

  4. Reboot to load the kernel module
  5. The wl module should be loaded automatically and wireless lan should be usable as before.
  6. There should not be any UBSAN warning in dmesg, e.g.:
     ```
     [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
     ```

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.

  Kernel 6.17 will not be introduced in Plucky

  ========== original bug report ==========

  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions



From 2060730 at bugs.launchpad.net  Thu Oct  9 09:39:46 2025
From: 2060730 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 09 Oct 2025 09:39:46 -0000
Subject: [Bug 2060730] [NEW] totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176000278651.3638682.6280008033110949993.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Alessandro Astone (aleasto):

[ Impact ]

While attempting to play a video on Ubuntu noble desktop for raspberry
pi, totem attempts to locate a package for the H.264 codec but cannot
find a service providing org.freedesktop.PackageKit.

The main source of the bug is that App Center does not implement
org.freedesktop.PackageKit.Modify2 on the session bus, which would
prompt the user to install the missing codecs. This is being worked on
and will be delivered as a snap update.

But a fix to PackageKit itself is also necessary in order to correctly
resolve the codec providers.

[ Test Plan ]

For the purpose of the SRU, we're only going to verify the PackageKit fix.
Verify the output of the following commands:

1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
   -> gstreamer1.0-fdkaac-*.amd64
   -> gstreamer1.0-libav-*.amd64
   -> gstreamer1.0-plugins-bad-*.amd64
   -> gstreamer1.0-plugins-good-*.amd64

2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
   -> gstreamer1.0-fdkaac-*.amd64
   -> gstreamer1.0-libav-*.amd64
   -> gstreamer1.0-plugins-bad-*.amd64
   -> gstreamer1.0-plugins-good-*.amd64
   Additionally, if you have enabled the i386 dpkg architecture on amd64:
   -> gstreamer1.0-libav-*.i386
   -> gstreamer1.0-plugins-bad-*.i386
   -> gstreamer1.0-plugins-good-*.i386

3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
   -> gstreamer1.0-libav-*.amd64
   -> gstreamer1.0-plugins-bad-*.amd64

4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
   -> gstreamer1.0-libav-*.amd64
   -> gstreamer1.0-plugins-bad-*.amd64
   Additionally, if you have enabled the i386 dpkg architecture on amd64:
   -> gstreamer1.0-libav-*.i386
   -> gstreamer1.0-plugins-bad-*.i386

[ Where problems could occur ]

The patch can only affect the behaviour of matching GStreamer capabilities.
No other packagekit features are affected.
Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

[ Other info ]

Specifically, the following is output by totem:

    ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
    ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
    ** Message: 21:13:39.414: PackageKit: xid = 0
    ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
    ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
    ** Message: 21:13:39.414: PackageKit: ignoring field named level
    ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
    ** Message: 21:13:39.414: PackageKit: ignoring field named profile
    ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
    ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
    ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
    ** Message: 21:13:39.414: PackageKit: ignoring field named level
    ** Message: 21:13:39.414: PackageKit: ignoring field named profile
    ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
    ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
    ** Message: 21:13:39.441: No installation candidate for missing plugins found.

** Affects: app-center
     Importance: Undecided
     Assignee: Alessandro Astone (aleasto)
         Status: In Progress

** Affects: packagekit (Ubuntu)
     Importance: Medium
         Status: Fix Released

** Affects: totem (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: packagekit (Ubuntu Noble)
     Importance: Medium
     Assignee: Alessandro Astone (aleasto)
         Status: In Progress

** Affects: packagekit (Ubuntu Oracular)
     Importance: Undecided
         Status: Won't Fix

** Affects: packagekit (Ubuntu Plucky)
     Importance: Low
     Assignee: Alessandro Astone (aleasto)
         Status: In Progress


** Tags: desktop-needs-sru iso-testing noble raspi verification-failed verification-failed-noble verification-failed-plucky
-- 
totem cannot install codecs via packagekit
https://bugs.launchpad.net/bugs/2060730
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127197 at bugs.launchpad.net  Thu Oct  9 16:53:22 2025
From: 2127197 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 09 Oct 2025 16:53:22 -0000
Subject: [Bug 2127197] [NEW] [needs-packaging] vulkancapsviewer
References: <176002246846.46000.64268570687693205.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176002880266.769710.4183662339793223116.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Antoine Lassagne (antoinelassagne):

URL: https://github.com/SaschaWillems/VulkanCapsViewer
License: LGPL-3
Notes: Client application to display hardware implementation details for GPUs supporting the Vulkan API by Khronos.

I wish to package vulkancapsviewer for Ubuntu.

** Affects: ubuntu
     Importance: Undecided
     Assignee: Antoine Lassagne (antoinelassagne)
         Status: New

-- 
[needs-packaging] vulkancapsviewer
https://bugs.launchpad.net/bugs/2127197
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127197 at bugs.launchpad.net  Thu Oct  9 16:56:36 2025
From: 2127197 at bugs.launchpad.net (Antoine Lassagne)
Date: Thu, 09 Oct 2025 16:56:36 -0000
Subject: [Bug 2127197] Re: [needs-packaging] vulkancapsviewer
References: <176002246846.46000.64268570687693205.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176002899701.775094.9929531213078647514.malone@juju-98d295-prod-launchpad-7>

I have the packaging somehow ready and uploaded to a PPA already:
https://launchpad.net/~antoinelassagne/+archive/ubuntu/vulkan-321

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

Title:
  [needs-packaging] vulkancapsviewer

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/SaschaWillems/VulkanCapsViewer
  License: LGPL-3
  Notes: Client application to display hardware implementation details for GPUs supporting the Vulkan API by Khronos.

  I wish to package vulkancapsviewer for Ubuntu.

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



From 2120508 at bugs.launchpad.net  Thu Oct  9 17:45:39 2025
From: 2120508 at bugs.launchpad.net (Andreas Hasenack)
Date: Thu, 09 Oct 2025 17:45:39 -0000
Subject: [Bug 2120508] Re: [SRU] Kernel 6.17 support in broadcom-sta
References: <175504979388.1070318.10498456978486065255.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176003193999.861492.11678361547482384268.malone@juju-98d295-prod-launchpad-7>

Hello satmandu, or anyone else affected,

Accepted broadcom-sta into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/broadcom-
sta/6.30.223.271-23ubuntu1.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: broadcom-sta (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  [SRU] Kernel 6.17 support in broadcom-sta

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  Fix Committed
Status in broadcom-sta source package in Plucky:
  Invalid
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.17-rc1.

  [ Test Plan ]

  1. Install kernels >= 6.17. For Noble, linux-oem-6.17 is available:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-oem-6.17

  2. For Questing and Noble, install also stock kernel to ensure we don't break existing setup:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-generic

  3. Install broadcom-sta-dkms from noble -proposed pocket. The dkms
  should rebuild itself against the running kernel automatically; if not
  rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
     # With Questing
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-5-generic, x86_64: installed
     # With Noble
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-1002-oem, x86_64: installed
     broadcom-sta/6.30.223.271, 6.8.0-81-generic, x86_64: installed

  4. Reboot to load the kernel module
  5. The wl module should be loaded automatically and wireless lan should be usable as before.
  6. There should not be any UBSAN warning in dmesg, e.g.:
     ```
     [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
     ```

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.

  Kernel 6.17 will not be introduced in Plucky

  ========== original bug report ==========

  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions



From 2120508 at bugs.launchpad.net  Thu Oct  9 18:40:24 2025
From: 2120508 at bugs.launchpad.net (satmandu)
Date: Thu, 09 Oct 2025 18:40:24 -0000
Subject: [Bug 2120508] Re: [SRU] Kernel 6.17 support in broadcom-sta
References: <175504979388.1070318.10498456978486065255.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176003522433.2739945.4427482890531260219.malone@juju-98d295-prod-launchpad-4>

Thanks all.

This is working great for me on questing.

Best,

Satadru

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

Title:
  [SRU] Kernel 6.17 support in broadcom-sta

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  Fix Committed
Status in broadcom-sta source package in Plucky:
  Invalid
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.17-rc1.

  [ Test Plan ]

  1. Install kernels >= 6.17. For Noble, linux-oem-6.17 is available:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-oem-6.17

  2. For Questing and Noble, install also stock kernel to ensure we don't break existing setup:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-generic

  3. Install broadcom-sta-dkms from noble -proposed pocket. The dkms
  should rebuild itself against the running kernel automatically; if not
  rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
     # With Questing
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-5-generic, x86_64: installed
     # With Noble
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-1002-oem, x86_64: installed
     broadcom-sta/6.30.223.271, 6.8.0-81-generic, x86_64: installed

  4. Reboot to load the kernel module
  5. The wl module should be loaded automatically and wireless lan should be usable as before.
  6. There should not be any UBSAN warning in dmesg, e.g.:
     ```
     [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
     ```

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.

  Kernel 6.17 will not be introduced in Plucky

  ========== original bug report ==========

  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions



From 2127197 at bugs.launchpad.net  Fri Oct 10 04:20:55 2025
From: 2127197 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Fri, 10 Oct 2025 04:20:55 -0000
Subject: [Bug 2127197] Re: [needs-packaging] vulkancapsviewer
References: <176002246846.46000.64268570687693205.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176007005592.1210101.5340949087575476110.launchpad@juju-98d295-prod-launchpad-3>

** Tags added: needs-packaging

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

Title:
  [needs-packaging] vulkancapsviewer

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/SaschaWillems/VulkanCapsViewer
  License: LGPL-3
  Notes: Client application to display hardware implementation details for GPUs supporting the Vulkan API by Khronos.

  I wish to package vulkancapsviewer for Ubuntu.

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



From 2127243 at bugs.launchpad.net  Fri Oct 10 08:08:23 2025
From: 2127243 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 10 Oct 2025 08:08:23 -0000
Subject: [Bug 2127243] [NEW]  [needs-packaging] spirv-reflect
References: <176008368998.1624766.844184339739748034.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176008370378.1627737.4229330505538426127.launchpad@juju-98d295-prod-launchpad-2>

You have been subscribed to a public bug by Antoine Lassagne (antoinelassagne):

URL: https://github.com/KhronosGroup/SPIRV-Reflect
License: Apache-2.0
Notes: SPIRV-Reflect is a lightweight library that provides a C/C++ reflection API for SPIR-V shader bytecode in Vulkan applications.

I wish to package spirv-reflect for Ubuntu.

** Affects: ubuntu
     Importance: Undecided
         Status: New

-- 
 [needs-packaging] spirv-reflect
https://bugs.launchpad.net/bugs/2127243
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127243 at bugs.launchpad.net  Fri Oct 10 08:10:28 2025
From: 2127243 at bugs.launchpad.net (Antoine Lassagne)
Date: Fri, 10 Oct 2025 08:10:28 -0000
Subject: [Bug 2127243] Re:  [needs-packaging] spirv-reflect
References: <176008368998.1624766.844184339739748034.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176008382841.3964652.2513951894682259201.malone@juju-98d295-prod-launchpad-4>

I have the packaging somehow ready and uploaded to a PPA already:
https://launchpad.net/~antoinelassagne/+archive/ubuntu/vulkan-321


** Tags added: needs-packaging

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

Title:
   [needs-packaging] spirv-reflect

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/KhronosGroup/SPIRV-Reflect
  License: Apache-2.0
  Notes: SPIRV-Reflect is a lightweight library that provides a C/C++ reflection API for SPIR-V shader bytecode in Vulkan applications.

  I wish to package spirv-reflect for Ubuntu.

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



From 2122556 at bugs.launchpad.net  Fri Oct 10 12:42:08 2025
From: 2122556 at bugs.launchpad.net (Kai-Chuan Hsieh)
Date: Fri, 10 Oct 2025 12:42:08 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176010012886.2090797.3202926552791172412.malone@juju-98d295-prod-launchpad-2>

@sylon

Would you please sponsor the package upload to queue, so that we can ask
SRU team to review it and get their feedback, thanks.

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  New

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2124239 at bugs.launchpad.net  Fri Oct 10 14:44:29 2025
From: 2124239 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 10 Oct 2025 14:44:29 -0000
Subject: [Bug 2124239] [NEW] [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176010747057.2301778.4859792898128663881.launchpad@juju-98d295-prod-launchpad-2>

You have been subscribed to a public bug by Ernest Lotter (ernestl):

New Snapd release 2.72 is required for Jammy, Noble, Plucky and
Questing.

Snapd 2.72 is the latest upstream release. It follows the the previous
Ubuntu release snapd 2.71.

The Snapd package deviates from the standard SRU process. The following
special SRU process was followed:
https://documentation.ubuntu.com/sru/en/latest/reference/exception-
Snapd-Updates/. We are in the process of updating to refreshed
documentation:
https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
(draft)

Release preparation: https://github.com/canonical/snapd/pull/16000
Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

Release notes:
https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

Please refer to snapd release notes documentation to understand how this
is put together:
https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

Content overview:
 - Full Disk Encryption (FDE)
 - Confdb
 - AppArmor Prompting
 - Notices
 - Many interface extensions including:
   - GPIO chardev interface as replacement for sysfs based GPIO
   - Multiple interfaces for different Nvidia driver components
 - Various LP bug fixes
 - Various packaging changes, only one minor change for Ubuntu

Areas of potential regressions:
- FDE just because it's complex, but risk is low given the level of integration tests in place

Source packages on `ppa:snappy-dev/image` for upload to -proposed:
- Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
- Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
- Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
- Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
- Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

Validation already completed:

- Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
- QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
- Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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

** Affects: snapd (Ubuntu Jammy)
     Importance: Undecided
         Status: Confirmed

** Affects: snapd (Ubuntu Noble)
     Importance: Undecided
         Status: Confirmed

** Affects: snapd (Ubuntu Plucky)
     Importance: Undecided
         Status: Confirmed

** Affects: snapd (Ubuntu Questing)
     Importance: Undecided
         Status: Confirmed

** Affects: snapd (Ubuntu Resolute)
     Importance: Undecided
         Status: Confirmed

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


From 2121675 at bugs.launchpad.net  Fri Oct 10 16:41:10 2025
From: 2121675 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 16:41:10 -0000
Subject: [Bug 2121675] Re: Add support for Intel Arrowlake codec RT711
References: <175646454585.4137041.14778958458442065073.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176011447139.639809.7154823490763195453.launchpad@juju-98d295-prod-launchpad-4>

** Also affects: firmware-sof (Ubuntu Resolute)
   Importance: Medium
     Assignee: Hector CAO (hectorcao)
       Status: In Progress

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

Title:
  Add support for Intel Arrowlake codec RT711

Status in firmware-sof package in Ubuntu:
  In Progress
Status in firmware-sof source package in Noble:
  Confirmed
Status in firmware-sof source package in Plucky:
  Confirmed
Status in firmware-sof source package in Questing:
  In Progress
Status in firmware-sof source package in Resolute:
  In Progress

Bug description:
  Ubuntu lacks audio support on Intel arrowlake platform

  Here is the boot message log on Ubuntu 24.04.3:

  
  ubuntu at ubuntu:~$ sudo dmesg | grep sof
  [    0.023486] software IO TLB: area num 16.
  [    0.253235] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [    0.253236] software IO TLB: mapped [mem 0x00000000576b2000-0x000000005b6b2000] (64MB)
  [    0.424919] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  [    0.425616] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  [    2.438071] sof-audio-pci-intel-mtl 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver
  [    2.438085] sof-audio-pci-intel-mtl 0000:00:1f.3: enabling device (0000 -> 0002)
  [    2.438215] sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
  [    2.440235] sof-audio-pci-intel-mtl 0000:00:1f.3: use msi interrupt mode
  [    2.444650] sof-audio-pci-intel-mtl 0000:00:1f.3: no hda codecs found!
  [    2.444652] sof-audio-pci-intel-mtl 0000:00:1f.3: NHLT device BT(0) detected, ssp_mask 0x4
  [    2.444653] sof-audio-pci-intel-mtl 0000:00:1f.3: BT link detected in NHLT tables: 0x4
  [    2.444654] sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 2
  [    2.447689] sof-audio-pci-intel-mtl 0000:00:1f.3: SOF firmware and/or topology file not found.
  [    2.447698] sof-audio-pci-intel-mtl 0000:00:1f.3: Supported default profiles
  [    2.447698] sof-audio-pci-intel-mtl 0000:00:1f.3: - ipc type 1 (Requested):
  [    2.447699] sof-audio-pci-intel-mtl 0000:00:1f.3:  Firmware file: intel/sof-ipc4/arl/sof-arl.ri
  [    2.447699] sof-audio-pci-intel-mtl 0000:00:1f.3:  Topology file: intel/sof-ace-tplg/sof-arl-rt711-l0-2ch.tplg
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3: Check if you have 'sof-firmware' package installed.
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3: Optionally it can be manually downloaded from:
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3:    https://github.com/thesofproject/sof-bin/
  [    2.448991] sof-audio-pci-intel-mtl 0000:00:1f.3: error: sof_probe_work failed err: -2

  
  The missing piece is the topology file: intel/sof-ace-tplg/sof-arl-rt711-l0-2ch.tplg

  The latest topology file for this platform that has been validated by
  Intel is available at:

  https://github.com/thesofproject/sof-bin/blob/main/v2.8.x/sof-ace-
  tplg-v2.8.1/sof-mtl-rt711-4ch.tplg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2121675/+subscriptions



From 2114259 at bugs.launchpad.net  Fri Oct 10 16:56:13 2025
From: 2114259 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 16:56:13 -0000
Subject: [Bug 2114259] Re: Failed to build against linux-6.16
References: <174980980423.1737369.2832519615118497535.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176011537322.2520090.6320243673839891579.malone@juju-98d295-prod-launchpad-2>

I don't see a diff or git branch linked to this bug for noble, and the
questing one was sponsored already. Unsubscribing sponsors. When there
is something new to sponsor, please resubscribe.

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

Title:
  Failed to build against linux-6.16

Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in v4l2loopback source package in Noble:
  In Progress
Status in v4l2loopback source package in Plucky:
  Invalid
Status in v4l2loopback source package in Questing:
  Fix Released

Bug description:
  1. from_timer macro renamed in v6.16-rc1 commit 41cb08555c416
  ("treewide, timers: Rename from_timer() to timer_container_of()"):

  CC [M]  v4l2loopback.o
  v4l2loopback.c: In function 'v4l2_loopback_add':
  v4l2loopback.c:2910:9: error: implicit declaration of function 'setup_timer' [-Wimplicit-function-declaration]
   2910 |         setup_timer(&dev->sustain_timer, sustain_timer_clb, nr);
        |         ^~~~~~~~~~~
  make[4]: *** [/usr/src/linux-headers-6.16.0-1-generic/scripts/Makefile.build:287: v4l2loopback.o] Error 1

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



From 2121783 at bugs.launchpad.net  Fri Oct 10 17:04:29 2025
From: 2121783 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 17:04:29 -0000
Subject: [Bug 2121783] Re: [SRU][jammy] oem-somerville-wartortle-amd-meta
References: <175669802721.4174010.1102513115673847470.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176011586960.3074682.6906101157183157382.malone@juju-98d295-prod-launchpad-7>

The SRU template needs work, it still has the boilerplate text that
needs to be replaced.

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

Title:
  [SRU][jammy] oem-somerville-wartortle-amd-meta

Status in OEM Priority Project:
  Fix Committed
Status in oem-somerville-wartortle-amd-meta package in Ubuntu:
  In Progress

Bug description:
  [ Background ]

  Why are we making this update?

  [ 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

  [ 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.

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



From 2121580 at bugs.launchpad.net  Fri Oct 10 17:03:30 2025
From: 2121580 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 17:03:30 -0000
Subject: [Bug 2121580] Re: [SRU][jammy] oem-somerville-wartortle-meta
References: <175637012322.1698499.15987368707040264496.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176011581094.2488663.2070881862808857911.malone@juju-98d295-prod-launchpad-3>

The SRU template needs work, the first two sections look like
boilerplate that needs to be replaced.

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

Title:
  [SRU][jammy] oem-somerville-wartortle-meta

Status in OEM Priority Project:
  Fix Committed
Status in oem-somerville-wartortle-meta package in Ubuntu:
  In Progress

Bug description:
  [ Background ]

  Why are we making this update?

  [ 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

  [ 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.

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



From 2121543 at bugs.launchpad.net  Fri Oct 10 17:05:55 2025
From: 2121543 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 17:05:55 -0000
Subject: [Bug 2121543] Re: [SRU] Poor performance of libnss-db on large db
 files
References: <175631388981.2420923.2641733358444941449.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176011595559.3078792.7180879746266517863.malone@juju-98d295-prod-launchpad-7>

Removing sponsors, please resubscribe when the questions from the
comment above were addressed/answered, thanks.

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

Title:
  [SRU] Poor performance of libnss-db on large db files

Status in libnss-db package in Ubuntu:
  Incomplete
Status in libnss-db source package in Noble:
  New
Status in libnss-db source package in Plucky:
  New
Status in libnss-db source package in Questing:
  Incomplete

Bug description:
  libdnss-db opens and closes the DB file each time. This is normally
  not an issue as the DB files are small.

  However, in a user environment, this takes considerably longer because
  the DB files have entries to the tune of 20k which severely impacts
  the performance of lookups.

  ----

  [ Impact ]

  The libnss-db library, which processes Berkeley DB files, closes
  and re-opens the DB file for each entry in the file that it currently scans.
  This results in very poor performance and noticiable botteneck on the
  application side. In a user environment that has 20k entries in the DB,
  this results in about 40 times worse performance (compared to keeping
  the file open).

  [ Test Plan ]

  The test plan sets up some DB files and queries them to see if the
  open(2) and close(2) calls are repeatedly called.

  1. update /etc/default/libnss-db
  DBS = passwd group shadow
  VAR_DB = /var/lib/misc
  ETC = ${VAR_DB}/etc
  AWK = awk
  MAKEDB = makedb --quiet
   
  2. update /etc/nsswitch.conf
  passwd:         files systemd db
  group:          files systemd db
  shadow:         files systemd db
   
  3. create required files
  mkdir -p /var/lib/misc/etc
  touch /var/lib/misc/etc/{passwd,group,shadow}
  cp /etc/login.defs /var/lib/misc/etc
   
  4. update /var/lib/misc/etc/login.defs so that UIDs are less likely to conflict
  UID_MIN                  5000
   
  5. create test users in berkelydb file
  cd /var/lib/misc
  for i in $(seq 0001 1000); do useradd -P /var/lib/misc test$i; done
  make
   
  6. verify users in berkeleydb is recognized
  id test1000
   
  7. verify that 'getent passwd' and 'getenv group' calls correctly retrieve the entr fom 
  verify that there's not as many open/close calls as there are entries in the DB files

  [ Where problems could occur ]

  To my understanding the historical reason for doing close-open for each line is to
  minimise possible resource usage and reduce the possibility of DB files getting stale
  if DB files get updated externally. Potential risks revolve around those two.

  In the former case, this could result in higher load on the system (modern hardware should be capable of handling that).
  In the latter case, lookups could fail and likely result in re-scans from the application.

  [ Other Info ]

  Debian bug and patch(not merged): https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1101371

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-db/+bug/2121543/+subscriptions



From 2072516 at bugs.launchpad.net  Fri Oct 10 17:45:46 2025
From: 2072516 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 17:45:46 -0000
Subject: [Bug 2072516] Re: autopkgtests fail on oracular & noble
References: <172046559753.1686510.5621038444234864772.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176011834703.2599850.10085744548139809486.malone@juju-98d295-prod-launchpad-2>

Why a new bug report...
Now we have:
- original FTBFS: LP: #2069384
- dep8 failure (this bug): LP: #2072516
- another bug about dep8 failure: LP: #2084635
- with its own pr: https://code.launchpad.net/~pushkarnk/ubuntu/+source/puppetdb/+git/puppetdb/+merge/475170

And that new bug didn't have sponsors subscribed.

Ok, heading over there now...

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

Title:
  autopkgtests fail on oracular & noble

Status in puppetdb package in Ubuntu:
  Fix Released
Status in puppetdb source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]
  * The puppetdb autopkgtests fail on noble after the FTBFS bug [1] is fixed. 

  [ Test Plan ]
  * Running autopkgtests on noble reveals the failure.

  [ Where problems could occur ]
  Currently, both tests under debian/test fail on oracular [2].

  ====

  autopkgtest [00:30:43]: @@@@@@@@@@@@@@@@@@@@ summary
  standalone FAIL stderr: warn: JDK 21.0.4-ea is neither tested nor supported. Please use JDK 17
  with-puppetserver FAIL non-zero exit status 1

  ====

  Test "standalone" fails because of Java 21 usage warning appears on stderr. Test "with-puppetserver" is an integration
  test of puppetdb and puppetserver. The latter has been updated to 8.4.1-1 on noble. Use of a custom format named PSON was
  completely abandoned in puppetserver 8. Any use of PSON in puppetdb 7 on noble needs to be removed.

  [ Other Info ]
  PuppetDB 7.X is compatible with PuppetServer 8.X [3]

  [1] https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2069384
  [2] https://paste.ubuntu.com/p/74h3nmKpXB/
  [3] https://www.puppet.com/docs/puppetdb/7/overview.html

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



From 2124239 at bugs.launchpad.net  Fri Oct 10 20:14:31 2025
From: 2124239 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 20:14:31 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176012727154.3385460.13195157595029168271.malone@juju-98d295-prod-launchpad-7>

Regarding this change:

      - Add architecture to 'snap version' output

Questing builds may have the amd64v3 architecture available. Some
packages build for it already, and it can be enabled in the ppa:

 AMD x86-64 (amd64)
 AMD64 x86-64-v3 (amd64v3) <===

Do you foresee issues with this, if snapd is built and installed on such
an arch? Perhaps enable it in your ppa as well, to check?

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 10 20:27:27 2025
From: 2124239 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 20:27:27 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176012804773.3406412.18005187453582607832.malone@juju-98d295-prod-launchpad-7>

This 2.72 version seems to be still missing the new coreutils paths
introduced in questing[1]. At least I still see references to things
like /{,usr/}bin/ls in [2]. Is deb snapd somehow not affected by this
change in questing?


1. https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2123870
2. interfaces/apparmor/template.go

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 10 20:42:22 2025
From: 2124239 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 20:42:22 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176012894208.2847382.13456795487012014452.malone@juju-98d295-prod-launchpad-3>

This bit of the diff scared me:

--- a/interfaces/builtin/microstack_support.go
+++ b/interfaces/builtin/microstack_support.go
@@ -215,6 +215,17 @@ unmount /run/netns/ovnmeta-*,

 # Required by libvirtd to detect and utilise AMD SEV capabilities for AMD CPU's
 /dev/sev rw,
+
+# Required by OVS to initialize DPDK
+# https://doc.dpdk.org/guides/linux_gsg/enable_func.html
+@{PROC}/@{pids}/pagemap r,
+capability ipc_lock,
+# Allow anonymous files backed by huge pages.
+# https://gitlab.com/apparmor/apparmor/-/issues/545
+# Note that this rule doesn't allow top level files and directories to be removed.
+# At the same time, subpaths are expected to be on squashfs unless modified
+# through layouts.
+owner / rw,
 `

 const microStackSupportConnectedPlugSecComp = `


Even though the comment tries to explain that this rule "does not allow top level files and directories to be removed". Why is that? In which context is this rule used that makes it "safe"?

** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #545
   https://gitlab.com/apparmor/apparmor/-/issues/545

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 10 21:06:51 2025
From: 2124239 at bugs.launchpad.net (Andreas Hasenack)
Date: Fri, 10 Oct 2025 21:06:51 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176013041186.2889503.4733096618510005876.malone@juju-98d295-prod-launchpad-3>

I saw that one of the failed tests involved "sudo -E", and that is not
supported by sudo-rs in questing. What exactly are the implications of
that for snap 2.72 on questing? Is "sudo -E" only used in some tests,
which we would be skipping, or is it used "for real" by some snap
component, at runtime?

A quick grep found "sudo -E" being used in cmd/snap/cmd_run.go by what
looks like a helper to debug something.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2127243 at bugs.launchpad.net  Fri Oct 10 23:55:05 2025
From: 2127243 at bugs.launchpad.net (Brian Murray)
Date: Fri, 10 Oct 2025 23:55:05 -0000
Subject: [Bug 2127243] Re:  [needs-packaging] spirv-reflect
References: <176008368998.1624766.844184339739748034.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176014050570.3131532.12967133933426120552.malone@juju-98d295-prod-launchpad-3>

*** 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.

** Changed in: ubuntu
   Importance: Undecided => Wishlist

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

Title:
   [needs-packaging] spirv-reflect

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/KhronosGroup/SPIRV-Reflect
  License: Apache-2.0
  Notes: SPIRV-Reflect is a lightweight library that provides a C/C++ reflection API for SPIR-V shader bytecode in Vulkan applications.

  I wish to package spirv-reflect for Ubuntu.

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



From 2127197 at bugs.launchpad.net  Fri Oct 10 23:55:08 2025
From: 2127197 at bugs.launchpad.net (Brian Murray)
Date: Fri, 10 Oct 2025 23:55:08 -0000
Subject: [Bug 2127197] Re: [needs-packaging] vulkancapsviewer
References: <176002246846.46000.64268570687693205.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176014050809.1300856.4869445074044484702.malone@juju-98d295-prod-launchpad-4>

*** 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.

** Changed in: ubuntu
   Importance: Undecided => Wishlist

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

Title:
  [needs-packaging] vulkancapsviewer

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/SaschaWillems/VulkanCapsViewer
  License: LGPL-3
  Notes: Client application to display hardware implementation details for GPUs supporting the Vulkan API by Khronos.

  I wish to package vulkancapsviewer for Ubuntu.

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



From 2127480 at bugs.launchpad.net  Sat Oct 11 04:22:05 2025
From: 2127480 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 11 Oct 2025 04:22:05 -0000
Subject: [Bug 2127480] [NEW] lshw incorrectly detects frame buffer devices
References: <176010375520.2147597.4447164906795993813.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176015652579.1675620.12167922412940835419.launchpad@juju-98d295-prod-launchpad-4>

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

[ Impact ]

 * Executing lshw can provide incorrect output for devices if frame
buffer (fb) devices are present in the system.

 * Issue happens when lshw parses fb devices, internally it tries to look for a PCI device which matches a set of requirements (it's looking for iommu address ranges for device based on data from FB device IOCTL). If a device is matched it will append it's metadata to it and later print it.
Problem is in logic used to detect fb devices metadata. As a result the first device on the list with iommu resource can be correlated with fb device.

 * In following example, fb metadata has been added to network adapter.
        *-network:0
             description: Ethernet interface
             product: Ethernet Controller XXV710 for 25GbE SFP28
             vendor: Intel Corporation
             physical id: 0
             bus info: pci at 0000:5e:00.0
             logical name: enp94s0f0
             logical name: /dev/fb0
             version: 02
             serial: 50:7c:6f:45:ca:23
             capacity: 25Gbit/s
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi msix pciexpress vpd bus_master cap_list rom ethernet physical fibre 25000bt-fd autonegotiation fb
             configuration: autonegotiation=off broadcast=yes depth=32 driver=i40e driverversion=5.15.0-107-generic duplex=full firmware=9.50 0x8000f251 23.0.8 latency=0 link=yes mode=1024x768 multicast=yes slave=yes visual=truecolor xres=1024 yres=768
             resources: iomemory:38c00-38bff iomemory:38c00-38bff irq:36 memory:38c000000000-38c000ffffff memory:38c002800000-38c002807fff memory:b8800000-b887ffff memory:38c002000000-38c0023fffff memory:38c002810000-38c00290ffff

 * More discussion on the issue in [0]

[ Test Plan ]

 * FB (/dev/fb0) device is required to reproduce the issue, then run
"lshw" and check output of all devices.

In my local local laptop fb data is added to 3D controller device:
           *-display
                description: 3D controller
                product: NVIDIA Corporation
                vendor: NVIDIA Corporation
                physical id: 0
                bus info: pci at 0000:01:00.0
                logical name: /dev/fb0
                version: a1
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list rom fb
                configuration: depth=32 driver=nvidia latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
                resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
        *-display
             description: VGA compatible controller
             product: Intel Corporation
             vendor: Intel Corporation
             physical id: 2
             bus info: pci at 0000:00:02.0
             logical name: /dev/fb0
             version: 04
             width: 64 bits
             clock: 33MHz
             capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
             configuration: depth=32 driver=i915 latency=0 resolution=1920,1200

With fix:
           *-display
                description: 3D controller
                product: NVIDIA Corporation
                vendor: NVIDIA Corporation
                physical id: 0
                bus info: pci at 0000:01:00.0
                version: a1
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list rom
                configuration: driver=nvidia latency=0
                resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
        *-display
             description: VGA compatible controller
             product: Intel Corporation
             vendor: Intel Corporation
             physical id: 2
             bus info: pci at 0000:00:02.0
             logical name: /dev/fb0
             version: 04
             width: 64 bits
             clock: 33MHz
             capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
             configuration: depth=32 driver=i915 latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
             resources: iomemory:620-61f iomemory:400-3ff irq:181 memory:6288000000-6288ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff


[ Where problems could occur ]

 * Fix is written in a way that if new way of detecting fb metadata does
not work it will fall back to previous method.

 * Worst case scenario is that fb data will not be printed

[ Other Info ]

 * To workaround the problem disable fb detection by adding -disable fb

 * Upstream patches [1]

[0] - https://github.com/lyonel/lshw/pull/106
[1] - https://ezix.org/src/pkg/lshw/commits/branch/master af7c69e1b6 8798c9f1a2

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

** Affects: lshw (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: lshw (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: lshw (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: lshw (Ubuntu Plucky)
     Importance: Undecided
         Status: New

** Affects: lshw (Ubuntu Questing)
     Importance: Undecided
         Status: New


** Tags: patch
-- 
lshw incorrectly detects frame buffer devices
https://bugs.launchpad.net/bugs/2127480
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127480 at bugs.launchpad.net  Sat Oct 11 04:22:06 2025
From: 2127480 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Sat, 11 Oct 2025 04:22:06 -0000
Subject: [Bug 2127480] Re: lshw incorrectly detects frame buffer devices
References: <176010375520.2147597.4447164906795993813.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176015652617.4084410.2799038851434342671.malone@juju-98d295-prod-launchpad-7>

The attachment "focal 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2127480

Title:
  lshw incorrectly detects frame buffer devices

Status in lshw package in Ubuntu:
  New
Status in lshw source package in Focal:
  New
Status in lshw source package in Jammy:
  New
Status in lshw source package in Noble:
  New
Status in lshw source package in Plucky:
  New
Status in lshw source package in Questing:
  New

Bug description:
  [ Impact ]

   * Executing lshw can provide incorrect output for devices if frame
  buffer (fb) devices are present in the system.

   * Issue happens when lshw parses fb devices, internally it tries to look for a PCI device which matches a set of requirements (it's looking for iommu address ranges for device based on data from FB device IOCTL). If a device is matched it will append it's metadata to it and later print it.
  Problem is in logic used to detect fb devices metadata. As a result the first device on the list with iommu resource can be correlated with fb device.

   * In following example, fb metadata has been added to network adapter.
          *-network:0
               description: Ethernet interface
               product: Ethernet Controller XXV710 for 25GbE SFP28
               vendor: Intel Corporation
               physical id: 0
               bus info: pci at 0000:5e:00.0
               logical name: enp94s0f0
               logical name: /dev/fb0
               version: 02
               serial: 50:7c:6f:45:ca:23
               capacity: 25Gbit/s
               width: 64 bits
               clock: 33MHz
               capabilities: pm msi msix pciexpress vpd bus_master cap_list rom ethernet physical fibre 25000bt-fd autonegotiation fb
               configuration: autonegotiation=off broadcast=yes depth=32 driver=i40e driverversion=5.15.0-107-generic duplex=full firmware=9.50 0x8000f251 23.0.8 latency=0 link=yes mode=1024x768 multicast=yes slave=yes visual=truecolor xres=1024 yres=768
               resources: iomemory:38c00-38bff iomemory:38c00-38bff irq:36 memory:38c000000000-38c000ffffff memory:38c002800000-38c002807fff memory:b8800000-b887ffff memory:38c002000000-38c0023fffff memory:38c002810000-38c00290ffff

   * More discussion on the issue in [0]

  [ Test Plan ]

   * FB (/dev/fb0) device is required to reproduce the issue, then run
  "lshw" and check output of all devices.

  In my local local laptop fb data is added to 3D controller device:
             *-display
                  description: 3D controller
                  product: NVIDIA Corporation
                  vendor: NVIDIA Corporation
                  physical id: 0
                  bus info: pci at 0000:01:00.0
                  logical name: /dev/fb0
                  version: a1
                  width: 64 bits
                  clock: 33MHz
                  capabilities: pm msi pciexpress bus_master cap_list rom fb
                  configuration: depth=32 driver=nvidia latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
                  resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
          *-display
               description: VGA compatible controller
               product: Intel Corporation
               vendor: Intel Corporation
               physical id: 2
               bus info: pci at 0000:00:02.0
               logical name: /dev/fb0
               version: 04
               width: 64 bits
               clock: 33MHz
               capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
               configuration: depth=32 driver=i915 latency=0 resolution=1920,1200

  With fix:
             *-display
                  description: 3D controller
                  product: NVIDIA Corporation
                  vendor: NVIDIA Corporation
                  physical id: 0
                  bus info: pci at 0000:01:00.0
                  version: a1
                  width: 64 bits
                  clock: 33MHz
                  capabilities: pm msi pciexpress bus_master cap_list rom
                  configuration: driver=nvidia latency=0
                  resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
          *-display
               description: VGA compatible controller
               product: Intel Corporation
               vendor: Intel Corporation
               physical id: 2
               bus info: pci at 0000:00:02.0
               logical name: /dev/fb0
               version: 04
               width: 64 bits
               clock: 33MHz
               capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
               configuration: depth=32 driver=i915 latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
               resources: iomemory:620-61f iomemory:400-3ff irq:181 memory:6288000000-6288ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff

  
  [ Where problems could occur ]

   * Fix is written in a way that if new way of detecting fb metadata
  does not work it will fall back to previous method.

   * Worst case scenario is that fb data will not be printed

  [ Other Info ]

   * To workaround the problem disable fb detection by adding -disable
  fb

   * Upstream patches [1]

  [0] - https://github.com/lyonel/lshw/pull/106
  [1] - https://ezix.org/src/pkg/lshw/commits/branch/master af7c69e1b6 8798c9f1a2

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



From 2121675 at bugs.launchpad.net  Sat Oct 11 19:36:37 2025
From: 2121675 at bugs.launchpad.net (Michael Morrison)
Date: Sat, 11 Oct 2025 19:36:37 -0000
Subject: [Bug 2121675] Re: Add support for Intel Arrowlake codec RT711
References: <175646454585.4137041.14778958458442065073.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176021139735.550551.13006596901544075973.malone@juju-98d295-prod-launchpad-2>

Here is dmesg output as you asked for:

> sudo dmesg | grep sof
[    0.045264] software IO TLB: area num 16.
[    0.410108] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.410109] software IO TLB: mapped [mem 0x00000000452b9000-0x00000000492b9000] (64MB)
[    2.476204] sof-audio-pci-intel-mtl 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver
[    2.476218] sof-audio-pci-intel-mtl 0000:00:1f.3: enabling device (0000 -> 0002)
[    2.476355] sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[    2.478589] sof-audio-pci-intel-mtl 0000:00:1f.3: use msi interrupt mode
[    2.483616] sof-audio-pci-intel-mtl 0000:00:1f.3: no hda codecs found!
[    2.483618] sof-audio-pci-intel-mtl 0000:00:1f.3: NHLT device BT(0) detected, ssp_mask 0x4
[    2.483620] sof-audio-pci-intel-mtl 0000:00:1f.3: BT link detected in NHLT tables: 0x4
[    2.483622] sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 2
[    2.486969] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware paths/files for ipc type 1:
[    2.486971] sof-audio-pci-intel-mtl 0000:00:1f.3:  Firmware file:     intel/sof-ipc4/arl/sof-arl.ri
[    2.486972] sof-audio-pci-intel-mtl 0000:00:1f.3:  Firmware lib path: intel/sof-ipc4-lib/arl
[    2.486973] sof-audio-pci-intel-mtl 0000:00:1f.3:  Topology file:     intel/sof-ace-tplg/sof-arl-rt711-l0-2ch.tplg
[    2.488739] sof-audio-pci-intel-mtl 0000:00:1f.3: Loaded firmware library: ADSPFW, version: 2.12.0.1
[    2.629919] sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.12.0.1
[    2.638429] sof_sdw sof_sdw: Overriding quirk 0x2 => 0x1
[    2.638669] sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:0 Kernel ABI 3:23:1
[    2.638856] sof_sdw sof_sdw: ASoC: Parent card not yet available, widget card binding deferred
[    2.642244] input: sof-soundwire Headset Jack as /devices/pci0000:00/0000:00:1f.3/sof_sdw/sound/card0/input18

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

Title:
  Add support for Intel Arrowlake codec RT711

Status in firmware-sof package in Ubuntu:
  In Progress
Status in firmware-sof source package in Noble:
  Confirmed
Status in firmware-sof source package in Plucky:
  Confirmed
Status in firmware-sof source package in Questing:
  In Progress
Status in firmware-sof source package in Resolute:
  In Progress

Bug description:
  Ubuntu lacks audio support on Intel arrowlake platform

  Here is the boot message log on Ubuntu 24.04.3:

  
  ubuntu at ubuntu:~$ sudo dmesg | grep sof
  [    0.023486] software IO TLB: area num 16.
  [    0.253235] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [    0.253236] software IO TLB: mapped [mem 0x00000000576b2000-0x000000005b6b2000] (64MB)
  [    0.424919] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  [    0.425616] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  [    2.438071] sof-audio-pci-intel-mtl 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver
  [    2.438085] sof-audio-pci-intel-mtl 0000:00:1f.3: enabling device (0000 -> 0002)
  [    2.438215] sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
  [    2.440235] sof-audio-pci-intel-mtl 0000:00:1f.3: use msi interrupt mode
  [    2.444650] sof-audio-pci-intel-mtl 0000:00:1f.3: no hda codecs found!
  [    2.444652] sof-audio-pci-intel-mtl 0000:00:1f.3: NHLT device BT(0) detected, ssp_mask 0x4
  [    2.444653] sof-audio-pci-intel-mtl 0000:00:1f.3: BT link detected in NHLT tables: 0x4
  [    2.444654] sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 2
  [    2.447689] sof-audio-pci-intel-mtl 0000:00:1f.3: SOF firmware and/or topology file not found.
  [    2.447698] sof-audio-pci-intel-mtl 0000:00:1f.3: Supported default profiles
  [    2.447698] sof-audio-pci-intel-mtl 0000:00:1f.3: - ipc type 1 (Requested):
  [    2.447699] sof-audio-pci-intel-mtl 0000:00:1f.3:  Firmware file: intel/sof-ipc4/arl/sof-arl.ri
  [    2.447699] sof-audio-pci-intel-mtl 0000:00:1f.3:  Topology file: intel/sof-ace-tplg/sof-arl-rt711-l0-2ch.tplg
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3: Check if you have 'sof-firmware' package installed.
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3: Optionally it can be manually downloaded from:
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3:    https://github.com/thesofproject/sof-bin/
  [    2.448991] sof-audio-pci-intel-mtl 0000:00:1f.3: error: sof_probe_work failed err: -2

  
  The missing piece is the topology file: intel/sof-ace-tplg/sof-arl-rt711-l0-2ch.tplg

  The latest topology file for this platform that has been validated by
  Intel is available at:

  https://github.com/thesofproject/sof-bin/blob/main/v2.8.x/sof-ace-
  tplg-v2.8.1/sof-mtl-rt711-4ch.tplg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2121675/+subscriptions



From 2121842 at bugs.launchpad.net  Mon Oct 13 02:15:42 2025
From: 2121842 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 13 Oct 2025 02:15:42 -0000
Subject: [Bug 2121842] [NEW] [SRU] [FFE] add Intel mbim service to send AT
 command on Dell DW5933e
References: <175678485878.2154842.16197342457815429794.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176032174277.1068827.2735979361959062261.launchpad@juju-98d295-prod-launchpad-4>

You have been subscribed to a public bug by Dirk Su (dirksu):

[ User impact ]

 * Currently we are not able use AT command to communicate with WWAN
module DW5933e. This SRU will add a service to make mbimcli able to send
AT command to the WWAN module.

[ Test Plan ]

 * On the platform with Dell WWAN module DW5933e:
 * Open terminal Ctrl + Alt + t
 * Use command "sudo mbimcli -d /dev/wwan0mbim0 -p --intel-at-tunnel-set-at-command=at+productinfo=1"
 * it will get output:

   SW VERSION: RMM-G1.99.00.075_0075

   OK

[ Where problems could occur ]

 * It adds new mbim service for supporting DW5933e module, there is no
existing service modification.

[ Other Info ]

 * upstream patch from https://gitlab.freedesktop.org/mobile-
broadband/libmbim/-/merge_requests/235

** Affects: oem-priority
     Importance: High
     Assignee: Dirk Su (dirksu)
         Status: Confirmed

** Affects: libmbim (Ubuntu)
     Importance: Wishlist
         Status: Fix Released

** Affects: libmbim (Ubuntu Noble)
     Importance: Wishlist
         Status: New

** Affects: libmbim (Ubuntu Plucky)
     Importance: Wishlist
         Status: New


** Tags: jira-somerville-3098 oem-priority
-- 
[SRU] [FFE] add Intel mbim service to send AT command on Dell DW5933e
https://bugs.launchpad.net/bugs/2121842
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127245 at bugs.launchpad.net  Mon Oct 13 13:17:09 2025
From: 2127245 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 13 Oct 2025 13:17:09 -0000
Subject: [Bug 2127245] [NEW]  [needs-packaging] directxshadercompiler
References: <176008395390.2184435.48421595919338201.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176036143012.4056917.18276846366760072933.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Antoine Lassagne (antoinelassagne):

URL: github.com/microsoft/DirectXShaderCompiler
License: University of Illinois/NCSA Open Source License
Notes: The DirectX Shader Compiler project includes a compiler and related tools used to compile High-Level Shader Language (HLSL) programs into DirectX Intermediate Language (DXIL) representation. Applications that make use of DirectX for graphics, games, and computation can use it to generate shader programs.

I wish to package directxshadercompiler for Ubuntu.

** Affects: ubuntu
     Importance: Wishlist
         Status: New


** Tags: needs-packaging
-- 
 [needs-packaging] directxshadercompiler
https://bugs.launchpad.net/bugs/2127245
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2117396 at bugs.launchpad.net  Mon Oct 13 13:27:35 2025
From: 2117396 at bugs.launchpad.net (Dave Jones)
Date: Mon, 13 Oct 2025 13:27:35 -0000
Subject: [Bug 2117396] Re: Accessibility issues with password entries
References: <175310172787.434349.2122261130858560208.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176036205549.303093.228195252796270637.malone@juju-98d295-prod-launchpad-7>

Is there a debdiff or Launchpad git branch that adds these changes to
the package in question (i.e. under debian/patches given the package is
in quilt format)? Unsubscribing ubuntu-sponsors for now -- please re-add
when there is something we can directly sponsor.

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

Title:
  Accessibility issues with password entries

Status in libnma package in Ubuntu:
  New
Status in libnma source package in Noble:
  New
Status in libnma source package in Plucky:
  New
Status in libnma source package in Questing:
  New

Bug description:
  Libnma has, at least, two accessibility problems:

  * when an invalid password is typed, the text entry change its color
  to red, but nothing else. This is an invalid behavior because it
  relies exclusively in color to notify an error.

  * the password storage options are accessed through the secondary icon
  in the password entry, but those icons aren't accessible, because
  neither can be accessed using only keyboard navigation, nor have a11y
  labels/descriptions.

  [ Impact ]

  Users that rely on keyboard navigation and/or screen readers won't be
  able to change the password storage options.

  Also, color-blind users won't be able to notice that a password is
  invalid.

  There are two patches that fix these problems:

  https://gitlab.gnome.org/GNOME/libnma/-/merge_requests/70
  https://gitlab.gnome.org/GNOME/libnma/-/merge_requests/71

  Even more: applying the second patch, which fixes the accessibility
  for the password storage options, allows to move the error icon in the
  first patch to the secondary place, which gives a better appearance.

  [ Test plan ]

  * Open gnome-control-center
  * Go to the Wireless tab (or Network tab if the computer lacks wireless interface)
  * Open the properties of any of the interfaces
  * Go to the `Security` tab
  * For each of the possible security options (from the first expandable menu), and using the TAB key, ensure (with the patch) that it's possible to access all the buttons for setting the password storage.
  * Ensure that, when the password is invalid (for example, because it's empty) the entry not only is red, but also shows the `error` icon.

  [ Where problems could occur ]

  The first patch is quite simple, so the only problems that could be
  expected to happen are related to the accessibility; for example, an
  incorrect icon when there is an error, or an incorrect description in
  that case.

  The second patch, instead, is quite extensive and touches several
  parts, specifically the interface. Several problems could occur if it
  hasn't been correctly done:

  * the interface can be left in an inconsistent state (for example, the button to change the password storage could be set to insensitive and, thus, don't allow to change again to sensitive, due to being linked to the sensitivity of the text entry)
  * the interface files have been modified to include an extra button. Although care has been taken to ensure that the appearance is consistent, the buttons are inside a grid, so it could be that, due to a mistake, the rest of the interface wasn't expanded accordingly, and the button appear "outside the margins"
  * since the interface files (.ui) in the current packages' code is different for Gtk3 and Gtk4 (in upstream this is fixed, and both sets have been unified), and gnome-control-center only uses Gtk4, it is possible that the backport made from the upstream patch contain errors in the Gtk3 interface files, which only could be detected with a Gtk3 program that uses this library. Unfortunately, at the moment no such program is known (with the exception of even older versions of gnome-control-center).
  * there are more differences between upstream and the versions in Noble/Plucky/Questing. Specifically, nma-cert-chooser.ui doesn't exist, and everything is created with code in nma-cert-chooser.c, which results in some extra changes to accommodate what in upstream goes into the .ui file, into the .c code. This is an important point to review and where errors could be made, resulting in errors in the TLS page.

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



From 2127792 at bugs.launchpad.net  Mon Oct 13 14:44:03 2025
From: 2127792 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 13 Oct 2025 14:44:03 -0000
Subject: [Bug 2127792] [NEW] Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176036664343.4050082.15245218622094548644.launchpad@juju-98d295-prod-launchpad-2>

You have been subscribed to a public bug by Antoine Lassagne (antoinelassagne):

There is image distorsion in gnome-remote-desktop when a Blackwell GPU
is in use and NVENC is responsible for the video streaming.

Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
desktop/-/issues/263

A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

---------------------------
SRU Justification:

[ Impact ]

 * This is a hardware enablement SRU.

 * gnome-remote-desktop, when used alongside NVENC for video streaming,
simply does not work, because the image is broken.

 * With the above, the streaming is fixed.

[ Fix ]

 * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
Though the code worked for past, it causes interlaced line artifacts on
Blackwell GPUs.

* Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
`grd-cuda-avc-utils` to produce progressive frames works on
Blackwell and on older GPU generations.

[ Test Plan ]

 * Test gnome-remote-desktop with and without the fix. Make sure which
backend is in use. This can be checked by running `nvidia-smi dmon` and
observing an encoder activity >0%. The repro only occurs when the NVENC
path is used. CPU encoding path or non-H264 streaming is unaffected

* Run the same test on an older GPU generation (Maxwell, ideally)


[ Where problems could occur ]

 * Given the nature of the fix, it should not impact non-nvidia machines.
 * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

** Affects: gnome-remote-desktop (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: gnome-remote-desktop (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: gnome-remote-desktop (Ubuntu Questing)
     Importance: Undecided
         Status: New

** Affects: gnome-remote-desktop (Ubuntu Resolute)
     Importance: Undecided
         Status: New

-- 
Images are corrupted on blackwell GPUs
https://bugs.launchpad.net/bugs/2127792
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2122551 at bugs.launchpad.net  Tue Oct 14 02:24:27 2025
From: 2122551 at bugs.launchpad.net (Quang Ngo)
Date: Tue, 14 Oct 2025 02:24:27 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176040866786.1440084.15931637542196262850.malone@juju-98d295-prod-launchpad-7>

** Patch removed: "lp2122551_plucky.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5914485/+files/lp2122551_plucky.patch

** Patch removed: "lp2122551_uca_epoxy.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5914487/+files/lp2122551_uca_epoxy.patch

** Patch removed: "lp2122551_noble.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5914486/+files/lp2122551_noble.patch

** Patch added: "lp2122551_plucky.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5917633/+files/lp2122551_plucky.patch

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  Fix Released
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  Fix Released

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2122551 at bugs.launchpad.net  Tue Oct 14 02:24:47 2025
From: 2122551 at bugs.launchpad.net (Quang Ngo)
Date: Tue, 14 Oct 2025 02:24:47 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176040868797.1440122.1094020443791477613.malone@juju-98d295-prod-launchpad-7>

** Patch added: "lp2122551_noble.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5917634/+files/lp2122551_noble.patch

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  Fix Released
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  Fix Released

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2122551 at bugs.launchpad.net  Tue Oct 14 02:25:28 2025
From: 2122551 at bugs.launchpad.net (Quang Ngo)
Date: Tue, 14 Oct 2025 02:25:28 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176040872872.1023160.4243543100595366516.malone@juju-98d295-prod-launchpad-3>

** Patch added: "lp2122551_uca_epoxy.patch"
   https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2122551/+attachment/5917635/+files/lp2122551_uca_epoxy.patch

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  Fix Released
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  Fix Released

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2127828 at bugs.launchpad.net  Tue Oct 14 06:36:46 2025
From: 2127828 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 14 Oct 2025 06:36:46 -0000
Subject: [Bug 2127828] [NEW] Sync libchewing 0.10.3-1 (main) from Debian
 unstable (main)
References: <176042377781.1824167.10764101011463192573.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176042380722.1406292.15944910496671263967.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Shih-Yuan Lee (fourdollars):

Please sync libchewing 0.10.3-1 (main) from Debian unstable (main)

Changelog entries since current resolute version 0.10.1-1:

libchewing (0.10.3-1) unstable; urgency=medium

  * New upstream version 0.10.3

 -- ChangZhuo Chen (陳昌倬) <czchen at debian.org>  Sun, 24 Aug 2025 20:14:33
+0800

libchewing (0.10.2-1) unstable; urgency=medium

  * New upstream version 0.10.2

 -- ChangZhuo Chen (陳昌倬) <czchen at debian.org>  Thu, 14 Aug 2025 21:12:31
+0800

** Affects: libchewing (Ubuntu)
     Importance: Wishlist
         Status: New

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


From 2124969 at bugs.launchpad.net  Tue Oct 14 07:30:17 2025
From: 2124969 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 14 Oct 2025 07:30:17 -0000
Subject: [Bug 2124969] Re: lintian ftbfs in questing archive rebuild
References: <175812435085.3365866.6903273481855528851.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176042702036.2236593.2926531184633132146.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~hyask/ubuntu/+source/lintian/+git/lintian/+merge/494273

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

Title:
  lintian ftbfs in questing archive rebuild

Status in lintian package in Ubuntu:
  In Progress

Bug description:
  The package fails to build in the recent archive rebuild
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250910-questing-questing.html

  Test Summary Report
  -------------------
  debian/test-out/eval/checks/binaries/architecture/binaries-misplaced/generic.t                                                      (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
    Failed test:  1
    Non-zero exit status: 1
  debian/test-out/eval/checks/binaries/location/binaries-misplaced/generic.t                                                          (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
    Failed test:  1
    Non-zero exit status: 1
  Files=1503, Tests=64208, 1934 wallclock secs ( 8.69 usr  7.17 sys + 5745.63 cusr 1724.78 csys = 7486.27 CPU)
  Result: FAIL

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



From 2127792 at bugs.launchpad.net  Tue Oct 14 07:48:59 2025
From: 2127792 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 14 Oct 2025 07:48:59 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176042814165.2236593.10782322282577723049.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~antoinelassagne/ubuntu/+source/gnome-remote-desktop/+git/gnome-remote-desktop/+merge/494352

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  New
Status in gnome-remote-desktop source package in Noble:
  New
Status in gnome-remote-desktop source package in Questing:
  New
Status in gnome-remote-desktop source package in Resolute:
  New

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Tue Oct 14 07:59:08 2025
From: 2127792 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 14 Oct 2025 07:59:08 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176042874938.2236593.3361217137767500565.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~antoinelassagne/ubuntu/+source/gnome-remote-desktop/+git/gnome-remote-desktop/+merge/494354

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  New
Status in gnome-remote-desktop source package in Noble:
  New
Status in gnome-remote-desktop source package in Questing:
  New
Status in gnome-remote-desktop source package in Resolute:
  New

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2124969 at bugs.launchpad.net  Tue Oct 14 09:58:46 2025
From: 2124969 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 14 Oct 2025 09:58:46 -0000
Subject: [Bug 2124969] Re: lintian ftbfs in questing archive rebuild
References: <175812435085.3365866.6903273481855528851.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176043592780.2236593.12396134671139452646.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~hyask/ubuntu/+source/lintian/+git/lintian/+merge/494368

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

Title:
  lintian ftbfs in questing archive rebuild

Status in lintian package in Ubuntu:
  In Progress

Bug description:
  The package fails to build in the recent archive rebuild
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250910-questing-questing.html

  Test Summary Report
  -------------------
  debian/test-out/eval/checks/binaries/architecture/binaries-misplaced/generic.t                                                      (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
    Failed test:  1
    Non-zero exit status: 1
  debian/test-out/eval/checks/binaries/location/binaries-misplaced/generic.t                                                          (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
    Failed test:  1
    Non-zero exit status: 1
  Files=1503, Tests=64208, 1934 wallclock secs ( 8.69 usr  7.17 sys + 5745.63 cusr 1724.78 csys = 7486.27 CPU)
  Result: FAIL

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



From 2121812 at bugs.launchpad.net  Tue Oct 14 11:04:57 2025
From: 2121812 at bugs.launchpad.net (Julian Andres Klode)
Date: Tue, 14 Oct 2025 11:04:57 -0000
Subject: [Bug 2121812] Re: [SRU] cinder-netapp driver fails to start when a
 node is down
References: <175673748370.1030211.13188833222685198043.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176043989775.2244198.14837718811974702888.malone@juju-98d295-prod-launchpad-7>

Hello Mostafa, or anyone else affected,

Accepted cinder into plucky-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cinder/2:26.0.0-0ubuntu1.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-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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: cinder (Ubuntu Plucky)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-plucky

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

Title:
  [SRU] cinder-netapp driver fails to start when a node is down

Status in Cinder:
  In Progress
Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive caracal series:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in cinder package in Ubuntu:
  Fix Released
Status in cinder source package in Noble:
  New
Status in cinder source package in Plucky:
  Fix Committed
Status in cinder source package in Questing:
  Fix Released

Bug description:
  We're trying to use cinder-netapp, and the driver fails to start with the following error.
  https://pastebin.ubuntu.com/p/dwMdrVwdtf/

  After enabling debugging, I noticed that one node doesn't report its model.
  Checking on netapp side, the node is down due to a hardware issue, and another one is taking over the current node.

  If i add or ''  to get_cluster_nodes_info. it works fine.

  In this current setup, if any node goes down and the driver restarts,
  Cinder won't be able to recover.

  ***************************

  [SRU]

  [Impact]
  cinder-volume service fails to start when cinder-netapp driver is used with some netapp nodes in maintenance state.

  The service during driver initialization queries the netapp server for all the nodes information. Typically the node
  name, model and certain other attributes are expected. However in case if the node is in maintenance mode, the
  model information is missing.
  cinder-volume service does not handle properly in case the model value is None and so the service goes to failed state.

  The fix checks if the model value is None and assigns empty string as default value. In addition, a warning message is
  logged for missing model values.

  [Test Case]

  To test the bug, we need netapp storage nodes. Instead developed a
  small python script that responds to couple of netapp requests that
  are required to reproduce the bug.

  Here are the reproducer steps:

  1. Deploy regress-stack (https://github.com/canonical/regress-stack)
  2. Install the packages required for cinder service to get setup
     
     sudo snap install astral-uv --classic
     sudo apt-get update
     uvx pre-commit install
     sudo apt install dpkg-dev python3-dev python-apt-dev -y
     uv sync
     sudo apt install ceph mysql-server rabbitmq-server keystone cinder-api cinder-scheduler cinder-volume -y

  3. Run regress-stack setup step

     uv run regress-stack setup

  4. Simulate netapp server

     The simulated code responds to couple of initial netapp requests and you can
     see in L#33 one of the node has no model information.
     Python code: https://pastebin.ubuntu.com/p/7pBSXzFSGY/
     python <netapp.py>

  5. Update cinder.conf to add netapp configuration

     https://pastebin.ubuntu.com/p/xK52rT5f7V/ (modified cinder configs)
     systemctl restart cinder-volume.service

  6. Check for cinder-volume logs

     Non-Working case:
     Should fail with error `TypeError: argument of type 'NoneType' is not iterable`

     Working case:
     Should see a printout in logs: `Reported ONTAPI Version: 1.261`
     (At this point of time the code execution crossed the bug)

     Note: The service wont start and fail with following error as the
  simulation does not support all the netapp API calls.

     cinder.volume.drivers.netapp.dataontap.client.api.NaApiError:
  NetApp API failed. Reason - 400:BAD REQUEST

  
  [Regression Potential]
  In order to mitigate any regression potential, the fix has been tested with real hardware for jammy caracal. The unit test cases are also updated to verify the bug. Also the default logic is not changed when model is provided by netapp server.

  [Discussion]
  n/a

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



From 2121812 at bugs.launchpad.net  Tue Oct 14 11:07:27 2025
From: 2121812 at bugs.launchpad.net (Julian Andres Klode)
Date: Tue, 14 Oct 2025 11:07:27 -0000
Subject: [Bug 2121812] Proposed package upload rejected
References: <175673748370.1030211.13188833222685198043.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176044004795.2253149.6203472056911646545.malone@juju-98d295-prod-launchpad-7>

An upload of cinder to noble-proposed has been rejected from the upload
queue for the following reason: "incorrectly edits previous changelog
entry to remove SRU tracking bug.".

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

Title:
  [SRU] cinder-netapp driver fails to start when a node is down

Status in Cinder:
  In Progress
Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive caracal series:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in cinder package in Ubuntu:
  Fix Released
Status in cinder source package in Noble:
  New
Status in cinder source package in Plucky:
  Fix Committed
Status in cinder source package in Questing:
  Fix Released

Bug description:
  We're trying to use cinder-netapp, and the driver fails to start with the following error.
  https://pastebin.ubuntu.com/p/dwMdrVwdtf/

  After enabling debugging, I noticed that one node doesn't report its model.
  Checking on netapp side, the node is down due to a hardware issue, and another one is taking over the current node.

  If i add or ''  to get_cluster_nodes_info. it works fine.

  In this current setup, if any node goes down and the driver restarts,
  Cinder won't be able to recover.

  ***************************

  [SRU]

  [Impact]
  cinder-volume service fails to start when cinder-netapp driver is used with some netapp nodes in maintenance state.

  The service during driver initialization queries the netapp server for all the nodes information. Typically the node
  name, model and certain other attributes are expected. However in case if the node is in maintenance mode, the
  model information is missing.
  cinder-volume service does not handle properly in case the model value is None and so the service goes to failed state.

  The fix checks if the model value is None and assigns empty string as default value. In addition, a warning message is
  logged for missing model values.

  [Test Case]

  To test the bug, we need netapp storage nodes. Instead developed a
  small python script that responds to couple of netapp requests that
  are required to reproduce the bug.

  Here are the reproducer steps:

  1. Deploy regress-stack (https://github.com/canonical/regress-stack)
  2. Install the packages required for cinder service to get setup
     
     sudo snap install astral-uv --classic
     sudo apt-get update
     uvx pre-commit install
     sudo apt install dpkg-dev python3-dev python-apt-dev -y
     uv sync
     sudo apt install ceph mysql-server rabbitmq-server keystone cinder-api cinder-scheduler cinder-volume -y

  3. Run regress-stack setup step

     uv run regress-stack setup

  4. Simulate netapp server

     The simulated code responds to couple of initial netapp requests and you can
     see in L#33 one of the node has no model information.
     Python code: https://pastebin.ubuntu.com/p/7pBSXzFSGY/
     python <netapp.py>

  5. Update cinder.conf to add netapp configuration

     https://pastebin.ubuntu.com/p/xK52rT5f7V/ (modified cinder configs)
     systemctl restart cinder-volume.service

  6. Check for cinder-volume logs

     Non-Working case:
     Should fail with error `TypeError: argument of type 'NoneType' is not iterable`

     Working case:
     Should see a printout in logs: `Reported ONTAPI Version: 1.261`
     (At this point of time the code execution crossed the bug)

     Note: The service wont start and fail with following error as the
  simulation does not support all the netapp API calls.

     cinder.volume.drivers.netapp.dataontap.client.api.NaApiError:
  NetApp API failed. Reason - 400:BAD REQUEST

  
  [Regression Potential]
  In order to mitigate any regression potential, the fix has been tested with real hardware for jammy caracal. The unit test cases are also updated to verify the bug. Also the default logic is not changed when model is provided by netapp server.

  [Discussion]
  n/a

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



From 2127769 at bugs.launchpad.net  Tue Oct 14 12:23:13 2025
From: 2127769 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 14 Oct 2025 12:23:13 -0000
Subject: [Bug 2127769] [NEW] [SRU] Add resolute as a known distro series
References: <176034730931.4096710.17663813294038095555.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176044459389.2378086.1185080211637777853.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Skia (hyask):

[ Impact ]

 * Lintian in stable releases of Ubuntu doesn't know about the Resolute
Raccon, and it should.

[ Test Plan ]

 * Obtain or create a source.changes file targeted towards `resolute`.
 * Run 'lintian $package_source.changes'
 * With the current version of lintian, you'll receive the following error:
   ```
   E: $package changes: bad-distribution-in-changes-file resolute
   ```
 * You should receive no such error with the new version of lintian.

[ Where problems could occur ]

 * This fairly trivial change is common after every archive opening.
 * As usual, we can always discover that the package is FTBFS for some weird reasons.
 * As lintian is usually part of some CI and/or developer tooling, we can always expect regressions in those areas, but that's unlikely that lintian is going to break stuff for regular non-developer Ubuntu users.

** Affects: lintian (Ubuntu)
     Importance: Undecided
     Assignee: Skia (hyask)
         Status: New

** Affects: lintian (Ubuntu Jammy)
     Importance: Undecided
     Assignee: Skia (hyask)
         Status: New

** Affects: lintian (Ubuntu Noble)
     Importance: Undecided
     Assignee: Skia (hyask)
         Status: New

** Affects: lintian (Ubuntu Plucky)
     Importance: Undecided
     Assignee: Skia (hyask)
         Status: New

** Affects: lintian (Ubuntu Questing)
     Importance: Undecided
     Assignee: Skia (hyask)
         Status: New

** Affects: lintian (Ubuntu Resolute)
     Importance: Undecided
     Assignee: Skia (hyask)
         Status: New

-- 
[SRU] Add resolute as a known distro series
https://bugs.launchpad.net/bugs/2127769
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2060730 at bugs.launchpad.net  Tue Oct 14 14:08:51 2025
From: 2060730 at bugs.launchpad.net (Sebastien Bacher)
Date: Tue, 14 Oct 2025 14:08:51 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176045093185.2558682.11084053532529404491.malone@juju-98d295-prod-launchpad-7>

@Alessandro, it seems the new fix isn't in questing/resolute yet?

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  In Progress
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  In Progress

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  Verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2127828 at bugs.launchpad.net  Tue Oct 14 14:11:28 2025
From: 2127828 at bugs.launchpad.net (Sebastien Bacher)
Date: Tue, 14 Oct 2025 14:11:28 -0000
Subject: [Bug 2127828] Re: Sync libchewing 0.10.3-1 (main) from Debian
 unstable (main)
References: <176042377781.1824167.10764101011463192573.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176045108850.1966823.9798031599836623739.malone@juju-98d295-prod-launchpad-2>

Thank you for your bug report. The package has currently no delta and
the update is in Debian/unstable so it will auto-synced once resolute
opens and the auto-sync job is started. Closing the bug since that
doesn't require any sponsoring

** Changed in: libchewing (Ubuntu)
       Status: New => Invalid

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

Title:
  Sync libchewing 0.10.3-1 (main) from Debian unstable (main)

Status in libchewing package in Ubuntu:
  Invalid

Bug description:
  Please sync libchewing 0.10.3-1 (main) from Debian unstable (main)

  Changelog entries since current resolute version 0.10.1-1:

  libchewing (0.10.3-1) unstable; urgency=medium

    * New upstream version 0.10.3

   -- ChangZhuo Chen (陳昌倬) <czchen at debian.org>  Sun, 24 Aug 2025
  20:14:33 +0800

  libchewing (0.10.2-1) unstable; urgency=medium

    * New upstream version 0.10.2

   -- ChangZhuo Chen (陳昌倬) <czchen at debian.org>  Thu, 14 Aug 2025
  21:12:31 +0800

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



From 2127769 at bugs.launchpad.net  Tue Oct 14 15:06:37 2025
From: 2127769 at bugs.launchpad.net (Sebastien Bacher)
Date: Tue, 14 Oct 2025 15:06:37 -0000
Subject: [Bug 2127769] Re: [SRU] Add resolute as a known distro series
References: <176034730931.4096710.17663813294038095555.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176045439804.2238070.5007324049913717877.launchpad@juju-98d295-prod-launchpad-3>

** Changed in: lintian (Ubuntu Resolute)
       Status: New => Fix Committed

** Changed in: lintian (Ubuntu Questing)
       Status: New => Fix Committed

** Changed in: lintian (Ubuntu Plucky)
       Status: New => Fix Committed

** Changed in: lintian (Ubuntu Noble)
       Status: New => Fix Committed

** Changed in: lintian (Ubuntu Jammy)
       Status: New => Fix Committed

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

Title:
  [SRU] Add resolute as a known distro series

Status in lintian package in Ubuntu:
  Fix Committed
Status in lintian source package in Jammy:
  Fix Committed
Status in lintian source package in Noble:
  Fix Committed
Status in lintian source package in Plucky:
  Fix Committed
Status in lintian source package in Questing:
  Fix Committed
Status in lintian source package in Resolute:
  Fix Committed

Bug description:
  [ Impact ]

   * Lintian in stable releases of Ubuntu doesn't know about the
  Resolute Raccon, and it should.

  [ Test Plan ]

   * Obtain or create a source.changes file targeted towards `resolute`.
   * Run 'lintian $package_source.changes'
   * With the current version of lintian, you'll receive the following error:
     ```
     E: $package changes: bad-distribution-in-changes-file resolute
     ```
   * You should receive no such error with the new version of lintian.

  [ Where problems could occur ]

   * This fairly trivial change is common after every archive opening.
   * As usual, we can always discover that the package is FTBFS for some weird reasons.
   * As lintian is usually part of some CI and/or developer tooling, we can always expect regressions in those areas, but that's unlikely that lintian is going to break stuff for regular non-developer Ubuntu users.

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



From 2124239 at bugs.launchpad.net  Tue Oct 14 19:37:29 2025
From: 2124239 at bugs.launchpad.net (Ernest Lotter)
Date: Tue, 14 Oct 2025 19:37:29 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176047064975.2683468.17910804004522729121.malone@juju-98d295-prod-launchpad-3>

Regarding comment #5:
---------------------

- I confirmed snapd builds for fine for amd64_v3 on my personal ppa:
https://launchpad.net/~ernestl/+archive/ubuntu/snapd2/+build/31361729/+files/snapd_2.72+ubuntu25.10.2_amd64v3.deb

- Its runs fine on my AMD Ryzen 7 2700X (Zen+) which supports amd64_v3.

- Following this, I enabled amd64_v3 on snappy-dev/image (this was
checked with all stakeholders first).

- snapd version uses two methods to retrieve arch info: (1)
runtime.GOARCH, and secondly (2) uname syscall. Neither would
distinguish amd64_v3, it will just show up as amd64.

```
snap version
snap          2.72+ubuntu25.10.2
snapd         2.72+ubuntu25.10.2
series        16
ubuntu        25.10
kernel        6.15.0-4-generic
architecture  amd64
```

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Tue Oct 14 20:34:15 2025
From: 2124239 at bugs.launchpad.net (Ernest Lotter)
Date: Tue, 14 Oct 2025 20:34:15 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176047405557.3174790.14657225029441790690.malone@juju-98d295-prod-launchpad-7>

Regarding comment #6:
---------------------

Thanks for pointing this out.

I will double check with the team, but here is my take:

(1) 
interfaces/apparmor/template.go applies inside the snap, so its relevant to the fs view that consist mainly of core<version> base snap provided fs (including core utils) and select mounts from the host.

Core24 is the most recent base, so the questing core utils location
changes are not yet relevant.

It is however vital that this gets addressed before Core26.04!

(2) 
Snapd daemon itself is not confined, but snap-confine helper come with a profile: /etc/apparmor.d/usr.lib.snapd.snap-confine.real

I looked at this profile, and do not see reference to core-utils, so I
believe this is not a problem.

As far as I can tell we are fine for the moment, but have to make
changes in preperation for Core26.04.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Tue Oct 14 20:57:08 2025
From: 2124239 at bugs.launchpad.net (Ernest Lotter)
Date: Tue, 14 Oct 2025 20:57:08 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176047542826.2614870.4946167322544663089.malone@juju-98d295-prod-launchpad-2>

Regarding comment #7:
---------------------

I think the comment can be improved.

This was detected during review as somewhat problematic:
https://github.com/canonical/snapd/pull/15832/files#r2281656504

The comment means to say that inside a snaps mount namespace, there are
no writable locations at /, so its inherently safe even though the rule
does does not restrict write actions...

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Tue Oct 14 21:03:58 2025
From: 2124239 at bugs.launchpad.net (Ernest Lotter)
Date: Tue, 14 Oct 2025 21:03:58 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176047583815.3221610.6994156873516531803.malone@juju-98d295-prod-launchpad-7>

Regarding comment #8:
---------------------

We have already dealt with the failing test
https://github.com/canonical/snapd/pull/16073.

We have no immediate solution for this issue, but as you say, it only
affects `snap run` with option `gdb-server` (so debugging only) which is
something we can live with.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2121812 at bugs.launchpad.net  Wed Oct 15 03:50:29 2025
From: 2121812 at bugs.launchpad.net (Hemanth Nakkina)
Date: Wed, 15 Oct 2025 03:50:29 -0000
Subject: [Bug 2121812] Re: [SRU] cinder-netapp driver fails to start when a
 node is down
References: <175673748370.1030211.13188833222685198043.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176050022933.3791805.13063212966160220758.malone@juju-98d295-prod-launchpad-7>

Tested 2:26.0.0-0ubuntu1.2 package using test steps mentioned in Test plan.
Installed the packages using venv instead of uv.

The error message "`TypeError: argument of type 'NoneType' is not
iterable`" is not displayed with the new package version and can see the
printout "Reported ONTAPI Version: 1.261" in cinder-volume service logs.

2025-10-15 03:48:12.520 19505 INFO cinder.volume.manager [None req-32b18bd5-27c5-4baa-aaa4-36896d6eff12 - - - - - -] Starting volume driver NetAppCmodeFibreChannelDriver (4.0.0)
2025-10-15 03:48:12.537 19405 INFO cinder.volume.manager [None req-c3ab9131-7827-47ce-8899-a98628d6d34f - - - - - -] Initializing RPC dependent components of volume driver RBDDriver (1.3.0)
2025-10-15 03:48:12.557 19505 WARNING cinder.volume.drivers.netapp.dataontap.client.client_cmode [None req-32b18bd5-27c5-4baa-aaa4-36896d6eff12 - - - - - -] No model information available for node CLUSTER-02
2025-10-15 03:48:12.558 19505 INFO cinder.volume.drivers.netapp.dataontap.client.client_cmode [None req-32b18bd5-27c5-4baa-aaa4-36896d6eff12 - - - - - -] Reported ONTAPI Version: 1.261


Package used for testing:
sudo apt list --installed | grep cinder-volume

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

cinder-volume/plucky-proposed,now 2:26.0.0-0ubuntu1.2 all [installed]

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

Title:
  [SRU] cinder-netapp driver fails to start when a node is down

Status in Cinder:
  In Progress
Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive caracal series:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in cinder package in Ubuntu:
  Fix Released
Status in cinder source package in Noble:
  New
Status in cinder source package in Plucky:
  Fix Committed
Status in cinder source package in Questing:
  Fix Released

Bug description:
  We're trying to use cinder-netapp, and the driver fails to start with the following error.
  https://pastebin.ubuntu.com/p/dwMdrVwdtf/

  After enabling debugging, I noticed that one node doesn't report its model.
  Checking on netapp side, the node is down due to a hardware issue, and another one is taking over the current node.

  If i add or ''  to get_cluster_nodes_info. it works fine.

  In this current setup, if any node goes down and the driver restarts,
  Cinder won't be able to recover.

  ***************************

  [SRU]

  [Impact]
  cinder-volume service fails to start when cinder-netapp driver is used with some netapp nodes in maintenance state.

  The service during driver initialization queries the netapp server for all the nodes information. Typically the node
  name, model and certain other attributes are expected. However in case if the node is in maintenance mode, the
  model information is missing.
  cinder-volume service does not handle properly in case the model value is None and so the service goes to failed state.

  The fix checks if the model value is None and assigns empty string as default value. In addition, a warning message is
  logged for missing model values.

  [Test Case]

  To test the bug, we need netapp storage nodes. Instead developed a
  small python script that responds to couple of netapp requests that
  are required to reproduce the bug.

  Here are the reproducer steps:

  1. Deploy regress-stack (https://github.com/canonical/regress-stack)
  2. Install the packages required for cinder service to get setup
     
     sudo snap install astral-uv --classic
     sudo apt-get update
     uvx pre-commit install
     sudo apt install dpkg-dev python3-dev python-apt-dev -y
     uv sync
     sudo apt install ceph mysql-server rabbitmq-server keystone cinder-api cinder-scheduler cinder-volume -y

  3. Run regress-stack setup step

     uv run regress-stack setup

  4. Simulate netapp server

     The simulated code responds to couple of initial netapp requests and you can
     see in L#33 one of the node has no model information.
     Python code: https://pastebin.ubuntu.com/p/7pBSXzFSGY/
     python <netapp.py>

  5. Update cinder.conf to add netapp configuration

     https://pastebin.ubuntu.com/p/xK52rT5f7V/ (modified cinder configs)
     systemctl restart cinder-volume.service

  6. Check for cinder-volume logs

     Non-Working case:
     Should fail with error `TypeError: argument of type 'NoneType' is not iterable`

     Working case:
     Should see a printout in logs: `Reported ONTAPI Version: 1.261`
     (At this point of time the code execution crossed the bug)

     Note: The service wont start and fail with following error as the
  simulation does not support all the netapp API calls.

     cinder.volume.drivers.netapp.dataontap.client.api.NaApiError:
  NetApp API failed. Reason - 400:BAD REQUEST

  
  [Regression Potential]
  In order to mitigate any regression potential, the fix has been tested with real hardware for jammy caracal. The unit test cases are also updated to verify the bug. Also the default logic is not changed when model is provided by netapp server.

  [Discussion]
  n/a

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



From 2121812 at bugs.launchpad.net  Wed Oct 15 03:55:38 2025
From: 2121812 at bugs.launchpad.net (Hemanth Nakkina)
Date: Wed, 15 Oct 2025 03:55:38 -0000
Subject: [Bug 2121812] Re: [SRU] cinder-netapp driver fails to start when a
 node is down
References: <175673748370.1030211.13188833222685198043.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176050053893.1412475.12317158403158310891.launchpad@juju-98d295-prod-launchpad-4>

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

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

Title:
  [SRU] cinder-netapp driver fails to start when a node is down

Status in Cinder:
  In Progress
Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive caracal series:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in cinder package in Ubuntu:
  Fix Released
Status in cinder source package in Noble:
  New
Status in cinder source package in Plucky:
  Fix Committed
Status in cinder source package in Questing:
  Fix Released

Bug description:
  We're trying to use cinder-netapp, and the driver fails to start with the following error.
  https://pastebin.ubuntu.com/p/dwMdrVwdtf/

  After enabling debugging, I noticed that one node doesn't report its model.
  Checking on netapp side, the node is down due to a hardware issue, and another one is taking over the current node.

  If i add or ''  to get_cluster_nodes_info. it works fine.

  In this current setup, if any node goes down and the driver restarts,
  Cinder won't be able to recover.

  ***************************

  [SRU]

  [Impact]
  cinder-volume service fails to start when cinder-netapp driver is used with some netapp nodes in maintenance state.

  The service during driver initialization queries the netapp server for all the nodes information. Typically the node
  name, model and certain other attributes are expected. However in case if the node is in maintenance mode, the
  model information is missing.
  cinder-volume service does not handle properly in case the model value is None and so the service goes to failed state.

  The fix checks if the model value is None and assigns empty string as default value. In addition, a warning message is
  logged for missing model values.

  [Test Case]

  To test the bug, we need netapp storage nodes. Instead developed a
  small python script that responds to couple of netapp requests that
  are required to reproduce the bug.

  Here are the reproducer steps:

  1. Deploy regress-stack (https://github.com/canonical/regress-stack)
  2. Install the packages required for cinder service to get setup
     
     sudo snap install astral-uv --classic
     sudo apt-get update
     uvx pre-commit install
     sudo apt install dpkg-dev python3-dev python-apt-dev -y
     uv sync
     sudo apt install ceph mysql-server rabbitmq-server keystone cinder-api cinder-scheduler cinder-volume -y

  3. Run regress-stack setup step

     uv run regress-stack setup

  4. Simulate netapp server

     The simulated code responds to couple of initial netapp requests and you can
     see in L#33 one of the node has no model information.
     Python code: https://pastebin.ubuntu.com/p/7pBSXzFSGY/
     python <netapp.py>

  5. Update cinder.conf to add netapp configuration

     https://pastebin.ubuntu.com/p/xK52rT5f7V/ (modified cinder configs)
     systemctl restart cinder-volume.service

  6. Check for cinder-volume logs

     Non-Working case:
     Should fail with error `TypeError: argument of type 'NoneType' is not iterable`

     Working case:
     Should see a printout in logs: `Reported ONTAPI Version: 1.261`
     (At this point of time the code execution crossed the bug)

     Note: The service wont start and fail with following error as the
  simulation does not support all the netapp API calls.

     cinder.volume.drivers.netapp.dataontap.client.api.NaApiError:
  NetApp API failed. Reason - 400:BAD REQUEST

  
  [Regression Potential]
  In order to mitigate any regression potential, the fix has been tested with real hardware for jammy caracal. The unit test cases are also updated to verify the bug. Also the default logic is not changed when model is provided by netapp server.

  [Discussion]
  n/a

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



From 2125145 at bugs.launchpad.net  Wed Oct 15 04:21:32 2025
From: 2125145 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 15 Oct 2025 04:21:32 -0000
Subject: [Bug 2125145] [NEW] [SRU] Makedumpfile: Errors and Page Exclusions
 When Opening Kernel Crashdump Files Generated on the Latest HWE Kernel
References: <175821630447.1842424.14764010785335167964.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176050209293.3441131.11893904998904526029.launchpad@juju-98d295-prod-launchpad-3>

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

Note: Original description is at the bottom of this report

[Impact]

The current versions of Makedumpfile and Crash in the -updates pocket on
Noble do not support the latest hardware enablement kernel for that
platform, which is 6.14. There are several architecture-dependent and
kernel flavor-dependent behaviours that I will outline below, but the
steps to reproduce are the same.

Reproducer steps:
-----------------

Boot into a hardware enablement kernel. For example, on arm64 use the
6.14.0-1008-nvidia-64k kernel:

KERNEL_VERSION=6.14.0-1008-nvidia-64k
DISTRO=noble

sudo apt update
sudo apt install ubuntu-dbgsym-keyring
echo "deb http://ddebs.ubuntu.com ${DISTRO} main restricted universe multiverse
deb http://ddebs.ubuntu.com ${DISTRO}-updates main restricted universe multiverse | \
  sudo tee /etc/apt/sources.list.d/ddebs.list
sudo apt update
sudo apt install linux-image-${KERNEL_VERSION}
sudo apt install linux-image-unsigned-${KERNEL_VERSION}-dbgsym

Modify grub's cmdline to specify a crashkernel: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=512M" # Or similar
sudo update-grub
sudo apt install kexec-tools kdump-tools crash makedumpfile
sudo systemctl enable kdump-tools
sudo systemctl start kdump-tools
sudo reboot

echo c | sudo tee /proc/sysrq-trigger

After the machine recovers,

crash /usr/lib/debug/boot/<kernel-dbgsym> /var/crash/<dump-dir>/<dump-
file>

Results on Arm64
----------------

crash 8.0.4
Copyright (C) 2002-2022  Red Hat, Inc.
...
For help, type "help".
Type "apropos word" to search for commands related to "word"...

please wait... (gathering task table data)
crash: page excluded: kernel virtual address: ffff07ffa042d8e0  type: "xa_node.slots[off]"

Results on amd64
----------------

On an amd64 machine, using a kernel such as linux-
image-6.14.0-29-generic results in crash failing to open. No error is
printed but we don't obtain the prompt:

crash 8.0.4
...
For help, type "help".
Type "apropos word" to search for commands related to "word"...

# Program exits and no prompt is presented

[Test Plan]

* Ensure that with the proposed combination of makedumpfile and crash is capable of generating and subsequently opening crashdumps on the HWE and GA kernels available for that platform. Here is the mapping ATOW:
Noble GA: 6.8
Noble HWE: 6.14
Plucky (interim release, no HWE): 6.14
Questing (interim release, no HWE): 6.17
Resolute (development): 6.17 (as of Oct. 14th 2025)

* Ensure all of crash's commands produce the expected output (eg. ps,
mount, files, vm, vtop, runq, etc.)

* If bugs are found in generating and reading crashdumps on the HWE
kernel on other architectures (s390x, etc.), this test plan can be
expanded to include those.

[Where Problems Could Occur]
* Crash and Makedumpfile are designed to be backwards-compatible, so the risk of regression when backporting a commit is low - however, not zero. This is why it will be important to ensure that the proposed combination of Makedumpfile and crash does not break existing environments - eg. the GA kernel

* The matrix of hardware and kernel versions (including derivative /
cloud kernels) to test again is extensive. It's possible that the
commits identified to solve the known problems will not be
comprehensive. For example, cpu architectures and kernels not in the
test matrix may require additional commits to be backported.

[Other Info]

* Support/SEG are currently having conversations with the kernel team
about the potential to proactively SRU / MRE the latest upstream crash
version, and potentially Makedumpfile as well, alongside -hwe kernel
releases to avoid this sort of regression in the future. Though, we
understand this would require an SRUExceptionPolicy to be approved and
published.

[Investigation and summary of changes]

We have identified that on the Makedumpfile at least two commits are needed:
[1] https://github.com/makedumpfile/makedumpfile/commit/985e575253f1c2de8d6876cfe685c68a24ee06e1
[2] https://github.com/makedumpfile/makedumpfile/commit/bad2a7c4fa75d37a41578441468584963028bdda

These are patches to compensate for a change in the kernel's mapping of
memory. Using the patched Makedumpfile helps, but it is not sufficient.
Including the patches in Makedumpfile (or using the tip of upstream
master), but opening with the currently distributed crash results in the
following errors:

eg. Patched Makedumpfile with crash 8.0.4 on Arm64:
---------------------------------------------------
...
WARNING: cannot determine starting stack frame for task ffffd574e21b4800

WARNING: cannot determine starting stack frame for task ffff07ff83296300

WARNING: cannot determine starting stack frame for task ffff07ff83293f80

WARNING: cannot determine starting stack frame for task ffff07ff83a04700

WARNING: cannot determine starting stack frame for task ffff08010507c400
      KERNEL: /usr/lib/debug/boot/vmlinux-6.14.0-1008-nvidia-64k
    DUMPFILE: /var/crash/patched_mdf/dump.202509191531  [PARTIAL DUMP]
        CPUS: 128 [OFFLINE: 127]
        DATE: Thu Jan  1 00:00:00 UTC 1970
      UPTIME: 00:13:38
LOAD AVERAGE: 0.12, 0.16, 0.10
       TASKS: 1573
    NODENAME: penguru
     RELEASE: 6.14.0-1008-nvidia-64k
     VERSION: #8-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 26 02:43:53 UTC 2025
     MACHINE: aarch64  (unknown Mhz)
      MEMORY: 63.8 GB
       PANIC: "Kernel panic - not syncing: sysrq triggered crash"
         PID: 7886
     COMMAND: "tee"
        TASK: ffff08010507c400  [THREAD_INFO: ffff08010507c400]
         CPU: 85
       STATE: TASK_RUNNING (PANIC)

On Amd64
--------
Crash still fails to open.

Therefore, in addition to the above Makedumpfile commits, crash requires
some patching. With the above two commits to Makedumpfile I did a bisect
on crash on amd64 and arm64.

On the amd64 crash side, I have identified that [3] applied in isolation (cherry-picked) is sufficient on amd64
[3] https://github.com/crash-utility/crash/commit/6752571d8d782d07537a258a1ec8919ebd1308ad

I have also found that cherry-picking [4] and [5] resolves the issue on arm64 hardware in testflinger (using the machine agent penguru)
[4] https://github.com/crash-utility/crash/commit/3879e9104826d5ae14a0824ec47ab60056a249a7
[5] https://github.com/crash-utility/crash/commit/968debd0d5979dd9ddca3af0766bad714dbd51e3

At this point, crash's commands such as mount, files, vm, etc. were
still broken. To resolve this, [6] and [7] are needed

[6] https://github.com/crash-utility/crash/commit/3d60d9d40457239683a5f20b01437db94f964fb8
[7] https://github.com/crash-utility/crash/commit/2795136a515446b798ebbfa257c97f0ca6ecb8ec

To SRU for Noble, crash must also be work on Plucky, Questing, and Resolute. The current version of makedumpfile on all of those series was found to be sufficient and so no SRU for makedumpfile is required on those. However for crash:
* Plucky uses the 6.14 kernel, so no additional commits are needed - in fact due to the newer version available on Plucky, only [7] is needed.
* Questing uses the 6.17 kernel. No issues other than [7] were observed on arm, but on amd64, an infinite loop while gdb loaded module symbols was observed, This is fixed in [8].
* Resolute will ship with a newer kernel than 6.17, but as of October 14th, 2025 is currently based on 6.17. Currently the package in Debian unstable, which will autosync to Resolute does not contain the required fixes and so it will also require SRU with [7] and [8] unless superceded by an upstream (Debian) version bump.

[8] https://github.com/crash-
utility/crash/commit/e44a9a9d808c83fb846060f65e5aaa9d30b6e2c4

PPA with all of the packages built (except resolute):
https://launchpad.net/~bryanfraschetti/+archive/ubuntu/lp2125145

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

Original Description:
=====================

24.04 LTS,
Linux 6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 14 16:52:50 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Problem Description:
crash utility is crashing (error code 1) when attempting to analyze kernel crash dumps.

Setup kdump & generated kernel panic using “echo 1 >
/proc/sys/kernel/sysrq” but, crash cannot access it:

# crash /usr/lib/debug/boot/vmlinux-6.14.0-29-generic
dump.202509161821

crash 8.0.4
Copyright (C) 2002-2022  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011, 2020-2022  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
Copyright (C) 2015, 2021  VMware, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.

GNU gdb (GDB) 10.2
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...

# echo $?
1

running as root user and file is readable fine:

$ :/var/crash/202509161821# ls -l
total 299144
-rw------- 1 root whoopsie    119627 Sep 16 18:21 dmesg.202509161821
-rw-r--r-- 1 root whoopsie 306200163 Sep 16 18:21 dump.202509161821

symbol file is there:

# ls -l /usr/lib/debug/boot/vmlinux-6.14.0-29-generic*
-rw-r--r-- 1 root root 450705920 Aug 14 18:02 /usr/lib/debug/boot/vmlinux-6.14.0-29-generic

tail of strace:

14:06:20.661240 rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
14:06:20.661281 rt_sigaction(SIGINT, {sa_handler=0x5ec383cbceb0, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
14:06:20.661322 rt_sigaction(SIGSEGV, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
14:06:20.661360 write(1, "\n", 1
)       = 1 <0.000119>
14:06:20.661579 lseek(3, 10312, SEEK_SET) = 10312 <0.000010>
14:06:20.661617 read(3, "OSRELEASE=6.14.0-29-generic\nBUIL"..., 3276) = 3276 <0.000011>
14:06:20.661748 unlink("/var/tmp/ramdump_elf_XXXXXX") = -1 ENOENT (No such file or directory) <0.002921>
14:06:20.664817 exit_group(1)           = ?
14:06:20.690105 +++ exited with 1 +++

full crash strace https://filebin.net/custom-bin/crash.strace.1

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: crash 8.0.4-1ubuntu2
ProcVersionSignature: Ubuntu 6.14.0-29.29~24.04.1-generic 6.14.8
Uname: Linux 6.14.0-29-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Sep 18 20:21:26 2025
InstallationDate: Installed on 2025-09-04 (14 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
SourcePackage: crash
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: makedumpfile (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: crash (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: makedumpfile (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: crash (Ubuntu Plucky)
     Importance: Undecided
         Status: New

** Affects: makedumpfile (Ubuntu Plucky)
     Importance: Undecided
         Status: Fix Released

** Affects: crash (Ubuntu Questing)
     Importance: Undecided
         Status: New

** Affects: makedumpfile (Ubuntu Questing)
     Importance: Undecided
         Status: Fix Released

** Affects: crash (Ubuntu Resolute)
     Importance: Undecided
         Status: Confirmed

** Affects: makedumpfile (Ubuntu Resolute)
     Importance: Undecided
         Status: Fix Released


** Tags: amd64 apport-bug noble patch
-- 
[SRU] Makedumpfile: Errors and Page Exclusions When Opening Kernel Crashdump Files Generated on the Latest HWE Kernel
https://bugs.launchpad.net/bugs/2125145
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2125145 at bugs.launchpad.net  Wed Oct 15 04:21:33 2025
From: 2125145 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Wed, 15 Oct 2025 04:21:33 -0000
Subject: [Bug 2125145] Re: [SRU] Makedumpfile: Errors and Page Exclusions When
 Opening Kernel Crashdump Files Generated on the Latest HWE Kernel
References: <175821630447.1842424.14764010785335167964.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176050209330.3434495.6400992198852310586.malone@juju-98d295-prod-launchpad-3>

The attachment "questing_crash.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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2125145

Title:
  [SRU] Makedumpfile: Errors and Page Exclusions When Opening Kernel
  Crashdump Files Generated on the Latest HWE Kernel

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in crash source package in Noble:
  New
Status in makedumpfile source package in Noble:
  New
Status in crash source package in Plucky:
  New
Status in makedumpfile source package in Plucky:
  Fix Released
Status in crash source package in Questing:
  New
Status in makedumpfile source package in Questing:
  Fix Released
Status in crash source package in Resolute:
  Confirmed
Status in makedumpfile source package in Resolute:
  Fix Released

Bug description:
  Note: Original description is at the bottom of this report

  [Impact]

  The current versions of Makedumpfile and Crash in the -updates pocket
  on Noble do not support the latest hardware enablement kernel for that
  platform, which is 6.14. There are several architecture-dependent and
  kernel flavor-dependent behaviours that I will outline below, but the
  steps to reproduce are the same.

  Reproducer steps:
  -----------------

  Boot into a hardware enablement kernel. For example, on arm64 use the
  6.14.0-1008-nvidia-64k kernel:

  KERNEL_VERSION=6.14.0-1008-nvidia-64k
  DISTRO=noble

  sudo apt update
  sudo apt install ubuntu-dbgsym-keyring
  echo "deb http://ddebs.ubuntu.com ${DISTRO} main restricted universe multiverse
  deb http://ddebs.ubuntu.com ${DISTRO}-updates main restricted universe multiverse | \
    sudo tee /etc/apt/sources.list.d/ddebs.list
  sudo apt update
  sudo apt install linux-image-${KERNEL_VERSION}
  sudo apt install linux-image-unsigned-${KERNEL_VERSION}-dbgsym

  Modify grub's cmdline to specify a crashkernel: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=512M" # Or similar
  sudo update-grub
  sudo apt install kexec-tools kdump-tools crash makedumpfile
  sudo systemctl enable kdump-tools
  sudo systemctl start kdump-tools
  sudo reboot

  echo c | sudo tee /proc/sysrq-trigger

  After the machine recovers,

  crash /usr/lib/debug/boot/<kernel-dbgsym> /var/crash/<dump-dir>/<dump-
  file>

  Results on Arm64
  ----------------

  crash 8.0.4
  Copyright (C) 2002-2022  Red Hat, Inc.
  ...
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  please wait... (gathering task table data)
  crash: page excluded: kernel virtual address: ffff07ffa042d8e0  type: "xa_node.slots[off]"

  Results on amd64
  ----------------

  On an amd64 machine, using a kernel such as linux-
  image-6.14.0-29-generic results in crash failing to open. No error is
  printed but we don't obtain the prompt:

  crash 8.0.4
  ...
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  # Program exits and no prompt is presented

  [Test Plan]

  * Ensure that with the proposed combination of makedumpfile and crash is capable of generating and subsequently opening crashdumps on the HWE and GA kernels available for that platform. Here is the mapping ATOW:
  Noble GA: 6.8
  Noble HWE: 6.14
  Plucky (interim release, no HWE): 6.14
  Questing (interim release, no HWE): 6.17
  Resolute (development): 6.17 (as of Oct. 14th 2025)

  * Ensure all of crash's commands produce the expected output (eg. ps,
  mount, files, vm, vtop, runq, etc.)

  * If bugs are found in generating and reading crashdumps on the HWE
  kernel on other architectures (s390x, etc.), this test plan can be
  expanded to include those.

  [Where Problems Could Occur]
  * Crash and Makedumpfile are designed to be backwards-compatible, so the risk of regression when backporting a commit is low - however, not zero. This is why it will be important to ensure that the proposed combination of Makedumpfile and crash does not break existing environments - eg. the GA kernel

  * The matrix of hardware and kernel versions (including derivative /
  cloud kernels) to test again is extensive. It's possible that the
  commits identified to solve the known problems will not be
  comprehensive. For example, cpu architectures and kernels not in the
  test matrix may require additional commits to be backported.

  [Other Info]

  * Support/SEG are currently having conversations with the kernel team
  about the potential to proactively SRU / MRE the latest upstream crash
  version, and potentially Makedumpfile as well, alongside -hwe kernel
  releases to avoid this sort of regression in the future. Though, we
  understand this would require an SRUExceptionPolicy to be approved and
  published.

  [Investigation and summary of changes]

  We have identified that on the Makedumpfile at least two commits are needed:
  [1] https://github.com/makedumpfile/makedumpfile/commit/985e575253f1c2de8d6876cfe685c68a24ee06e1
  [2] https://github.com/makedumpfile/makedumpfile/commit/bad2a7c4fa75d37a41578441468584963028bdda

  These are patches to compensate for a change in the kernel's mapping
  of memory. Using the patched Makedumpfile helps, but it is not
  sufficient. Including the patches in Makedumpfile (or using the tip of
  upstream master), but opening with the currently distributed crash
  results in the following errors:

  eg. Patched Makedumpfile with crash 8.0.4 on Arm64:
  ---------------------------------------------------
  ...
  WARNING: cannot determine starting stack frame for task ffffd574e21b4800

  WARNING: cannot determine starting stack frame for task
  ffff07ff83296300

  WARNING: cannot determine starting stack frame for task
  ffff07ff83293f80

  WARNING: cannot determine starting stack frame for task
  ffff07ff83a04700

  WARNING: cannot determine starting stack frame for task ffff08010507c400
        KERNEL: /usr/lib/debug/boot/vmlinux-6.14.0-1008-nvidia-64k
      DUMPFILE: /var/crash/patched_mdf/dump.202509191531  [PARTIAL DUMP]
          CPUS: 128 [OFFLINE: 127]
          DATE: Thu Jan  1 00:00:00 UTC 1970
        UPTIME: 00:13:38
  LOAD AVERAGE: 0.12, 0.16, 0.10
         TASKS: 1573
      NODENAME: penguru
       RELEASE: 6.14.0-1008-nvidia-64k
       VERSION: #8-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 26 02:43:53 UTC 2025
       MACHINE: aarch64  (unknown Mhz)
        MEMORY: 63.8 GB
         PANIC: "Kernel panic - not syncing: sysrq triggered crash"
           PID: 7886
       COMMAND: "tee"
          TASK: ffff08010507c400  [THREAD_INFO: ffff08010507c400]
           CPU: 85
         STATE: TASK_RUNNING (PANIC)

  On Amd64
  --------
  Crash still fails to open.

  Therefore, in addition to the above Makedumpfile commits, crash
  requires some patching. With the above two commits to Makedumpfile I
  did a bisect on crash on amd64 and arm64.

  On the amd64 crash side, I have identified that [3] applied in isolation (cherry-picked) is sufficient on amd64
  [3] https://github.com/crash-utility/crash/commit/6752571d8d782d07537a258a1ec8919ebd1308ad

  I have also found that cherry-picking [4] and [5] resolves the issue on arm64 hardware in testflinger (using the machine agent penguru)
  [4] https://github.com/crash-utility/crash/commit/3879e9104826d5ae14a0824ec47ab60056a249a7
  [5] https://github.com/crash-utility/crash/commit/968debd0d5979dd9ddca3af0766bad714dbd51e3

  At this point, crash's commands such as mount, files, vm, etc. were
  still broken. To resolve this, [6] and [7] are needed

  [6] https://github.com/crash-utility/crash/commit/3d60d9d40457239683a5f20b01437db94f964fb8
  [7] https://github.com/crash-utility/crash/commit/2795136a515446b798ebbfa257c97f0ca6ecb8ec

  To SRU for Noble, crash must also be work on Plucky, Questing, and Resolute. The current version of makedumpfile on all of those series was found to be sufficient and so no SRU for makedumpfile is required on those. However for crash:
  * Plucky uses the 6.14 kernel, so no additional commits are needed - in fact due to the newer version available on Plucky, only [7] is needed.
  * Questing uses the 6.17 kernel. No issues other than [7] were observed on arm, but on amd64, an infinite loop while gdb loaded module symbols was observed, This is fixed in [8].
  * Resolute will ship with a newer kernel than 6.17, but as of October 14th, 2025 is currently based on 6.17. Currently the package in Debian unstable, which will autosync to Resolute does not contain the required fixes and so it will also require SRU with [7] and [8] unless superceded by an upstream (Debian) version bump.

  [8] https://github.com/crash-
  utility/crash/commit/e44a9a9d808c83fb846060f65e5aaa9d30b6e2c4

  PPA with all of the packages built (except resolute):
  https://launchpad.net/~bryanfraschetti/+archive/ubuntu/lp2125145

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

  Original Description:
  =====================

  24.04 LTS,
  Linux 6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 14 16:52:50 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  Problem Description:
  crash utility is crashing (error code 1) when attempting to analyze kernel crash dumps.

  Setup kdump & generated kernel panic using “echo 1 >
  /proc/sys/kernel/sysrq” but, crash cannot access it:

  # crash /usr/lib/debug/boot/vmlinux-6.14.0-29-generic
  dump.202509161821

  crash 8.0.4
  Copyright (C) 2002-2022  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2022  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-pc-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
      <http://www.gnu.org/software/gdb/documentation/>.

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  # echo $?
  1

  running as root user and file is readable fine:

  $ :/var/crash/202509161821# ls -l
  total 299144
  -rw------- 1 root whoopsie    119627 Sep 16 18:21 dmesg.202509161821
  -rw-r--r-- 1 root whoopsie 306200163 Sep 16 18:21 dump.202509161821

  symbol file is there:

  # ls -l /usr/lib/debug/boot/vmlinux-6.14.0-29-generic*
  -rw-r--r-- 1 root root 450705920 Aug 14 18:02 /usr/lib/debug/boot/vmlinux-6.14.0-29-generic

  tail of strace:

  14:06:20.661240 rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661281 rt_sigaction(SIGINT, {sa_handler=0x5ec383cbceb0, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661322 rt_sigaction(SIGSEGV, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661360 write(1, "\n", 1
  )       = 1 <0.000119>
  14:06:20.661579 lseek(3, 10312, SEEK_SET) = 10312 <0.000010>
  14:06:20.661617 read(3, "OSRELEASE=6.14.0-29-generic\nBUIL"..., 3276) = 3276 <0.000011>
  14:06:20.661748 unlink("/var/tmp/ramdump_elf_XXXXXX") = -1 ENOENT (No such file or directory) <0.002921>
  14:06:20.664817 exit_group(1)           = ?
  14:06:20.690105 +++ exited with 1 +++

  full crash strace https://filebin.net/custom-bin/crash.strace.1

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: crash 8.0.4-1ubuntu2
  ProcVersionSignature: Ubuntu 6.14.0-29.29~24.04.1-generic 6.14.8
  Uname: Linux 6.14.0-29-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Sep 18 20:21:26 2025
  InstallationDate: Installed on 2025-09-04 (14 days ago)
  InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: crash
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 2124969 at bugs.launchpad.net  Wed Oct 15 08:37:14 2025
From: 2124969 at bugs.launchpad.net (Sebastien Bacher)
Date: Wed, 15 Oct 2025 08:37:14 -0000
Subject: [Bug 2124969] Re: lintian ftbfs in questing archive rebuild
References: <175812435085.3365866.6903273481855528851.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176051743537.3647504.14502991591312376909.launchpad@juju-98d295-prod-launchpad-2>

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

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

Title:
  lintian ftbfs in questing archive rebuild

Status in lintian package in Ubuntu:
  Fix Committed

Bug description:
  The package fails to build in the recent archive rebuild
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250910-questing-questing.html

  Test Summary Report
  -------------------
  debian/test-out/eval/checks/binaries/architecture/binaries-misplaced/generic.t                                                      (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
    Failed test:  1
    Non-zero exit status: 1
  debian/test-out/eval/checks/binaries/location/binaries-misplaced/generic.t                                                          (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
    Failed test:  1
    Non-zero exit status: 1
  Files=1503, Tests=64208, 1934 wallclock secs ( 8.69 usr  7.17 sys + 5745.63 cusr 1724.78 csys = 7486.27 CPU)
  Result: FAIL

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



From 2127792 at bugs.launchpad.net  Wed Oct 15 09:21:37 2025
From: 2127792 at bugs.launchpad.net (Daniel van Vugt)
Date: Wed, 15 Oct 2025 09:21:37 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176052009857.130772.15669926473674102419.launchpad@juju-98d295-prod-launchpad-7>

** Changed in: gnome-remote-desktop (Ubuntu Resolute)
     Assignee: (unassigned) => Antoine Lassagne (antoinelassagne)

** Changed in: gnome-remote-desktop (Ubuntu Resolute)
       Status: New => In Progress

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  In Progress
Status in gnome-remote-desktop source package in Noble:
  New
Status in gnome-remote-desktop source package in Questing:
  New
Status in gnome-remote-desktop source package in Resolute:
  In Progress

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2124969 at bugs.launchpad.net  Wed Oct 15 12:01:54 2025
From: 2124969 at bugs.launchpad.net (Nick Rosbrook)
Date: Wed, 15 Oct 2025 12:01:54 -0000
Subject: [Bug 2124969] Re: lintian ftbfs in questing archive rebuild
References: <175812435085.3365866.6903273481855528851.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176052971470.380964.17393147997065975851.malone@juju-98d295-prod-launchpad-7>

Hello Sebastien, or anyone else affected,

Accepted lintian into questing-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/lintian/2.122.0ubuntu2 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-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. 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: lintian (Ubuntu Questing)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-questing

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

Title:
  lintian ftbfs in questing archive rebuild

Status in lintian package in Ubuntu:
  Fix Committed
Status in lintian source package in Questing:
  Fix Committed

Bug description:
  The package fails to build in the recent archive rebuild
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250910-questing-questing.html

  Test Summary Report
  -------------------
  debian/test-out/eval/checks/binaries/architecture/binaries-misplaced/generic.t                                                      (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
    Failed test:  1
    Non-zero exit status: 1
  debian/test-out/eval/checks/binaries/location/binaries-misplaced/generic.t                                                          (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
    Failed test:  1
    Non-zero exit status: 1
  Files=1503, Tests=64208, 1934 wallclock secs ( 8.69 usr  7.17 sys + 5745.63 cusr 1724.78 csys = 7486.27 CPU)
  Result: FAIL

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



From 2121812 at bugs.launchpad.net  Wed Oct 15 12:57:53 2025
From: 2121812 at bugs.launchpad.net (Nick Rosbrook)
Date: Wed, 15 Oct 2025 12:57:53 -0000
Subject: [Bug 2121812] Re: [SRU] cinder-netapp driver fails to start when a
 node is down
References: <175673748370.1030211.13188833222685198043.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176053307383.4068462.3959569629419027702.malone@juju-98d295-prod-launchpad-2>

Hello Mostafa, or anyone else affected,

Accepted cinder into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cinder/2:24.2.0-0ubuntu2 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: cinder (Ubuntu Noble)
       Status: New => Fix Committed

** Tags added: verification-needed-noble

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

Title:
  [SRU] cinder-netapp driver fails to start when a node is down

Status in Cinder:
  In Progress
Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive caracal series:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in cinder package in Ubuntu:
  Fix Released
Status in cinder source package in Noble:
  Fix Committed
Status in cinder source package in Plucky:
  Fix Committed
Status in cinder source package in Questing:
  Fix Released

Bug description:
  We're trying to use cinder-netapp, and the driver fails to start with the following error.
  https://pastebin.ubuntu.com/p/dwMdrVwdtf/

  After enabling debugging, I noticed that one node doesn't report its model.
  Checking on netapp side, the node is down due to a hardware issue, and another one is taking over the current node.

  If i add or ''  to get_cluster_nodes_info. it works fine.

  In this current setup, if any node goes down and the driver restarts,
  Cinder won't be able to recover.

  ***************************

  [SRU]

  [Impact]
  cinder-volume service fails to start when cinder-netapp driver is used with some netapp nodes in maintenance state.

  The service during driver initialization queries the netapp server for all the nodes information. Typically the node
  name, model and certain other attributes are expected. However in case if the node is in maintenance mode, the
  model information is missing.
  cinder-volume service does not handle properly in case the model value is None and so the service goes to failed state.

  The fix checks if the model value is None and assigns empty string as default value. In addition, a warning message is
  logged for missing model values.

  [Test Case]

  To test the bug, we need netapp storage nodes. Instead developed a
  small python script that responds to couple of netapp requests that
  are required to reproduce the bug.

  Here are the reproducer steps:

  1. Deploy regress-stack (https://github.com/canonical/regress-stack)
  2. Install the packages required for cinder service to get setup
     
     sudo snap install astral-uv --classic
     sudo apt-get update
     uvx pre-commit install
     sudo apt install dpkg-dev python3-dev python-apt-dev -y
     uv sync
     sudo apt install ceph mysql-server rabbitmq-server keystone cinder-api cinder-scheduler cinder-volume -y

  3. Run regress-stack setup step

     uv run regress-stack setup

  4. Simulate netapp server

     The simulated code responds to couple of initial netapp requests and you can
     see in L#33 one of the node has no model information.
     Python code: https://pastebin.ubuntu.com/p/7pBSXzFSGY/
     python <netapp.py>

  5. Update cinder.conf to add netapp configuration

     https://pastebin.ubuntu.com/p/xK52rT5f7V/ (modified cinder configs)
     systemctl restart cinder-volume.service

  6. Check for cinder-volume logs

     Non-Working case:
     Should fail with error `TypeError: argument of type 'NoneType' is not iterable`

     Working case:
     Should see a printout in logs: `Reported ONTAPI Version: 1.261`
     (At this point of time the code execution crossed the bug)

     Note: The service wont start and fail with following error as the
  simulation does not support all the netapp API calls.

     cinder.volume.drivers.netapp.dataontap.client.api.NaApiError:
  NetApp API failed. Reason - 400:BAD REQUEST

  
  [Regression Potential]
  In order to mitigate any regression potential, the fix has been tested with real hardware for jammy caracal. The unit test cases are also updated to verify the bug. Also the default logic is not changed when model is provided by netapp server.

  [Discussion]
  n/a

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



From 2124239 at bugs.launchpad.net  Wed Oct 15 13:37:59 2025
From: 2124239 at bugs.launchpad.net (Andreas Hasenack)
Date: Wed, 15 Oct 2025 13:37:59 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176053547951.4131876.8984488500908945081.malone@juju-98d295-prod-launchpad-2>

The questing version seems wrong.

Today we have:
 snapd | 2.71+ubuntu25.04     | plucky-updates  | source
 snapd | 2.71.1+ubuntu25.10.1 | questing        | source
 snapd | 2.71.1+ubuntu25.10.1 | resolute        | source

Questing in the ppa linked to this SRU is 2.72+ubuntu25.10.2. It should
be 2.72+ubuntu25.10.1, no? I'm ok changing that before sponsoring, just
need your +1 on this.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Wed Oct 15 13:40:48 2025
From: 2124239 at bugs.launchpad.net (Andreas Hasenack)
Date: Wed, 15 Oct 2025 13:40:48 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176053564838.558516.14670475813037369422.malone@juju-98d295-prod-launchpad-7>

There are some broken symlinks in these packages, is that expected?

For example:

$ l snapd-2.72+ubuntu26.04.1/core-initrd/latest/factory/
total 16K
drwxrwxr-x  4 andreas andreas 4.0K Sep 18 05:00 .
drwxrwxr-x 10 andreas andreas 4.0K Sep 18 05:00 ..
drwxrwxr-x  3 andreas andreas 4.0K Sep 18 05:00 etc
lrwxrwxrwx  1 andreas andreas   23 Sep 18 05:00 init -> usr/lib/systemd/systemd ### broken
drwxrwxr-x  5 andreas andreas 4.0K Sep 18 05:00 usr

$ l snapd-2.72+ubuntu26.04.1/core-initrd/latest/factory/usr/lib/systemd
total 20K
drwxrwxr-x  5 andreas andreas 4.0K Sep 18 05:00 .
drwxrwxr-x  5 andreas andreas 4.0K Sep 18 05:00 ..
drwxrwxr-x  2 andreas andreas 4.0K Sep 18 05:00 bootchart.conf.d
drwxrwxr-x  2 andreas andreas 4.0K Sep 18 05:00 journald.conf.d
drwxrwxr-x 15 andreas andreas 4.0K Sep 18 05:00 system     ### here it's "system", not "systemd"

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2127938 at bugs.launchpad.net  Wed Oct 15 17:01:40 2025
From: 2127938 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 15 Oct 2025 17:01:40 -0000
Subject: [Bug 2127938] [NEW] Ubuntu 26.04 needs to install LXD from 6/stable
 channel
References: <176054763421.886238.10530919287910518146.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176054770116.2703014.5551589617750392336.launchpad@juju-98d295-prod-launchpad-4>

You have been subscribed to a public bug by Simon Déziel (sdeziel):

In preparation of the next Ubuntu LTS release, the LXD team has opened a
new track in the 6/stable channel for 26.04: `6/stable/ubuntu-26.04`

lxd-installer needs to be modified to pull from that new track/channel
when executing on 26.04.

** Affects: lxd-installer (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Ubuntu 26.04 needs to install LXD from 6/stable channel
https://bugs.launchpad.net/bugs/2127938
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127938 at bugs.launchpad.net  Wed Oct 15 17:02:12 2025
From: 2127938 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 15 Oct 2025 17:02:12 -0000
Subject: [Bug 2127938] Re: Ubuntu 26.04 needs to install LXD from 6/stable
 channel
References: <176054763421.886238.10530919287910518146.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176054773276.2700203.11575079749919091780.malone@juju-98d295-prod-launchpad-4>

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

** Changed in: lxd-installer (Ubuntu)
       Status: New => Confirmed

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

Title:
  Ubuntu 26.04 needs to install LXD from 6/stable channel

Status in lxd-installer package in Ubuntu:
  Confirmed

Bug description:
  In preparation of the next Ubuntu LTS release, the LXD team has opened
  a new track in the 6/stable channel for 26.04: `6/stable/ubuntu-26.04`

  lxd-installer needs to be modified to pull from that new track/channel
  when executing on 26.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2127938/+subscriptions



From 2124239 at bugs.launchpad.net  Wed Oct 15 21:27:47 2025
From: 2124239 at bugs.launchpad.net (Ernest Lotter)
Date: Wed, 15 Oct 2025 21:27:47 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176056366731.1292401.7983931156774637407.malone@juju-98d295-prod-launchpad-7>

Regarding comment #13:
----------------------

Questing should be snapd - 2.72+ubuntu25.10.2.

-> Version snapd - 2.72+ubuntu25.10 had to have changelog modified due
to late out of order arrival of 2.71.1

-> Then Version snapd - 2.72+ubuntu25.10.1 again required tiny patch to
fix a seccomp related test issue.

So this brings us to 2.72+ubuntu25.10.2.


So as things stand now:

(1)    snapd - 2.72+ubuntu26.04.1
(2)    snapd - 2.72+ubuntu25.10.2
(3)    snapd - 2.72+ubuntu25.04
(4)    snapd - 2.72+ubuntu24.04

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2121812 at bugs.launchpad.net  Thu Oct 16 05:33:36 2025
From: 2121812 at bugs.launchpad.net (Hemanth Nakkina)
Date: Thu, 16 Oct 2025 05:33:36 -0000
Subject: [Bug 2121812] Re: [SRU] cinder-netapp driver fails to start when a
 node is down
References: <175673748370.1030211.13188833222685198043.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176059281658.1566954.451777106641032172.malone@juju-98d295-prod-launchpad-3>

Tested 2:24.2.0-0ubuntu2 package using test steps mentioned in Test
plan.

The error message "`TypeError: argument of type 'NoneType' is not
iterable`" is not displayed with the new package version and can see the
printout "Reported ONTAPI Version: 1.261" in cinder-volume service logs.

2025-10-16 05:31:40.551 18170 INFO cinder.volume.manager [None req-6003bd10-8af9-44da-92c1-0952c8299c79 - - - - - -] Starting volume driver NetAppCmodeFibreChannelDriver (3.0.0)
2025-10-16 05:31:40.619 18170 WARNING cinder.volume.drivers.netapp.dataontap.client.client_cmode [None req-6003bd10-8af9-44da-92c1-0952c8299c79 - - - - - -] No model information available for node CLUSTER-02
2025-10-16 05:31:40.619 18170 INFO cinder.volume.drivers.netapp.dataontap.client.client_cmode [None req-6003bd10-8af9-44da-92c1-0952c8299c79 - - - - - -] Reported ONTAPI Version: 1.261


Package used for testing:
sudo apt list --installed | grep cinder-volume

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

cinder-volume/noble-proposed,now 2:24.2.0-0ubuntu2 all [installed]

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

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

Title:
  [SRU] cinder-netapp driver fails to start when a node is down

Status in Cinder:
  In Progress
Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive caracal series:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in cinder package in Ubuntu:
  Fix Released
Status in cinder source package in Noble:
  Fix Committed
Status in cinder source package in Plucky:
  Fix Committed
Status in cinder source package in Questing:
  Fix Released

Bug description:
  We're trying to use cinder-netapp, and the driver fails to start with the following error.
  https://pastebin.ubuntu.com/p/dwMdrVwdtf/

  After enabling debugging, I noticed that one node doesn't report its model.
  Checking on netapp side, the node is down due to a hardware issue, and another one is taking over the current node.

  If i add or ''  to get_cluster_nodes_info. it works fine.

  In this current setup, if any node goes down and the driver restarts,
  Cinder won't be able to recover.

  ***************************

  [SRU]

  [Impact]
  cinder-volume service fails to start when cinder-netapp driver is used with some netapp nodes in maintenance state.

  The service during driver initialization queries the netapp server for all the nodes information. Typically the node
  name, model and certain other attributes are expected. However in case if the node is in maintenance mode, the
  model information is missing.
  cinder-volume service does not handle properly in case the model value is None and so the service goes to failed state.

  The fix checks if the model value is None and assigns empty string as default value. In addition, a warning message is
  logged for missing model values.

  [Test Case]

  To test the bug, we need netapp storage nodes. Instead developed a
  small python script that responds to couple of netapp requests that
  are required to reproduce the bug.

  Here are the reproducer steps:

  1. Deploy regress-stack (https://github.com/canonical/regress-stack)
  2. Install the packages required for cinder service to get setup
     
     sudo snap install astral-uv --classic
     sudo apt-get update
     uvx pre-commit install
     sudo apt install dpkg-dev python3-dev python-apt-dev -y
     uv sync
     sudo apt install ceph mysql-server rabbitmq-server keystone cinder-api cinder-scheduler cinder-volume -y

  3. Run regress-stack setup step

     uv run regress-stack setup

  4. Simulate netapp server

     The simulated code responds to couple of initial netapp requests and you can
     see in L#33 one of the node has no model information.
     Python code: https://pastebin.ubuntu.com/p/7pBSXzFSGY/
     python <netapp.py>

  5. Update cinder.conf to add netapp configuration

     https://pastebin.ubuntu.com/p/xK52rT5f7V/ (modified cinder configs)
     systemctl restart cinder-volume.service

  6. Check for cinder-volume logs

     Non-Working case:
     Should fail with error `TypeError: argument of type 'NoneType' is not iterable`

     Working case:
     Should see a printout in logs: `Reported ONTAPI Version: 1.261`
     (At this point of time the code execution crossed the bug)

     Note: The service wont start and fail with following error as the
  simulation does not support all the netapp API calls.

     cinder.volume.drivers.netapp.dataontap.client.api.NaApiError:
  NetApp API failed. Reason - 400:BAD REQUEST

  
  [Regression Potential]
  In order to mitigate any regression potential, the fix has been tested with real hardware for jammy caracal. The unit test cases are also updated to verify the bug. Also the default logic is not changed when model is provided by netapp server.

  [Discussion]
  n/a

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



From 2124239 at bugs.launchpad.net  Thu Oct 16 07:31:06 2025
From: 2124239 at bugs.launchpad.net (Ernest Lotter)
Date: Thu, 16 Oct 2025 07:31:06 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176059986652.1750086.17833263967536137096.malone@juju-98d295-prod-launchpad-3>

Regarding comment #14:
----------------------

>From Alfonso:
```
those folders are used to build UC initramfs, they might not point anywhere until the initramfs is built
so yes, that is expected
```

This makes sense. We could consider excluding it from the source tarball
in the future, but its harmless as is.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Confirmed
Status in snapd source package in Jammy:
  Confirmed
Status in snapd source package in Noble:
  Confirmed
Status in snapd source package in Plucky:
  Confirmed
Status in snapd source package in Questing:
  Confirmed
Status in snapd source package in Resolute:
  Confirmed

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2060730 at bugs.launchpad.net  Thu Oct 16 07:44:47 2025
From: 2060730 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 16 Oct 2025 07:44:47 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176060068824.1772947.13349134786054330162.launchpad@juju-98d295-prod-launchpad-3>

** Also affects: totem (Ubuntu Questing)
   Importance: Undecided
       Status: New

** Also affects: packagekit (Ubuntu Questing)
   Importance: Undecided
       Status: New

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  In Progress
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  In Progress
Status in packagekit source package in Questing:
  New
Status in totem source package in Questing:
  New

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  Verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2060730 at bugs.launchpad.net  Thu Oct 16 07:53:40 2025
From: 2060730 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 16 Oct 2025 07:53:40 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176060122103.1563429.16265417357196587609.launchpad@juju-98d295-prod-launchpad-2>

** No longer affects: totem (Ubuntu Questing)

** Changed in: packagekit (Ubuntu Questing)
       Status: New => In Progress

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

** Changed in: packagekit (Ubuntu Questing)
     Assignee: (unassigned) => Alessandro Astone (aleasto)

** Changed in: packagekit (Ubuntu Questing)
    Milestone: None => questing-updates

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  In Progress
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  In Progress
Status in packagekit source package in Questing:
  In Progress

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2060730 at bugs.launchpad.net  Thu Oct 16 07:57:57 2025
From: 2060730 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 16 Oct 2025 07:57:57 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176060147797.2965816.7330510473048753815.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~aleasto/ubuntu/+source/packagekit/+git/packagekit/+merge/494530

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  In Progress
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  In Progress
Status in packagekit source package in Questing:
  In Progress

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2060730 at bugs.launchpad.net  Thu Oct 16 08:01:14 2025
From: 2060730 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 16 Oct 2025 08:01:14 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176060167415.2185936.10806394740976257614.malone@juju-98d295-prod-launchpad-7>

> @Alessandro, it seems the new fix isn't in questing/resolute yet?

Right, sorry.
Opened a new merge proposal for questing too. For resolute, packagekit should be synced from debian instead (thus "Fix Committed").


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

** Changed in: packagekit (Ubuntu)
    Milestone: ubuntu-25.10 => ubuntu-26.04

** Description changed:

  [ Impact ]
  
  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.
  
  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.
  
  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.
  
  [ Test Plan ]
  
  For the purpose of the SRU, we're only going to verify the PackageKit fix.
- Verify the output of the following commands:
+ On both AMD64 and ARM64, verify the output of the following commands:
  
  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
  
  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386
  
  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
  
  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
  
  [ Where problems could occur ]
  
  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.
  
  [ Other info ]
  
  Specifically, the following is output by totem:
  
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  In Progress
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  In Progress
Status in packagekit source package in Questing:
  In Progress

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2127792 at bugs.launchpad.net  Thu Oct 16 08:07:04 2025
From: 2127792 at bugs.launchpad.net (Daniel van Vugt)
Date: Thu, 16 Oct 2025 08:07:04 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176060202512.1811745.15086612778506513183.launchpad@juju-98d295-prod-launchpad-3>

** Tags added: udeng-8338

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  In Progress
Status in gnome-remote-desktop source package in Noble:
  New
Status in gnome-remote-desktop source package in Questing:
  New
Status in gnome-remote-desktop source package in Resolute:
  In Progress

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2126559 at bugs.launchpad.net  Thu Oct 16 14:43:55 2025
From: 2126559 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 16 Oct 2025 14:43:55 -0000
Subject: [Bug 2126559] [NEW] Missing usb/host/xhci-pci-renesas kernel module
 in the initramfs
References: <175931583063.1368946.9154850780421681274.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176062583574.2229684.4203892595147557388.launchpad@juju-98d295-prod-launchpad-2>

You have been subscribed to a public bug by Thibault Ferrante (thibf):

[ Impact ]

 * Unable to boot from usb for specific intel hardware (GNR)
 * Especially an issue for ubuntu ISO.

[ Fix ]

 * As done for questing, whitelist the missing module to be included in the initramfs.
 * This is a similar fix that what was done by dracut [1].

[ Test Plan ]

 * Build an initramfs with initramfs-tools updated and check that
drivers/usb/host/xhci-pci-renesas.ko.zst has been included

[ Where problems could occur ]

 * Increase slightly size of the initramfs.

[ Other info ]

 * Checked for other missing usb drivers in dracut code, nothing is
coming up.

1: https://github.com/dracut-ng/dracut-ng/commit/20cc20d2ac9c2908da6735b04dba49c1cb1b0bab
__________
On specific intel hardware (GNR), the Ubuntu ISO 24.04.3 doesn't boot when selecting the hwe kernel.
After looking at the initrd generated, the hwe-initrd is missing kernel/drivers/usb/host/xhci-pci-renesas.ko.zst:

$ lsinitramfs casper/initrd | grep kernel/drivers/usb/host/
usr/lib/modules/6.8.0-71-generic/kernel/drivers/usb/host/xhci-pci-renesas.ko.zst
usr/lib/modules/6.8.0-71-generic/kernel/drivers/usb/host/xhci-pci.ko.zst
usr/lib/modules/6.8.0-71-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko.zst
$ lsinitramfs casper/hwe-initrd | grep kernel/drivers/usb/host/
usr/lib/modules/6.14.0-27-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko.zst

xhci-pci module is also not there as it's in 6.14 a builtin.

As depmod is used to find dependencies across modules, I guess it is
missing dependencies for builtins.

In 6.8.0 we can find in the associated modules.dep:
kernel/drivers/usb/host/xhci-pci.ko.zst: kernel/drivers/usb/host/xhci-pci-renesas.ko.zst
But it's not the case in 6.14.0.

Related bug:
- https://bugs.launchpad.net/cisco-ucs-server/+bug/2121594
- https://bugs.launchpad.net/ubuntu/+bug/2124218

** Affects: initramfs-tools (Ubuntu)
     Importance: High
         Status: Fix Released

** Affects: initramfs-tools (Ubuntu Noble)
     Importance: Medium
     Assignee: Thibault Ferrante (thibf)
         Status: In Progress

** Affects: initramfs-tools (Ubuntu Plucky)
     Importance: Medium
     Assignee: Thibault Ferrante (thibf)
         Status: In Progress

** Affects: initramfs-tools (Ubuntu Questing)
     Importance: High
         Status: Fix Released

-- 
Missing usb/host/xhci-pci-renesas kernel module in the initramfs
https://bugs.launchpad.net/bugs/2126559
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2124239 at bugs.launchpad.net  Thu Oct 16 17:07:24 2025
From: 2124239 at bugs.launchpad.net (Andreas Hasenack)
Date: Thu, 16 Oct 2025 17:07:24 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176063444425.3082670.14287536931376800948.malone@juju-98d295-prod-launchpad-7>

Sponsored for resolute, questing, plucky, noble, jammy.

** Changed in: snapd (Ubuntu Resolute)
       Status: Confirmed => In Progress

** Changed in: snapd (Ubuntu Questing)
       Status: Confirmed => In Progress

** Changed in: snapd (Ubuntu Plucky)
       Status: Confirmed => In Progress

** Changed in: snapd (Ubuntu Noble)
       Status: Confirmed => In Progress

** Changed in: snapd (Ubuntu Jammy)
       Status: Confirmed => In Progress

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  In Progress
Status in snapd source package in Noble:
  In Progress
Status in snapd source package in Plucky:
  In Progress
Status in snapd source package in Questing:
  In Progress
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2120508 at bugs.launchpad.net  Thu Oct 16 17:29:40 2025
From: 2120508 at bugs.launchpad.net (Andreas Hasenack)
Date: Thu, 16 Oct 2025 17:29:40 -0000
Subject: [Bug 2120508] Re: [SRU] Kernel 6.17 support in broadcom-sta
References: <175504979388.1070318.10498456978486065255.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176063578045.3122204.14934962516081266109.malone@juju-98d295-prod-launchpad-7>

Thanks for your confirmation, satmandu, than helps.

In order to release the proposed package into updates, however, we need
a bit more details, like requested in the accept comment #11:

> 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-noble to verification-done-noble.

If you or anyone else would be able to complete those steps
successfully, then we can release this update.

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

Title:
  [SRU] Kernel 6.17 support in broadcom-sta

Status in broadcom-sta package in Ubuntu:
  Fix Released
Status in broadcom-sta source package in Noble:
  Fix Committed
Status in broadcom-sta source package in Plucky:
  Invalid
Status in broadcom-sta source package in Questing:
  Fix Released

Bug description:
  [SRU Justification]

  [ Impact ]

  Failed to build against kernel v6.17-rc1.

  [ Test Plan ]

  1. Install kernels >= 6.17. For Noble, linux-oem-6.17 is available:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-oem-6.17

  2. For Questing and Noble, install also stock kernel to ensure we don't break existing setup:
     $ sudo apt-get install --no-install-recommends --yes \
         linux-generic

  3. Install broadcom-sta-dkms from noble -proposed pocket. The dkms
  should rebuild itself against the running kernel automatically; if not
  rebuild them manually with:

     $ sudo dkms install --force broadcom-sta/6.30.223.271 -k $(uname -r)
     # With Questing
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-5-generic, x86_64: installed
     # With Noble
     $ dkms status
     broadcom-sta/6.30.223.271, 6.17.0-1002-oem, x86_64: installed
     broadcom-sta/6.30.223.271, 6.8.0-81-generic, x86_64: installed

  4. Reboot to load the kernel module
  5. The wl module should be loaded automatically and wireless lan should be usable as before.
  6. There should not be any UBSAN warning in dmesg, e.g.:
     ```
     [ 28.822952] UBSAN: array-index-out-of-bounds in /var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
     ```

  [ Where problems could occur ]

  This doesn't affect the rest part of the system, and it doesn't
  introduce functional changes.

  [ Other Info ]

  This affects series with kernels >= 6.17. Nominate Questing and Noble
  for fixing.

  Kernel 6.17 will not be introduced in Plucky

  ========== original bug report ==========

  A patch to fix building for kernel 6.17-rc1 is at
  https://gist.github.com/joanbm/4e7f18febc2c25f5fdf8143a739dccd1?permalink_comment_id=5717588#gistcomment-5717588

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2120508/+subscriptions



From 2120204 at bugs.launchpad.net  Thu Oct 16 23:14:35 2025
From: 2120204 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 16 Oct 2025 23:14:35 -0000
Subject: [Bug 2120204] [NEW] [SRU] MariaDB 11.4.8, 10.11.14,
 10.6.23 in all maintained Ubuntu releases
References: <175469379196.829008.11755758274290387043.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176065647582.1265968.8965508246872276204.launchpad@juju-98d295-prod-launchpad-4>

You have been subscribed to a public bug by Otto Kekäläinen (otto):

This issue tracks an update for the MariaDB and Galera packages, moving
to versions:

* questing (25.10): MariaDB 1:11.8.3
* plucky (25.04): MariaDB 1:11.4.8
* noble (24.04): MariaDB 1:10.11.14
* jammy (22.04): MariaDB 1:10.6.23

These minor maintenance releases include bug fixes following the SRU special case documentation at
https://documentation.ubuntu.com/sru/en/latest/reference/exception-MariaDB-Galera-Updates/.

Upstream did not announce any new CVEs fixed by this release, so these
versions will not be uploaded as security updates, but as regular stable
updates.

[Upstream changes]

The new versions, along with descriptions of changes and detailed
changelogs for each version will be posted as MRs
https://salsa.debian.org/mariadb-team/mariadb-server/

So far the 11.8.3 import to Debian unstable (and Ubuntu devel) has been
posted for review at https://salsa.debian.org/mariadb-team/mariadb-
server/-/merge_requests/129

[Test Plan]

TODO: Check that builds pass on all Ubuntu architectures
TODO: Check that the full build passed, including checks for file locations,
      symbols file and ABI stability and the post-build upstream tests
TODO: Check DEP-8 (autopkgtests) pass
TODO: If that the same update in Debian unstable and Ubuntu devel passed all
      QA systems, including DEP-8 (autopkgtests) for reverse dependencies
TODO: If there are any non passing tests - explain why that is ok in this case
TODO: Add results of an autopkgtest run against all the new versions
TODO: If available, check status of Debian Salsa pipelines

[Regression Potential]

The build incorporates an extensive build and integration test suite. The
upstream also releases their own .deb packages and they too run extensive
tests on them. Regressions would likely arise from a change in interaction
with Ubuntu-specific integrations.

Some regressions were already discovered while preparing
https://salsa.debian.org/mariadb-team/mariadb-
server/-/merge_requests/129 and patched to partially revert some
upstream changes.

** Affects: mariadb (Ubuntu)
     Importance: Undecided
     Assignee: Otto Kekäläinen (otto)
         Status: New

-- 
[SRU] MariaDB 11.4.8, 10.11.14, 10.6.23 in all maintained Ubuntu releases
https://bugs.launchpad.net/bugs/2120204
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2120204 at bugs.launchpad.net  Thu Oct 16 23:21:02 2025
From: 2120204 at bugs.launchpad.net (=?utf-8?b?T3R0byBLZWvDpGzDpGluZW4=?=)
Date: Thu, 16 Oct 2025 23:21:02 -0000
Subject: [Bug 2120204] Re: [SRU] MariaDB 11.4.8, 10.11.14,
 10.6.23 in all maintained Ubuntu releases
References: <175469379196.829008.11755758274290387043.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176065686244.3643379.1676133687273267893.malone@juju-98d295-prod-launchpad-7>

As per process in
https://documentation.ubuntu.com/sru/en/latest/explanation/further-
requirements/#newer-releases the Plucky upload is no longer required as
Questing was released.

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

Title:
  [SRU] MariaDB 11.4.8, 10.11.14, 10.6.23 in all maintained Ubuntu
  releases

Status in mariadb package in Ubuntu:
  New

Bug description:
  This issue tracks an update for the MariaDB and Galera packages,
  moving to versions:

  * questing (25.10): MariaDB 1:11.8.3
  * plucky (25.04): MariaDB 1:11.4.8
  * noble (24.04): MariaDB 1:10.11.14
  * jammy (22.04): MariaDB 1:10.6.23

  These minor maintenance releases include bug fixes following the SRU special case documentation at
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-MariaDB-Galera-Updates/.

  Upstream did not announce any new CVEs fixed by this release, so these
  versions will not be uploaded as security updates, but as regular
  stable updates.

  [Upstream changes]

  The new versions, along with descriptions of changes and detailed
  changelogs for each version will be posted as MRs
  https://salsa.debian.org/mariadb-team/mariadb-server/

  So far the 11.8.3 import to Debian unstable (and Ubuntu devel) has
  been posted for review at https://salsa.debian.org/mariadb-
  team/mariadb-server/-/merge_requests/129

  [Test Plan]

  TODO: Check that builds pass on all Ubuntu architectures
  TODO: Check that the full build passed, including checks for file locations,
        symbols file and ABI stability and the post-build upstream tests
  TODO: Check DEP-8 (autopkgtests) pass
  TODO: If that the same update in Debian unstable and Ubuntu devel passed all
        QA systems, including DEP-8 (autopkgtests) for reverse dependencies
  TODO: If there are any non passing tests - explain why that is ok in this case
  TODO: Add results of an autopkgtest run against all the new versions
  TODO: If available, check status of Debian Salsa pipelines

  [Regression Potential]

  The build incorporates an extensive build and integration test suite. The
  upstream also releases their own .deb packages and they too run extensive
  tests on them. Regressions would likely arise from a change in interaction
  with Ubuntu-specific integrations.

  Some regressions were already discovered while preparing
  https://salsa.debian.org/mariadb-team/mariadb-
  server/-/merge_requests/129 and patched to partially revert some
  upstream changes.

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



From 2128682 at bugs.launchpad.net  Fri Oct 17 06:05:12 2025
From: 2128682 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 17 Oct 2025 06:05:12 -0000
Subject: [Bug 2128682] [NEW] Sync java-websocket 1.6.0-2 (universe) from
 Debian unstable (main)
References: <176068110445.9711.10975448766915441423.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176068111246.14690.345539995058910287.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Rico Tzschichholz (ricotz):

Please sync java-websocket 1.6.0-2 (universe) from Debian unstable
(main)

All changelog entries:

java-websocket (1.6.0-2) unstable; urgency=medium

  * upload to unstable

 -- Rene Engelhard <rene at debian.org>  Sun, 10 Aug 2025 14:29:58 +0200

java-websocket (1.6.0-1) experimental; urgency=medium

  * Initial release (Closes: #1108919)

 -- Rene Engelhard <rene at debian.org>  Tue, 08 Jul 2025 18:54:08 +0200

** Affects: ubuntu
     Importance: Wishlist
         Status: New

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


From 2128682 at bugs.launchpad.net  Fri Oct 17 07:05:08 2025
From: 2128682 at bugs.launchpad.net (Rico Tzschichholz)
Date: Fri, 17 Oct 2025 07:05:08 -0000
Subject: [Bug 2128682] Re: Sync java-websocket 1.6.0-2 (universe) from Debian
 unstable (main)
References: <176068110445.9711.10975448766915441423.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176068470961.1939777.6938416923126063696.launchpad@juju-98d295-prod-launchpad-4>

** Changed in: ubuntu
       Status: New => Fix Committed

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

Title:
  Sync java-websocket 1.6.0-2 (universe) from Debian unstable (main)

Status in Ubuntu:
  Fix Committed

Bug description:
  Please sync java-websocket 1.6.0-2 (universe) from Debian unstable
  (main)

  All changelog entries:

  java-websocket (1.6.0-2) unstable; urgency=medium

    * upload to unstable

   -- Rene Engelhard <rene at debian.org>  Sun, 10 Aug 2025 14:29:58 +0200

  java-websocket (1.6.0-1) experimental; urgency=medium

    * Initial release (Closes: #1108919)

   -- Rene Engelhard <rene at debian.org>  Tue, 08 Jul 2025 18:54:08 +0200

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



From 2128682 at bugs.launchpad.net  Fri Oct 17 07:29:14 2025
From: 2128682 at bugs.launchpad.net (Rico Tzschichholz)
Date: Fri, 17 Oct 2025 07:29:14 -0000
Subject: [Bug 2128682] Re: Sync java-websocket 1.6.0-2 (universe) from Debian
 unstable (main)
References: <176068110445.9711.10975448766915441423.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176068615650.3719328.16759192094262808862.launchpad@juju-98d295-prod-launchpad-2>

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

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

Title:
  Sync java-websocket 1.6.0-2 (universe) from Debian unstable (main)

Status in Ubuntu:
  Fix Released

Bug description:
  Please sync java-websocket 1.6.0-2 (universe) from Debian unstable
  (main)

  All changelog entries:

  java-websocket (1.6.0-2) unstable; urgency=medium

    * upload to unstable

   -- Rene Engelhard <rene at debian.org>  Sun, 10 Aug 2025 14:29:58 +0200

  java-websocket (1.6.0-1) experimental; urgency=medium

    * Initial release (Closes: #1108919)

   -- Rene Engelhard <rene at debian.org>  Tue, 08 Jul 2025 18:54:08 +0200

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



From 2122551 at bugs.launchpad.net  Fri Oct 17 09:06:07 2025
From: 2122551 at bugs.launchpad.net (Simon Chopin)
Date: Fri, 17 Oct 2025 09:06:07 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176069196713.4111198.5191902687812083963.malone@juju-98d295-prod-launchpad-3>

I think it's reasonable. I was a bit skeptical of the test plan since it
doesn't actually exercise the migrations, but thinking some more about
it, it's OK since the touched code is the one selecting the actions, not
the actions themselves.

However, the debdiffs aren't minimal. Normally, SRUs shouldn't contain
stuff like

+  [ James Page ]
+  * d/gbp.conf: Create stable/2024.1 branch.
+  * d/gbp.conf, .launchpad.yaml: Sync from cloud-archive-tools for
+    caracal.

Since OpenStack is a special beast, there might be some precedent for
shipping SRUs with this kind of change bundled in, or some exception
explicitly documented somewhere. Could you please either minimize the
diff or dig up the relevant documentation?

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  Fix Released
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  Fix Released

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2122551 at bugs.launchpad.net  Fri Oct 17 09:06:57 2025
From: 2122551 at bugs.launchpad.net (Simon Chopin)
Date: Fri, 17 Oct 2025 09:06:57 -0000
Subject: [Bug 2122551] Re: [SRU] Backport feature for disabling migration to
 Noble and Plucky
References: <175755099916.112364.13524918193862216738.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176069201736.3870821.11172995001697054991.malone@juju-98d295-prod-launchpad-2>

Also, please resubscribe ubuntu-sponsors once this is cleared up :)

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

Title:
  [SRU] Backport feature for disabling migration to Noble and Plucky

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive epoxy series:
  New
Status in watcher package in Ubuntu:
  Fix Released
Status in watcher source package in Noble:
  New
Status in watcher source package in Plucky:
  New
Status in watcher source package in Questing:
  Fix Released

Bug description:
  Watcher upstream has adopted a new feature to the Host Maintenance
  strategy to disable live or cold migration and safely stop active
  instances when migration cannot proceed. This feature is planned for
  Watcher 15.0.0 shipped with OpenStack 25.02, but will be useful if it
  can be backported to Ubuntu Plucky and Noble.

  For example, currently Sunbeam/Canonical OpenStack is mainly using
  Watcher rock images which are pulled from Ubuntu Cloud Archive Epoxy
  (watcher 2:14.0.0) and Caracal (watcher 2:12.0.0). Having this new
  feature will help address this known issue: https://canonical-
  openstack.readthedocs-hosted.com/en/latest/how-
  to/operations/maintenance-mode/#known-issues

  Upstream commit:
  https://opendev.org/openstack/watcher/commit/cc26b3b334e5d60bf04c927c771d572445e4a8bc

  [ Impact ]
   * User problem: Current host maintenance strategy forces migration operations that may not be suitable for all deployment scenarios.

   * Functional Enhancement: Introduces two new input parameters to the Host Maintenance strategy:
    - `disable_live_migration`: When True, forces cold migration instead of live migration
    - `disable_cold_migration`: When True, prevents cold migration of inactive instances
    - Combined usage: When both are True, only stop actions are performed on active instances

   * Backward Compatibility: All changes are additive with sensible
  defaults (both new parameters default to False), ensuring existing
  Host Maintenance strategy deployments continue working unchanged.

   * No API Changes: The feature adds only configuration parameters to
  current schema and internal action handling - no API modifications or
  breaking changes to existing interfaces.

   * Target Releases:
     - Ubuntu 25.04 (Plucky) with watcher 2:14.0.0 -> enables UCA Epoxy
     - Ubuntu 24.04 (Noble) with watcher 2:12.0.0

  [ Test Case ]

   Prerequisite:
    * OpenStack cluster with Watcher enabled.
    * At least two compute nodes in the cluster
    * Test instances running on the maintenance target node

   1. Test Case 1: Backward Compatibility
   # Verify existing behavior is unchanged
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p backup_node=compute02

   # Expected: Traditional live/cold migration behavior (no stop actions)
   openstack actionplan show <audit_uuid>

   2. Test Case 2: Both Migrations Disabled
   # Test stop-only behavior (the new stop action)
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True \
     -p disable_cold_migration=True

   # Expected: Action plan contains only "stop" actions for instances
   openstack actionplan show <audit_uuid>

   3. Test Case 3: Live Migration Disabled Only
   # Test cold migration fallback
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_live_migration=True

   # Expected: Active instances use cold migration, inactive instances use cold migration
   openstack actionplan show <audit_uuid>

   4. Test Case 4: Cold Migration Disabled Only
   # Test live migration with no cold migration
   openstack optimize audit create -g cluster_maintaining -s host_maintenance \
     -p maintenance_node=compute01 -p disable_cold_migration=True

   # Expected: Active instances use live migration, inactive instances remain untouched
   openstack actionplan show <audit_uuid>

  The testing can also be done via Ubuntu OpenStack CI system using
  Tempest to verify the backward compatibility.

  [ Regression Potential / Where problems could occur]

   Configuration Conflicts:
   * Risk: Administrators might misconfigure parameters, leading to unexpected behavior
   * Manifestation: Instances stopped when migration was intended, or vice versa
   * Detection: Review action plans before execution; monitor Watcher logs for parameter validation

   Stop Action Failures:
    * Risk: New stop action might fail on instances with complex configurations (attached volumes, special networking, etc.)
    * Manifestation: Action plan execution failures; instances left in inconsistent states
    * Detection: Failed action plan execution; Nova API errors in Watcher applier logs

   Otherwise, due to no changes in API and the new parameters are set to
  False by default, the regression potential is mitigated with low risk.
  All existing CI jobs in upstream have passed.

  [ Discussion ]
   N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2122551/+subscriptions



From 2122576 at bugs.launchpad.net  Fri Oct 17 09:16:07 2025
From: 2122576 at bugs.launchpad.net (Simon Chopin)
Date: Fri, 17 Oct 2025 09:16:07 -0000
Subject: [Bug 2122576] Re: Add support Intel PTL platform and ITMT3.0 policy
References: <175758076411.1792167.10087975254811915865.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176069256792.315094.9786524334068711660.malone@juju-98d295-prod-launchpad-7>

Hi,

The timing for this is a bit awkward, with the release and archive
opening.

Could you please fix the questing debdiff so that it conforms to the SRU
versioning policy, and prepare a resolute upload?

I would also add the Applied-Upstream field to the patch with the first
upstream version the fixes appear in, so that when we move to a new
version we can know at a glance that this patch can be dropped.

Please resubscribe ubuntu-sponsors to this bug once you feel my comments
have been addressed.

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

Title:
  Add support Intel PTL platform and ITMT3.0 policy

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * The thermald will not be active on Intel PTL platform.

   * The thermald still use passive policy on board with ITMI3
  configured.

  [ Test Plan ]

   * On Intel PTL platform with ITMT3.0 policy configured

   * Boot into Ubuntu

   * Stop the default thermald by $ sudo systemctl stop thermald

   * run the thermlad with extra parameter $ sudo thermald --systemd
  --dbus-enable --adaptive --log-level=info

   * check the journalctl log to confirm that thermald apply the policy
  successfully

  1. Make sure to see ITMT3.0 policy defined in the APAT table
  [1754988644][INFO]..apat dump begin..
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance

  2. Check that ITMT3 policy is applied
  [1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance

  [ Where problems could occur ]

   * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.

   *
  https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  enhance the support for the ITMT3.0 policy. No code logic change for
  ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
  change the thermal behavior.

  [ Other Info ]

   * ITMT stands for Intel Turbo Boost Max Technology, a feature that
  identifies the best-performing cores on a processor and directs
  workloads to them for increased single-threaded performance. This
  technology assigns a higher priority to the fastest cores, ensuring
  that demanding tasks get the maximum possible speed on those select
  cores, while other cores handle less intensive work or remain idle.
  The advantage of ITMT3 can be found in The advantage of ITMT3 can be
  found in https://edc.intel.com/content/www/us/en/design/ipla/software-
  development-platforms/client/platforms/alder-lake-desktop/12th-
  generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
  turbo-boost-max-technology-3-0/.

   * Upstream commits:
     https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28

   * extra commit for noble to add PTL support.
     https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
     these two I combine them into one patch
     https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
     https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659

   * According to Dell architect yijun.shen at dell.com, there is no
  certified Dell platform has ITMI3 configured, it will only be
  available on the coming PTL platform.

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



From 2107145 at bugs.launchpad.net  Fri Oct 17 09:54:39 2025
From: 2107145 at bugs.launchpad.net (Simon Chopin)
Date: Fri, 17 Oct 2025 09:54:39 -0000
Subject: [Bug 2107145] Re: [SRU] Backport wsl-pro-service to Jammy and Focal
References: <174438577005.287075.5848047027233506555.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176069487982.3951337.2486246761681400580.malone@juju-98d295-prod-launchpad-2>

What's the actual status here? ubuntu-sponsors has been resubscribe but
the MPs are still marked as WIP.

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

Title:
  [SRU] Backport wsl-pro-service to Jammy and Focal

Status in wsl-pro-service package in Ubuntu:
  New
Status in wsl-pro-service source package in Focal:
  New
Status in wsl-pro-service source package in Jammy:
  Incomplete

Bug description:
  As part of our offerings to bring Ubuntu Pro to wider audiences we
  need to backport this service to Ubuntu 22.04 LTS, so users can
  benefit of the upcoming GA of Ubuntu Pro for WSL, as Windows system
  that allows more easily secure and manage WSL instances, by
  automatically pro-attaching Ubuntu on WSL instances and even register
  with and manage them via Lansdcape.

  wsl-pro-service is our bridge to the Windows application that performs
  key  post-provisioning actions on an instance, such as updating a Pro
  token and Landscape configuration data if that changes on the Windows
  side.

  As this service is only applicable for Ubuntu on WSL, its systemd unit is contained to not even start
  if the condition `ConditionVirtualization=wsl` is unmet. systemd confinement options were validated to work on Jammy as of wsl-pro-service version 0.1.18 (the one being proposed via this SRU).

  [Impact]

  * wsl-pro-service is a new package for Jammy and Focal
  * It depends on golang-1.23-go at build time, which is available on jammy-updates.
  * A certain level of downgrades was necessary for focal, that requires golang-1.22-go.
  * Ubuntu Pro for WSL relies on this service being seeded on the Ubuntu instances.
  * That system is not yet generally available, but planned for later this year.
  * At minimum Jammy and Noble must be supported, but Focal is planned.
  * Beta customers were already provided with custom images of 22.04 and 24.04 from the get-go.
  * As a new daemon, more often inert if the Windows side is not present, this should not affect users experience.
  * Boot time measurements reveals negligible impact.
  * The systemd unit is carefully and purposefully confined to allow only minimum requirements of our application while remaining compatible with systemd v245 (thus, compatible with Jammy and Focal).

  [ Test plan ]

  == 1. Less loging:

  * Make sure the Ubuntu Pro for WSL Windows agent is not running:
    - On Windows run `taskkill /f /im ubuntu-pro-agent.exe`
    - Depending on the OS settings elevated permissions might be required.
  * Install wsl-pro-service version 0.1.18 on Ubuntu 22.04 on WSL.
  * Follow it's journal with `journalctl -f -u wsl-pro.service`
  * Notice that it starts logging connection attempts too often, backing off exponentially up to 1min interval.
    Approximately 10 minutes after attempting to connect without success, it silents.
  * systemd should take approximately 20 min to attempt to restart the unit.

  == 2. Pro attachment works under systemd restrictions and without
  livepatch being installed.

  (Most of this test case would be testing ubuntu-pro-client v35 indeed, but we must verify that our integration
  is not harmed with the changes in wsl-pro-service systemd confinement)

  * Create a fresh instance of Ubuntu on WSL:
    - On Windows run `wsl.exe --install -d Ubuntu-22.04`
  * Install ubuntu-pro-agent v35 (currently available via the `-proposed` repository)
  * Make sure livepatch is not installed: `sudo snap remove canonical-livepatch`
  * Make sure the Ubuntu on WSL instance is not pro attached: `pro status` (`pro detach` if needed).
  * Install wsl-pro-service version 0.1.18 on Ubuntu on WSL (Noble, Oracular and Plucky should behave exactly
  the same)
  * Install Ubuntu Pro for WSL (download the latest production build from https://github.com/canonical/ubuntu-pro-for-wsl/actions/runs/14386282882/artifacts/2921576467)
  * Follow this guide to attach your Pro token: https://documentation.ubuntu.com/wsl/en/stable/tutorials/getting-started-with-up4w/#set-up-ubuntu-pro-for-wsl
  * Follow it's journal with `journalctl -f -u wsl-pro.service`:
    - If pro-attaching fails because of systemd restrictions we should see some "permission denied" or "bad system
    call" errors in the journal.
    - If the livepatch fix was not correct, we should see mentions to `canonical-livepatch` in the journal.
    - Both conditions should be considered a failure. Otherwise, proceed.
  * Confirm pro attachment `pro status` inside the Ubuntu instance.
  * Finally assert that canonical-livepatch remains not installed on this machine.

  == 3. wsl-pro-service outside of WSL

  (Ensures the unit does nothing outside of WSL)

  * Install wsl-pro-service on an instance of Ubuntu 22.04 on any platform other than WSL (Desktop,
  Server bare-metal or VM, OCI containers).
  * Verify that the unit is disabled due unmet condition: `systemctl status wsl-pro.service`

  == 4. Boot time

  (Ensures the unit does not significantly impact the boot time duration)
  * Install wsl-pro-service on an Ubuntu 22.04 instance on WSL.
  * Modify the default user's .bashrc to just exit (by appending `exit` as the last line of that script)
  * On Windows PowerShell run `wsl --terminate Ubuntu-22.04; Measure-Command {wsl -d Ubuntu-22.04}` a few times and take notes of the duration that command takes to finish
  * Start the WSL instance as root `wsl -d Ubuntu-22.04 -u root`
  * Remove wsl-pro-service
  * Repeat the measurement step
  * Compare the results.

  Spot differences are expected, because of the many layers involved,
  but there should not be more than 2% difference in **median** between
  boot times with and without that service enabled, per recent
  measurements taken by our team.

  [ Where problems could occur ]

  The few beta customers we have might have noticed that up until now, wsl-pro-service remains running all the time the unit is alive, thus anytime a user installs the
  Ubuntu Pro for WSL application on Windows they could expect the communication with the Windows agents to start
  briefly. That's also the case for the custom 22.04 images they've been playing with, which come with wsl-pro-service 0.1.5.

  With the behaviour changes in v0.1.18, that won't be the case always, as the service could just had quit seconds before
  and systemd will take about 20min to restart it. Users can always `sudo systemctl restart wsl-pro.service`.

  Since the entire system is not yet generally available the number of users affected by this behaviour change
  is very minimal, comprising of a handful of beta testers and internal collaborators (such as the
  Landscape team).

  
  [ Other Info ]

  I intentionally skipped testing the changes related to Landscape because it's too complex to set up a server
  just for this purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2107145/+subscriptions



From 2123886 at bugs.launchpad.net  Fri Oct 17 10:00:17 2025
From: 2123886 at bugs.launchpad.net (Simon Chopin)
Date: Fri, 17 Oct 2025 10:00:17 -0000
Subject: [Bug 2123886] Re: Add missing ARM-cores to support Vera-based systems
References: <175797801894.3652365.4625127746591030660.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176069521786.3953713.1275383391573717530.malone@juju-98d295-prod-launchpad-2>

Hi,

I'm sorry to have to tell you this, but you'll have to rework your
questing patch since questing has been released and resolute is now the
new development series.

For resolute, I'd check whether the issue would be fixed by a merge from
Debian, as their upstream version is higher.

Please resubscribe ubuntu-sponsors once you feel this is ready for
another round of reviews.

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

Title:
  Add missing ARM-cores to support Vera-based systems

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Noble:
  In Progress
Status in util-linux source package in Plucky:
  In Progress
Status in util-linux source package in Questing:
  In Progress

Bug description:
  [Impact]

  When running "lscpu" on a Vera-based system, it doesn't report a model
  name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Noble's
  (and previous) versions.

  https://github.com/util-linux/util-
  linux/commit/908777470d403ec30c525472ba0d3701c9c5a223

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Olympus

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems.

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2123886/+subscriptions



From 2121675 at bugs.launchpad.net  Fri Oct 17 10:02:09 2025
From: 2121675 at bugs.launchpad.net (Simon Chopin)
Date: Fri, 17 Oct 2025 10:02:09 -0000
Subject: [Bug 2121675] Re: Add support for Intel Arrowlake codec RT711
References: <175646454585.4137041.14778958458442065073.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176069532926.3959172.6587533164298427569.malone@juju-98d295-prod-launchpad-2>

Hey Hector, I'm unsubscribing ubuntu-sponsors from this as it seems this
isn't ready for us just yet?

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

Title:
  Add support for Intel Arrowlake codec RT711

Status in firmware-sof package in Ubuntu:
  In Progress
Status in firmware-sof source package in Noble:
  Confirmed
Status in firmware-sof source package in Plucky:
  Confirmed
Status in firmware-sof source package in Questing:
  In Progress
Status in firmware-sof source package in Resolute:
  In Progress

Bug description:
  Ubuntu lacks audio support on Intel arrowlake platform

  Here is the boot message log on Ubuntu 24.04.3:

  
  ubuntu at ubuntu:~$ sudo dmesg | grep sof
  [    0.023486] software IO TLB: area num 16.
  [    0.253235] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [    0.253236] software IO TLB: mapped [mem 0x00000000576b2000-0x000000005b6b2000] (64MB)
  [    0.424919] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  [    0.425616] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  [    2.438071] sof-audio-pci-intel-mtl 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver
  [    2.438085] sof-audio-pci-intel-mtl 0000:00:1f.3: enabling device (0000 -> 0002)
  [    2.438215] sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
  [    2.440235] sof-audio-pci-intel-mtl 0000:00:1f.3: use msi interrupt mode
  [    2.444650] sof-audio-pci-intel-mtl 0000:00:1f.3: no hda codecs found!
  [    2.444652] sof-audio-pci-intel-mtl 0000:00:1f.3: NHLT device BT(0) detected, ssp_mask 0x4
  [    2.444653] sof-audio-pci-intel-mtl 0000:00:1f.3: BT link detected in NHLT tables: 0x4
  [    2.444654] sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 2
  [    2.447689] sof-audio-pci-intel-mtl 0000:00:1f.3: SOF firmware and/or topology file not found.
  [    2.447698] sof-audio-pci-intel-mtl 0000:00:1f.3: Supported default profiles
  [    2.447698] sof-audio-pci-intel-mtl 0000:00:1f.3: - ipc type 1 (Requested):
  [    2.447699] sof-audio-pci-intel-mtl 0000:00:1f.3:  Firmware file: intel/sof-ipc4/arl/sof-arl.ri
  [    2.447699] sof-audio-pci-intel-mtl 0000:00:1f.3:  Topology file: intel/sof-ace-tplg/sof-arl-rt711-l0-2ch.tplg
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3: Check if you have 'sof-firmware' package installed.
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3: Optionally it can be manually downloaded from:
  [    2.447700] sof-audio-pci-intel-mtl 0000:00:1f.3:    https://github.com/thesofproject/sof-bin/
  [    2.448991] sof-audio-pci-intel-mtl 0000:00:1f.3: error: sof_probe_work failed err: -2

  
  The missing piece is the topology file: intel/sof-ace-tplg/sof-arl-rt711-l0-2ch.tplg

  The latest topology file for this platform that has been validated by
  Intel is available at:

  https://github.com/thesofproject/sof-bin/blob/main/v2.8.x/sof-ace-
  tplg-v2.8.1/sof-mtl-rt711-4ch.tplg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2121675/+subscriptions



From 2107145 at bugs.launchpad.net  Fri Oct 17 12:19:04 2025
From: 2107145 at bugs.launchpad.net (Carlos Nihelton)
Date: Fri, 17 Oct 2025 12:19:04 -0000
Subject: [Bug 2107145] Re: [SRU] Backport wsl-pro-service to Jammy and Focal
References: <174438577005.287075.5848047027233506555.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176070354421.4168273.16408098236084177447.malone@juju-98d295-prod-launchpad-2>

It's ready for review now. I kept it on hold while SRU'ing the same
version for Noble was still ongoing. That SRU now is clear and close to
complete aging, so my understanding is that's safe to resume this one.

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

Title:
  [SRU] Backport wsl-pro-service to Jammy and Focal

Status in wsl-pro-service package in Ubuntu:
  New
Status in wsl-pro-service source package in Focal:
  New
Status in wsl-pro-service source package in Jammy:
  Incomplete

Bug description:
  As part of our offerings to bring Ubuntu Pro to wider audiences we
  need to backport this service to Ubuntu 22.04 LTS, so users can
  benefit of the upcoming GA of Ubuntu Pro for WSL, as Windows system
  that allows more easily secure and manage WSL instances, by
  automatically pro-attaching Ubuntu on WSL instances and even register
  with and manage them via Lansdcape.

  wsl-pro-service is our bridge to the Windows application that performs
  key  post-provisioning actions on an instance, such as updating a Pro
  token and Landscape configuration data if that changes on the Windows
  side.

  As this service is only applicable for Ubuntu on WSL, its systemd unit is contained to not even start
  if the condition `ConditionVirtualization=wsl` is unmet. systemd confinement options were validated to work on Jammy as of wsl-pro-service version 0.1.18 (the one being proposed via this SRU).

  [Impact]

  * wsl-pro-service is a new package for Jammy and Focal
  * It depends on golang-1.23-go at build time, which is available on jammy-updates.
  * A certain level of downgrades was necessary for focal, that requires golang-1.22-go.
  * Ubuntu Pro for WSL relies on this service being seeded on the Ubuntu instances.
  * That system is not yet generally available, but planned for later this year.
  * At minimum Jammy and Noble must be supported, but Focal is planned.
  * Beta customers were already provided with custom images of 22.04 and 24.04 from the get-go.
  * As a new daemon, more often inert if the Windows side is not present, this should not affect users experience.
  * Boot time measurements reveals negligible impact.
  * The systemd unit is carefully and purposefully confined to allow only minimum requirements of our application while remaining compatible with systemd v245 (thus, compatible with Jammy and Focal).

  [ Test plan ]

  == 1. Less loging:

  * Make sure the Ubuntu Pro for WSL Windows agent is not running:
    - On Windows run `taskkill /f /im ubuntu-pro-agent.exe`
    - Depending on the OS settings elevated permissions might be required.
  * Install wsl-pro-service version 0.1.18 on Ubuntu 22.04 on WSL.
  * Follow it's journal with `journalctl -f -u wsl-pro.service`
  * Notice that it starts logging connection attempts too often, backing off exponentially up to 1min interval.
    Approximately 10 minutes after attempting to connect without success, it silents.
  * systemd should take approximately 20 min to attempt to restart the unit.

  == 2. Pro attachment works under systemd restrictions and without
  livepatch being installed.

  (Most of this test case would be testing ubuntu-pro-client v35 indeed, but we must verify that our integration
  is not harmed with the changes in wsl-pro-service systemd confinement)

  * Create a fresh instance of Ubuntu on WSL:
    - On Windows run `wsl.exe --install -d Ubuntu-22.04`
  * Install ubuntu-pro-agent v35 (currently available via the `-proposed` repository)
  * Make sure livepatch is not installed: `sudo snap remove canonical-livepatch`
  * Make sure the Ubuntu on WSL instance is not pro attached: `pro status` (`pro detach` if needed).
  * Install wsl-pro-service version 0.1.18 on Ubuntu on WSL (Noble, Oracular and Plucky should behave exactly
  the same)
  * Install Ubuntu Pro for WSL (download the latest production build from https://github.com/canonical/ubuntu-pro-for-wsl/actions/runs/14386282882/artifacts/2921576467)
  * Follow this guide to attach your Pro token: https://documentation.ubuntu.com/wsl/en/stable/tutorials/getting-started-with-up4w/#set-up-ubuntu-pro-for-wsl
  * Follow it's journal with `journalctl -f -u wsl-pro.service`:
    - If pro-attaching fails because of systemd restrictions we should see some "permission denied" or "bad system
    call" errors in the journal.
    - If the livepatch fix was not correct, we should see mentions to `canonical-livepatch` in the journal.
    - Both conditions should be considered a failure. Otherwise, proceed.
  * Confirm pro attachment `pro status` inside the Ubuntu instance.
  * Finally assert that canonical-livepatch remains not installed on this machine.

  == 3. wsl-pro-service outside of WSL

  (Ensures the unit does nothing outside of WSL)

  * Install wsl-pro-service on an instance of Ubuntu 22.04 on any platform other than WSL (Desktop,
  Server bare-metal or VM, OCI containers).
  * Verify that the unit is disabled due unmet condition: `systemctl status wsl-pro.service`

  == 4. Boot time

  (Ensures the unit does not significantly impact the boot time duration)
  * Install wsl-pro-service on an Ubuntu 22.04 instance on WSL.
  * Modify the default user's .bashrc to just exit (by appending `exit` as the last line of that script)
  * On Windows PowerShell run `wsl --terminate Ubuntu-22.04; Measure-Command {wsl -d Ubuntu-22.04}` a few times and take notes of the duration that command takes to finish
  * Start the WSL instance as root `wsl -d Ubuntu-22.04 -u root`
  * Remove wsl-pro-service
  * Repeat the measurement step
  * Compare the results.

  Spot differences are expected, because of the many layers involved,
  but there should not be more than 2% difference in **median** between
  boot times with and without that service enabled, per recent
  measurements taken by our team.

  [ Where problems could occur ]

  The few beta customers we have might have noticed that up until now, wsl-pro-service remains running all the time the unit is alive, thus anytime a user installs the
  Ubuntu Pro for WSL application on Windows they could expect the communication with the Windows agents to start
  briefly. That's also the case for the custom 22.04 images they've been playing with, which come with wsl-pro-service 0.1.5.

  With the behaviour changes in v0.1.18, that won't be the case always, as the service could just had quit seconds before
  and systemd will take about 20min to restart it. Users can always `sudo systemctl restart wsl-pro.service`.

  Since the entire system is not yet generally available the number of users affected by this behaviour change
  is very minimal, comprising of a handful of beta testers and internal collaborators (such as the
  Landscape team).

  
  [ Other Info ]

  I intentionally skipped testing the changes related to Landscape because it's too complex to set up a server
  just for this purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2107145/+subscriptions



From 2124239 at bugs.launchpad.net  Fri Oct 17 13:39:40 2025
From: 2124239 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 13:39:40 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176070838064.727349.5907057418278384828.malone@juju-98d295-prod-launchpad-7>

-> Then Version snapd - 2.72+ubuntu25.10.1 again required tiny patch to
fix a seccomp related test issue.

This also of course applies to the 26.04.1 change and both of these
should have that mentioned in the changelog as the code usually is
exactly the same and only the changelog differs.

** Changed in: snapd (Ubuntu Questing)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-questing

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 17 13:40:19 2025
From: 2124239 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 13:40:19 -0000
Subject: [Bug 2124239] Please test proposed package
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176070841967.727300.9486102050216558034.malone@juju-98d295-prod-launchpad-7>

Hello Ernest, or anyone else affected,

Accepted snapd into questing-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/snapd/2.72+ubuntu25.10.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-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. 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: snapd (Ubuntu Plucky)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-plucky

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 17 13:42:35 2025
From: 2124239 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 13:42:35 -0000
Subject: [Bug 2124239] Please test proposed package
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176070855588.357340.11724312247524005354.malone@juju-98d295-prod-launchpad-3>

Hello Ernest, or anyone else affected,

Accepted snapd into plucky-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/snapd/2.72+ubuntu25.04
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-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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: snapd (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-noble

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 17 13:44:49 2025
From: 2124239 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 13:44:49 -0000
Subject: [Bug 2124239] Please test proposed package
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176070868925.734893.14490463849371691084.malone@juju-98d295-prod-launchpad-7>

Hello Ernest, or anyone else affected,

Accepted snapd into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/snapd/2.72+ubuntu24.04
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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: snapd (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 17 13:47:42 2025
From: 2124239 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 13:47:42 -0000
Subject: [Bug 2124239] Please test proposed package
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176070886239.372327.13288720845574572198.malone@juju-98d295-prod-launchpad-3>

Hello Ernest, or anyone else affected,

Accepted snapd into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/snapd/2.72+ubuntu22.04
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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2124239

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 17 13:48:38 2025
From: 2124239 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 13:48:38 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176070891896.748454.9413806455069225878.malone@juju-98d295-prod-launchpad-7>

-> Then Version snapd - 2.72+ubuntu25.10.1 again required tiny patch to
fix a seccomp related test issue.

Please ensure that going forward, tarballs have no different content
outside of debian/. snapd is a native package at this point purely for
some obscure technical reasons, but that's no reason to take advantage
of it: the upstream portions should be the same across all releases.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2060730 at bugs.launchpad.net  Fri Oct 17 13:58:44 2025
From: 2060730 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 13:58:44 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176070952424.388780.4760312837552593437.malone@juju-98d295-prod-launchpad-3>

Hello Dave, or anyone else affected,

Accepted packagekit into questing-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/packagekit/1.3.1-1ubuntu1 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-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. 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: packagekit (Ubuntu Questing)
       Status: In Progress => Fix Committed

** Tags removed: verification-failed
** Tags added: verification-needed verification-needed-questing

** Changed in: packagekit (Ubuntu Plucky)
       Status: In Progress => Fix Committed

** Tags removed: verification-failed-plucky
** Tags added: verification-needed-plucky

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  In Progress
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  Fix Committed
Status in packagekit source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2060730 at bugs.launchpad.net  Fri Oct 17 14:00:22 2025
From: 2060730 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 14:00:22 -0000
Subject: [Bug 2060730] Please test proposed package
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176070962260.763334.16256944522849870630.malone@juju-98d295-prod-launchpad-7>

Hello Dave, or anyone else affected,

Accepted packagekit into plucky-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.3.0-3ubuntu0.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-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2060730

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  In Progress
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  Fix Committed
Status in packagekit source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2060730 at bugs.launchpad.net  Fri Oct 17 14:08:28 2025
From: 2060730 at bugs.launchpad.net (Julian Andres Klode)
Date: Fri, 17 Oct 2025 14:08:28 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176071010891.157541.5795537132824594759.malone@juju-98d295-prod-launchpad-2>

Hello Dave, or anyone else affected,

Accepted packagekit into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.2.8-2ubuntu1.4 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: packagekit (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags removed: verification-failed-noble
** Tags added: verification-needed-noble

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  Fix Committed
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  Fix Committed
Status in packagekit source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2126559 at bugs.launchpad.net  Fri Oct 17 15:52:56 2025
From: 2126559 at bugs.launchpad.net (Thibault Ferrante)
Date: Fri, 17 Oct 2025 15:52:56 -0000
Subject: [Bug 2126559] Re: Missing usb/host/xhci-pci-renesas kernel module in
 the initramfs
References: <175931583063.1368946.9154850780421681274.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176071637717.324632.2528505033216713571.launchpad@juju-98d295-prod-launchpad-2>

** Changed in: initramfs-tools (Ubuntu Noble)
       Status: In Progress => New

** Changed in: initramfs-tools (Ubuntu Noble)
       Status: New => Confirmed

** Changed in: initramfs-tools (Ubuntu Plucky)
       Status: In Progress => Confirmed

** Changed in: initramfs-tools (Ubuntu Noble)
     Assignee: Thibault Ferrante (thibf) => (unassigned)

** Changed in: initramfs-tools (Ubuntu Plucky)
     Assignee: Thibault Ferrante (thibf) => (unassigned)

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

Title:
  Missing usb/host/xhci-pci-renesas kernel module in the initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Noble:
  Confirmed
Status in initramfs-tools source package in Plucky:
  Confirmed
Status in initramfs-tools source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

   * Unable to boot from usb for specific intel hardware (GNR)
   * Especially an issue for ubuntu ISO.

  [ Fix ]

   * As done for questing, whitelist the missing module to be included in the initramfs.
   * This is a similar fix that what was done by dracut [1].

  [ Test Plan ]

   * Build an initramfs with initramfs-tools updated and check that
  drivers/usb/host/xhci-pci-renesas.ko.zst has been included

  [ Where problems could occur ]

   * Increase slightly size of the initramfs.

  [ Other info ]

   * Checked for other missing usb drivers in dracut code, nothing is
  coming up.

  1: https://github.com/dracut-ng/dracut-ng/commit/20cc20d2ac9c2908da6735b04dba49c1cb1b0bab
  __________
  On specific intel hardware (GNR), the Ubuntu ISO 24.04.3 doesn't boot when selecting the hwe kernel.
  After looking at the initrd generated, the hwe-initrd is missing kernel/drivers/usb/host/xhci-pci-renesas.ko.zst:

  $ lsinitramfs casper/initrd | grep kernel/drivers/usb/host/
  usr/lib/modules/6.8.0-71-generic/kernel/drivers/usb/host/xhci-pci-renesas.ko.zst
  usr/lib/modules/6.8.0-71-generic/kernel/drivers/usb/host/xhci-pci.ko.zst
  usr/lib/modules/6.8.0-71-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko.zst
  $ lsinitramfs casper/hwe-initrd | grep kernel/drivers/usb/host/
  usr/lib/modules/6.14.0-27-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko.zst

  xhci-pci module is also not there as it's in 6.14 a builtin.

  As depmod is used to find dependencies across modules, I guess it is
  missing dependencies for builtins.

  In 6.8.0 we can find in the associated modules.dep:
  kernel/drivers/usb/host/xhci-pci.ko.zst: kernel/drivers/usb/host/xhci-pci-renesas.ko.zst
  But it's not the case in 6.14.0.

  Related bug:
  - https://bugs.launchpad.net/cisco-ucs-server/+bug/2121594
  - https://bugs.launchpad.net/ubuntu/+bug/2124218

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2126559/+subscriptions



From 2060730 at bugs.launchpad.net  Fri Oct 17 20:28:53 2025
From: 2060730 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Fri, 17 Oct 2025 20:28:53 -0000
Subject: [Bug 2060730] Autopkgtest regression report
 (packagekit/1.3.1-1ubuntu1)
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <20251017202853.B9C9AFC130@ubuntu-archive-toolbox.internal>

All autopkgtests for the newly accepted packagekit (1.3.1-1ubuntu1) for questing have finished running.
The following regressions have been reported in tests triggered by the package:

deja-dup/49.0-1ubuntu1 (s390x)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/questing/update_excuses.html#packagekit

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  Fix Committed
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  Fix Committed
Status in packagekit source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2123886 at bugs.launchpad.net  Fri Oct 17 21:28:20 2025
From: 2123886 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 17 Oct 2025 21:28:20 -0000
Subject: [Bug 2123886] [NEW] Add missing ARM-cores to support Vera-based
 systems 
References: <175797801894.3652365.4625127746591030660.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176073650029.1106354.7091797466384810370.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Zachary Raines (raineszm):

[Impact]

When running "lscpu" on a Vera-based system, it doesn't report a model
name:

Vendor ID: ARM
Model: 0

[Fix]

Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
problem. The commit below adds the specific codes missing from Noble's
(and previous) versions.

https://github.com/util-linux/util-
linux/commit/908777470d403ec30c525472ba0d3701c9c5a223

[Test Steps]

* Verify whether output of lscpu is correct on new CPUs; eg:
Vendor ID: ARM
Model name: Olympus

* Verify whether output of lscpu doesn't change on old CPUs; eg:
Vendor ID: ARM
Model name: Neoverse-N1

[What Could Go Wrong]

The fix only introduces additional model identifiers to match
against and print a model name string, thus regression impact
should be contained within lscpu and printing cpus model name
on ARM systems.

Output doesn't change on systems with non-affected CPU models.

** Affects: util-linux (Ubuntu)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: In Progress

** Affects: util-linux (Ubuntu Noble)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: In Progress

** Affects: util-linux (Ubuntu Plucky)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: In Progress

** Affects: util-linux (Ubuntu Questing)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: In Progress

** Affects: util-linux (Ubuntu Resolute)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: In Progress


** Tags: se-sponsors
-- 
Add missing ARM-cores to support Vera-based systems 
https://bugs.launchpad.net/bugs/2123886
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2124239 at bugs.launchpad.net  Fri Oct 17 21:43:25 2025
From: 2124239 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Fri, 17 Oct 2025 21:43:25 -0000
Subject: [Bug 2124239] Autopkgtest regression report (snapd/2.72+ubuntu24.04)
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <20251017214325.C8079FC135@ubuntu-archive-toolbox.internal>

All autopkgtests for the newly accepted snapd (2.72+ubuntu24.04) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io-app/28.2.2-0ubuntu1~24.04.1 (amd64, arm64, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#snapd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 17 22:56:04 2025
From: 2124239 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Fri, 17 Oct 2025 22:56:04 -0000
Subject: [Bug 2124239] Autopkgtest regression report (snapd/2.72+ubuntu22.04)
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <20251017225604.8490AFC138@ubuntu-archive-toolbox.internal>

All autopkgtests for the newly accepted snapd (2.72+ubuntu22.04) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io-app/28.2.2-0ubuntu1~22.04.1 (amd64, ppc64el, s390x)
livecd-rootfs/2.765.55 (amd64)
systemd/249.11-0ubuntu3.17 (amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#snapd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Fri Oct 17 23:15:41 2025
From: 2124239 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Fri, 17 Oct 2025 23:15:41 -0000
Subject: [Bug 2124239] Autopkgtest regression report (snapd/2.72+ubuntu25.10.2)
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <20251017231541.EA7F6FC131@ubuntu-archive-toolbox.internal>

All autopkgtests for the newly accepted snapd (2.72+ubuntu25.10.2) for questing have finished running.
The following regressions have been reported in tests triggered by the package:

linux-realtime/6.17.0-1002.3 (amd64)
livecd-rootfs/25.10.24 (arm64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/questing/update_excuses.html#snapd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Sat Oct 18 00:15:52 2025
From: 2124239 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Sat, 18 Oct 2025 00:15:52 -0000
Subject: [Bug 2124239] Autopkgtest regression report (snapd/2.72+ubuntu25.04)
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <20251018001552.D06F1FC18E@ubuntu-archive-toolbox.internal>

All autopkgtests for the newly accepted snapd (2.72+ubuntu25.04) for plucky have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io-app/28.2.2-0ubuntu1~25.04.1 (amd64, arm64, ppc64el, s390x)
systemd/257.4-1ubuntu3.2 (amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/plucky/update_excuses.html#snapd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2117339 at bugs.launchpad.net  Sat Oct 18 07:15:49 2025
From: 2117339 at bugs.launchpad.net (Jaromir Obr)
Date: Sat, 18 Oct 2025 07:15:49 -0000
Subject: [Bug 2117339] Re: [nvidia] Software rendering in GNOME Shell Wayland
 sessions
References: <175301674770.266547.6964628150134918072.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176077174911.2259851.8989026119378957829.malone@juju-98d295-prod-launchpad-7>

As a workaround, install the driver from the repo "ppa:graphics-drivers/ppa". Tested with ver. 580. Then "libnvidia-egl-wayland1 1.1.17" will be installed and HW rendering should work.
Another alternative is installation of nVidia driver from https://www.nvidia.com/en-us/drivers/

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

Title:
  [nvidia] Software rendering in GNOME Shell Wayland sessions

Status in egl-wayland package in Ubuntu:
  Fix Released
Status in egl-wayland source package in Noble:
  In Progress
Status in egl-wayland source package in Plucky:
  Fix Released
Status in egl-wayland source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

  In Ubuntu 24.04 the NVIDIA drivers 570 or newer break the
  EGL_PLATFORM_WAYLAND_EXT extension, preventing most graphical
  applications from using OpenGL in a Wayland session.

  The libnvidia-egl-wayland.so.1 library implementing the
  EGL_PLATFORM_WAYLAND_EXT extension has an incorrect version check
  which makes it refuse to load on the newer NVIDIA drivers.

  This was fixed upstream by: https://github.com/NVIDIA/egl-
  wayland/pull/106

  [ Test Plan ]

  1. Set up Ubuntu 24.04 on a machine with an NVIDIA GPU
  1. Install an affected NVIDIA driver:
     $ sudo apt install nvidia-driver-570
  2. Install the update with:
     $ sudo apt install -t noble-proposed libnvidia-egl-wayland1
  2. Log in to "Ubuntu on Wayland"
  3. Run in a terminal:
     $ eglinfo -B -p wayland
     Verify that it prints information about your NVIDIA card and driver
  4. Open Settings > System > Info > Details
  5. Verify that it detects your NVIDIA GPU.

  [ Regression Test Plan ]

  Perform the same steps as the main Test Plan, but using an older NVIDIA driver:
  $ sudo apt install nvidia-driver-550

  [ Where problems could occur ]

  The change inverts a version check, so there is a risk that the older
  NVIDIA drivers the used to be working will stop working. The [
  Regression Test Plan ] verifies that this is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2117339/+subscriptions



From 2128879 at bugs.launchpad.net  Sat Oct 18 08:37:36 2025
From: 2128879 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 18 Oct 2025 08:37:36 -0000
Subject: [Bug 2128879] [NEW] Sync racket-mode 20251013~git.b9a4f51-1
 (universe) from Debian unstable (main)
References: <176077665354.2356837.17878975205460634294.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176077665637.1994851.119771061976400123.launchpad@juju-98d295-prod-launchpad-3>

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

Please sync racket-mode 20251013~git.b9a4f51-1 (universe) from Debian
unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * d/control: change Build-Depends to use libjpeg-dev instead of
    libjpeg62-turbo-dev (LP: #2117522).
  * d/control: change Build-Depends to use libjpeg-dev instead of
    libjpeg62-turbo-dev (LP: #2117522).

The Debian package has switch build dependency to libjpeg-dev as well


Changelog entries since current resolute version 20250501~git.2eec63c-1ubuntu1:

racket-mode (20251013~git.b9a4f51-1) unstable; urgency=medium

  * Update to new upstream version 20251013~git.b9a4f51.
  * Drop "Rules-Requires-Root: no"
    - This has been the default since dpkg 1.22.13.

 -- Xiyue Deng <manphiz at gmail.com>  Fri, 17 Oct 2025 00:52:15 -0700

racket-mode (20250830~git.f3952cd-1) unstable; urgency=medium

  * Update to new upstream version 20250830~git.f3952cd.

 -- Xiyue Deng <manphiz at gmail.com>  Thu, 11 Sep 2025 00:06:56 -0700

racket-mode (20250828~git.172b7d4-1) unstable; urgency=medium

  * Update to new upstream version 20250828~git.172b7d4.
  * Migrate d/watch to rfc822-style version 5 foramt
  * Drop custom autopkgtest handling
    - The intension was to skip architectures that fails the tests, but
      that didn't work for arch:all package, so there is no advantage over
      autopkgtest-pkg-elpa at all.
    - Re-enable autopkgtest-pkg-elpa in d/control.

 -- Xiyue Deng <manphiz at gmail.com>  Sun, 31 Aug 2025 00:14:57 -0700

racket-mode (20250711~git.8a80578-1) unstable; urgency=medium

  [ Xiyue Deng ]
  * Update to new upstream version 20250711~git.8a80578.

  [ Ural Tunaboyu ]
  * d/control: change Build-Depends to use libjpeg-dev instead of
    libjpeg62-turbo-dev.
     - Ubuntu does not have libjpeg62-turbo-dev but instead uses
       libjpeg-turbo8-dev to provide the libjpeg-dev virtual package. Use
       the more general package to avoid build failures.

 -- Xiyue Deng <manphiz at gmail.com>  Thu, 14 Aug 2025 23:23:22 -0700

** Affects: racket-mode (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync racket-mode 20251013~git.b9a4f51-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/2128879
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2128880 at bugs.launchpad.net  Sat Oct 18 08:39:41 2025
From: 2128880 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 18 Oct 2025 08:39:41 -0000
Subject: [Bug 2128880] [NEW] Sync python-aiowebostv 0.4.2-3 (universe) from
 Debian unstable (main)
References: <176077677871.1994945.3545045479656113219.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176077678131.1725127.8925039451915934143.launchpad@juju-98d295-prod-launchpad-2>

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

Please sync python-aiowebostv 0.4.2-3 (universe) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Fix typo in runtime dependency name preventing migration.
  * Fix typo in runtime dependency name preventing migration.
  * Fix typo in runtime dependency name preventing migration.

The dependency typo is fixed in the Debian package as well.


Changelog entries since current resolute version 0.4.2-2ubuntu1:

python-aiowebostv (0.4.2-3) unstable; urgency=medium

  [ Ciel Zhao ]
  * Fix dependency typo.

  [ Tianyu Chen ]
  * Add myself to Uploaders.
  * Add d/salsa-ci.yml.
  * Update d/watch to version 5.
  * Use Github template in d/watch.

 -- Tianyu Chen <billchenchina2001 at gmail.com>  Sat, 30 Aug 2025 17:10:44
+0800

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

-- 
Sync python-aiowebostv 0.4.2-3 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/2128880
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2128881 at bugs.launchpad.net  Sat Oct 18 08:48:27 2025
From: 2128881 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 18 Oct 2025 08:48:27 -0000
Subject: [Bug 2128881] [NEW] Sync stegseek 0.6+git20210910.ff677b9-2
 (universe) from Debian unstable (main)
References: <176077730510.2002076.6576041745009546915.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176077730729.1736956.4298264334095984299.launchpad@juju-98d295-prod-launchpad-2>

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

Please sync stegseek 0.6+git20210910.ff677b9-2 (universe) from Debian
unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
  * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
  * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
  * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
  * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
  * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev

The Debian package changed the build dependency to libjpeg-dev. Note
that this is a different change than the current Ubuntu patch, but from
my understanding the "generic" libjpeg-dev package is provided by the
versioned 62 package in Debian and the versioned 8 package in Ubuntu. So
I believe this replacement should work both places. :)


Changelog entries since current resolute version 0.6+git20210910.ff677b9-1ubuntu1:

stegseek (0.6+git20210910.ff677b9-2) unstable; urgency=medium

  * Team upload.
  * d/control:
    - Build-Depends: libjpeg62-turbo-dev -> libjpeg-dev (Closes: #1089021)
    - Drop 'Rules-Requires-Root: no', it's the standard now.
    - Bump Standards-Version to 4.7.2.
  * d/watch: Convert watch file to version 5 format.
  * d/copyright: Update copyright holders regarding Debian packaging.

 -- Sven Geuer <sge at debian.org>  Fri, 03 Oct 2025 21:44:40 +0200

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

-- 
Sync stegseek 0.6+git20210910.ff677b9-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/2128881
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2115895 at bugs.launchpad.net  Sun Oct 19 14:41:13 2025
From: 2115895 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 19 Oct 2025 14:41:13 -0000
Subject: [Bug 2115895] [NEW] jetty12 fails to build due to unmet build
 dependencies
References: <175154522252.2001127.16494622969851328446.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176088487334.2303379.15884120369345746488.launchpad@juju-98d295-prod-launchpad-4>

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

jetty12 12.0.17-3 currently fails to build on Ubuntu Questing due to two
unmet build dependencies: libjakarta-standard-taglib-api-java,
libjakarta-standard-taglib-impl-java. [1]

Both packages are built from the source package jakarta-standard-taglib
which looks like it was removed in Plucky due to other missing build
dependencies [2].

As a test, I tried rebuilding first jakarta-standard-taglib then jetty12
on a Questing VM. Both packages built successfully. So presumably, if
jakarta-standard-taglib is resynced or rebuilt in Questing it would make
both packages available in the archive.


[1] https://launchpad.net/ubuntu/+source/jetty12/12.0.17-3/+build/30679554
[2] https://launchpad.net/ubuntu/+source/jakarta-standard-taglib/+publishinghistory

** Affects: jakarta-standard-taglib (Ubuntu)
     Importance: Undecided
         Status: New

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


** Tags: ftbfs questing resolute
-- 
jetty12 fails to build due to unmet build dependencies
https://bugs.launchpad.net/bugs/2115895
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2115895 at bugs.launchpad.net  Sun Oct 19 14:41:25 2025
From: 2115895 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Sun, 19 Oct 2025 14:41:25 -0000
Subject: [Bug 2115895] Re: jetty12 fails to build due to unmet build
 dependencies
References: <175154522252.2001127.16494622969851328446.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176088488581.3997747.1947290036112565892.malone@juju-98d295-prod-launchpad-2>

Tried again with a Resolute VM and both still builds sucessfully (at
least on amd64). So my theory is if jakarta-standard-taglib was "synced"
or reintroduced to the archive since there's no newer version, the
dependency wait would resolve itself. Must admit I don't quite know how
to proceed on that so I'll try to subscribe ubuntu-sponsors similar to
other syncs. (Let me know if I should try to contact archive admins
instead :) )

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

Title:
  jetty12 fails to build due to unmet build dependencies

Status in jakarta-standard-taglib package in Ubuntu:
  New
Status in jetty12 package in Ubuntu:
  New

Bug description:
  jetty12 12.0.17-3 currently fails to build on Ubuntu Questing due to
  two unmet build dependencies: libjakarta-standard-taglib-api-java,
  libjakarta-standard-taglib-impl-java. [1]

  Both packages are built from the source package jakarta-standard-
  taglib which looks like it was removed in Plucky due to other missing
  build dependencies [2].

  As a test, I tried rebuilding first jakarta-standard-taglib then
  jetty12 on a Questing VM. Both packages built successfully. So
  presumably, if jakarta-standard-taglib is resynced or rebuilt in
  Questing it would make both packages available in the archive.

  
  [1] https://launchpad.net/ubuntu/+source/jetty12/12.0.17-3/+build/30679554
  [2] https://launchpad.net/ubuntu/+source/jakarta-standard-taglib/+publishinghistory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jakarta-standard-taglib/+bug/2115895/+subscriptions



From 2122576 at bugs.launchpad.net  Mon Oct 20 08:32:05 2025
From: 2122576 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 20 Oct 2025 08:32:05 -0000
Subject: [Bug 2122576] [NEW] Add support Intel PTL platform and ITMT3.0 policy
References: <175758076411.1792167.10087975254811915865.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176094912592.1901593.1867750498740236938.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Kai-Chuan Hsieh (kchsieh):

[ Impact ]

 * The thermald will not be active on Intel PTL platform.

 * The thermald still use passive policy for the platform with ITMI3
configured.

[ Test Plan ]

 * On Intel PTL platform with ITMT3.0 policy configured

 * Boot into Ubuntu

 * Stop the default thermald by $ sudo systemctl stop thermald

 * run the thermlad with extra parameter $ sudo thermald --systemd
--dbus-enable --adaptive --log-level=info

 * check the journalctl log to confirm that thermald apply the policy
successfully

1. Make sure to see ITMT3.0 policy defined in the APAT table
[1754988644][INFO]..apat dump begin..
[1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
[1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
[1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
[1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
[1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
[1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance

2. Check that ITMT3 policy is applied
[1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance

[ Where problems could occur ]

 * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
   If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.

 *
https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
enhance the support for the ITMT3.0 policy. No code logic change for
ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
change the thermal behavior.

[ Other Info ]

 * ITMT stands for Intel Turbo Boost Max Technology, a feature that
identifies the best-performing cores on a processor and directs
workloads to them for increased single-threaded performance. This
technology assigns a higher priority to the fastest cores, ensuring that
demanding tasks get the maximum possible speed on those select cores,
while other cores handle less intensive work or remain idle. The
advantage of ITMT3 can be found in The advantage of ITMT3 can be found
in https://edc.intel.com/content/www/us/en/design/ipla/software-
development-platforms/client/platforms/alder-lake-desktop/12th-
generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
turbo-boost-max-technology-3-0/.

 * Upstream commits:
   https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
   https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
   https://github.com/intel/thermal_daemon/commit/352125763b8f9866cd9318c1c2a70a5dcf841b20

 * extra commit for noble to add PTL support.
   https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
   another 2 commits for noble combined into 1 patch
   https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
   https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659

 * According to Dell architect yijun.shen at dell.com, there is no
certified Dell platform has ITMI3 configured, it will only be available
on the coming PTL platform.

** Affects: oem-priority
     Importance: Undecided
     Assignee: Kai-Chuan Hsieh (kchsieh)
         Status: New

** Affects: thermald (Ubuntu)
     Importance: Undecided
     Assignee: Kai-Chuan Hsieh (kchsieh)
         Status: New


** Tags: jira-somerville-1991 jira-somerville-2753 oem-priority
-- 
Add support Intel PTL platform and ITMT3.0 policy
https://bugs.launchpad.net/bugs/2122576
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2122576 at bugs.launchpad.net  Mon Oct 20 08:33:03 2025
From: 2122576 at bugs.launchpad.net (Kai-Chuan Hsieh)
Date: Mon, 20 Oct 2025 08:33:03 -0000
Subject: [Bug 2122576] Re: Add support Intel PTL platform and ITMT3.0 policy
References: <175758076411.1792167.10087975254811915865.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176094918320.1243973.12761196673313923027.malone@juju-98d295-prod-launchpad-2>

@schopin

Hello,

I have re-upload the debdiff, could you help to review and sponsor it?

Thanks,

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

Title:
  Add support Intel PTL platform and ITMT3.0 policy

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * The thermald will not be active on Intel PTL platform.

   * The thermald still use passive policy for the platform with ITMI3
  configured.

  [ Test Plan ]

   * On Intel PTL platform with ITMT3.0 policy configured

   * Boot into Ubuntu

   * Stop the default thermald by $ sudo systemctl stop thermald

   * run the thermlad with extra parameter $ sudo thermald --systemd
  --dbus-enable --adaptive --log-level=info

   * check the journalctl log to confirm that thermald apply the policy
  successfully

  1. Make sure to see ITMT3.0 policy defined in the APAT table
  [1754988644][INFO]..apat dump begin..
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance

  2. Check that ITMT3 policy is applied
  [1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance

  [ Where problems could occur ]

   * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.

   *
  https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  enhance the support for the ITMT3.0 policy. No code logic change for
  ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
  change the thermal behavior.

  [ Other Info ]

   * ITMT stands for Intel Turbo Boost Max Technology, a feature that
  identifies the best-performing cores on a processor and directs
  workloads to them for increased single-threaded performance. This
  technology assigns a higher priority to the fastest cores, ensuring
  that demanding tasks get the maximum possible speed on those select
  cores, while other cores handle less intensive work or remain idle.
  The advantage of ITMT3 can be found in The advantage of ITMT3 can be
  found in https://edc.intel.com/content/www/us/en/design/ipla/software-
  development-platforms/client/platforms/alder-lake-desktop/12th-
  generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
  turbo-boost-max-technology-3-0/.

   * Upstream commits:
     https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
     https://github.com/intel/thermal_daemon/commit/352125763b8f9866cd9318c1c2a70a5dcf841b20

   * extra commit for noble to add PTL support.
     https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
     another 2 commits for noble combined into 1 patch
     https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
     https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659

   * According to Dell architect yijun.shen at dell.com, there is no
  certified Dell platform has ITMI3 configured, it will only be
  available on the coming PTL platform.

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



From 2129012 at bugs.launchpad.net  Mon Oct 20 08:52:07 2025
From: 2129012 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 20 Oct 2025 08:52:07 -0000
Subject: [Bug 2129012] [NEW] Sync elinks 0.18.0-1 (universe) from Debian sid
 (main)
References: <176095032577.1270725.8130093536412882514.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176095032814.1926470.6848452108839832819.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Oibaf (oibaf):

Please sync elinks 0.18.0-1 (universe) from Debian sid (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * No-change rebuild for libperl soname.
  * No-change rebuild for libperl soname.
  * No-change rebuild for libperl soname.
  * No-change rebuild for CVE-2024-3094
  * No-change rebuild for CVE-2024-3094
  * No-change rebuild for CVE-2024-3094
  * No-change rebuild for perlapi5.38t64.
  * Merge with Debian; remaining changes:
    - d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
      and arm64 failures leading to FTBFS issues in Ubuntu builders.
  * Non-maintainer upload.
  * Fix "FTBFS with Perl 5.38: error: redefinition of 'struct object'":
    add patch from upstream pull request/commit.
    (Closes: #1042844)
  * d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
    and arm64 failures leading to FTBFS issues in Ubuntu builders.
  * d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
    and arm64 failures leading to FTBFS issues in Ubuntu builders.
  * Rebuild against new perlapi-5.36.
  * Rebuild against new perlapi-5.36.
  * No-change rebuild for the perl update.
  * No-change rebuild for the perl update.
  * No-change rebuild for the perl update.
  * No-change rebuild against libidn12
  * No-change rebuild for the perl update.
  * No-change rebuild for the perl update.
  * No-change rebuild for the perl update.

Explanation:
According to Ubuntu changelog the only useful change looks the d/p/increase-test-timeout.diff patch (no idea if it can be dropped).
The Fix "FTBFS with Perl 5.38: error: redefinition of 'struct object'": is also in Debian.

Changelog entries since current resolute version 0.16.1.1-4.1ubuntu4:

elinks (0.18.0-1) unstable; urgency=medium

  * New upstream version 0.18.0
  * Refreshed patch: 03_459467_ui.leds.enable_0.diff
  * Add fix-libdomdeps.patch to fix default value of libdomdeps to an empty
    list instead of false
  * Added define_SOCKS_SHIFT.patch to add missing definition for SOCKS_SHIFT

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Sun, 29 Dec 2024 18:40:32 +0100

elinks (0.17.1.1-2) unstable; urgency=medium

  * d/rules: disable unicode combining characters (Closes: #1089693)

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Sat, 21 Dec 2024 15:35:18 +0100

elinks (0.17.1.1-1) unstable; urgency=medium

  * New upstream version 0.17.1.1
  * Refreshed 14_debug_disable_Werror.diff patch
  * Remove fix_nonascii_inpfield.patch, applied upstream
  * Remove fix-protocol-test.patch, applied upstream
  * d/control:
    + bump standards version to 4.7.0
    + prettify build-deps list
  * Enable python hooks.
    Thanks to Dimitry Ishenko

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Fri, 06 Dec 2024 18:14:16 +0100

elinks (0.17.0-2) unstable; urgency=medium

  * Add fix_nonascii_inpfield.patch to fix a bug with input fields not
    accepting non-ASCII input.

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Fri, 26 Jul 2024 04:29:19 +0200

elinks (0.17.0-1) unstable; urgency=medium

  * New upstream version 0.17.0
  * Dropped patches applied upstream: fix-mailcap-test.diff & perl_5.38.patch
  * Refresh patches: 07_617713_cache_control.diff,
    14_debug_disable_Werror.diff
  * Added fix-protocol-test.patch to fix path for protocol.c test
  * d/rules:
    + remove sysconfdir setting (Closes: #1040656)
    + disable libcss support
    + fix typo
  * Update copyright years
  * d/control:
    + update build deps libidn-dev -> libidn2-dev
    + add libcurl4-gnutls-dev to build deps
    + update build-dep: pkg-config -> pkgconf
  * d/elinks-data.docs: README -> README.md
  * d/source.lintian-overrides: add an override for test/data.html
  * d/t/dump: add -no-home when invoking ELinks

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Thu, 11 Jul 2024 18:01:47 +0200

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

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


From 2129025 at bugs.launchpad.net  Mon Oct 20 11:48:26 2025
From: 2129025 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 20 Oct 2025 11:48:26 -0000
Subject: [Bug 2129025] [NEW] New upstream release 3.3.0
References: <176096088894.2192222.6717053874311348856.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176096090727.1831908.12077818582171411461.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Antoine Lassagne (antoinelassagne):

A new release was released upstream, and is now in debian unstable
(3.3.0+dfsg-1).

Could we have it synced with ubuntu?

** Affects: vulkan-memory-allocator (Ubuntu)
     Importance: Undecided
         Status: New

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


From 2127933 at bugs.launchpad.net  Mon Oct 20 12:01:50 2025
From: 2127933 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 20 Oct 2025 12:01:50 -0000
Subject: [Bug 2127933] [NEW] Network status shows ethernet connected when no
 connection is available
References: <176054299488.762979.6399394703797330386.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176096171046.1851135.475502119566108923.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Antoine Lassagne (antoinelassagne):

Per upstream bugs: 
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7357
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8549

And it got fixed with https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/3910

---------------------------
SRU Justification:

[ Impact ]

 * The "ethernet connected" symbol is displayed when no network
connection is available.  If a WiFi connection is available then the
WiFi symbol is displayed and if an Ethernet connection is available then
the Ethernet icon is (correctly) displayed but if neither is available
(WiFi switched off and cable unplugged) then the Ethernet icon is still
displayed.

 * With the above, the reconnection is fixed.

[ Fix ]

 * When there is no active main connection or it uses a device type we do not handle, the indicator icon and its visibility depend on the global connectivity.
 
 * However we currently don't update the icon on connectivity changes, with the result that we sometimes show the fallback connection icon when the network is in fact disconnected.

 * To fix this, update the icon whenever the (global) connectivity
changes.

[ Test Plan ]

 1. Connect to wifi, see the wifi icon

 2. Disconnect wifi from the menubar, see the ethernet icon pops in

 3. Do it again with the fix: no ethernet icon pops in

 4. Reconnect wifi, see the icon transitioning to connecting ->
connected.

[ Where problems could occur ]

 * The _updateIcon is now called more often than before, not less, so
more frequent icon updates can be expected, but only when they are
actually relevant thankfully.

** Affects: gnome-shell
     Importance: Unknown
         Status: New

** Affects: gnome-shell (Ubuntu)
     Importance: Undecided
     Assignee: Antoine Lassagne (antoinelassagne)
         Status: In Progress

-- 
Network status shows ethernet connected when no connection is available
https://bugs.launchpad.net/bugs/2127933
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127933 at bugs.launchpad.net  Mon Oct 20 12:05:06 2025
From: 2127933 at bugs.launchpad.net (Frank Heimes)
Date: Mon, 20 Oct 2025 12:05:06 -0000
Subject: [Bug 2127933] Re: Network status shows ethernet connected when no
 connection is available
References: <176054299488.762979.6399394703797330386.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176096190662.2220743.7354223284142641839.launchpad@juju-98d295-prod-launchpad-7>

** Also affects: gnome-shell (Ubuntu Questing)
   Importance: Undecided
       Status: New

** Also affects: gnome-shell (Ubuntu Resolute)
   Importance: Undecided
     Assignee: Antoine Lassagne (antoinelassagne)
       Status: In Progress

** Also affects: gnome-shell (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Changed in: gnome-shell (Ubuntu Questing)
     Assignee: (unassigned) => Antoine Lassagne (antoinelassagne)

** Changed in: gnome-shell (Ubuntu Noble)
     Assignee: (unassigned) => Antoine Lassagne (antoinelassagne)

** Also affects: gnome-shell (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Changed in: gnome-shell (Ubuntu Plucky)
     Assignee: (unassigned) => Antoine Lassagne (antoinelassagne)

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

Title:
  Network status shows ethernet connected when no connection is
  available

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell source package in Plucky:
  New
Status in gnome-shell source package in Questing:
  New
Status in gnome-shell source package in Resolute:
  In Progress

Bug description:
  Per upstream bugs: 
  - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7357
  - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8549

  And it got fixed with https://gitlab.gnome.org/GNOME/gnome-
  shell/-/merge_requests/3910

  ---------------------------
  SRU Justification:

  [ Impact ]

   * The "ethernet connected" symbol is displayed when no network
  connection is available.  If a WiFi connection is available then the
  WiFi symbol is displayed and if an Ethernet connection is available
  then the Ethernet icon is (correctly) displayed but if neither is
  available (WiFi switched off and cable unplugged) then the Ethernet
  icon is still displayed.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * When there is no active main connection or it uses a device type we do not handle, the indicator icon and its visibility depend on the global connectivity.
   
   * However we currently don't update the icon on connectivity changes, with the result that we sometimes show the fallback connection icon when the network is in fact disconnected.

   * To fix this, update the icon whenever the (global) connectivity
  changes.

  [ Test Plan ]

   1. Connect to wifi, see the wifi icon

   2. Disconnect wifi from the menubar, see the ethernet icon pops in

   3. Do it again with the fix: no ethernet icon pops in

   4. Reconnect wifi, see the icon transitioning to connecting ->
  connected.

  [ Where problems could occur ]

   * The _updateIcon is now called more often than before, not less, so
  more frequent icon updates can be expected, but only when they are
  actually relevant thankfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2127933/+subscriptions



From 2127792 at bugs.launchpad.net  Mon Oct 20 12:09:02 2025
From: 2127792 at bugs.launchpad.net (Frank Heimes)
Date: Mon, 20 Oct 2025 12:09:02 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176096214296.1560859.9929601129843743670.launchpad@juju-98d295-prod-launchpad-2>

** Also affects: gnome-remote-desktop (Ubuntu Plucky)
   Importance: Undecided
       Status: New

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  In Progress
Status in gnome-remote-desktop source package in Noble:
  New
Status in gnome-remote-desktop source package in Plucky:
  New
Status in gnome-remote-desktop source package in Questing:
  New
Status in gnome-remote-desktop source package in Resolute:
  In Progress

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2129032 at bugs.launchpad.net  Mon Oct 20 13:26:32 2025
From: 2129032 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 20 Oct 2025 13:26:32 -0000
Subject: [Bug 2129032] [NEW] [needs-packaging] slang-compiler
References: <176096654830.2341446.10563703781807672575.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176096679251.2344974.3594886547391915269.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Andreas Glinserer (aglinserer):

URL: https://github.com/shader-slang/slang
License: Apache-2.0 WITH LLVM-exception
Notes: Slang is a shading language aiming to make shader codebases mroe maintainable and modular. It also maintians a high performance on modern GPUs and graphic APIs. They aim to rename slang to slang-compiler in order to avoid a naming conflict with s-lang.

I wish to package slang-compiler for Ubuntu.

** Affects: ubuntu
     Importance: Undecided
         Status: New


** Tags: needs-packaging
-- 
[needs-packaging] slang-compiler
https://bugs.launchpad.net/bugs/2129032
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127933 at bugs.launchpad.net  Mon Oct 20 14:04:19 2025
From: 2127933 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 20 Oct 2025 14:04:19 -0000
Subject: [Bug 2127933] Re: Network status shows ethernet connected when no
 connection is available
References: <176054299488.762979.6399394703797330386.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176096906094.224787.11024110776833979264.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~antoinelassagne/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/494697

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

Title:
  Network status shows ethernet connected when no connection is
  available

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell source package in Plucky:
  New
Status in gnome-shell source package in Questing:
  New
Status in gnome-shell source package in Resolute:
  In Progress

Bug description:
  Per upstream bugs: 
  - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7357
  - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8549

  And it got fixed with https://gitlab.gnome.org/GNOME/gnome-
  shell/-/merge_requests/3910

  ---------------------------
  SRU Justification:

  [ Impact ]

   * The "ethernet connected" symbol is displayed when no network
  connection is available.  If a WiFi connection is available then the
  WiFi symbol is displayed and if an Ethernet connection is available
  then the Ethernet icon is (correctly) displayed but if neither is
  available (WiFi switched off and cable unplugged) then the Ethernet
  icon is still displayed.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * When there is no active main connection or it uses a device type we do not handle, the indicator icon and its visibility depend on the global connectivity.
   
   * However we currently don't update the icon on connectivity changes, with the result that we sometimes show the fallback connection icon when the network is in fact disconnected.

   * To fix this, update the icon whenever the (global) connectivity
  changes.

  [ Test Plan ]

   1. Connect to wifi, see the wifi icon

   2. Disconnect wifi from the menubar, see the ethernet icon pops in

   3. Do it again with the fix: no ethernet icon pops in

   4. Reconnect wifi, see the icon transitioning to connecting ->
  connected.

  [ Where problems could occur ]

   * The _updateIcon is now called more often than before, not less, so
  more frequent icon updates can be expected, but only when they are
  actually relevant thankfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2127933/+subscriptions



From 2127792 at bugs.launchpad.net  Mon Oct 20 14:29:17 2025
From: 2127792 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 20 Oct 2025 14:29:17 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176097055869.224787.3630670987708321481.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~antoinelassagne/ubuntu/+source/gnome-remote-desktop/+git/gnome-remote-desktop/+merge/494700

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  In Progress
Status in gnome-remote-desktop source package in Noble:
  New
Status in gnome-remote-desktop source package in Plucky:
  New
Status in gnome-remote-desktop source package in Questing:
  New
Status in gnome-remote-desktop source package in Resolute:
  In Progress

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2117339 at bugs.launchpad.net  Mon Oct 20 17:32:15 2025
From: 2117339 at bugs.launchpad.net (Nick Rosbrook)
Date: Mon, 20 Oct 2025 17:32:15 -0000
Subject: [Bug 2117339] Re: [nvidia] Software rendering in GNOME Shell Wayland
 sessions
References: <175301674770.266547.6964628150134918072.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176098153573.390042.12323696604621211504.malone@juju-98d295-prod-launchpad-4>

I sponsored the upload in the linked PR.

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

Title:
  [nvidia] Software rendering in GNOME Shell Wayland sessions

Status in egl-wayland package in Ubuntu:
  Fix Released
Status in egl-wayland source package in Noble:
  In Progress
Status in egl-wayland source package in Plucky:
  Fix Released
Status in egl-wayland source package in Questing:
  Fix Released

Bug description:
  [ Impact ]

  In Ubuntu 24.04 the NVIDIA drivers 570 or newer break the
  EGL_PLATFORM_WAYLAND_EXT extension, preventing most graphical
  applications from using OpenGL in a Wayland session.

  The libnvidia-egl-wayland.so.1 library implementing the
  EGL_PLATFORM_WAYLAND_EXT extension has an incorrect version check
  which makes it refuse to load on the newer NVIDIA drivers.

  This was fixed upstream by: https://github.com/NVIDIA/egl-
  wayland/pull/106

  [ Test Plan ]

  1. Set up Ubuntu 24.04 on a machine with an NVIDIA GPU
  1. Install an affected NVIDIA driver:
     $ sudo apt install nvidia-driver-570
  2. Install the update with:
     $ sudo apt install -t noble-proposed libnvidia-egl-wayland1
  2. Log in to "Ubuntu on Wayland"
  3. Run in a terminal:
     $ eglinfo -B -p wayland
     Verify that it prints information about your NVIDIA card and driver
  4. Open Settings > System > Info > Details
  5. Verify that it detects your NVIDIA GPU.

  [ Regression Test Plan ]

  Perform the same steps as the main Test Plan, but using an older NVIDIA driver:
  $ sudo apt install nvidia-driver-550

  [ Where problems could occur ]

  The change inverts a version check, so there is a risk that the older
  NVIDIA drivers the used to be working will stop working. The [
  Regression Test Plan ] verifies that this is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2117339/+subscriptions



From 2125407 at bugs.launchpad.net  Mon Oct 20 17:45:26 2025
From: 2125407 at bugs.launchpad.net (Nick Rosbrook)
Date: Mon, 20 Oct 2025 17:45:26 -0000
Subject: [Bug 2125407] Re: New upstream release landed in debian
References: <175854935122.2339268.5514828628887767207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176098232634.417770.3100448572221660327.malone@juju-98d295-prod-launchpad-4>

Any particular reason we need to sync from experimental instead of
waiting for it to land in unstable (and then autosync to Ubuntu)?

** Changed in: glm (Ubuntu)
       Status: New => Incomplete

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

Title:
  New upstream release landed in debian

Status in glm package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  The latest version of this package, from Feb. 2024, landed in debian:

  libglm-dev | 1.0.1+ds-2    | experimental | all

  Could it be synced to ubuntu/devel?

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



From 2118845 at bugs.launchpad.net  Mon Oct 20 17:53:11 2025
From: 2118845 at bugs.launchpad.net (Nick Rosbrook)
Date: Mon, 20 Oct 2025 17:53:11 -0000
Subject: [Bug 2118845] Re: valentina: failing autopkgtest
References: <175361228170.2423805.13457270715638468215.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176098279161.2410301.10870582846597003060.malone@juju-98d295-prod-launchpad-3>

Left questions on the MP. Unsubscribing Ubuntu sponsors for now.

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

Title:
  valentina: failing autopkgtest

Status in valentina package in Ubuntu:
  New
Status in valentina package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1087710:

  Source: valentina
  Version: 0.7.53~dfsg-2
  Severity: serious

  The latest upload of valentina is unable to migrate to Testing because
  its autopkgtests are failing.

  https://qa.debian.org/excuses.php?package=valentina

  Thank you,
  Jeremy Bícha

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



From 2117497 at bugs.launchpad.net  Mon Oct 20 17:57:56 2025
From: 2117497 at bugs.launchpad.net (Nick Rosbrook)
Date: Mon, 20 Oct 2025 17:57:56 -0000
Subject: [Bug 2117497] Re: No Wifi 7 MLO support
References: <175318877075.99807.12174772095875865008.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176098307622.2420609.13446018725714660845.malone@juju-98d295-prod-launchpad-3>

It sounds like there is no action for Ubuntu sponsors at this time, so
unsubscribing.

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

Title:
  No Wifi 7 MLO support

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Noble:
  New
Status in wpa source package in Plucky:
  New
Status in wpa source package in Questing:
  Fix Released

Bug description:
  SRU Justification:

  [ Impact ]

   * This is a hardware-enablement SRU

   * Recent wifi modules are compatible with wifi 7 that comes with a
  bunch of cool features like Multi-Link Operation (MLO) which speeds up
  wifi. The kernel is compatible with these since 24.04 (Noble)

   * wpa 2.11 is required for these features to be available. it's
  available in Questing already. The release note is here:
  https://lists.infradead.org/pipermail/hostap/2024-July/042847.html

   * There were 2295 commits from 2.10 to 2.11. During these, the wifi 7
  support and reliability was gradually improved. It feels much safer to
  backport the version from Questing entirely compared to cherry-picking
  patches.

   * The 2.11 version landed in Questing a bit more than a month ago,
  which gave time for this new version to be tested by all questing
  users.

  [ Fix ]

   * The proposed fix consists in backporting the version from questing,
  entirely.

  [ Test Plan ]

   1. Run the Wireless Network certification suite from Checkbox, that will
      * Connect and disconnect to all kind of wifi
      * Scan the network

      wireless/wireless_scanning_interface
      wireless/wireless_connection_wpa_bg_nm_interface
      wireless/wireless_connection_open_bg_nm_interface
      wireless/wireless_connection_wpa_n_nm_interface
      wireless/wireless_connection_open_n_nm_interface
      wireless/wireless_connection_wpa_ac_nm_interface
      wireless/wireless_connection_open_ac_nm_interface
      wireless/wireless_connection_wpa_ax_nm_interface
      wireless/wireless_connection_wpa3_ax_nm_interface
      wireless/wireless_connection_open_ax_nm_interface
      wireless/wireless_connection_wpa_be_nm_interface
      wireless/wireless_connection_wpa3_be_nm_interface
      wireless/wireless_connection_open_be_nm_interface

   2. Run the Multi-link operation test suite from Checkbox, that will
  test the compatibility with MLO

      wireless/wifi7_mlo_interface

   3. My test plan involves having 5 persons using this daily for a week
  (at least on Noble). I'd like to have a diverse set of routers and
  machines involved. The testers will be asked to be more aware than
  usual about wifi disconnections, and reliability. I'll ask them to run
  bandwith test every morning with both the proposed package and the
  original one.

  [ Where problems could occur ]

   * Given the size of the update, any wifi-related issue could happen.
   * The test plan tries to cover as much wifi usage as possible to reflect this.

  [ Other Info ]

   * I've been using wpa 2.11 on my side for a month, on Noble. No issue
  there, but I don't have a wifi 7 router.

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

  original description:

  hostapd/wpa_supplicant got a new version:
  https://lists.infradead.org/pipermail/hostap/2024-July/042847.html

  This issue is about bumping the version Ubuntu. Debian is not up-to-
  date, yet.

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



From 2112632 at bugs.launchpad.net  Mon Oct 20 19:28:15 2025
From: 2112632 at bugs.launchpad.net (Nick Rosbrook)
Date: Mon, 20 Oct 2025 19:28:15 -0000
Subject: [Bug 2112632] Re: efibootmgr: commands Active and Inactive do not
 work.
References: <174920467524.2398730.1979390969348049521.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176098849570.2918491.5285434006750321116.launchpad@juju-98d295-prod-launchpad-7>

** Tags added: rls-nn-incoming

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

Title:
  efibootmgr: commands Active and Inactive do not work.

Status in efibootmgr package in Ubuntu:
  Triaged
Status in efibootmgr source package in Noble:
  Triaged
Status in efibootmgr source package in Oracular:
  Won't Fix
Status in efibootmgr source package in Plucky:
  Triaged
Status in efibootmgr source package in Questing:
  Triaged

Bug description:
  OS version: Ubuntu 24.04
  package version: 18-1build2

  My PCs has boot entries 0010, 0020 and 0021.

  $ sudo efibootmgr
  BootCurrent: 0010
  Timeout: 1 seconds
  BootOrder: 0020,0010
  Boot0010* NORMAL	HD(1,GPT,XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX,0x800,0x80000)/<<snip>>
  Boot0020* UPDATE	HD(1,GPT,XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX,0x800,0x80000)/<<snip>>
  Boot0021* UEFI: TOSHIBA, Partition 1	PciRoot(0x0)/Pci(0x14,0x0)/USB(16,0)/HD(1,GPT,XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX,0x800,0x80000)0000424f

  I tried to active/inactive 10 or 20 entry. But these are not found.

  $ sudo efibootmgr -A -b 0010
  efibootmgr: Boot entry 10 not found
  Could not set active state for Boot0010: No such file or directory
  $ sudo efibootmgr -A -b 0020
  efibootmgr: Boot entry 20 not found
  Could not set active state for Boot0020: No such file or directory
  $ sudo efibootmgr -a -b 0010
  efibootmgr: Boot entry 10 not found
  Could not set active state for Boot0010: No such file or directory
  $ sudo efibootmgr -a -b 0020
  efibootmgr: Boot entry 20 not found
  Could not set active state for Boot0020: No such file or directory

  I investigated the cause and found a problem with the get_entry()
  function in src/efibootmgr.c.

  static var_entry_t *
  get_entry(list_t *entries, uint16_t num)
  {
   list_t *pos;
   var_entry_t *entry = NULL;

   list_for_each(pos, entries) {
    entry = list_entry(pos, var_entry_t, list);
    if (entry->num != num) {
     entry = NULL;
     continue;
    }
   }

   return entry;
  }

  This code does not break the loop when an entry is found.
  Therefore, NULL is returned unless the matching entry is the last one.

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



From 2112632 at bugs.launchpad.net  Mon Oct 20 19:54:13 2025
From: 2112632 at bugs.launchpad.net (Nick Rosbrook)
Date: Mon, 20 Oct 2025 19:54:13 -0000
Subject: [Bug 2112632] Re: efibootmgr: commands Active and Inactive do not
 work.
References: <174920467524.2398730.1979390969348049521.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176099005308.2956092.1424947723170346331.malone@juju-98d295-prod-launchpad-7>

Hi,

Sorry this was not reviewed sooner. I have adapted your changes into a
git branch here:
https://git.launchpad.net/~enr0n/ubuntu/+source/efibootmgr/log/?h=lp2112632.
I made the following changes:

1. I added a Bug-Ubuntu: field to the patch headers, pointing to this bug.
2. I slightly modified the format of the Description field to adhere to DEP3 line continuation rules.
3. I added "(LP: #2112632)" to the changelog entry. This helps Launchpad track the status of this bug as the package is uploaded, and eventually is released.

With that, I have uploaded the fix to the development release. In order
to fix the bug in stable releases (i.e. actively supported Ubuntu
releases such as 24.04 LTS), the Stable Release Update (SRU) process
must be followed: https://documentation.ubuntu.com/sru/en/latest/.

Foundations - I think it would be good if someone helped @bucchi out
with the SRU.

Unsubscribing sponsors for now.

** Changed in: efibootmgr (Ubuntu)
       Status: Triaged => Fix Committed

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

Title:
  efibootmgr: commands Active and Inactive do not work.

Status in efibootmgr package in Ubuntu:
  Fix Committed
Status in efibootmgr source package in Noble:
  Triaged
Status in efibootmgr source package in Oracular:
  Won't Fix
Status in efibootmgr source package in Plucky:
  Triaged
Status in efibootmgr source package in Questing:
  Triaged

Bug description:
  OS version: Ubuntu 24.04
  package version: 18-1build2

  My PCs has boot entries 0010, 0020 and 0021.

  $ sudo efibootmgr
  BootCurrent: 0010
  Timeout: 1 seconds
  BootOrder: 0020,0010
  Boot0010* NORMAL	HD(1,GPT,XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX,0x800,0x80000)/<<snip>>
  Boot0020* UPDATE	HD(1,GPT,XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX,0x800,0x80000)/<<snip>>
  Boot0021* UEFI: TOSHIBA, Partition 1	PciRoot(0x0)/Pci(0x14,0x0)/USB(16,0)/HD(1,GPT,XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX,0x800,0x80000)0000424f

  I tried to active/inactive 10 or 20 entry. But these are not found.

  $ sudo efibootmgr -A -b 0010
  efibootmgr: Boot entry 10 not found
  Could not set active state for Boot0010: No such file or directory
  $ sudo efibootmgr -A -b 0020
  efibootmgr: Boot entry 20 not found
  Could not set active state for Boot0020: No such file or directory
  $ sudo efibootmgr -a -b 0010
  efibootmgr: Boot entry 10 not found
  Could not set active state for Boot0010: No such file or directory
  $ sudo efibootmgr -a -b 0020
  efibootmgr: Boot entry 20 not found
  Could not set active state for Boot0020: No such file or directory

  I investigated the cause and found a problem with the get_entry()
  function in src/efibootmgr.c.

  static var_entry_t *
  get_entry(list_t *entries, uint16_t num)
  {
   list_t *pos;
   var_entry_t *entry = NULL;

   list_for_each(pos, entries) {
    entry = list_entry(pos, var_entry_t, list);
    if (entry->num != num) {
     entry = NULL;
     continue;
    }
   }

   return entry;
  }

  This code does not break the loop when an entry is found.
  Therefore, NULL is returned unless the matching entry is the last one.

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



From 2126596 at bugs.launchpad.net  Mon Oct 20 20:18:59 2025
From: 2126596 at bugs.launchpad.net (Nick Rosbrook)
Date: Mon, 20 Oct 2025 20:18:59 -0000
Subject: [Bug 2126596] Re: gvfs 1.57.2-2ubuntu5 autopkgtests failing on
 test_media_player
References: <175934729636.3257950.7089237589155834792.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176099153968.2333670.1457042092494768309.malone@juju-98d295-prod-launchpad-2>

Unsubscribing sponsors since the git-ubuntu MP has a review slot for
sponsors.

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

Title:
  gvfs 1.57.2-2ubuntu5 autopkgtests failing on test_media_player

Status in gvfs package in Ubuntu:
  In Progress

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  questing/questing/amd64/g/gvfs/20251001_144858_724dc@/log.gz

   97s test_media_player (__main__.Drive.test_media_player)
   99s drive mount: media player ... FAIL
   99s <unknown>:2: SyntaxWarning: invalid escape sequence '\s'
   99s <unknown>:1: SyntaxWarning: invalid escape sequence '\s'
   99s 
   99s ----- dbus stdout -----
   99s 
   99s ----- dbus stderr -----
   99s 
   99s

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



From 2129032 at bugs.launchpad.net  Mon Oct 20 23:55:07 2025
From: 2129032 at bugs.launchpad.net (Brian Murray)
Date: Mon, 20 Oct 2025 23:55:07 -0000
Subject: [Bug 2129032] Re: [needs-packaging] slang-compiler
References: <176096654830.2341446.10563703781807672575.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176100450774.973440.12865018022813360427.malone@juju-98d295-prod-launchpad-4>

*** 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.

** Changed in: ubuntu
   Importance: Undecided => Wishlist

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

Title:
  [needs-packaging] slang-compiler

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/shader-slang/slang
  License: Apache-2.0 WITH LLVM-exception
  Notes: Slang is a shading language aiming to make shader codebases mroe maintainable and modular. It also maintians a high performance on modern GPUs and graphic APIs. They aim to rename slang to slang-compiler in order to avoid a naming conflict with s-lang.

  I wish to package slang-compiler for Ubuntu.

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



From 2127933 at bugs.launchpad.net  Tue Oct 21 00:55:59 2025
From: 2127933 at bugs.launchpad.net (Daniel van Vugt)
Date: Tue, 21 Oct 2025 00:55:59 -0000
Subject: [Bug 2127933] Re: Network status shows ethernet connected when no
 connection is available
References: <176054299488.762979.6399394703797330386.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176100816007.2721491.18335821760359013497.launchpad@juju-98d295-prod-launchpad-2>

** Tags added: fixed-in-gnome-shell-50.alpha fixed-upstream

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

Title:
  Network status shows ethernet connected when no connection is
  available

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell source package in Plucky:
  New
Status in gnome-shell source package in Questing:
  New
Status in gnome-shell source package in Resolute:
  In Progress

Bug description:
  Per upstream bugs: 
  - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7357
  - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8549

  And it got fixed with https://gitlab.gnome.org/GNOME/gnome-
  shell/-/merge_requests/3910

  ---------------------------
  SRU Justification:

  [ Impact ]

   * The "ethernet connected" symbol is displayed when no network
  connection is available.  If a WiFi connection is available then the
  WiFi symbol is displayed and if an Ethernet connection is available
  then the Ethernet icon is (correctly) displayed but if neither is
  available (WiFi switched off and cable unplugged) then the Ethernet
  icon is still displayed.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * When there is no active main connection or it uses a device type we do not handle, the indicator icon and its visibility depend on the global connectivity.
   
   * However we currently don't update the icon on connectivity changes, with the result that we sometimes show the fallback connection icon when the network is in fact disconnected.

   * To fix this, update the icon whenever the (global) connectivity
  changes.

  [ Test Plan ]

   1. Connect to wifi, see the wifi icon

   2. Disconnect wifi from the menubar, see the ethernet icon pops in

   3. Do it again with the fix: no ethernet icon pops in

   4. Reconnect wifi, see the icon transitioning to connecting ->
  connected.

  [ Where problems could occur ]

   * The _updateIcon is now called more often than before, not less, so
  more frequent icon updates can be expected, but only when they are
  actually relevant thankfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2127933/+subscriptions



From 2127792 at bugs.launchpad.net  Tue Oct 21 01:44:45 2025
From: 2127792 at bugs.launchpad.net (Daniel van Vugt)
Date: Tue, 21 Oct 2025 01:44:45 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176101108550.1116033.11794278557598282144.malone@juju-98d295-prod-launchpad-4>

https://launchpad.net/ubuntu/+source/gnome-remote-desktop/49.1-1

** Changed in: gnome-remote-desktop (Ubuntu Resolute)
       Status: In Progress => Fix Released

** Changed in: gnome-remote-desktop (Ubuntu Resolute)
     Assignee: Antoine Lassagne (antoinelassagne) => (unassigned)

** Changed in: gnome-remote-desktop (Ubuntu Questing)
     Assignee: (unassigned) => Antoine Lassagne (antoinelassagne)

** Changed in: gnome-remote-desktop (Ubuntu Resolute)
    Milestone: None => ubuntu-26.04

** Changed in: gnome-remote-desktop (Ubuntu Plucky)
     Assignee: (unassigned) => Antoine Lassagne (antoinelassagne)

** Changed in: gnome-remote-desktop (Ubuntu Noble)
     Assignee: (unassigned) => Antoine Lassagne (antoinelassagne)

** Changed in: gnome-remote-desktop (Ubuntu Questing)
    Milestone: None => questing-updates

** Changed in: gnome-remote-desktop (Ubuntu Plucky)
    Milestone: None => plucky-updates

** Changed in: gnome-remote-desktop (Ubuntu Noble)
    Milestone: None => noble-updates

** Changed in: gnome-remote-desktop (Ubuntu Questing)
       Status: New => In Progress

** Changed in: gnome-remote-desktop (Ubuntu Plucky)
       Status: New => In Progress

** Changed in: gnome-remote-desktop (Ubuntu Noble)
       Status: New => In Progress

** Tags added: fixed-in-gnome-remote-desktop-49.1 fixed-upstream

** Tags added: fixed-in-gnome-remote-desktop-48.3

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2125407 at bugs.launchpad.net  Tue Oct 21 06:40:33 2025
From: 2125407 at bugs.launchpad.net (Antoine Lassagne)
Date: Tue, 21 Oct 2025 06:40:33 -0000
Subject: [Bug 2125407] Re: New upstream release landed in debian
References: <175854935122.2339268.5514828628887767207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176102883319.3565562.17404547628535541594.malone@juju-98d295-prod-launchpad-3>

I'm not (yet) familiar enough with the autosync and I did not know that
the autosync required unstable. Then I suppose it can wait, no problem.

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

Title:
  New upstream release landed in debian

Status in glm package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  The latest version of this package, from Feb. 2024, landed in debian:

  libglm-dev | 1.0.1+ds-2    | experimental | all

  Could it be synced to ubuntu/devel?

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



From 2125407 at bugs.launchpad.net  Tue Oct 21 07:20:19 2025
From: 2125407 at bugs.launchpad.net (Daniel van Vugt)
Date: Tue, 21 Oct 2025 07:20:19 -0000
Subject: [Bug 2125407] Re: New upstream release landed in debian
References: <175854935122.2339268.5514828628887767207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176103122021.3984276.13199778389268983283.launchpad@juju-98d295-prod-launchpad-7>

** Tags added: resolute

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

Title:
  New upstream release landed in debian

Status in glm package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  The latest version of this package, from Feb. 2024, landed in debian:

  libglm-dev | 1.0.1+ds-2    | experimental | all

  Could it be synced to ubuntu/devel?

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



From 2126737 at bugs.launchpad.net  Tue Oct 21 09:13:36 2025
From: 2126737 at bugs.launchpad.net (Tzu-Hsien Kao)
Date: Tue, 21 Oct 2025 09:13:36 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176103801757.1825751.13106617404908123675.launchpad@juju-98d295-prod-launchpad-4>

** Changed in: alsa-ucm-conf (Ubuntu)
     Assignee: (unassigned) => Tzu-Hsien Kao (tzuhsien-kao)

** Changed in: alsa-ucm-conf (Ubuntu)
       Status: New => In Progress

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

  **Affected Releases**

  This bug has been filed against Noble Numbat (24.04 LTS) as the
  primary target for the SRU.

  Following the SRU policy, this fix also needs to be verified in the
  development release. Could a bug triager please also mark this bug as
  affecting **`Ubuntu (Development)`**?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2127925 at bugs.launchpad.net  Tue Oct 21 09:51:13 2025
From: 2127925 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 21 Oct 2025 09:51:13 -0000
Subject: [Bug 2127925] [NEW] "policy: auto-activating connection" never occurs
 on adapter restart for networks where user entered incorrect password before
 correct password
References: <176053406915.105350.7511956944740384426.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176104027376.3885332.456776608844701756.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Antoine Lassagne (antoinelassagne):

This bug was reported upstream:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1812

And it got fixed with
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2295

---------------------------
SRU Justification:

[ Impact ]

 * When trying to connect to a wifi network, if one does cancel the
credential popup, the network is gets an internal in-memory flag
preventing its auto reconnection. If then the user succeeds to connect
to it, this flag is not removed. As a result, if the user disable and
re-enables wifi, the network will not reconnect automatically.

 * With the above, the reconnection is fixed.

[ Fix ]

 * Whenever the connection succeeds, the autoconnect blocker flag must
be removed and reset correctly.

[ Test Plan ]

 * Test network-manager without and with this fix:
1. Forget all wifi networks
2. Click on one on the gnome menubar
3. Cancel the popup without entering credentials
4. Check NM's logs to see if an autoconnection is attempted. No autoconnection should be attempted at this point.
5. Click on this same network again, connect successfully.
6. Disable and re-enable wifi.
7. See if an automatic reconnection occurs.

[ Where problems could occur ]

 * Given the nature of the fix (it's one line), I don't see how anything
could go wrong here, given we properly run the test plan.

** Affects: network-manager (Ubuntu)
     Importance: Undecided
     Assignee: Antoine Lassagne (antoinelassagne)
         Status: New

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

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

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

** Affects: network-manager (Ubuntu Resolute)
     Importance: Undecided
     Assignee: Antoine Lassagne (antoinelassagne)
         Status: New

-- 
"policy: auto-activating connection" never occurs on adapter restart for networks where user entered incorrect password before correct password
https://bugs.launchpad.net/bugs/2127925
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127925 at bugs.launchpad.net  Tue Oct 21 09:51:37 2025
From: 2127925 at bugs.launchpad.net (Antoine Lassagne)
Date: Tue, 21 Oct 2025 09:51:37 -0000
Subject: [Bug 2127925] Re: "policy: auto-activating connection" never occurs
 on adapter restart for networks where user entered incorrect password before
 correct password
References: <176053406915.105350.7511956944740384426.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176104029793.1883311.16571164004992687887.malone@juju-98d295-prod-launchpad-4>

The PR was now merged upstream. This is ready for sponsoring.

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

Title:
  "policy: auto-activating connection" never occurs on adapter restart
  for networks where user entered incorrect password before correct
  password

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Noble:
  New
Status in network-manager source package in Plucky:
  New
Status in network-manager source package in Questing:
  New
Status in network-manager source package in Resolute:
  New

Bug description:
  This bug was reported upstream:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1812

  And it got fixed with
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2295

  ---------------------------
  SRU Justification:

  [ Impact ]

   * When trying to connect to a wifi network, if one does cancel the
  credential popup, the network is gets an internal in-memory flag
  preventing its auto reconnection. If then the user succeeds to connect
  to it, this flag is not removed. As a result, if the user disable and
  re-enables wifi, the network will not reconnect automatically.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * Whenever the connection succeeds, the autoconnect blocker flag must
  be removed and reset correctly.

  [ Test Plan ]

   * Test network-manager without and with this fix:
  1. Forget all wifi networks
  2. Click on one on the gnome menubar
  3. Cancel the popup without entering credentials
  4. Check NM's logs to see if an autoconnection is attempted. No autoconnection should be attempted at this point.
  5. Click on this same network again, connect successfully.
  6. Disable and re-enable wifi.
  7. See if an automatic reconnection occurs.

  [ Where problems could occur ]

   * Given the nature of the fix (it's one line), I don't see how
  anything could go wrong here, given we properly run the test plan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2127925/+subscriptions



From 2127933 at bugs.launchpad.net  Tue Oct 21 10:43:24 2025
From: 2127933 at bugs.launchpad.net (Bug Watch Updater)
Date: Tue, 21 Oct 2025 10:43:24 -0000
Subject: [Bug 2127933] Re: Network status shows ethernet connected when no
 connection is available
References: <176054299488.762979.6399394703797330386.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176104340659.3764064.18370301400942252311.launchpad@scripts.lp.internal>

** Changed in: gnome-shell
       Status: New => Fix Released

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

Title:
  Network status shows ethernet connected when no connection is
  available

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Noble:
  New
Status in gnome-shell source package in Plucky:
  New
Status in gnome-shell source package in Questing:
  New
Status in gnome-shell source package in Resolute:
  In Progress

Bug description:
  Per upstream bugs: 
  - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7357
  - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8549

  And it got fixed with https://gitlab.gnome.org/GNOME/gnome-
  shell/-/merge_requests/3910

  ---------------------------
  SRU Justification:

  [ Impact ]

   * The "ethernet connected" symbol is displayed when no network
  connection is available.  If a WiFi connection is available then the
  WiFi symbol is displayed and if an Ethernet connection is available
  then the Ethernet icon is (correctly) displayed but if neither is
  available (WiFi switched off and cable unplugged) then the Ethernet
  icon is still displayed.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * When there is no active main connection or it uses a device type we do not handle, the indicator icon and its visibility depend on the global connectivity.
   
   * However we currently don't update the icon on connectivity changes, with the result that we sometimes show the fallback connection icon when the network is in fact disconnected.

   * To fix this, update the icon whenever the (global) connectivity
  changes.

  [ Test Plan ]

   1. Connect to wifi, see the wifi icon

   2. Disconnect wifi from the menubar, see the ethernet icon pops in

   3. Do it again with the fix: no ethernet icon pops in

   4. Reconnect wifi, see the icon transitioning to connecting ->
  connected.

  [ Where problems could occur ]

   * The _updateIcon is now called more often than before, not less, so
  more frequent icon updates can be expected, but only when they are
  actually relevant thankfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2127933/+subscriptions



From 2129196 at bugs.launchpad.net  Tue Oct 21 16:22:03 2025
From: 2129196 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 21 Oct 2025 16:22:03 -0000
Subject: [Bug 2129196] [NEW] mysql-server fails to install when an ext4 fs is
 mounted to /var/lib/mysql 
References: <176105583922.2334596.9944933464066925340.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176106372368.2582543.15859008969348842060.launchpad@juju-98d295-prod-launchpad-4>

You have been subscribed to a public bug by Zachary Raines (raineszm):

[ Impact ]

 * The postinst script for mysql-server checks whether the
`/var/lib/mysql` directory is empty before setting up the database
state. When `/var/lib/mysql` is an ext4 filesystem, the `lost+found`
directory causes this check to fail and the database is not properly set
up.

 * Mounting a separate volume to hold the mysql state is a common
pattern, and ext4 is extremely prevalent so this is likely to be a
common pain point. Although workarounds are straightforward, it makes
for bad UX.

 * This can be remedied by ignoring the lost+found directory in the
check.

[ Test Plan ]

 To ensure bug is fixed:
 * Create an empty ext4 volume and mount it to /var/lib/mysql
 * Install mysql-server
 * Check whether the installation succeeds

 To check that data is preserved:
 * Uninstall and reinstall mysql-server
 * Ensure that the data in /var/lib/mysql is not overwritten

[ Where problems could occur ]

 * In this case, the only change is to the postinst script, so problems should be related to install.
 * If the check being done were incorrect it could lead to loss of user data.
   - We keep the change to script to a minimum to reduce the risk of this
   - Test plan includes confirming that user data is not overwritten

** Affects: mysql-8.0 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: mysql-8.4 (Ubuntu)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: New

** Affects: mysql-8.0 (Ubuntu Jammy)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: New

** Affects: mysql-8.0 (Ubuntu Noble)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: New

** Affects: mysql-8.4 (Ubuntu Plucky)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: New

** Affects: mysql-8.4 (Ubuntu Questing)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: New

** Affects: mysql-8.4 (Ubuntu Resolute)
     Importance: Undecided
     Assignee: Zachary Raines (raineszm)
         Status: New


** Tags: se-sponsors
-- 
mysql-server fails to install when an ext4 fs is mounted to /var/lib/mysql 
https://bugs.launchpad.net/bugs/2129196
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2125163 at bugs.launchpad.net  Tue Oct 21 18:22:28 2025
From: 2125163 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 21 Oct 2025 18:22:28 -0000
Subject: [Bug 2125163] [NEW] libstd-rust-1.* ships unversioned
 /usr/lib/x86_64-linux-gnu/libEnzyme-19.so
References: <175823525077.2417919.15388729577946954583.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176107094827.942014.12731784863035054224.launchpad@juju-98d295-prod-launchpad-7>

You have been subscribed to a public bug by Karl Smeltzer (karljs):

This breaks parallel installations of different versions of libstd-rust.
The library should either be versioned like:
  /usr/lib/x86_64-linux-gnu/librustc_driver-2e1d29aa68123e6b.so

Or dropped entirely if it was added by accident.

** Affects: rustc-1.83 (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Affects: rustc-1.84 (Ubuntu)
     Importance: Medium
         Status: Confirmed

-- 
libstd-rust-1.* ships unversioned /usr/lib/x86_64-linux-gnu/libEnzyme-19.so
https://bugs.launchpad.net/bugs/2125163
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2129196 at bugs.launchpad.net  Tue Oct 21 19:43:42 2025
From: 2129196 at bugs.launchpad.net (Zachary Raines)
Date: Tue, 21 Oct 2025 19:43:42 -0000
Subject: [Bug 2129196] Re: mysql-server fails to install when an ext4 fs is
 mounted to /var/lib/mysql 
References: <176105583922.2334596.9944933464066925340.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176107582268.2922837.897575878588620511.malone@juju-98d295-prod-launchpad-4>

PPA: https://launchpad.net/~raineszm/+archive/ubuntu/mysql-
lp2129196-sru-postinst

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

Title:
  mysql-server fails to install when an ext4 fs is mounted to
  /var/lib/mysql

Status in mysql-8.0 package in Ubuntu:
  New
Status in mysql-8.4 package in Ubuntu:
  New
Status in mysql-8.0 source package in Jammy:
  New
Status in mysql-8.0 source package in Noble:
  New
Status in mysql-8.4 source package in Plucky:
  New
Status in mysql-8.4 source package in Questing:
  New
Status in mysql-8.4 source package in Resolute:
  New

Bug description:
  [ Impact ]

   * The postinst script for mysql-server checks whether the
  `/var/lib/mysql` directory is empty before setting up the database
  state. When `/var/lib/mysql` is an ext4 filesystem, the `lost+found`
  directory causes this check to fail and the database is not properly
  set up.

   * Mounting a separate volume to hold the mysql state is a common
  pattern, and ext4 is extremely prevalent so this is likely to be a
  common pain point. Although workarounds are straightforward, it makes
  for bad UX.

   * This can be remedied by ignoring the lost+found directory in the
  check.

  [ Test Plan ]

   To ensure bug is fixed:
   * Create an empty ext4 volume and mount it to /var/lib/mysql
   * Install mysql-server
   * Check whether the installation succeeds

   To check that data is preserved:
   * Uninstall and reinstall mysql-server
   * Ensure that the data in /var/lib/mysql is not overwritten

  [ Where problems could occur ]

   * In this case, the only change is to the postinst script, so problems should be related to install.
   * If the check being done were incorrect it could lead to loss of user data.
     - We keep the change to script to a minimum to reduce the risk of this
     - Test plan includes confirming that user data is not overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2129196/+subscriptions



From 2122576 at bugs.launchpad.net  Wed Oct 22 05:28:09 2025
From: 2122576 at bugs.launchpad.net (Kai-Chuan Hsieh)
Date: Wed, 22 Oct 2025 05:28:09 -0000
Subject: [Bug 2122576] Re: Add support Intel PTL platform and ITMT3.0 policy
References: <175758076411.1792167.10087975254811915865.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176111089017.1926277.7600300788753890829.launchpad@juju-98d295-prod-launchpad-7>

** Tags added: jira-somerville-3350

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

Title:
  Add support Intel PTL platform and ITMT3.0 policy

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * The thermald will not be active on Intel PTL platform.

   * The thermald still use passive policy for the platform with ITMI3
  configured.

  [ Test Plan ]

   * On Intel PTL platform with ITMT3.0 policy configured

   * Boot into Ubuntu

   * Stop the default thermald by $ sudo systemctl stop thermald

   * run the thermlad with extra parameter $ sudo thermald --systemd
  --dbus-enable --adaptive --log-level=info

   * check the journalctl log to confirm that thermald apply the policy
  successfully

  1. Make sure to see ITMT3.0 policy defined in the APAT table
  [1754988644][INFO]..apat dump begin..
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MIN argument:30000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1MAX argument:130000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL2PowerLimit argument:150000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.PC00.TCPU domain:9 code:PL1TimeWindow argument:56000
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:PSVT argument:18_psvt
  [1754988644][INFO]target_id:62 name:18_MB1_Balance participant:\SB.IETM domain:14 code:ITMT3 argument:18_itmt3_mb1_balance

  2. Check that ITMT3 policy is applied
  [1754988649][INFO]set_int3400 ITMT target 18_itmt3_mb1_balance

  [ Where problems could occur ]

   * https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     If ITMT3 target present in the BIOS, system will go for ITMT policy instead of the default passive policy setup.

   *
  https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
  enhance the support for the ITMT3.0 policy. No code logic change for
  ITMT1.0 and ITMT2.0. For platform within ITMT3.0 configured, might
  change the thermal behavior.

  [ Other Info ]

   * ITMT stands for Intel Turbo Boost Max Technology, a feature that
  identifies the best-performing cores on a processor and directs
  workloads to them for increased single-threaded performance. This
  technology assigns a higher priority to the fastest cores, ensuring
  that demanding tasks get the maximum possible speed on those select
  cores, while other cores handle less intensive work or remain idle.
  The advantage of ITMT3 can be found in The advantage of ITMT3 can be
  found in https://edc.intel.com/content/www/us/en/design/ipla/software-
  development-platforms/client/platforms/alder-lake-desktop/12th-
  generation-intel-core-processors-datasheet-volume-1-of-2/004/intel-
  turbo-boost-max-technology-3-0/.

   * Upstream commits:
     https://github.com/intel/thermal_daemon/commit/3144beaf22c4ab27fdb75696bae878668ce02ac8
     https://github.com/intel/thermal_daemon/commit/03b4a139388f65f093277554ae5e025723320d28
     https://github.com/intel/thermal_daemon/commit/352125763b8f9866cd9318c1c2a70a5dcf841b20

   * extra commit for noble to add PTL support.
     https://github.com/intel/thermal_daemon/commit/be2049afdee8049b3d9deca72c92cc9262c2b1eb
     another 2 commits for noble combined into 1 patch
     https://github.com/intel/thermal_daemon/commit/3ea73d5fc4608e83b510f30b70153a299788cbc7
     https://github.com/intel/thermal_daemon/commit/8258cb25b919cfced60904f5ebc313c4b9257659

   * According to Dell architect yijun.shen at dell.com, there is no
  certified Dell platform has ITMI3 configured, it will only be
  available on the coming PTL platform.

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



From 2121607 at bugs.launchpad.net  Wed Oct 22 08:55:24 2025
From: 2121607 at bugs.launchpad.net (Dariusz Gadomski)
Date: Wed, 22 Oct 2025 08:55:24 -0000
Subject: [Bug 2121607] Re: [SRU] Nova-api showing latency after upgrading to
 Caracal
References: <175639705793.728435.16126226382096763223.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176112332436.4103578.15724984934468321757.malone@juju-98d295-prod-launchpad-4>

Thanks @raineszm & @cxue22

I have sponsored the patch for jammy.

Just a small remark: please replace UNRELEASED in the changelog with the
appropriate distro series name for future SRUs.

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

Title:
  [SRU] Nova-api showing latency after upgrading to Caracal

Status in OpenStack Compute (nova):
  Confirmed
Status in python-attrs package in Ubuntu:
  In Progress
Status in python-attrs source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  * A resource leak bug in 21.2.0 of python-attrs (<https://github.com/python-attrs/attrs/issues/826>)
   caused performance issues when an application created many classes with the same name.

  * This caused a performance regression in nova through its dependency on python-jsonschema
    * The latency of API calls to nova increases over time

  [ Test Plan ]

   To reproduce the issue and confirm the fix:

  * Create a minimal openstack deployment, using e.g. devstack
  (<https://docs.openstack.org/devstack/latest/>).

  * Run a script which makes many calls to the nova API

   ---Script to call API---
   #!/bin/bash
   # --- Get a fresh token (requires openrc sourced first) ---
   get_token() {
       openstack token issue -f value -c id
   }

   OS_TOKEN=$(get_token)
   echo "Using token: $OS_TOKEN"

   # --- Send requests at 10 per second ---
   COUNT=0
   while true; do
       COUNT=$((COUNT + 1))
       STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
           -H "X-Auth-Token: $OS_TOKEN" \
           -H "Accept: application/json" \
           "$NOVA_URL/servers/detail")

       echo "$(date +'%F %T') [$COUNT] HTTP $STATUS"

       if [ "$STATUS" = "401" ]; then
           echo "[$(date)] Got 401 → refreshing token..."
           OS_TOKEN=$(get_token)
           continue # retry next loop with fresh token
       fi
       # sleep 0.1 # 0.1 sec → 10 per second
   done
   ---/Script to call API---

  * Simultaneously monitor the response time of API calls using the
  openstack CLI

   ---Script to monitor response time---
   #!/bin/bash

   # --- Again openrc must be sourced first ---
   os_quota() {
       openstack quota list --compute --timing --format=json
   }

   headers() {
       os_quota | grep -o -P '/(\w|\d){32}(/d)?' | tr '\n' ','
   }

   time_api() {
       os_quota |
           awk 'BEGIN { FS=","; ORS=","} /quota/ {print $2} END { printf "\n" }'
   }

   OUTPUT="api_calls_$(date +%Y-%m-%dT%H_%M_%S)"

   echo -n "# time," >>"$OUTPUT"
   headers >>"$OUTPUT"
   echo >>"$OUTPUT"

   i=0
   while true; do
       echo -n "$(date +'%F %T')," >>"$OUTPUT"
       time_api >>"$OUTPUT"
       echo -n "."
       if ((i > 80)); then
           i=0
           echo
       fi
       sleep 5
   done

  ---/Script to monitor response time---

  * Observe that the response time increases over time with python-attrs 21.2.0
    * I did this over a period of about 20 hrs.

  * Log in to the server hosting the nova API and upgrade python-attrs
  to 21.4.0

  * Repeat the above steps and observe that the response time remains
  stable over time.

  [ Where problems could occur ]

  * Other packages depend on python-attrs as a library and so could be
  affected.

  * From 21.2.0 to 21.4.0 there was one backward incompatible change change of which could potentailly cause issues:
    * <https://github.com/python-attrs/attrs/blob/21.4.0/CHANGELOG.rst>
      """
      When using @define, converters are now run by default when setting an attribute on an instance -- additionally to validators. I.e. the new default is on_setattr=[attrs.setters.convert, attrs.setters.validate].

      This is unfortunately a breaking change, but it was an oversight, impossible to raise a DeprecationWarning about, and it's better to fix it now while the APIs are very fresh with few users.
      """
    * Since there are no version pins of python-attrs excluding this version it is unlikely to break other packages.
    * It is possible that some users could be using the python3-attr package in their own code, but it is much more likely that
      for user code, attr would be installed via pip, either directly or within a virtualenv.

  * The version in noble is 23.2.0 which already includes all these
  changes and there doesn't seem to be any associated issues.

  [ Other Info ]

  * This SRU proposal bumps to 21.4.0 instead of 21.3.0 because 21.4.0 is a bug fix
    release for a regression in 21.3.0.

  * This is the first ubuntu specific modification to this package, but
  it is a fairly minor one and doesn't need to be carried forward to any
  other series.

  * A possible lighter weight alternative is to simply cherry pick the
  bugfix commit <https://github.com/python-
  attrs/attrs/commit/38580632ceac1cd6e477db71e1d190a4130beed4>

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



From 2125145 at bugs.launchpad.net  Wed Oct 22 09:04:10 2025
From: 2125145 at bugs.launchpad.net (Dariusz Gadomski)
Date: Wed, 22 Oct 2025 09:04:10 -0000
Subject: [Bug 2125145] Re: [SRU] Makedumpfile: Errors and Page Exclusions When
 Opening Kernel Crashdump Files Generated on the Latest HWE Kernel
References: <175821630447.1842424.14764010785335167964.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176112385056.4111934.7709924420421546742.malone@juju-98d295-prod-launchpad-4>

Thanks Bryan.

I have sponsored the makedumpfile patch for noble while we are still
waiting for crash to get into resolute.

2 minor remarks:
* the LP bug mention was missing a colon, I'm not sure if the automated tools will pick it up in this format. Please stick to LP: #<bug-num> just to be sure. More details [1]
* When you're introducing changes that are Ubuntu-specific (reflected by introducing *<X>ubuntu<Y>* in the version number) you also need to update the maintainer in debian/control. `update-maintainer` tool is your friend: just run it in your source and it'll update it for you. [2]

[1] https://canonical-ubuntu-packaging-guide.readthedocs-hosted.com/en/1.0/how-to/fixing-a-bug.html
[2] https://canonical-ubuntu-packaging-guide.readthedocs-hosted.com/en/latest/tutorial/make-changes-to-package/#committing-the-changes

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

Title:
  [SRU] Makedumpfile: Errors and Page Exclusions When Opening Kernel
  Crashdump Files Generated on the Latest HWE Kernel

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in crash source package in Noble:
  New
Status in makedumpfile source package in Noble:
  New
Status in crash source package in Plucky:
  New
Status in makedumpfile source package in Plucky:
  Fix Released
Status in crash source package in Questing:
  New
Status in makedumpfile source package in Questing:
  Fix Released
Status in crash source package in Resolute:
  Confirmed
Status in makedumpfile source package in Resolute:
  Fix Released

Bug description:
  Note: Original description is at the bottom of this report

  [Impact]

  The current versions of Makedumpfile and Crash in the -updates pocket
  on Noble do not support the latest hardware enablement kernel for that
  platform, which is 6.14. There are several architecture-dependent and
  kernel flavor-dependent behaviours that I will outline below, but the
  steps to reproduce are the same.

  Reproducer steps:
  -----------------

  Boot into a hardware enablement kernel. For example, on arm64 use the
  6.14.0-1008-nvidia-64k kernel:

  KERNEL_VERSION=6.14.0-1008-nvidia-64k
  DISTRO=noble

  sudo apt update
  sudo apt install ubuntu-dbgsym-keyring
  echo "deb http://ddebs.ubuntu.com ${DISTRO} main restricted universe multiverse
  deb http://ddebs.ubuntu.com ${DISTRO}-updates main restricted universe multiverse | \
    sudo tee /etc/apt/sources.list.d/ddebs.list
  sudo apt update
  sudo apt install linux-image-${KERNEL_VERSION}
  sudo apt install linux-image-unsigned-${KERNEL_VERSION}-dbgsym

  Modify grub's cmdline to specify a crashkernel: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=512M" # Or similar
  sudo update-grub
  sudo apt install kexec-tools kdump-tools crash makedumpfile
  sudo systemctl enable kdump-tools
  sudo systemctl start kdump-tools
  sudo reboot

  echo c | sudo tee /proc/sysrq-trigger

  After the machine recovers,

  crash /usr/lib/debug/boot/<kernel-dbgsym> /var/crash/<dump-dir>/<dump-
  file>

  Results on Arm64
  ----------------

  crash 8.0.4
  Copyright (C) 2002-2022  Red Hat, Inc.
  ...
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  please wait... (gathering task table data)
  crash: page excluded: kernel virtual address: ffff07ffa042d8e0  type: "xa_node.slots[off]"

  Results on amd64
  ----------------

  On an amd64 machine, using a kernel such as linux-
  image-6.14.0-29-generic results in crash failing to open. No error is
  printed but we don't obtain the prompt:

  crash 8.0.4
  ...
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  # Program exits and no prompt is presented

  [Test Plan]

  * Ensure that with the proposed combination of makedumpfile and crash is capable of generating and subsequently opening crashdumps on the HWE and GA kernels available for that platform. Here is the mapping ATOW:
  Noble GA: 6.8
  Noble HWE: 6.14
  Plucky (interim release, no HWE): 6.14
  Questing (interim release, no HWE): 6.17
  Resolute (development): 6.17 (as of Oct. 14th 2025)

  * Ensure all of crash's commands produce the expected output (eg. ps,
  mount, files, vm, vtop, runq, etc.)

  * If bugs are found in generating and reading crashdumps on the HWE
  kernel on other architectures (s390x, etc.), this test plan can be
  expanded to include those.

  [Where Problems Could Occur]
  * Crash and Makedumpfile are designed to be backwards-compatible, so the risk of regression when backporting a commit is low - however, not zero. This is why it will be important to ensure that the proposed combination of Makedumpfile and crash does not break existing environments - eg. the GA kernel

  * The matrix of hardware and kernel versions (including derivative /
  cloud kernels) to test again is extensive. It's possible that the
  commits identified to solve the known problems will not be
  comprehensive. For example, cpu architectures and kernels not in the
  test matrix may require additional commits to be backported.

  [Other Info]

  * Support/SEG are currently having conversations with the kernel team
  about the potential to proactively SRU / MRE the latest upstream crash
  version, and potentially Makedumpfile as well, alongside -hwe kernel
  releases to avoid this sort of regression in the future. Though, we
  understand this would require an SRUExceptionPolicy to be approved and
  published.

  [Investigation and summary of changes]

  We have identified that on the Makedumpfile at least two commits are needed:
  [1] https://github.com/makedumpfile/makedumpfile/commit/985e575253f1c2de8d6876cfe685c68a24ee06e1
  [2] https://github.com/makedumpfile/makedumpfile/commit/bad2a7c4fa75d37a41578441468584963028bdda

  These are patches to compensate for a change in the kernel's mapping
  of memory. Using the patched Makedumpfile helps, but it is not
  sufficient. Including the patches in Makedumpfile (or using the tip of
  upstream master), but opening with the currently distributed crash
  results in the following errors:

  eg. Patched Makedumpfile with crash 8.0.4 on Arm64:
  ---------------------------------------------------
  ...
  WARNING: cannot determine starting stack frame for task ffffd574e21b4800

  WARNING: cannot determine starting stack frame for task
  ffff07ff83296300

  WARNING: cannot determine starting stack frame for task
  ffff07ff83293f80

  WARNING: cannot determine starting stack frame for task
  ffff07ff83a04700

  WARNING: cannot determine starting stack frame for task ffff08010507c400
        KERNEL: /usr/lib/debug/boot/vmlinux-6.14.0-1008-nvidia-64k
      DUMPFILE: /var/crash/patched_mdf/dump.202509191531  [PARTIAL DUMP]
          CPUS: 128 [OFFLINE: 127]
          DATE: Thu Jan  1 00:00:00 UTC 1970
        UPTIME: 00:13:38
  LOAD AVERAGE: 0.12, 0.16, 0.10
         TASKS: 1573
      NODENAME: penguru
       RELEASE: 6.14.0-1008-nvidia-64k
       VERSION: #8-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 26 02:43:53 UTC 2025
       MACHINE: aarch64  (unknown Mhz)
        MEMORY: 63.8 GB
         PANIC: "Kernel panic - not syncing: sysrq triggered crash"
           PID: 7886
       COMMAND: "tee"
          TASK: ffff08010507c400  [THREAD_INFO: ffff08010507c400]
           CPU: 85
         STATE: TASK_RUNNING (PANIC)

  On Amd64
  --------
  Crash still fails to open.

  Therefore, in addition to the above Makedumpfile commits, crash
  requires some patching. With the above two commits to Makedumpfile I
  did a bisect on crash on amd64 and arm64.

  On the amd64 crash side, I have identified that [3] applied in isolation (cherry-picked) is sufficient on amd64
  [3] https://github.com/crash-utility/crash/commit/6752571d8d782d07537a258a1ec8919ebd1308ad

  I have also found that cherry-picking [4] and [5] resolves the issue on arm64 hardware in testflinger (using the machine agent penguru)
  [4] https://github.com/crash-utility/crash/commit/3879e9104826d5ae14a0824ec47ab60056a249a7
  [5] https://github.com/crash-utility/crash/commit/968debd0d5979dd9ddca3af0766bad714dbd51e3

  At this point, crash's commands such as mount, files, vm, etc. were
  still broken. To resolve this, [6] and [7] are needed

  [6] https://github.com/crash-utility/crash/commit/3d60d9d40457239683a5f20b01437db94f964fb8
  [7] https://github.com/crash-utility/crash/commit/2795136a515446b798ebbfa257c97f0ca6ecb8ec

  To SRU for Noble, crash must also be work on Plucky, Questing, and Resolute. The current version of makedumpfile on all of those series was found to be sufficient and so no SRU for makedumpfile is required on those. However for crash:
  * Plucky uses the 6.14 kernel, so no additional commits are needed - in fact due to the newer version available on Plucky, only [7] is needed.
  * Questing uses the 6.17 kernel. No issues other than [7] were observed on arm, but on amd64, an infinite loop while gdb loaded module symbols was observed, This is fixed in [8].
  * Resolute will ship with a newer kernel than 6.17, but as of October 14th, 2025 is currently based on 6.17. Currently the package in Debian unstable, which will autosync to Resolute does not contain the required fixes and so it will also require SRU with [7] and [8] unless superceded by an upstream (Debian) version bump.

  [8] https://github.com/crash-
  utility/crash/commit/e44a9a9d808c83fb846060f65e5aaa9d30b6e2c4

  PPA with all of the packages built (except resolute):
  https://launchpad.net/~bryanfraschetti/+archive/ubuntu/lp2125145

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

  Original Description:
  =====================

  24.04 LTS,
  Linux 6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 14 16:52:50 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  Problem Description:
  crash utility is crashing (error code 1) when attempting to analyze kernel crash dumps.

  Setup kdump & generated kernel panic using “echo 1 >
  /proc/sys/kernel/sysrq” but, crash cannot access it:

  # crash /usr/lib/debug/boot/vmlinux-6.14.0-29-generic
  dump.202509161821

  crash 8.0.4
  Copyright (C) 2002-2022  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2022  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-pc-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
      <http://www.gnu.org/software/gdb/documentation/>.

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  # echo $?
  1

  running as root user and file is readable fine:

  $ :/var/crash/202509161821# ls -l
  total 299144
  -rw------- 1 root whoopsie    119627 Sep 16 18:21 dmesg.202509161821
  -rw-r--r-- 1 root whoopsie 306200163 Sep 16 18:21 dump.202509161821

  symbol file is there:

  # ls -l /usr/lib/debug/boot/vmlinux-6.14.0-29-generic*
  -rw-r--r-- 1 root root 450705920 Aug 14 18:02 /usr/lib/debug/boot/vmlinux-6.14.0-29-generic

  tail of strace:

  14:06:20.661240 rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661281 rt_sigaction(SIGINT, {sa_handler=0x5ec383cbceb0, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661322 rt_sigaction(SIGSEGV, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661360 write(1, "\n", 1
  )       = 1 <0.000119>
  14:06:20.661579 lseek(3, 10312, SEEK_SET) = 10312 <0.000010>
  14:06:20.661617 read(3, "OSRELEASE=6.14.0-29-generic\nBUIL"..., 3276) = 3276 <0.000011>
  14:06:20.661748 unlink("/var/tmp/ramdump_elf_XXXXXX") = -1 ENOENT (No such file or directory) <0.002921>
  14:06:20.664817 exit_group(1)           = ?
  14:06:20.690105 +++ exited with 1 +++

  full crash strace https://filebin.net/custom-bin/crash.strace.1

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: crash 8.0.4-1ubuntu2
  ProcVersionSignature: Ubuntu 6.14.0-29.29~24.04.1-generic 6.14.8
  Uname: Linux 6.14.0-29-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Sep 18 20:21:26 2025
  InstallationDate: Installed on 2025-09-04 (14 days ago)
  InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: crash
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 2126737 at bugs.launchpad.net  Wed Oct 22 09:20:42 2025
From: 2126737 at bugs.launchpad.net (Frank Heimes)
Date: Wed, 22 Oct 2025 09:20:42 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176112484309.1981633.1136584794591270687.launchpad@juju-98d295-prod-launchpad-3>

** Also affects: alsa-ucm-conf (Ubuntu Questing)
   Importance: Undecided
       Status: New

** Also affects: alsa-ucm-conf (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Also affects: alsa-ucm-conf (Ubuntu Resolute)
   Importance: Undecided
     Assignee: Tzu-Hsien Kao (tzuhsien-kao)
       Status: In Progress

** Also affects: alsa-ucm-conf (Ubuntu Noble)
   Importance: Undecided
       Status: New

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Noble:
  New
Status in alsa-ucm-conf source package in Plucky:
  New
Status in alsa-ucm-conf source package in Questing:
  New
Status in alsa-ucm-conf source package in Resolute:
  In Progress

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

  **Affected Releases**

  This bug has been filed against Noble Numbat (24.04 LTS) as the
  primary target for the SRU.

  Following the SRU policy, this fix also needs to be verified in the
  development release. Could a bug triager please also mark this bug as
  affecting **`Ubuntu (Development)`**?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2129196 at bugs.launchpad.net  Wed Oct 22 10:17:34 2025
From: 2129196 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Wed, 22 Oct 2025 10:17:34 -0000
Subject: [Bug 2129196] Re: mysql-server fails to install when an ext4 fs is
 mounted to /var/lib/mysql 
References: <176105583922.2334596.9944933464066925340.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176112825559.51226.1995635279912366134.launchpad@juju-98d295-prod-launchpad-4>

** Tags added: server-triage-discuss

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

Title:
  mysql-server fails to install when an ext4 fs is mounted to
  /var/lib/mysql

Status in mysql-8.0 package in Ubuntu:
  New
Status in mysql-8.4 package in Ubuntu:
  New
Status in mysql-8.0 source package in Jammy:
  New
Status in mysql-8.0 source package in Noble:
  New
Status in mysql-8.4 source package in Plucky:
  New
Status in mysql-8.4 source package in Questing:
  New
Status in mysql-8.4 source package in Resolute:
  New

Bug description:
  [ Impact ]

   * The postinst script for mysql-server checks whether the
  `/var/lib/mysql` directory is empty before setting up the database
  state. When `/var/lib/mysql` is an ext4 filesystem, the `lost+found`
  directory causes this check to fail and the database is not properly
  set up.

   * Mounting a separate volume to hold the mysql state is a common
  pattern, and ext4 is extremely prevalent so this is likely to be a
  common pain point. Although workarounds are straightforward, it makes
  for bad UX.

   * This can be remedied by ignoring the lost+found directory in the
  check.

  [ Test Plan ]

   To ensure bug is fixed:
   * Create an empty ext4 volume and mount it to /var/lib/mysql
   * Install mysql-server
   * Check whether the installation succeeds

   To check that data is preserved:
   * Uninstall and reinstall mysql-server
   * Ensure that the data in /var/lib/mysql is not overwritten

  [ Where problems could occur ]

   * In this case, the only change is to the postinst script, so problems should be related to install.
   * If the check being done were incorrect it could lead to loss of user data.
     - We keep the change to script to a minimum to reduce the risk of this
     - Test plan includes confirming that user data is not overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2129196/+subscriptions



From 2125163 at bugs.launchpad.net  Wed Oct 22 16:23:56 2025
From: 2125163 at bugs.launchpad.net (Karl Smeltzer)
Date: Wed, 22 Oct 2025 16:23:56 -0000
Subject: [Bug 2125163] Re: libstd-rust-1.* ships unversioned
 /usr/lib/x86_64-linux-gnu/libEnzyme-19.so
References: <175823525077.2417919.15388729577946954583.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176115023692.666135.908225289780334266.malone@juju-98d295-prod-launchpad-4>

This patch removes Enzyme from the rustc-1.83 build for Plucky.  Since
this bug only affects 1.83 and 1.84 on Plucky (the period between Enzyme
being merged in, and being disabled for future builds), it's sufficient
to disable it for 1.83 and leave 1.84 alone.  There are no reverse
dependencies on 1.83, whereas 1.84 is the default version of rustc in
Plucky, so changing 1.83 should be very low-impact.

The package built successfully in this PPA: https://launchpad.net/~rust-toolchain/+archive/ubuntu/staging
The source is here: https://git.launchpad.net/~canonical-foundations/ubuntu/+source/rustc/log/?h=merge-1.83

** Patch added: "1-1.83.0+dfsg0ubuntu2-0ubuntu1.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/rustc-1.83/+bug/2125163/+attachment/5919766/+files/1-1.83.0+dfsg0ubuntu2-0ubuntu1.debdiff

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

Title:
  libstd-rust-1.* ships unversioned /usr/lib/x86_64-linux-
  gnu/libEnzyme-19.so

Status in rustc-1.83 package in Ubuntu:
  Confirmed
Status in rustc-1.84 package in Ubuntu:
  Confirmed

Bug description:
  This breaks parallel installations of different versions of libstd-rust.
  The library should either be versioned like:
    /usr/lib/x86_64-linux-gnu/librustc_driver-2e1d29aa68123e6b.so

  Or dropped entirely if it was added by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc-1.83/+bug/2125163/+subscriptions



From 2125163 at bugs.launchpad.net  Wed Oct 22 16:25:01 2025
From: 2125163 at bugs.launchpad.net (Karl Smeltzer)
Date: Wed, 22 Oct 2025 16:25:01 -0000
Subject: [Bug 2125163] Re: libstd-rust-1.* ships unversioned
 /usr/lib/x86_64-linux-gnu/libEnzyme-19.so
References: <175823525077.2417919.15388729577946954583.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176115030207.2716682.16199755921396274303.malone@juju-98d295-prod-launchpad-3>

Attaching the re-generated orig tarball, which has the enzyme code
removed.

** Attachment added: "rustc-1.83_1.83.0+dfsg0ubuntu2.orig.tar.xz"
   https://bugs.launchpad.net/ubuntu/+source/rustc-1.83/+bug/2125163/+attachment/5919767/+files/rustc-1.83_1.83.0+dfsg0ubuntu2.orig.tar.xz

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

Title:
  libstd-rust-1.* ships unversioned /usr/lib/x86_64-linux-
  gnu/libEnzyme-19.so

Status in rustc-1.83 package in Ubuntu:
  Confirmed
Status in rustc-1.84 package in Ubuntu:
  Confirmed

Bug description:
  This breaks parallel installations of different versions of libstd-rust.
  The library should either be versioned like:
    /usr/lib/x86_64-linux-gnu/librustc_driver-2e1d29aa68123e6b.so

  Or dropped entirely if it was added by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc-1.83/+bug/2125163/+subscriptions



From 2128881 at bugs.launchpad.net  Wed Oct 22 19:21:18 2025
From: 2128881 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Wed, 22 Oct 2025 19:21:18 -0000
Subject: [Bug 2128881] Re: Sync stegseek 0.6+git20210910.ff677b9-2 (universe)
 from Debian unstable (main)
References: <176077730510.2002076.6576041745009546915.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176116087879.945489.1269598522628562858.malone@juju-98d295-prod-launchpad-4>

https://launchpad.net/ubuntu/+source/stegseek/0.6+git20210910.ff677b9-2

** Changed in: stegseek (Ubuntu)
       Status: New => Fix Committed

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

Title:
  Sync stegseek 0.6+git20210910.ff677b9-2 (universe) from Debian
  unstable (main)

Status in stegseek package in Ubuntu:
  Fix Committed

Bug description:
  Please sync stegseek 0.6+git20210910.ff677b9-2 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev

  The Debian package changed the build dependency to libjpeg-dev. Note
  that this is a different change than the current Ubuntu patch, but
  from my understanding the "generic" libjpeg-dev package is provided by
  the versioned 62 package in Debian and the versioned 8 package in
  Ubuntu. So I believe this replacement should work both places. :)

  
  Changelog entries since current resolute version 0.6+git20210910.ff677b9-1ubuntu1:

  stegseek (0.6+git20210910.ff677b9-2) unstable; urgency=medium

    * Team upload.
    * d/control:
      - Build-Depends: libjpeg62-turbo-dev -> libjpeg-dev (Closes: #1089021)
      - Drop 'Rules-Requires-Root: no', it's the standard now.
      - Bump Standards-Version to 4.7.2.
    * d/watch: Convert watch file to version 5 format.
    * d/copyright: Update copyright holders regarding Debian packaging.

   -- Sven Geuer <sge at debian.org>  Fri, 03 Oct 2025 21:44:40 +0200

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



From 2128881 at bugs.launchpad.net  Wed Oct 22 19:21:20 2025
From: 2128881 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Wed, 22 Oct 2025 19:21:20 -0000
Subject: [Bug 2128881] Re: Sync stegseek 0.6+git20210910.ff677b9-2 (universe)
 from Debian unstable (main)
References: <176077730510.2002076.6576041745009546915.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176116088094.949790.16031390091265007172.malone@juju-98d295-prod-launchpad-4>

https://launchpad.net/ubuntu/+source/stegseek/0.6+git20210910.ff677b9-2

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

Title:
  Sync stegseek 0.6+git20210910.ff677b9-2 (universe) from Debian
  unstable (main)

Status in stegseek package in Ubuntu:
  Fix Committed

Bug description:
  Please sync stegseek 0.6+git20210910.ff677b9-2 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev

  The Debian package changed the build dependency to libjpeg-dev. Note
  that this is a different change than the current Ubuntu patch, but
  from my understanding the "generic" libjpeg-dev package is provided by
  the versioned 62 package in Debian and the versioned 8 package in
  Ubuntu. So I believe this replacement should work both places. :)

  
  Changelog entries since current resolute version 0.6+git20210910.ff677b9-1ubuntu1:

  stegseek (0.6+git20210910.ff677b9-2) unstable; urgency=medium

    * Team upload.
    * d/control:
      - Build-Depends: libjpeg62-turbo-dev -> libjpeg-dev (Closes: #1089021)
      - Drop 'Rules-Requires-Root: no', it's the standard now.
      - Bump Standards-Version to 4.7.2.
    * d/watch: Convert watch file to version 5 format.
    * d/copyright: Update copyright holders regarding Debian packaging.

   -- Sven Geuer <sge at debian.org>  Fri, 03 Oct 2025 21:44:40 +0200

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



From 2125163 at bugs.launchpad.net  Wed Oct 22 19:53:50 2025
From: 2125163 at bugs.launchpad.net (Karl Smeltzer)
Date: Wed, 22 Oct 2025 19:53:50 -0000
Subject: [Bug 2125163] Re: libstd-rust-1.* ships unversioned
 /usr/lib/x86_64-linux-gnu/libEnzyme-19.so
References: <175823525077.2417919.15388729577946954583.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176116283051.3341359.5809485855691309681.malone@juju-98d295-prod-launchpad-7>

I've been running the autopkgtests, but am struggling to overcome some
testbed issues.  I think there's evidence that the tests themselves are
passing, but I'll keep retrying the one that hasn't actually run yet:

❯ ppa tests ppa:rust-toolchain/staging --release plucky --packages rustc-1.83
* Triggers:
  - Source plucky/rustc-1.83/1.83.0+dfsg0ubuntu2-0ubuntu1: Published
    + Trigger basic @amd64♻️    Trigger all-proposed @amd64💍
    + Trigger basic @arm64♻️    Trigger all-proposed @arm64💍
    + Trigger basic @armhf♻️    Trigger all-proposed @armhf💍
    + Trigger basic @i386♻️     Trigger all-proposed @i386💍
    + Trigger basic @ppc64el♻️  Trigger all-proposed @ppc64el💍
    + Trigger basic @s390x♻️    Trigger all-proposed @s390x💍
    + Trigger basic @riscv64♻️  Trigger all-proposed @riscv64💍
* Results:
  - rustc-1.83: plucky/rustc-1.83/1.83.0+dfsg0ubuntu2-0ubuntu1 [amd64]
    + ✅ rustc-1.83 on plucky for amd64   @ 21.10.25 18:34:45  Log 🗒️
    + ⛔ rustc-1.83 on plucky for amd64   @ 21.10.25 19:41:49  Log 🗒️
      • testbed                   BAD    ⛔
    + ⛔ rustc-1.83 on plucky for amd64   @ 22.10.25 01:27:14  Log 🗒️
      • testbed                   BAD    ⛔
    + ⛔ rustc-1.83 on plucky for amd64   @ 22.10.25 19:45:44  Log 🗒️
      • testbed                   BAD    ⛔
  - rustc-1.83: plucky/rustc-1.83/1.83.0+dfsg0ubuntu2-0ubuntu1 [arm64]
    + ✅ rustc-1.83 on plucky for arm64   @ 21.10.25 19:07:56  Log 🗒️
    + ✅ rustc-1.83 on plucky for arm64   @ 21.10.25 19:23:57  Log 🗒️
  - rustc-1.83: plucky/rustc-1.83/1.83.0+dfsg0ubuntu2-0ubuntu1 [armhf]
    + ✅ rustc-1.83 on plucky for armhf   @ 21.10.25 18:31:53  Log 🗒️
    + ✅ rustc-1.83 on plucky for armhf   @ 21.10.25 19:42:25  Log 🗒️
  - rustc-1.83: plucky/rustc-1.83/1.83.0+dfsg0ubuntu2-0ubuntu1 [ppc64el]
    + ✅ rustc-1.83 on plucky for ppc64el @ 21.10.25 18:09:25  Log 🗒️
    + ✅ rustc-1.83 on plucky for ppc64el @ 21.10.25 18:23:22  Log 🗒️
  - rustc-1.83: plucky/rustc-1.83/1.83.0+dfsg0ubuntu2-0ubuntu1 [s390x]
    + ✅ rustc-1.83 on plucky for s390x   @ 21.10.25 18:07:24  Log 🗒️
    + ⛔ rustc-1.83 on plucky for s390x   @ 21.10.25 19:37:01  Log 🗒️
      • testbed                   BAD    ⛔
    + ✅ rustc-1.83 on plucky for s390x   @ 21.10.25 23:33:23  Log 🗒️
* Running: (none)
* Waiting: (none)

** Changed in: rustc-1.83 (Ubuntu)
     Assignee: (unassigned) => Karl Smeltzer (karljs)

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

Title:
  libstd-rust-1.* ships unversioned /usr/lib/x86_64-linux-
  gnu/libEnzyme-19.so

Status in rustc-1.83 package in Ubuntu:
  Confirmed
Status in rustc-1.84 package in Ubuntu:
  Confirmed

Bug description:
  This breaks parallel installations of different versions of libstd-rust.
  The library should either be versioned like:
    /usr/lib/x86_64-linux-gnu/librustc_driver-2e1d29aa68123e6b.so

  Or dropped entirely if it was added by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc-1.83/+bug/2125163/+subscriptions



From 2125163 at bugs.launchpad.net  Wed Oct 22 20:57:07 2025
From: 2125163 at bugs.launchpad.net (Karl Smeltzer)
Date: Wed, 22 Oct 2025 20:57:07 -0000
Subject: [Bug 2125163] Re: libstd-rust-1.* ships unversioned
 /usr/lib/x86_64-linux-gnu/libEnzyme-19.so
References: <175823525077.2417919.15388729577946954583.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176116662749.1085530.7852576440467261368.malone@juju-98d295-prod-launchpad-4>

======
BEFORE
======
ubuntu at pacific-bird:~$ sudo apt install rustc-1.84
[...]
ubuntu at pacific-bird:~$ sudo apt install rustc-1.83
[...]
Selecting previously unselected package rustc-1.83.
Preparing to unpack .../rustc-1.83_1.83.0+dfsg0ubuntu1-0ubuntu2_amd64.deb ...
Unpacking rustc-1.83 (1.83.0+dfsg0ubuntu1-0ubuntu2) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libstd-rust-1.83_1.83.0+dfsg0ubuntu1-0ubuntu2_amd64.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)

=====
AFTER
=====
ubuntu at pacific-bird:~$ sudo apt install rustc-1.84
[...]
ubuntu at pacific-bird:~$ sudo add-apt-repository ppa:rust-toolchain/staging
[...]
ubuntu at pacific-bird:~$ sudo apt install rustc-1.83
[...]
Get:1 https://ppa.launchpadcontent.net/rust-toolchain/staging/ubuntu plucky/main amd64 rustc-1.83 amd64 1.83.0+dfsg0ubuntu2-0ubuntu1 [5582 kB]
Fetched 5582 kB in 12s (458 kB/s)                                                                                                                                                                          
Selecting previously unselected package rustc-1.83.
(Reading database ... 78425 files and directories currently installed.)
Preparing to unpack .../rustc-1.83_1.83.0+dfsg0ubuntu2-0ubuntu1_amd64.deb ...
Unpacking rustc-1.83 (1.83.0+dfsg0ubuntu2-0ubuntu1) ...
Setting up rustc-1.83 (1.83.0+dfsg0ubuntu2-0ubuntu1) ...
Processing triggers for man-db (2.13.0-1) ...
Scanning processes...                                                                                                                                                                                       
Scanning linux images...

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

Title:
  libstd-rust-1.* ships unversioned /usr/lib/x86_64-linux-
  gnu/libEnzyme-19.so

Status in rustc-1.83 package in Ubuntu:
  Confirmed
Status in rustc-1.84 package in Ubuntu:
  Confirmed

Bug description:
  This breaks parallel installations of different versions of libstd-rust.
  The library should either be versioned like:
    /usr/lib/x86_64-linux-gnu/librustc_driver-2e1d29aa68123e6b.so

  Or dropped entirely if it was added by accident.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc-1.83/+bug/2125163/+subscriptions



From 2126737 at bugs.launchpad.net  Thu Oct 23 03:26:23 2025
From: 2126737 at bugs.launchpad.net (Tzu-Hsien Kao)
Date: Thu, 23 Oct 2025 03:26:23 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176118998340.3977682.13981011627473610576.malone@juju-98d295-prod-launchpad-7>

** Changed in: alsa-ucm-conf (Ubuntu Plucky)
     Assignee: (unassigned) => Tzu-Hsien Kao (tzuhsien-kao)

** Changed in: alsa-ucm-conf (Ubuntu Noble)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Plucky)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Noble)
     Assignee: (unassigned) => Tzu-Hsien Kao (tzuhsien-kao)

** Changed in: alsa-ucm-conf (Ubuntu Questing)
     Assignee: (unassigned) => Tzu-Hsien Kao (tzuhsien-kao)

** Changed in: alsa-ucm-conf (Ubuntu Questing)
       Status: New => In Progress

** Patch removed: "upstream-commits.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+attachment/5916008/+files/upstream-commits.debdiff

** Patch added: "alsa-ucm-conf_resolute_LP2126737.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+attachment/5919879/+files/alsa-ucm-conf_resolute_LP2126737.debdiff

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Noble:
  New
Status in alsa-ucm-conf source package in Plucky:
  New
Status in alsa-ucm-conf source package in Questing:
  New
Status in alsa-ucm-conf source package in Resolute:
  New

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

  **Affected Releases**

  This bug has been filed against Noble Numbat (24.04 LTS) as the
  primary target for the SRU.

  Following the SRU policy, this fix also needs to be verified in the
  development release. Could a bug triager please also mark this bug as
  affecting **`Ubuntu (Development)`**?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2126737 at bugs.launchpad.net  Thu Oct 23 03:26:42 2025
From: 2126737 at bugs.launchpad.net (Tzu-Hsien Kao)
Date: Thu, 23 Oct 2025 03:26:42 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176119000253.3977252.16734084756608789305.malone@juju-98d295-prod-launchpad-7>

** Patch added: "alsa-ucm-conf_questing_LP2126737.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+attachment/5919880/+files/alsa-ucm-conf_questing_LP2126737.debdiff

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Noble:
  New
Status in alsa-ucm-conf source package in Plucky:
  New
Status in alsa-ucm-conf source package in Questing:
  New
Status in alsa-ucm-conf source package in Resolute:
  New

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

  **Affected Releases**

  This bug has been filed against Noble Numbat (24.04 LTS) as the
  primary target for the SRU.

  Following the SRU policy, this fix also needs to be verified in the
  development release. Could a bug triager please also mark this bug as
  affecting **`Ubuntu (Development)`**?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2126737 at bugs.launchpad.net  Thu Oct 23 03:26:59 2025
From: 2126737 at bugs.launchpad.net (Tzu-Hsien Kao)
Date: Thu, 23 Oct 2025 03:26:59 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176119001932.3980700.16566174735453382228.malone@juju-98d295-prod-launchpad-7>

** Patch added: "alsa-ucm-conf_plucky_LP2126737.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+attachment/5919881/+files/alsa-ucm-conf_plucky_LP2126737.debdiff

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Noble:
  New
Status in alsa-ucm-conf source package in Plucky:
  New
Status in alsa-ucm-conf source package in Questing:
  New
Status in alsa-ucm-conf source package in Resolute:
  New

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

  **Affected Releases**

  This bug has been filed against Noble Numbat (24.04 LTS) as the
  primary target for the SRU.

  Following the SRU policy, this fix also needs to be verified in the
  development release. Could a bug triager please also mark this bug as
  affecting **`Ubuntu (Development)`**?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2126737 at bugs.launchpad.net  Thu Oct 23 03:27:15 2025
From: 2126737 at bugs.launchpad.net (Tzu-Hsien Kao)
Date: Thu, 23 Oct 2025 03:27:15 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176119003577.3258366.15553153345572444704.malone@juju-98d295-prod-launchpad-2>

** Patch added: "alsa-ucm-conf_noble_LP2126737.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+attachment/5919882/+files/alsa-ucm-conf_noble_LP2126737.debdiff

** Tags added: plucky questing resolute

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Noble:
  New
Status in alsa-ucm-conf source package in Plucky:
  New
Status in alsa-ucm-conf source package in Questing:
  New
Status in alsa-ucm-conf source package in Resolute:
  New

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

  **Affected Releases**

  This bug has been filed against Noble Numbat (24.04 LTS) as the
  primary target for the SRU.

  Following the SRU policy, this fix also needs to be verified in the
  development release. Could a bug triager please also mark this bug as
  affecting **`Ubuntu (Development)`**?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2126737 at bugs.launchpad.net  Thu Oct 23 03:32:26 2025
From: 2126737 at bugs.launchpad.net (Tzu-Hsien Kao)
Date: Thu, 23 Oct 2025 03:32:26 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176119034690.3265849.10624675894225652151.malone@juju-98d295-prod-launchpad-2>

Hello sponsors,

This is a follow-up to my previous sponsorship request.

I have now uploaded the updated and corrected debdiffs for all targeted
releases: Noble, Plucky, Questing, and Resolute. The previous debdiff
for Noble can be disregarded.

Could you please review the attached patches for sponsorship?

Thank you for your time.

** Changed in: alsa-ucm-conf (Ubuntu Noble)
     Assignee: Tzu-Hsien Kao (tzuhsien-kao) => (unassigned)

** Changed in: alsa-ucm-conf (Ubuntu Plucky)
     Assignee: Tzu-Hsien Kao (tzuhsien-kao) => (unassigned)

** Changed in: alsa-ucm-conf (Ubuntu Questing)
     Assignee: Tzu-Hsien Kao (tzuhsien-kao) => (unassigned)

** Changed in: alsa-ucm-conf (Ubuntu Resolute)
     Assignee: Tzu-Hsien Kao (tzuhsien-kao) => (unassigned)

** Changed in: alsa-ucm-conf (Ubuntu Noble)
       Status: In Progress => New

** Changed in: alsa-ucm-conf (Ubuntu Plucky)
       Status: In Progress => New

** Changed in: alsa-ucm-conf (Ubuntu Questing)
       Status: In Progress => New

** Changed in: alsa-ucm-conf (Ubuntu Resolute)
       Status: In Progress => New

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Noble:
  New
Status in alsa-ucm-conf source package in Plucky:
  New
Status in alsa-ucm-conf source package in Questing:
  New
Status in alsa-ucm-conf source package in Resolute:
  New

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

  **Affected Releases**

  This bug has been filed against Noble Numbat (24.04 LTS) as the
  primary target for the SRU.

  Following the SRU policy, this fix also needs to be verified in the
  development release. Could a bug triager please also mark this bug as
  affecting **`Ubuntu (Development)`**?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2124239 at bugs.launchpad.net  Thu Oct 23 06:58:03 2025
From: 2124239 at bugs.launchpad.net (Ernest Lotter)
Date: Thu, 23 Oct 2025 06:58:03 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176120268346.3590149.2211234158982881620.malone@juju-98d295-prod-launchpad-2>

Validation on -proposed in progress:
https://warthogs.atlassian.net/browse/SNAPDENG-34863

Please note we do not currently have resolute images available for
spread testing so this will be skipped.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2124239 at bugs.launchpad.net  Thu Oct 23 08:56:02 2025
From: 2124239 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 23 Oct 2025 08:56:02 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176120976275.3783066.2781837263734390446.malone@juju-98d295-prod-launchpad-2>

Hi snapd team.
Please beware of this regression: https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/2128350
I'm working on SRUing the fix to all series; ideally we would have that land in -updates before this.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2128881 at bugs.launchpad.net  Thu Oct 23 11:03:32 2025
From: 2128881 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 23 Oct 2025 11:03:32 -0000
Subject: [Bug 2128881] Re: Sync stegseek 0.6+git20210910.ff677b9-2 (universe)
 from Debian unstable (main)
References: <176077730510.2002076.6576041745009546915.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176121741349.2367170.4683899152879957089.malone@juju-98d295-prod-launchpad-4>

Oh, I synced it without seeing this sync request.

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

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

Title:
  Sync stegseek 0.6+git20210910.ff677b9-2 (universe) from Debian
  unstable (main)

Status in stegseek package in Ubuntu:
  Fix Released

Bug description:
  Please sync stegseek 0.6+git20210910.ff677b9-2 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev
    * Replace missing libjpeg62-turbo-dev by libjpeg-turbo8-dev

  The Debian package changed the build dependency to libjpeg-dev. Note
  that this is a different change than the current Ubuntu patch, but
  from my understanding the "generic" libjpeg-dev package is provided by
  the versioned 62 package in Debian and the versioned 8 package in
  Ubuntu. So I believe this replacement should work both places. :)

  
  Changelog entries since current resolute version 0.6+git20210910.ff677b9-1ubuntu1:

  stegseek (0.6+git20210910.ff677b9-2) unstable; urgency=medium

    * Team upload.
    * d/control:
      - Build-Depends: libjpeg62-turbo-dev -> libjpeg-dev (Closes: #1089021)
      - Drop 'Rules-Requires-Root: no', it's the standard now.
      - Bump Standards-Version to 4.7.2.
    * d/watch: Convert watch file to version 5 format.
    * d/copyright: Update copyright holders regarding Debian packaging.

   -- Sven Geuer <sge at debian.org>  Fri, 03 Oct 2025 21:44:40 +0200

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



From 2128880 at bugs.launchpad.net  Thu Oct 23 11:05:10 2025
From: 2128880 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 23 Oct 2025 11:05:10 -0000
Subject: [Bug 2128880] Re: Sync python-aiowebostv 0.4.2-3 (universe) from
 Debian unstable (main)
References: <176077677871.1994945.3545045479656113219.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176121751047.262156.3607345547460628701.malone@juju-98d295-prod-launchpad-3>

This bug was fixed in the package python-aiowebostv - 0.4.2-3
Sponsored for Hans Joachim Desserud (hjd)

---------------
python-aiowebostv (0.4.2-3) unstable; urgency=medium

  [ Ciel Zhao ]
  * Fix dependency typo.

  [ Tianyu Chen ]
  * Add myself to Uploaders.
  * Add d/salsa-ci.yml.
  * Update d/watch to version 5.
  * Use Github template in d/watch.

 -- Tianyu Chen <billchenchina2001 at gmail.com>  Sat, 30 Aug 2025 17:10:44
+0800

** Changed in: python-aiowebostv (Ubuntu)
       Status: New => Fix Released

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

Title:
  Sync python-aiowebostv 0.4.2-3 (universe) from Debian unstable (main)

Status in python-aiowebostv package in Ubuntu:
  Fix Released

Bug description:
  Please sync python-aiowebostv 0.4.2-3 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Fix typo in runtime dependency name preventing migration.
    * Fix typo in runtime dependency name preventing migration.
    * Fix typo in runtime dependency name preventing migration.

  The dependency typo is fixed in the Debian package as well.

  
  Changelog entries since current resolute version 0.4.2-2ubuntu1:

  python-aiowebostv (0.4.2-3) unstable; urgency=medium

    [ Ciel Zhao ]
    * Fix dependency typo.

    [ Tianyu Chen ]
    * Add myself to Uploaders.
    * Add d/salsa-ci.yml.
    * Update d/watch to version 5.
    * Use Github template in d/watch.

   -- Tianyu Chen <billchenchina2001 at gmail.com>  Sat, 30 Aug 2025
  17:10:44 +0800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-aiowebostv/+bug/2128880/+subscriptions



From 2129012 at bugs.launchpad.net  Thu Oct 23 11:15:20 2025
From: 2129012 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 23 Oct 2025 11:15:20 -0000
Subject: [Bug 2129012] Re: Sync elinks 0.18.0-1 (universe) from Debian sid
 (main)
References: <176095032577.1270725.8130093536412882514.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176121812085.2384058.9311231278493514303.malone@juju-98d295-prod-launchpad-4>

Looking at the build logs from Debian: sgml-parser-random takes 0.8s to
0.9s on amd64/armhf/arm64. So let's try to drop d/p/increase-test-
timeout.diff.

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

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

Title:
  Sync elinks 0.18.0-1 (universe) from Debian sid (main)

Status in elinks package in Ubuntu:
  Fix Released

Bug description:
  Please sync elinks 0.18.0-1 (universe) from Debian sid (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * No-change rebuild for libperl soname.
    * No-change rebuild for libperl soname.
    * No-change rebuild for libperl soname.
    * No-change rebuild for CVE-2024-3094
    * No-change rebuild for CVE-2024-3094
    * No-change rebuild for CVE-2024-3094
    * No-change rebuild for perlapi5.38t64.
    * Merge with Debian; remaining changes:
      - d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
        and arm64 failures leading to FTBFS issues in Ubuntu builders.
    * Non-maintainer upload.
    * Fix "FTBFS with Perl 5.38: error: redefinition of 'struct object'":
      add patch from upstream pull request/commit.
      (Closes: #1042844)
    * d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
      and arm64 failures leading to FTBFS issues in Ubuntu builders.
    * d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
      and arm64 failures leading to FTBFS issues in Ubuntu builders.
    * Rebuild against new perlapi-5.36.
    * Rebuild against new perlapi-5.36.
    * No-change rebuild for the perl update.
    * No-change rebuild for the perl update.
    * No-change rebuild for the perl update.
    * No-change rebuild against libidn12
    * No-change rebuild for the perl update.
    * No-change rebuild for the perl update.
    * No-change rebuild for the perl update.

  Explanation:
  According to Ubuntu changelog the only useful change looks the d/p/increase-test-timeout.diff patch (no idea if it can be dropped).
  The Fix "FTBFS with Perl 5.38: error: redefinition of 'struct object'": is also in Debian.

  Changelog entries since current resolute version 0.16.1.1-4.1ubuntu4:

  elinks (0.18.0-1) unstable; urgency=medium

    * New upstream version 0.18.0
    * Refreshed patch: 03_459467_ui.leds.enable_0.diff
    * Add fix-libdomdeps.patch to fix default value of libdomdeps to an empty
      list instead of false
    * Added define_SOCKS_SHIFT.patch to add missing definition for SOCKS_SHIFT

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Sun, 29 Dec 2024 18:40:32 +0100

  elinks (0.17.1.1-2) unstable; urgency=medium

    * d/rules: disable unicode combining characters (Closes: #1089693)

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Sat, 21 Dec 2024 15:35:18 +0100

  elinks (0.17.1.1-1) unstable; urgency=medium

    * New upstream version 0.17.1.1
    * Refreshed 14_debug_disable_Werror.diff patch
    * Remove fix_nonascii_inpfield.patch, applied upstream
    * Remove fix-protocol-test.patch, applied upstream
    * d/control:
      + bump standards version to 4.7.0
      + prettify build-deps list
    * Enable python hooks.
      Thanks to Dimitry Ishenko

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Fri, 06 Dec 2024 18:14:16 +0100

  elinks (0.17.0-2) unstable; urgency=medium

    * Add fix_nonascii_inpfield.patch to fix a bug with input fields not
      accepting non-ASCII input.

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Fri, 26 Jul 2024 04:29:19 +0200

  elinks (0.17.0-1) unstable; urgency=medium

    * New upstream version 0.17.0
    * Dropped patches applied upstream: fix-mailcap-test.diff & perl_5.38.patch
    * Refresh patches: 07_617713_cache_control.diff,
      14_debug_disable_Werror.diff
    * Added fix-protocol-test.patch to fix path for protocol.c test
    * d/rules:
      + remove sysconfdir setting (Closes: #1040656)
      + disable libcss support
      + fix typo
    * Update copyright years
    * d/control:
      + update build deps libidn-dev -> libidn2-dev
      + add libcurl4-gnutls-dev to build deps
      + update build-dep: pkg-config -> pkgconf
    * d/elinks-data.docs: README -> README.md
    * d/source.lintian-overrides: add an override for test/data.html
    * d/t/dump: add -no-home when invoking ELinks

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Thu, 11 Jul 2024 18:01:47 +0200

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



From 2129012 at bugs.launchpad.net  Thu Oct 23 11:15:50 2025
From: 2129012 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 23 Oct 2025 11:15:50 -0000
Subject: [Bug 2129012] Re: Sync elinks 0.18.0-1 (universe) from Debian sid
 (main)
References: <176095032577.1270725.8130093536412882514.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176121815034.282883.1164921397868355876.malone@juju-98d295-prod-launchpad-3>

This bug was fixed in the package elinks - 0.18.0-1
Sponsored for Oibaf (oibaf)

---------------
elinks (0.18.0-1) unstable; urgency=medium

  * New upstream version 0.18.0
  * Refreshed patch: 03_459467_ui.leds.enable_0.diff
  * Add fix-libdomdeps.patch to fix default value of libdomdeps to an empty
    list instead of false
  * Added define_SOCKS_SHIFT.patch to add missing definition for SOCKS_SHIFT

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Sun, 29 Dec 2024 18:40:32 +0100

elinks (0.17.1.1-2) unstable; urgency=medium

  * d/rules: disable unicode combining characters (Closes: #1089693)

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Sat, 21 Dec 2024 15:35:18 +0100

elinks (0.17.1.1-1) unstable; urgency=medium

  * New upstream version 0.17.1.1
  * Refreshed 14_debug_disable_Werror.diff patch
  * Remove fix_nonascii_inpfield.patch, applied upstream
  * Remove fix-protocol-test.patch, applied upstream
  * d/control:
    + bump standards version to 4.7.0
    + prettify build-deps list
  * Enable python hooks.
    Thanks to Dimitry Ishenko

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Fri, 06 Dec 2024 18:14:16 +0100

elinks (0.17.0-2) unstable; urgency=medium

  * Add fix_nonascii_inpfield.patch to fix a bug with input fields not
    accepting non-ASCII input.

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Fri, 26 Jul 2024 04:29:19 +0200

elinks (0.17.0-1) unstable; urgency=medium

  * New upstream version 0.17.0
  * Dropped patches applied upstream: fix-mailcap-test.diff & perl_5.38.patch
  * Refresh patches: 07_617713_cache_control.diff,
    14_debug_disable_Werror.diff
  * Added fix-protocol-test.patch to fix path for protocol.c test
  * d/rules:
    + remove sysconfdir setting (Closes: #1040656)
    + disable libcss support
    + fix typo
  * Update copyright years
  * d/control:
    + update build deps libidn-dev -> libidn2-dev
    + add libcurl4-gnutls-dev to build deps
    + update build-dep: pkg-config -> pkgconf
  * d/elinks-data.docs: README -> README.md
  * d/source.lintian-overrides: add an override for test/data.html
  * d/t/dump: add -no-home when invoking ELinks

 -- أحمد المحمودي (Ahmed El-Mahmoudy)
<aelmahmoudy at users.sourceforge.net>  Thu, 11 Jul 2024 18:01:47 +0200

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

Title:
  Sync elinks 0.18.0-1 (universe) from Debian sid (main)

Status in elinks package in Ubuntu:
  Fix Released

Bug description:
  Please sync elinks 0.18.0-1 (universe) from Debian sid (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * No-change rebuild for libperl soname.
    * No-change rebuild for libperl soname.
    * No-change rebuild for libperl soname.
    * No-change rebuild for CVE-2024-3094
    * No-change rebuild for CVE-2024-3094
    * No-change rebuild for CVE-2024-3094
    * No-change rebuild for perlapi5.38t64.
    * Merge with Debian; remaining changes:
      - d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
        and arm64 failures leading to FTBFS issues in Ubuntu builders.
    * Non-maintainer upload.
    * Fix "FTBFS with Perl 5.38: error: redefinition of 'struct object'":
      add patch from upstream pull request/commit.
      (Closes: #1042844)
    * d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
      and arm64 failures leading to FTBFS issues in Ubuntu builders.
    * d/p/increase-test-timeout.diff: increase test timeout to avoid armhf
      and arm64 failures leading to FTBFS issues in Ubuntu builders.
    * Rebuild against new perlapi-5.36.
    * Rebuild against new perlapi-5.36.
    * No-change rebuild for the perl update.
    * No-change rebuild for the perl update.
    * No-change rebuild for the perl update.
    * No-change rebuild against libidn12
    * No-change rebuild for the perl update.
    * No-change rebuild for the perl update.
    * No-change rebuild for the perl update.

  Explanation:
  According to Ubuntu changelog the only useful change looks the d/p/increase-test-timeout.diff patch (no idea if it can be dropped).
  The Fix "FTBFS with Perl 5.38: error: redefinition of 'struct object'": is also in Debian.

  Changelog entries since current resolute version 0.16.1.1-4.1ubuntu4:

  elinks (0.18.0-1) unstable; urgency=medium

    * New upstream version 0.18.0
    * Refreshed patch: 03_459467_ui.leds.enable_0.diff
    * Add fix-libdomdeps.patch to fix default value of libdomdeps to an empty
      list instead of false
    * Added define_SOCKS_SHIFT.patch to add missing definition for SOCKS_SHIFT

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Sun, 29 Dec 2024 18:40:32 +0100

  elinks (0.17.1.1-2) unstable; urgency=medium

    * d/rules: disable unicode combining characters (Closes: #1089693)

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Sat, 21 Dec 2024 15:35:18 +0100

  elinks (0.17.1.1-1) unstable; urgency=medium

    * New upstream version 0.17.1.1
    * Refreshed 14_debug_disable_Werror.diff patch
    * Remove fix_nonascii_inpfield.patch, applied upstream
    * Remove fix-protocol-test.patch, applied upstream
    * d/control:
      + bump standards version to 4.7.0
      + prettify build-deps list
    * Enable python hooks.
      Thanks to Dimitry Ishenko

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Fri, 06 Dec 2024 18:14:16 +0100

  elinks (0.17.0-2) unstable; urgency=medium

    * Add fix_nonascii_inpfield.patch to fix a bug with input fields not
      accepting non-ASCII input.

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Fri, 26 Jul 2024 04:29:19 +0200

  elinks (0.17.0-1) unstable; urgency=medium

    * New upstream version 0.17.0
    * Dropped patches applied upstream: fix-mailcap-test.diff & perl_5.38.patch
    * Refresh patches: 07_617713_cache_control.diff,
      14_debug_disable_Werror.diff
    * Added fix-protocol-test.patch to fix path for protocol.c test
    * d/rules:
      + remove sysconfdir setting (Closes: #1040656)
      + disable libcss support
      + fix typo
    * Update copyright years
    * d/control:
      + update build deps libidn-dev -> libidn2-dev
      + add libcurl4-gnutls-dev to build deps
      + update build-dep: pkg-config -> pkgconf
    * d/elinks-data.docs: README -> README.md
    * d/source.lintian-overrides: add an override for test/data.html
    * d/t/dump: add -no-home when invoking ELinks

   -- أحمد المحمودي (Ahmed El-Mahmoudy)
  <aelmahmoudy at users.sourceforge.net>  Thu, 11 Jul 2024 18:01:47 +0200

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



From 2125407 at bugs.launchpad.net  Thu Oct 23 11:26:57 2025
From: 2125407 at bugs.launchpad.net (Benjamin Drung)
Date: Thu, 23 Oct 2025 11:26:57 -0000
Subject: [Bug 2125407] Re: New upstream release landed in debian
References: <175854935122.2339268.5514828628887767207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176121881761.4021276.3213256879174168556.malone@juju-98d295-prod-launchpad-2>

The autosync takes the packages from Debian. Autosync is enabled until
feature freeze.

Unrelated to autosync or not: Any particular reason we need to sync from
experimental instead of waiting for it to land in unstable? In other
words: Is there a benefit of that version? Why hasn't it been uploaded
to unstable?

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

Title:
  New upstream release landed in debian

Status in glm package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  The latest version of this package, from Feb. 2024, landed in debian:

  libglm-dev | 1.0.1+ds-2    | experimental | all

  Could it be synced to ubuntu/devel?

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



From 2128350 at bugs.launchpad.net  Thu Oct 23 11:43:03 2025
From: 2128350 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 23 Oct 2025 11:43:03 -0000
Subject: [Bug 2128350] [NEW] Some desktop snaps are no longer visible in the
 apps menu
References: <176062998947.2963269.10879243361967771236.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176121978415.321337.9034926570655303086.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Alessandro Astone (aleasto):

[ Impact ]

Malcontent is a parental control mechanism implemented in GNOME Shell.
It supports hiding applications from the application menu.

Some desktop snaps like telegram-desktop are no longer visible in GNOME Shell when libmalcontent is installed, even without any filters applied. Which snaps are hidden depends on the numbers of command-line arguments they specify in the Exec line. If it's more than 2, then the snap will be hidden.
For example, telegram-desktop uses:

Exec=/snap/bin/telegram-desktop -- %U

Ubuntu ships a patch in malcontent to allow filtering non-flatpak applications too.
This patch assumed that a desktop snap Exec= line would always follow the format `Exec=env BAMF_DESKTOP_FILE_HINT=foo.desktop /snap/bin/foo arg1 arg2`, so it would interpret the third argument as the absolute binary path.

That was changed in snapd version 2.72 to remove the
BAMF_DESKTOP_FILE_HINT environment variable, so the Exec line now
follows the format `Exec=/snap/bin/foo arg1 arg2`. The third argument is
no longer the binary's absolute path, and things break.

Malcontent needs to be adapted to not assume that the snap binary is
always the third argument.

[ Test Plan ]

1. Install the `malcontent` deb package
   -> this is pre-installed on some OEM installs.
2. Log-out, log-in again.
3. Install snapd 2.72 or newer, available from the candidate channel:
   `sudo snap refresh snapd --candidate`
4. Install the `telegram-desktop` snap
5. Open the GNOME Shell application launcher
6. Search for Telegram
7. Verify that the Telegram app is listed.

[ Where problems could occur ]

Problems would manifest with applications being incorrectly filtered out
or not filtered out.

The patch should make sure that it is future-proof by not assuming the
position of the binary path in the command-line a-priori.

** Affects: malcontent (Ubuntu)
     Importance: High
     Assignee: Alessandro Astone (aleasto)
         Status: Fix Released

** Affects: malcontent (Ubuntu Jammy)
     Importance: High
     Assignee: Alessandro Astone (aleasto)
         Status: In Progress

** Affects: malcontent (Ubuntu Noble)
     Importance: High
     Assignee: Alessandro Astone (aleasto)
         Status: In Progress

** Affects: malcontent (Ubuntu Plucky)
     Importance: High
     Assignee: Alessandro Astone (aleasto)
         Status: Fix Committed

** Affects: malcontent (Ubuntu Questing)
     Importance: High
     Assignee: Alessandro Astone (aleasto)
         Status: Fix Committed


** Tags: udeng-8372
-- 
Some desktop snaps are no longer visible in the apps menu
https://bugs.launchpad.net/bugs/2128350
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2125407 at bugs.launchpad.net  Thu Oct 23 12:39:23 2025
From: 2125407 at bugs.launchpad.net (Antoine Lassagne)
Date: Thu, 23 Oct 2025 12:39:23 -0000
Subject: [Bug 2125407] Re: New upstream release landed in debian
References: <175854935122.2339268.5514828628887767207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176122316393.2520325.15990902579549225533.malone@juju-98d295-prod-launchpad-4>

Some context: I had a customer request for this to be updated. But now
it's not required anymore, so there is no rush really.

Sorry for the unnecessary noise.

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

Title:
  New upstream release landed in debian

Status in glm package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  The latest version of this package, from Feb. 2024, landed in debian:

  libglm-dev | 1.0.1+ds-2    | experimental | all

  Could it be synced to ubuntu/devel?

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



From 2060730 at bugs.launchpad.net  Thu Oct 23 14:27:21 2025
From: 2060730 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 23 Oct 2025 14:27:21 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176122964149.610346.7151090791949139442.malone@juju-98d295-prod-launchpad-3>

Tested packagekit 1.2.8-2ubuntu1.4 on ARM64 Ubuntu 24.04.3 LTS:

ubuntu at pipsey:~$ uname -a
Linux pipsey 6.8.0-86-generic #87-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 17:54:31 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

ubuntu at pipsey:~$ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-fdkaac-1.20.0-1build2.arm64 (ubuntu-noble-multiverse)	GStreamer FDK AAC plugins
Available   	gstreamer1.0-libav-1.24.1-1build1.arm64 (ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.arm64 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set
Available   	gstreamer1.0-plugins-good-1.24.2-1ubuntu1.2.arm64 (ubuntu-noble-updates-main)	GStreamer plugins from the "good" set

ubuntu at pipsey:~$ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-fdkaac-1.20.0-1build2.arm64 (ubuntu-noble-multiverse)	GStreamer FDK AAC plugins
Available   	gstreamer1.0-libav-1.24.1-1build1.arm64 (ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.arm64 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set
Available   	gstreamer1.0-plugins-good-1.24.2-1ubuntu1.2.arm64 (ubuntu-noble-updates-main)	GStreamer plugins from the "good" set

ubuntu at pipsey:~$ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-libav-1.24.1-1build1.arm64 (ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.arm64 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set

ubuntu at pipsey:~$ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-libav-1.24.1-1build1.arm64 (ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.arm64 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set

---

Tested packagekit 1.2.8-2ubuntu1.4 on AMD64 Ubuntu 24.04.3 LTS:

aleasto at noble:~$ uname -a
Linux noble 6.14.0-33-generic #33~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 19 17:02:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

aleasto at noble:~$ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-fdkaac-1.20.0-1build2.amd64 (ubuntu-noble-multiverse)	GStreamer FDK AAC plugins
Installed   	gstreamer1.0-libav-1.24.1-1build1.amd64 (manual:ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.amd64 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set
Installed   	gstreamer1.0-plugins-good-1.24.2-1ubuntu1.2.amd64 (auto:ubuntu-noble-updates-main)	GStreamer plugins from the "good" set

aleasto at noble:~$ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-fdkaac-1.20.0-1build2.amd64 (ubuntu-noble-multiverse)	GStreamer FDK AAC plugins
Installed   	gstreamer1.0-libav-1.24.1-1build1.amd64 (manual:ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-libav-1.24.1-1build1.i386 (ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.amd64 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.i386 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set
Installed   	gstreamer1.0-plugins-good-1.24.2-1ubuntu1.2.amd64 (auto:ubuntu-noble-updates-main)	GStreamer plugins from the "good" set
Available   	gstreamer1.0-plugins-good-1.24.2-1ubuntu1.2.i386 (ubuntu-noble-updates-main)	GStreamer plugins from the "good" set

aleasto at noble:~$ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Installed   	gstreamer1.0-libav-1.24.1-1build1.amd64 (manual:ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.amd64 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set

aleasto at noble:~$ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Installed   	gstreamer1.0-libav-1.24.1-1build1.amd64 (manual:ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-libav-1.24.1-1build1.i386 (ubuntu-noble-universe)	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.amd64 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set
Available   	gstreamer1.0-plugins-bad-1.24.2-1ubuntu4.i386 (ubuntu-noble-universe)	GStreamer plugins from the "bad" set


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

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  Fix Committed
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  Fix Committed
Status in packagekit source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2125448 at bugs.launchpad.net  Thu Oct 23 14:38:05 2025
From: 2125448 at bugs.launchpad.net (Dariusz Gadomski)
Date: Thu, 23 Oct 2025 14:38:05 -0000
Subject: [Bug 2125448] Re: Burst parameter of tc police only allows 4GB while
 the kernel can support much more
References: <175857809490.3129996.13210339429758148161.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176123028609.884044.10365811441633889989.launchpad@juju-98d295-prod-launchpad-7>

** Also affects: iproute2 (Ubuntu Resolute)
   Importance: Undecided
     Assignee: Jorge Merlino (jorge-merlino)
       Status: In Progress

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

Title:
  Burst parameter of tc police only allows 4GB while the kernel can
  support much more

Status in iproute2 package in Ubuntu:
  In Progress
Status in iproute2 source package in Jammy:
  In Progress
Status in iproute2 source package in Noble:
  In Progress
Status in iproute2 source package in Plucky:
  In Progress
Status in iproute2 source package in Questing:
  In Progress
Status in iproute2 source package in Resolute:
  In Progress

Bug description:
  [Impact]
  The tc police burst option limits the size of the burst up to 4 GiB, i.e., UINT_MAX for a 32 bit unsigned int. However, the underlying implementation of burst is computed as "time at the specified rate", and for higher rates, a burst size exceeding 4 GiB is feasible without modification to the kernel.
  Conversely, there can be bursts smaller that 4 GiB that overflow the burst time calculation and that was not detected.

  [Test Plan]
  All the following commands must be run as root. We are assuming the tested interface is eth0.

  Add fq_codel queuing discipline

  # tc qdisc add dev eth0 root fq_codel

  Check the assigned discipline number

  # tc -s qdisc show dev eth0
  qdisc fq_codel nnnn: root refcnt 13 limit ...

  Note the 4 digits nnnn number. It should be substituted for the nnnn
  number in the rest of the following commands.

  1) Tests before the patch is applied

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate and see
  that it fails:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-exceed reclassify
  Error: argument "4294967296" is wrong: buffer

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-
  exceed reclassify

  Check if it was set correctly:

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 1Mbit burst 15261b mtu 64Kb [001d1bf8] peakrate 10Gbit action reclassify overhead 0b

  We can see a result with the overflowed buffer (burst is 15261b)

  2) Tests after the patch is applied:

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-
  exceed reclassify

  We can check that it was set correctly (burst is 4Gb):

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 10Gbit burst 4Gb mtu 64Kb [03333334] peakrate 10Gbit action reclassify overhead 0b

  Remove the filter:

  # tc filter del dev eth0 protocol ip prio 1 parent nnnn:

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-exceed reclassify
  POLICE: burst out of range

  We see that it is out of range

  [Where problems could occur]
  Externally the only difference with the installed patch is that some commands that will previously overflow without errors will now fail. That might break some scripts but it can be argued that they were already broken before.

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



From 2124239 at bugs.launchpad.net  Thu Oct 23 14:58:41 2025
From: 2124239 at bugs.launchpad.net (Sergio Cazzolato)
Date: Thu, 23 Oct 2025 14:58:41 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176123152178.917309.9092706601129537919.malone@juju-98d295-prod-launchpad-7>

Executed automated tests and the results are ok. Left a comment in the
jira ticket about which prs address each test failure.

See https://warthogs.atlassian.net/browse/SNAPDENG-34863

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2060730 at bugs.launchpad.net  Thu Oct 23 15:00:39 2025
From: 2060730 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 23 Oct 2025 15:00:39 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176123163975.186168.7568919011881188989.malone@juju-98d295-prod-launchpad-2>

Tested packagekit 1.3.0-3ubuntu0.2 on ARM64 Ubuntu 25.04:

ubuntu at pipsey:~$ uname -a
Linux pipsey 6.14.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 16 16:43:19 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

ubuntu at pipsey:~$ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-fdkaac-1.20.0-1build2.arm64 (ubuntu-plucky-multiverse)	GStreamer FDK AAC plugins
Available   	gstreamer1.0-libav-1.26.0-1.arm64 (ubuntu-plucky-universe)  	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.26.0-1ubuntu2.1.arm64 (ubuntu-plucky-updates-universe)	GStreamer plugins from the "bad" set
Available   	gstreamer1.0-plugins-good-1.26.0-1ubuntu2.1.arm64 (ubuntu-plucky-updates-main)	GStreamer plugins from the "good" set

ubuntu at pipsey:~$ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-fdkaac-1.20.0-1build2.arm64 (ubuntu-plucky-multiverse)	GStreamer FDK AAC plugins
Available   	gstreamer1.0-libav-1.26.0-1.arm64 (ubuntu-plucky-universe)  	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.26.0-1ubuntu2.1.arm64 (ubuntu-plucky-updates-universe)	GStreamer plugins from the "bad" set
Available   	gstreamer1.0-plugins-good-1.26.0-1ubuntu2.1.arm64 (ubuntu-plucky-updates-main)	GStreamer plugins from the "good" set

ubuntu at pipsey:~$ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-libav-1.26.0-1.arm64 (ubuntu-plucky-universe)  	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.26.0-1ubuntu2.1.arm64 (ubuntu-plucky-updates-universe)	GStreamer plugins from the "bad" set

ubuntu at pipsey:~$ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-libav-1.26.0-1.arm64 (ubuntu-plucky-universe)  	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.26.0-1ubuntu2.1.arm64 (ubuntu-plucky-updates-universe)	GStreamer plugins from the "bad" set

---

Tested packagekit 1.3.0-3ubuntu0.2 on AMD64 Ubuntu 25.04, without the
i386 dpkg architecture:

aleasto at plucky:~$ uname -a
Linux plucky 6.14.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug  7 18:32:38 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

aleasto at plucky:~$ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-fdkaac-1.20.0-1build2.amd64 (ubuntu-plucky-multiverse)	GStreamer FDK AAC plugins
Available   	gstreamer1.0-libav-1.26.0-1.amd64 (ubuntu-plucky-universe)  	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.26.0-1ubuntu2.1.amd64 (ubuntu-plucky-updates-universe)	GStreamer plugins from the "bad" set
Installed   	gstreamer1.0-plugins-good-1.26.0-1ubuntu2.1.amd64 (auto:ubuntu-plucky-updates-main)	GStreamer plugins from the "good" set

aleasto at plucky:~$ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-fdkaac-1.20.0-1build2.amd64 (ubuntu-plucky-multiverse)	GStreamer FDK AAC plugins
Available   	gstreamer1.0-libav-1.26.0-1.amd64 (ubuntu-plucky-universe)  	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.26.0-1ubuntu2.1.amd64 (ubuntu-plucky-updates-universe)	GStreamer plugins from the "bad" set
Installed   	gstreamer1.0-plugins-good-1.26.0-1ubuntu2.1.amd64 (auto:ubuntu-plucky-updates-main)	GStreamer plugins from the "good" set

aleasto at plucky:~$ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-libav-1.26.0-1.amd64 (ubuntu-plucky-universe)  	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.26.0-1ubuntu2.1.amd64 (ubuntu-plucky-updates-universe)	GStreamer plugins from the "bad" set

aleasto at plucky:~$ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
Getting provides                        [=========================]         
Loading cache                           [=========================]         
Querying                                [=========================]         
Finished                                [=========================]         
Available   	gstreamer1.0-libav-1.26.0-1.amd64 (ubuntu-plucky-universe)  	ffmpeg plugin for GStreamer
Available   	gstreamer1.0-plugins-bad-1.26.0-1ubuntu2.1.amd64 (ubuntu-plucky-updates-universe)	GStreamer plugins from the "bad" set


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

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  Fix Committed
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  Fix Committed
Status in packagekit source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2127792 at bugs.launchpad.net  Thu Oct 23 16:44:02 2025
From: 2127792 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 23 Oct 2025 16:44:02 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176123784337.1314932.9438675063417914780.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~antoinelassagne/ubuntu/+source/gnome-remote-desktop/+git/gnome-remote-desktop/+merge/494934

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Thu Oct 23 16:53:26 2025
From: 2127792 at bugs.launchpad.net (Antoine Lassagne)
Date: Thu, 23 Oct 2025 16:53:26 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176123840693.2957733.10711897196054997308.malone@juju-98d295-prod-launchpad-4>

I've uploaded all versions in merge proposals to this PPA:
https://launchpad.net/~antoinelassagne/+archive/ubuntu/ppa/+packages?field.name_filter=gnome-remote-desktop&field.status_filter=published&field.series_filter=

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2123886 at bugs.launchpad.net  Thu Oct 23 18:55:35 2025
From: 2123886 at bugs.launchpad.net (Zachary Raines)
Date: Thu, 23 Oct 2025 18:55:35 -0000
Subject: [Bug 2123886] Re: Add missing ARM-cores to support Vera-based systems
References: <175797801894.3652365.4625127746591030660.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176124573588.3148454.9583689454823321902.malone@juju-98d295-prod-launchpad-4>

UPDATE: Version 2.41.2-4ubuntu1
(https://git.launchpad.net/ubuntu/+source/util-
linux/tag/?h=import/2.41.2-4ubuntu1) containing this fix has been merged
into resolute-proposed.

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

Title:
  Add missing ARM-cores to support Vera-based systems

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Noble:
  In Progress
Status in util-linux source package in Plucky:
  In Progress
Status in util-linux source package in Questing:
  In Progress
Status in util-linux source package in Resolute:
  In Progress

Bug description:
  [Impact]

  When running "lscpu" on a Vera-based system, it doesn't report a model
  name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Noble's
  (and previous) versions.

  https://github.com/util-linux/util-
  linux/commit/908777470d403ec30c525472ba0d3701c9c5a223

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Olympus

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems.

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2123886/+subscriptions



From 2125145 at bugs.launchpad.net  Thu Oct 23 19:34:40 2025
From: 2125145 at bugs.launchpad.net (Andreas Hasenack)
Date: Thu, 23 Oct 2025 19:34:40 -0000
Subject: [Bug 2125145] Re: [SRU] Makedumpfile: Errors and Page Exclusions When
 Opening Kernel Crashdump Files Generated on the Latest HWE Kernel
References: <175821630447.1842424.14764010785335167964.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176124808041.630041.1461162123753264650.malone@juju-98d295-prod-launchpad-2>

>From what I understood, without the updated src:crash package, it doesn't make sense to accept the src:makedumpfile upload for noble at this time, right? Because it's not going to be testable.
  And src:crash still has quite a long road to traverse, needing an update all the way up to Resolute still?

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

Title:
  [SRU] Makedumpfile: Errors and Page Exclusions When Opening Kernel
  Crashdump Files Generated on the Latest HWE Kernel

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in crash source package in Noble:
  New
Status in makedumpfile source package in Noble:
  New
Status in crash source package in Plucky:
  New
Status in makedumpfile source package in Plucky:
  Fix Released
Status in crash source package in Questing:
  New
Status in makedumpfile source package in Questing:
  Fix Released
Status in crash source package in Resolute:
  Confirmed
Status in makedumpfile source package in Resolute:
  Fix Released

Bug description:
  Note: Original description is at the bottom of this report

  [Impact]

  The current versions of Makedumpfile and Crash in the -updates pocket
  on Noble do not support the latest hardware enablement kernel for that
  platform, which is 6.14. There are several architecture-dependent and
  kernel flavor-dependent behaviours that I will outline below, but the
  steps to reproduce are the same.

  Reproducer steps:
  -----------------

  Boot into a hardware enablement kernel. For example, on arm64 use the
  6.14.0-1008-nvidia-64k kernel:

  KERNEL_VERSION=6.14.0-1008-nvidia-64k
  DISTRO=noble

  sudo apt update
  sudo apt install ubuntu-dbgsym-keyring
  echo "deb http://ddebs.ubuntu.com ${DISTRO} main restricted universe multiverse
  deb http://ddebs.ubuntu.com ${DISTRO}-updates main restricted universe multiverse | \
    sudo tee /etc/apt/sources.list.d/ddebs.list
  sudo apt update
  sudo apt install linux-image-${KERNEL_VERSION}
  sudo apt install linux-image-unsigned-${KERNEL_VERSION}-dbgsym

  Modify grub's cmdline to specify a crashkernel: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=512M" # Or similar
  sudo update-grub
  sudo apt install kexec-tools kdump-tools crash makedumpfile
  sudo systemctl enable kdump-tools
  sudo systemctl start kdump-tools
  sudo reboot

  echo c | sudo tee /proc/sysrq-trigger

  After the machine recovers,

  crash /usr/lib/debug/boot/<kernel-dbgsym> /var/crash/<dump-dir>/<dump-
  file>

  Results on Arm64
  ----------------

  crash 8.0.4
  Copyright (C) 2002-2022  Red Hat, Inc.
  ...
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  please wait... (gathering task table data)
  crash: page excluded: kernel virtual address: ffff07ffa042d8e0  type: "xa_node.slots[off]"

  Results on amd64
  ----------------

  On an amd64 machine, using a kernel such as linux-
  image-6.14.0-29-generic results in crash failing to open. No error is
  printed but we don't obtain the prompt:

  crash 8.0.4
  ...
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  # Program exits and no prompt is presented

  [Test Plan]

  * Ensure that with the proposed combination of makedumpfile and crash is capable of generating and subsequently opening crashdumps on the HWE and GA kernels available for that platform. Here is the mapping ATOW:
  Noble GA: 6.8
  Noble HWE: 6.14
  Plucky (interim release, no HWE): 6.14
  Questing (interim release, no HWE): 6.17
  Resolute (development): 6.17 (as of Oct. 14th 2025)

  * Ensure all of crash's commands produce the expected output (eg. ps,
  mount, files, vm, vtop, runq, etc.)

  * If bugs are found in generating and reading crashdumps on the HWE
  kernel on other architectures (s390x, etc.), this test plan can be
  expanded to include those.

  [Where Problems Could Occur]
  * Crash and Makedumpfile are designed to be backwards-compatible, so the risk of regression when backporting a commit is low - however, not zero. This is why it will be important to ensure that the proposed combination of Makedumpfile and crash does not break existing environments - eg. the GA kernel

  * The matrix of hardware and kernel versions (including derivative /
  cloud kernels) to test again is extensive. It's possible that the
  commits identified to solve the known problems will not be
  comprehensive. For example, cpu architectures and kernels not in the
  test matrix may require additional commits to be backported.

  [Other Info]

  * Support/SEG are currently having conversations with the kernel team
  about the potential to proactively SRU / MRE the latest upstream crash
  version, and potentially Makedumpfile as well, alongside -hwe kernel
  releases to avoid this sort of regression in the future. Though, we
  understand this would require an SRUExceptionPolicy to be approved and
  published.

  [Investigation and summary of changes]

  We have identified that on the Makedumpfile at least two commits are needed:
  [1] https://github.com/makedumpfile/makedumpfile/commit/985e575253f1c2de8d6876cfe685c68a24ee06e1
  [2] https://github.com/makedumpfile/makedumpfile/commit/bad2a7c4fa75d37a41578441468584963028bdda

  These are patches to compensate for a change in the kernel's mapping
  of memory. Using the patched Makedumpfile helps, but it is not
  sufficient. Including the patches in Makedumpfile (or using the tip of
  upstream master), but opening with the currently distributed crash
  results in the following errors:

  eg. Patched Makedumpfile with crash 8.0.4 on Arm64:
  ---------------------------------------------------
  ...
  WARNING: cannot determine starting stack frame for task ffffd574e21b4800

  WARNING: cannot determine starting stack frame for task
  ffff07ff83296300

  WARNING: cannot determine starting stack frame for task
  ffff07ff83293f80

  WARNING: cannot determine starting stack frame for task
  ffff07ff83a04700

  WARNING: cannot determine starting stack frame for task ffff08010507c400
        KERNEL: /usr/lib/debug/boot/vmlinux-6.14.0-1008-nvidia-64k
      DUMPFILE: /var/crash/patched_mdf/dump.202509191531  [PARTIAL DUMP]
          CPUS: 128 [OFFLINE: 127]
          DATE: Thu Jan  1 00:00:00 UTC 1970
        UPTIME: 00:13:38
  LOAD AVERAGE: 0.12, 0.16, 0.10
         TASKS: 1573
      NODENAME: penguru
       RELEASE: 6.14.0-1008-nvidia-64k
       VERSION: #8-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 26 02:43:53 UTC 2025
       MACHINE: aarch64  (unknown Mhz)
        MEMORY: 63.8 GB
         PANIC: "Kernel panic - not syncing: sysrq triggered crash"
           PID: 7886
       COMMAND: "tee"
          TASK: ffff08010507c400  [THREAD_INFO: ffff08010507c400]
           CPU: 85
         STATE: TASK_RUNNING (PANIC)

  On Amd64
  --------
  Crash still fails to open.

  Therefore, in addition to the above Makedumpfile commits, crash
  requires some patching. With the above two commits to Makedumpfile I
  did a bisect on crash on amd64 and arm64.

  On the amd64 crash side, I have identified that [3] applied in isolation (cherry-picked) is sufficient on amd64
  [3] https://github.com/crash-utility/crash/commit/6752571d8d782d07537a258a1ec8919ebd1308ad

  I have also found that cherry-picking [4] and [5] resolves the issue on arm64 hardware in testflinger (using the machine agent penguru)
  [4] https://github.com/crash-utility/crash/commit/3879e9104826d5ae14a0824ec47ab60056a249a7
  [5] https://github.com/crash-utility/crash/commit/968debd0d5979dd9ddca3af0766bad714dbd51e3

  At this point, crash's commands such as mount, files, vm, etc. were
  still broken. To resolve this, [6] and [7] are needed

  [6] https://github.com/crash-utility/crash/commit/3d60d9d40457239683a5f20b01437db94f964fb8
  [7] https://github.com/crash-utility/crash/commit/2795136a515446b798ebbfa257c97f0ca6ecb8ec

  To SRU for Noble, crash must also be work on Plucky, Questing, and Resolute. The current version of makedumpfile on all of those series was found to be sufficient and so no SRU for makedumpfile is required on those. However for crash:
  * Plucky uses the 6.14 kernel, so no additional commits are needed - in fact due to the newer version available on Plucky, only [7] is needed.
  * Questing uses the 6.17 kernel. No issues other than [7] were observed on arm, but on amd64, an infinite loop while gdb loaded module symbols was observed, This is fixed in [8].
  * Resolute will ship with a newer kernel than 6.17, but as of October 14th, 2025 is currently based on 6.17. Currently the package in Debian unstable, which will autosync to Resolute does not contain the required fixes and so it will also require SRU with [7] and [8] unless superceded by an upstream (Debian) version bump.

  [8] https://github.com/crash-
  utility/crash/commit/e44a9a9d808c83fb846060f65e5aaa9d30b6e2c4

  PPA with all of the packages built (except resolute):
  https://launchpad.net/~bryanfraschetti/+archive/ubuntu/lp2125145

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

  Original Description:
  =====================

  24.04 LTS,
  Linux 6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 14 16:52:50 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  Problem Description:
  crash utility is crashing (error code 1) when attempting to analyze kernel crash dumps.

  Setup kdump & generated kernel panic using “echo 1 >
  /proc/sys/kernel/sysrq” but, crash cannot access it:

  # crash /usr/lib/debug/boot/vmlinux-6.14.0-29-generic
  dump.202509161821

  crash 8.0.4
  Copyright (C) 2002-2022  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2022  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-pc-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
      <http://www.gnu.org/software/gdb/documentation/>.

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  # echo $?
  1

  running as root user and file is readable fine:

  $ :/var/crash/202509161821# ls -l
  total 299144
  -rw------- 1 root whoopsie    119627 Sep 16 18:21 dmesg.202509161821
  -rw-r--r-- 1 root whoopsie 306200163 Sep 16 18:21 dump.202509161821

  symbol file is there:

  # ls -l /usr/lib/debug/boot/vmlinux-6.14.0-29-generic*
  -rw-r--r-- 1 root root 450705920 Aug 14 18:02 /usr/lib/debug/boot/vmlinux-6.14.0-29-generic

  tail of strace:

  14:06:20.661240 rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661281 rt_sigaction(SIGINT, {sa_handler=0x5ec383cbceb0, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661322 rt_sigaction(SIGSEGV, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661360 write(1, "\n", 1
  )       = 1 <0.000119>
  14:06:20.661579 lseek(3, 10312, SEEK_SET) = 10312 <0.000010>
  14:06:20.661617 read(3, "OSRELEASE=6.14.0-29-generic\nBUIL"..., 3276) = 3276 <0.000011>
  14:06:20.661748 unlink("/var/tmp/ramdump_elf_XXXXXX") = -1 ENOENT (No such file or directory) <0.002921>
  14:06:20.664817 exit_group(1)           = ?
  14:06:20.690105 +++ exited with 1 +++

  full crash strace https://filebin.net/custom-bin/crash.strace.1

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: crash 8.0.4-1ubuntu2
  ProcVersionSignature: Ubuntu 6.14.0-29.29~24.04.1-generic 6.14.8
  Uname: Linux 6.14.0-29-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Sep 18 20:21:26 2025
  InstallationDate: Installed on 2025-09-04 (14 days ago)
  InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: crash
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 2121607 at bugs.launchpad.net  Thu Oct 23 20:02:22 2025
From: 2121607 at bugs.launchpad.net (Andreas Hasenack)
Date: Thu, 23 Oct 2025 20:02:22 -0000
Subject: [Bug 2121607] Re: [SRU] Nova-api showing latency after upgrading to
 Caracal
References: <175639705793.728435.16126226382096763223.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176124974208.679559.745441181920414512.malone@juju-98d295-prod-launchpad-2>

Hello Chang, or anyone else affected,

Accepted python-attrs into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
attrs/21.2.0-1ubuntu1 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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: python-attrs (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  [SRU] Nova-api showing latency after upgrading to Caracal

Status in OpenStack Compute (nova):
  Confirmed
Status in python-attrs package in Ubuntu:
  In Progress
Status in python-attrs source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  * A resource leak bug in 21.2.0 of python-attrs (<https://github.com/python-attrs/attrs/issues/826>)
   caused performance issues when an application created many classes with the same name.

  * This caused a performance regression in nova through its dependency on python-jsonschema
    * The latency of API calls to nova increases over time

  [ Test Plan ]

   To reproduce the issue and confirm the fix:

  * Create a minimal openstack deployment, using e.g. devstack
  (<https://docs.openstack.org/devstack/latest/>).

  * Run a script which makes many calls to the nova API

   ---Script to call API---
   #!/bin/bash
   # --- Get a fresh token (requires openrc sourced first) ---
   get_token() {
       openstack token issue -f value -c id
   }

   OS_TOKEN=$(get_token)
   echo "Using token: $OS_TOKEN"

   # --- Send requests at 10 per second ---
   COUNT=0
   while true; do
       COUNT=$((COUNT + 1))
       STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
           -H "X-Auth-Token: $OS_TOKEN" \
           -H "Accept: application/json" \
           "$NOVA_URL/servers/detail")

       echo "$(date +'%F %T') [$COUNT] HTTP $STATUS"

       if [ "$STATUS" = "401" ]; then
           echo "[$(date)] Got 401 → refreshing token..."
           OS_TOKEN=$(get_token)
           continue # retry next loop with fresh token
       fi
       # sleep 0.1 # 0.1 sec → 10 per second
   done
   ---/Script to call API---

  * Simultaneously monitor the response time of API calls using the
  openstack CLI

   ---Script to monitor response time---
   #!/bin/bash

   # --- Again openrc must be sourced first ---
   os_quota() {
       openstack quota list --compute --timing --format=json
   }

   headers() {
       os_quota | grep -o -P '/(\w|\d){32}(/d)?' | tr '\n' ','
   }

   time_api() {
       os_quota |
           awk 'BEGIN { FS=","; ORS=","} /quota/ {print $2} END { printf "\n" }'
   }

   OUTPUT="api_calls_$(date +%Y-%m-%dT%H_%M_%S)"

   echo -n "# time," >>"$OUTPUT"
   headers >>"$OUTPUT"
   echo >>"$OUTPUT"

   i=0
   while true; do
       echo -n "$(date +'%F %T')," >>"$OUTPUT"
       time_api >>"$OUTPUT"
       echo -n "."
       if ((i > 80)); then
           i=0
           echo
       fi
       sleep 5
   done

  ---/Script to monitor response time---

  * Observe that the response time increases over time with python-attrs 21.2.0
    * I did this over a period of about 20 hrs.

  * Log in to the server hosting the nova API and upgrade python-attrs
  to 21.4.0

  * Repeat the above steps and observe that the response time remains
  stable over time.

  [ Where problems could occur ]

  * Other packages depend on python-attrs as a library and so could be
  affected.

  * From 21.2.0 to 21.4.0 there was one backward incompatible change change of which could potentailly cause issues:
    * <https://github.com/python-attrs/attrs/blob/21.4.0/CHANGELOG.rst>
      """
      When using @define, converters are now run by default when setting an attribute on an instance -- additionally to validators. I.e. the new default is on_setattr=[attrs.setters.convert, attrs.setters.validate].

      This is unfortunately a breaking change, but it was an oversight, impossible to raise a DeprecationWarning about, and it's better to fix it now while the APIs are very fresh with few users.
      """
    * Since there are no version pins of python-attrs excluding this version it is unlikely to break other packages.
    * It is possible that some users could be using the python3-attr package in their own code, but it is much more likely that
      for user code, attr would be installed via pip, either directly or within a virtualenv.

  * The version in noble is 23.2.0 which already includes all these
  changes and there doesn't seem to be any associated issues.

  [ Other Info ]

  * This SRU proposal bumps to 21.4.0 instead of 21.3.0 because 21.4.0 is a bug fix
    release for a regression in 21.3.0.

  * This is the first ubuntu specific modification to this package, but
  it is a fairly minor one and doesn't need to be carried forward to any
  other series.

  * A possible lighter weight alternative is to simply cherry pick the
  bugfix commit <https://github.com/python-
  attrs/attrs/commit/38580632ceac1cd6e477db71e1d190a4130beed4>

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



From 2123886 at bugs.launchpad.net  Thu Oct 23 20:12:21 2025
From: 2123886 at bugs.launchpad.net (Zachary Raines)
Date: Thu, 23 Oct 2025 20:12:21 -0000
Subject: [Bug 2123886] Re: Add missing ARM-cores to support Vera-based systems
References: <175797801894.3652365.4625127746591030660.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176125034307.1419152.11802846385262534716.launchpad@juju-98d295-prod-launchpad-7>

** Changed in: util-linux (Ubuntu Resolute)
       Status: In Progress => Fix Committed

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

Title:
  Add missing ARM-cores to support Vera-based systems

Status in util-linux package in Ubuntu:
  Fix Committed
Status in util-linux source package in Noble:
  In Progress
Status in util-linux source package in Plucky:
  In Progress
Status in util-linux source package in Questing:
  In Progress
Status in util-linux source package in Resolute:
  Fix Committed

Bug description:
  [Impact]

  When running "lscpu" on a Vera-based system, it doesn't report a model
  name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Noble's
  (and previous) versions.

  https://github.com/util-linux/util-
  linux/commit/908777470d403ec30c525472ba0d3701c9c5a223

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Olympus

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems.

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2123886/+subscriptions



From 2124239 at bugs.launchpad.net  Thu Oct 23 21:49:23 2025
From: 2124239 at bugs.launchpad.net (Sergio Cazzolato)
Date: Thu, 23 Oct 2025 21:49:23 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176125616399.3409813.3233506536824284450.malone@juju-98d295-prod-launchpad-4>

Also all manual tests passed for ubuntu 22.04 24.04 25.04 and 25.10.

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  In Progress

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2121783 at bugs.launchpad.net  Thu Oct 23 22:57:12 2025
From: 2121783 at bugs.launchpad.net (Vladimir Petko)
Date: Thu, 23 Oct 2025 22:57:12 -0000
Subject: [Bug 2121783] Re: [SRU][jammy] oem-somerville-wartortle-amd-meta
References: <175669802721.4174010.1102513115673847470.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176126023274.1420587.5540999128280644329.malone@juju-98d295-prod-launchpad-3>

Hi,

I have unsubscribed Ubuntu Sponsors, please resubscribe once SRU
template is updated.

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

Title:
  [SRU][jammy] oem-somerville-wartortle-amd-meta

Status in OEM Priority Project:
  Fix Committed
Status in oem-somerville-wartortle-amd-meta package in Ubuntu:
  In Progress

Bug description:
  [ Background ]

  Why are we making this update?

  [ 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

  [ 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.

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



From 2121580 at bugs.launchpad.net  Thu Oct 23 22:56:02 2025
From: 2121580 at bugs.launchpad.net (Vladimir Petko)
Date: Thu, 23 Oct 2025 22:56:02 -0000
Subject: [Bug 2121580] Re: [SRU][jammy] oem-somerville-wartortle-meta
References: <175637012322.1698499.15987368707040264496.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176126016277.1650601.1316917346991760185.malone@juju-98d295-prod-launchpad-7>

Hi,

I have unsubscribed Ubuntu Sponsors, please resubscribe Ubuntu Sponsors
once the SRU template is updated.

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

Title:
  [SRU][jammy] oem-somerville-wartortle-meta

Status in OEM Priority Project:
  Fix Committed
Status in oem-somerville-wartortle-meta package in Ubuntu:
  In Progress

Bug description:
  [ Background ]

  Why are we making this update?

  [ 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

  [ 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.

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



From 2125448 at bugs.launchpad.net  Thu Oct 23 23:39:14 2025
From: 2125448 at bugs.launchpad.net (Jorge Merlino)
Date: Thu, 23 Oct 2025 23:39:14 -0000
Subject: [Bug 2125448] Re: Burst parameter of tc police only allows 4GB while
 the kernel can support much more
References: <175857809490.3129996.13210339429758148161.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176126275504.982709.3066553872331954012.malone@juju-98d295-prod-launchpad-2>

V2 patch for Questing. Renaming as Resolute is using the same version.

** Patch added: "lp2125448_questing_v2.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2125448/+attachment/5920106/+files/lp2125448_questing_v2.debdiff

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

Title:
  Burst parameter of tc police only allows 4GB while the kernel can
  support much more

Status in iproute2 package in Ubuntu:
  In Progress
Status in iproute2 source package in Jammy:
  In Progress
Status in iproute2 source package in Noble:
  In Progress
Status in iproute2 source package in Plucky:
  In Progress
Status in iproute2 source package in Questing:
  In Progress
Status in iproute2 source package in Resolute:
  In Progress

Bug description:
  [Impact]
  The tc police burst option limits the size of the burst up to 4 GiB, i.e., UINT_MAX for a 32 bit unsigned int. However, the underlying implementation of burst is computed as "time at the specified rate", and for higher rates, a burst size exceeding 4 GiB is feasible without modification to the kernel.
  Conversely, there can be bursts smaller that 4 GiB that overflow the burst time calculation and that was not detected.

  [Test Plan]
  All the following commands must be run as root. We are assuming the tested interface is eth0.

  Add fq_codel queuing discipline

  # tc qdisc add dev eth0 root fq_codel

  Check the assigned discipline number

  # tc -s qdisc show dev eth0
  qdisc fq_codel nnnn: root refcnt 13 limit ...

  Note the 4 digits nnnn number. It should be substituted for the nnnn
  number in the rest of the following commands.

  1) Tests before the patch is applied

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate and see
  that it fails:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-exceed reclassify
  Error: argument "4294967296" is wrong: buffer

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-
  exceed reclassify

  Check if it was set correctly:

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 1Mbit burst 15261b mtu 64Kb [001d1bf8] peakrate 10Gbit action reclassify overhead 0b

  We can see a result with the overflowed buffer (burst is 15261b)

  2) Tests after the patch is applied:

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-
  exceed reclassify

  We can check that it was set correctly (burst is 4Gb):

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 10Gbit burst 4Gb mtu 64Kb [03333334] peakrate 10Gbit action reclassify overhead 0b

  Remove the filter:

  # tc filter del dev eth0 protocol ip prio 1 parent nnnn:

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-exceed reclassify
  POLICE: burst out of range

  We see that it is out of range

  [Where problems could occur]
  Externally the only difference with the installed patch is that some commands that will previously overflow without errors will now fail. That might break some scripts but it can be argued that they were already broken before.

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



From 2125448 at bugs.launchpad.net  Thu Oct 23 23:39:54 2025
From: 2125448 at bugs.launchpad.net (Jorge Merlino)
Date: Thu, 23 Oct 2025 23:39:54 -0000
Subject: [Bug 2125448] Re: Burst parameter of tc police only allows 4GB while
 the kernel can support much more
References: <175857809490.3129996.13210339429758148161.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176126279448.981824.18434770876900590557.malone@juju-98d295-prod-launchpad-2>

Patch for Resolute

** Patch added: "lp2125448_resolute.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2125448/+attachment/5920107/+files/lp2125448_resolute.debdiff

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

Title:
  Burst parameter of tc police only allows 4GB while the kernel can
  support much more

Status in iproute2 package in Ubuntu:
  In Progress
Status in iproute2 source package in Jammy:
  In Progress
Status in iproute2 source package in Noble:
  In Progress
Status in iproute2 source package in Plucky:
  In Progress
Status in iproute2 source package in Questing:
  In Progress
Status in iproute2 source package in Resolute:
  In Progress

Bug description:
  [Impact]
  The tc police burst option limits the size of the burst up to 4 GiB, i.e., UINT_MAX for a 32 bit unsigned int. However, the underlying implementation of burst is computed as "time at the specified rate", and for higher rates, a burst size exceeding 4 GiB is feasible without modification to the kernel.
  Conversely, there can be bursts smaller that 4 GiB that overflow the burst time calculation and that was not detected.

  [Test Plan]
  All the following commands must be run as root. We are assuming the tested interface is eth0.

  Add fq_codel queuing discipline

  # tc qdisc add dev eth0 root fq_codel

  Check the assigned discipline number

  # tc -s qdisc show dev eth0
  qdisc fq_codel nnnn: root refcnt 13 limit ...

  Note the 4 digits nnnn number. It should be substituted for the nnnn
  number in the rest of the following commands.

  1) Tests before the patch is applied

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate and see
  that it fails:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-exceed reclassify
  Error: argument "4294967296" is wrong: buffer

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-
  exceed reclassify

  Check if it was set correctly:

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 1Mbit burst 15261b mtu 64Kb [001d1bf8] peakrate 10Gbit action reclassify overhead 0b

  We can see a result with the overflowed buffer (burst is 15261b)

  2) Tests after the patch is applied:

  Try to set a filter with a burst of exactly 4Gb at 10Gbit rate:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  police rate 10Gbit peakrate 10Gbit burst 4294967296 mtu 64Kb conform-
  exceed reclassify

  We can check that it was set correctly (burst is 4Gb):

  # tc -raw filter get dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw
  filter parent nnnn: protocol ip pref 1 fw chain 0 handle 0x1  police 0x1 rate 10Gbit burst 4Gb mtu 64Kb [03333334] peakrate 10Gbit action reclassify overhead 0b

  Remove the filter:

  # tc filter del dev eth0 protocol ip prio 1 parent nnnn:

  Try to set a filter with a burst that is greater than the maximum
  time:

  # tc filter add dev eth0 protocol ip prio 1 parent nnnn: handle 1 fw police rate 1Mbit peakrate 10Gbit burst 34375000 mtu 64Kb conform-exceed reclassify
  POLICE: burst out of range

  We see that it is out of range

  [Where problems could occur]
  Externally the only difference with the installed patch is that some commands that will previously overflow without errors will now fail. That might break some scripts but it can be argued that they were already broken before.

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



From 2121948 at bugs.launchpad.net  Fri Oct 24 01:37:57 2025
From: 2121948 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 24 Oct 2025 01:37:57 -0000
Subject: [Bug 2121948] Re: [SRU] Support suspend/resume for IMX471 camera
 sensor
References: <175690774470.3522322.3912132826639117162.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176126987734.3723819.15118232245258707507.malone@juju-98d295-prod-launchpad-4>

Hi,

It appears that all necessary uploads are already done. I unsubscribing
Ubuntu Sponsors, please resubscribe back if it is not the case.

Best Regards, 
 Vladimir.

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

Title:
  [SRU] Support suspend/resume for IMX471 camera sensor

Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in linux-oem-6.14 package in Ubuntu:
  Invalid
Status in linux-oem-6.17 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Noble:
  Invalid
Status in linux-oem-6.14 source package in Noble:
  Fix Released
Status in linux-oem-6.17 source package in Noble:
  In Progress
Status in ipu6-drivers source package in Plucky:
  Fix Released
Status in linux-oem-6.14 source package in Plucky:
  Invalid
Status in linux-oem-6.17 source package in Plucky:
  Invalid
Status in ipu6-drivers source package in Questing:
  Fix Released
Status in linux-oem-6.14 source package in Questing:
  Invalid
Status in linux-oem-6.17 source package in Questing:
  Invalid

Bug description:
  [SRU Justification]

  [ Impact ]

  Sony imx471 is not explicitly powered on before trying to identify the module, leaving following error messages in kernel dmesg buffer:
  ```
  kernel: imx471 i2c-SONY471A:00: failed to find sensor: -5
  kernel: imx471 i2c-SONY471A:00: probe with driver imx471 failed with error -5
  ```

  Proposed fix in
  https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.

  [ Test Plan ]

  1. Install the dkms from -proposed pocket. The corresponding binary kernel module should be built automatically; if not, run:
  ```
  $ sudo dkms install --force ipu6-drivers/0~git202506270118.9bff7368 -k $(uname -r)
  ```

  2. Reboot to the same kernel to reload the drivers.

  3. Make sure the device is probed and up running:
  ```
  $ media-ctl -p
  Media controller API version 6.14.8

  Media device information
  ------------------------
  driver          intel-ipu7
  model           ipu7
  serial          
  bus info        PCI:intel-ipu7
  hw revision     0x17aa233b
  driver version  6.14.8
  ...
  ```

  4. Use https://webcamtests.com to verify the camera is really capable
  of streaming.

  [ Where problems could occur ]

  This fills the probe procedure as other similar camera sensors do. No
  known problem so far.

  [ Other Info ]

  This is a follow-up for bug 2107320 that supports IMX471 in linux-
  oem-6.11 and on. Nominate for Plucky, Questing for ipu6-drivers, which
  will be compiled within linux-oem-6.11 and on.

  ========== original bug report ==========

  This is a follow-up for bug 2107320, support Sony IMX471 camera sensor
  for Intel IPU7 platforms.

  Proposed fix in https://github.com/intel/ipu6-drivers/commit/faef397c5bfedcd3182cce27eab1539f5eaca9eb.
  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu     1575 F.... pipewire
                        ubuntu     1579 F.... wireplumber
   /dev/snd/seq:        ubuntu     1575 F.... pipewire
  CRDA: N/A
  CasperMD5CheckMismatches: ./casper/initrd ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for Ubuntu 24.04 for Lenovo
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-noble-oem-24.04c-20250822-50
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2025-08-29 (12 days ago)
  InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20250821)
  IwConfig:
   lo        no wireless extensions.

   wlp0s20f3  no wireless extensions.

   enx607d099eaa26  no wireless extensions.
  MachineType: LENOVO 21Q7ZCM3US
  Package: ipu6-drivers
  ProcFB: 0 xedrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-9011-oem root=UUID=0f9adf29-e579-4dc5-82a4-a98b51147867 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.14.0-9011.11+exp.19-oem 6.14.8
  RelatedPackageVersions:
   linux-restricted-modules-6.14.0-9011-oem N/A
   linux-backports-modules-6.14.0-9011-oem  N/A
   linux-firmware                           20240318.git3b128b60-0ubuntu2.17
  Tags: noble
  Uname: Linux 6.14.0-9011-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/03/2025
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N4CET39W.T02.HotKey (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21Q7ZCM3US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76576 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: dmi:bvnLENOVO:bvrN4CET39W.T02.HotKey(1.15):bd09/03/2025:br1.15:efr1.11:svnLENOVO:pn21Q7ZCM3US:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7ZCM3US:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:
  dmi.product.family: ThinkPad X9-15 Gen 1
  dmi.product.name: 21Q7ZCM3US
  dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1
  dmi.product.version: ThinkPad X9-15 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2121948/+subscriptions



From 2125407 at bugs.launchpad.net  Fri Oct 24 02:14:11 2025
From: 2125407 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 24 Oct 2025 02:14:11 -0000
Subject: [Bug 2125407] Re: New upstream release landed in debian
References: <175854935122.2339268.5514828628887767207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176127205146.1192498.10982003326995399620.malone@juju-98d295-prod-launchpad-2>

Hi,

I've unsubscribed Ubuntu Sponsors. Please feel to resubscribe if you
need this particular version.

Best Regards, 
 Vladimir.

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

Title:
  New upstream release landed in debian

Status in glm package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  The latest version of this package, from Feb. 2024, landed in debian:

  libglm-dev | 1.0.1+ds-2    | experimental | all

  Could it be synced to ubuntu/devel?

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



From 2127243 at bugs.launchpad.net  Fri Oct 24 03:10:37 2025
From: 2127243 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 24 Oct 2025 03:10:37 -0000
Subject: [Bug 2127243] Re:  [needs-packaging] spirv-reflect
References: <176008368998.1624766.844184339739748034.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176127543748.3849374.12510266162379257062.malone@juju-98d295-prod-launchpad-4>

Hi Antoine,

Nice work! There are a couple things though that need to be done before more formal review =)
- we need to package latest upstream vulkan-sdk-1.4.328.1 (unless there is a good reason not to) 
- version should be 1.4.328.1-0ubuntu1 (since it is Ubuntu first package)
- the changelog should be collapsed to a single entry
- the changelog should target resolute - we will need to backport/sru the package once it is uploaded
- maintainer set to Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>\
- Vcs-Git: https://salsa.debian.org/xorg-team/vulkan/spirv-reflect.git
  Vcs-Browser: https://salsa.debian.org/xorg-team/vulkan/spirv-reflect - those should point to launchpad, unless the package is uploaded to Debian/hosted on salsa
- Extended description of the source package has too long lines
- Extended description of the binary package could use some details (e.g. copy source package description)
- We need google test in dependencies to run build-time tests (see https://github.com/KhronosGroup/SPIRV-Reflect/blob/main/.github/workflows/linux-cmake-build.yml)  
- we need a manual page, it can be created with help2man
- lintian reports some warnings:
W: libspirv-reflect: extended-description-line-too-long line 3
W: libspirv-reflect: no-manual-page [usr/bin/spirv-reflect-pp]
W: libspirv-reflect: no-manual-page [usr/bin/spirv-reflect]
P: spirv-reflect source: package-does-not-install-examples [examples/]
P: spirv-reflect source: redundant-rules-requires-root-no-field [debian/control:11]
P: spirv-reflect source: trailing-whitespace [debian/control:6]
- It would be nice to provide autopkgtests
- Maybe split into spriv-reflect package with utilities, libspriv-reflect with a library and libspriv-reflect-dev with headers.

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

Title:
   [needs-packaging] spirv-reflect

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/KhronosGroup/SPIRV-Reflect
  License: Apache-2.0
  Notes: SPIRV-Reflect is a lightweight library that provides a C/C++ reflection API for SPIR-V shader bytecode in Vulkan applications.

  I wish to package spirv-reflect for Ubuntu.

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



From 2127243 at bugs.launchpad.net  Fri Oct 24 03:10:54 2025
From: 2127243 at bugs.launchpad.net (Vladimir Petko)
Date: Fri, 24 Oct 2025 03:10:54 -0000
Subject: [Bug 2127243] Re:  [needs-packaging] spirv-reflect
References: <176008368998.1624766.844184339739748034.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176127545485.1271441.9798137612370953787.malone@juju-98d295-prod-launchpad-2>

Please resubscribe sponsors when the package is ready!

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

Title:
   [needs-packaging] spirv-reflect

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/KhronosGroup/SPIRV-Reflect
  License: Apache-2.0
  Notes: SPIRV-Reflect is a lightweight library that provides a C/C++ reflection API for SPIR-V shader bytecode in Vulkan applications.

  I wish to package spirv-reflect for Ubuntu.

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



From 2127963 at bugs.launchpad.net  Fri Oct 24 04:21:34 2025
From: 2127963 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 24 Oct 2025 04:21:34 -0000
Subject: [Bug 2127963] [NEW] [SRU] Fix built-in volume button could not change
 the volume on Dell Pro Rugged tablet 
References: <176059742057.2080472.4294274592130371067.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176127969489.3962008.1315204405343427050.launchpad@juju-98d295-prod-launchpad-4>

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

[ Impact ]
The built-in volume button could not change the volume on the Dell Pro Rugged tablet.

[ Test Plan ]
Press the volume up/down button to see if the sound volume changed.

[ Where problems could occur ]
The quirk relies on the DMI product name for device identification; if the DMI string changes, the fix will no longer apply.

[ Other Info ]
Upstream commit:
https://gitlab.freedesktop.org/libinput/libinput/-/commit/d19f95ec215657d7e2f5efe2a6fe235fcbbf4e49

** Affects: libinput (Ubuntu)
     Importance: Undecided
     Assignee: Cyrus Lien (cyruslien)
         Status: In Progress


** Tags: fixed-in-libinput-1.30.0 fixed-upstream patch
-- 
[SRU] Fix built-in volume button could not change the volume on Dell Pro Rugged tablet 
https://bugs.launchpad.net/bugs/2127963
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127963 at bugs.launchpad.net  Fri Oct 24 04:21:35 2025
From: 2127963 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Fri, 24 Oct 2025 04:21:35 -0000
Subject: [Bug 2127963] Re: [SRU] Fix built-in volume button could not change
 the volume on Dell Pro Rugged tablet 
References: <176059742057.2080472.4294274592130371067.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176127969529.1894981.6520973762205369397.malone@juju-98d295-prod-launchpad-3>

The attachment "noble-libinput_1.25.0-1ubuntu3.2.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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2127963

Title:
  [SRU] Fix built-in volume button could not change the volume on Dell
  Pro Rugged tablet

Status in libinput package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]
  The built-in volume button could not change the volume on the Dell Pro Rugged tablet.

  [ Test Plan ]
  Press the volume up/down button to see if the sound volume changed.

  [ Where problems could occur ]
  The quirk relies on the DMI product name for device identification; if the DMI string changes, the fix will no longer apply.

  [ Other Info ]
  Upstream commit:
  https://gitlab.freedesktop.org/libinput/libinput/-/commit/d19f95ec215657d7e2f5efe2a6fe235fcbbf4e49

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



From 2127792 at bugs.launchpad.net  Fri Oct 24 07:58:29 2025
From: 2127792 at bugs.launchpad.net (Alessandro Astone)
Date: Fri, 24 Oct 2025 07:58:29 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176129270984.2234067.9345532101502072635.malone@juju-98d295-prod-launchpad-3>

The test plan could use more details.

If I understand correctly, in order to reproduce you need:
* a Blackwell GPU
* Remote Login and not Desktop Sharing
* Maybe `chmod 0666 /dev/dri/renderD*` or `usermod -a -G render gdm` ?
* Maybe even requires a physical monitor connected to the server ?
* An RDP client that can negotiate AVC rendering. It cannot native Ubuntu package because our FreeRDP is compiled without ffmpeg. I think a snap like Remmina would work.

Sources:
* https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344#note_2571364
* https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/263#note_2530526

** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #263
   https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/263

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

   * Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  * Run the same test on an older GPU generation (Maxwell, ideally)

  
  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 24 08:14:50 2025
From: 2127792 at bugs.launchpad.net (Antoine Lassagne)
Date: Fri, 24 Oct 2025 08:14:50 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176129369015.135529.9966887421910188633.malone@juju-98d295-prod-launchpad-4>

Hello,

- The protocol should be RDP - Remote Desktop Protocol. Indeed in Gnome
settings panel it's called Remote Login.

- No additional chmod's should be required. But there is actually
another bug somewhat close that you're involved in already
(https://bugs.launchpad.net/ubuntu/+source/gnome-remote-
desktop/+bug/2077538?comments=all). Because of this one (I think) we
have to add the user we setup in the "Remote Login" to both the video
and render groups, otherwise it crashes. What do you think?

- The monitor: actually this fix is about headless sessions. But testing
with AND without a monitor would be safer. Adding to the test plan.

- The negociation: this is what I implied when I mentioned that the
backend should use NVENC. Reminna Snap uses NVENC, the .deb does not.
Adding these details in the test plan.

** Description changed:

  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.
  
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263
  
  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346
  
  ---------------------------
  SRU Justification:
  
  [ Impact ]
  
-  * This is a hardware enablement SRU.
+  * This is a hardware enablement SRU.
  
-  * gnome-remote-desktop, when used alongside NVENC for video streaming,
+  * gnome-remote-desktop, when used alongside NVENC for video streaming,
  simply does not work, because the image is broken.
  
-  * With the above, the streaming is fixed.
+  * With the above, the streaming is fixed.
  
  [ Fix ]
  
-  * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
+  * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.
  
  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.
  
  [ Test Plan ]
  
-  * Test gnome-remote-desktop with and without the fix. Make sure which
+ 1. Use a DUT that has a Blackwell GPU
+ (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)
+ 
+ 2. Enable Remote Login from the Gnome Settings on the DUT with a monitor
+ plugged in.
+ 
+ 3. Install Reminna from Snap. This version supports NVENC, the .deb does
+ not.
+ 
+ 4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon` and
  observing an encoder activity >0%. The repro only occurs when the NVENC
  path is used. CPU encoding path or non-H264 streaming is unaffected
  
- * Run the same test on an older GPU generation (Maxwell, ideally)
+ 5. Run the same test without a monitor plugged in to the DUT.
  
+ 6. Run the same tests (with and without monitors) on an older GPU
+ generation (Maxwell, ideally)
  
  [ Where problems could occur ]
  
-  * Given the nature of the fix, it should not impact non-nvidia machines.
-  * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.
+  * Given the nature of the fix, it should not impact non-nvidia machines.
+  * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 24 08:35:17 2025
From: 2127792 at bugs.launchpad.net (Alessandro Astone)
Date: Fri, 24 Oct 2025 08:35:17 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176129491787.163679.9620050639534894575.malone@juju-98d295-prod-launchpad-4>

> The protocol should be RDP - Remote Desktop Protocol. Indeed in Gnome
settings panel it's called Remote Login.

Both "Desktop Sharing" and "Remote Login" use RDP. Only the latter
presents the log-in screen, which according to the upstream maintainer
is the only place where you'd see these graphical artifacts.

> there is actually another bug somewhat close that you're involved in
already (https://bugs.launchpad.net/ubuntu/+source/gnome-remote-
desktop/+bug/2077538?comments=all). Because of this one (I think) we
have to add the user we setup in the "Remote Login" to both the video
and render groups

The credentials set in "Login Details" are for an RDP user, not a linux
user. The log-in screen **in plucky and older** is always presented by
the "gdm" user, which is why I proposed `usermod -a -G render gdm`.
Alternatively, if you don't want to guess the user then chmod 666 would
achieve the same result. Whether this is necessary for triggering this
bug, I don't know.

> otherwise it crashes. What do you think?

I'm not aware of bug 2077538 causing crashes. At most, it should prevent
GNOME Shell from doing hardware accelerated rendering and fall-back to
software rendering. But that is without NVIDIA remote desktop in the
mix: does it crash remote desktop on NVIDIA?

> The monitor: actually this fix is about headless sessions. But testing
with AND without a monitor would be safer. Adding to the test plan.

The upstream maintainer commented:
"""
CUDA seems to only work, when the application or service using it, runs as a user that has physical access to a monitor. In headless sessions, there is no physical monitor. Thus CUDA and NVENC should fail to initialize, and the session falls back to software encoding.
"""

which doesn't make a whole lot of sense to me, but maybe it's true at
least in this case?

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2060730 at bugs.launchpad.net  Fri Oct 24 10:56:26 2025
From: 2060730 at bugs.launchpad.net (Graham Inggs)
Date: Fri, 24 Oct 2025 10:56:26 -0000
Subject: [Bug 2060730] Re: totem cannot install codecs via packagekit
References: <171269424360.3756110.7688066685186507912.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176130338694.2750273.4037189051862847209.launchpad@juju-98d295-prod-launchpad-7>

** Also affects: totem (Ubuntu Resolute)
   Importance: Undecided
       Status: Invalid

** Also affects: packagekit (Ubuntu Resolute)
   Importance: Medium
       Status: Fix Committed

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  In Progress
Status in packagekit package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid
Status in packagekit source package in Noble:
  Fix Committed
Status in packagekit source package in Oracular:
  Won't Fix
Status in packagekit source package in Plucky:
  Fix Committed
Status in packagekit source package in Questing:
  Fix Committed
Status in packagekit source package in Resolute:
  Fix Committed
Status in totem source package in Resolute:
  Invalid

Bug description:
  [ Impact ]

  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit.

  The main source of the bug is that App Center does not implement
  org.freedesktop.PackageKit.Modify2 on the session bus, which would
  prompt the user to install the missing codecs. This is being worked on
  and will be delivered as a snap update.

  But a fix to PackageKit itself is also necessary in order to correctly
  resolve the codec providers.

  [ Test Plan ]

  For the purpose of the SRU, we're only going to verify the PackageKit fix.
  On both AMD64 and ARM64, verify the output of the following commands:

  1. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64

  2. $ pkcon what-provides "gstreamer1(decoder-audio/mpeg)(mpegversion=4)"
     -> gstreamer1.0-fdkaac-*.amd64
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     -> gstreamer1.0-plugins-good-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386
     -> gstreamer1.0-plugins-good-*.i386

  3. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)()(64bit)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64

  4. $ pkcon what-provides "gstreamer1(decoder-video/x-h265)"
     -> gstreamer1.0-libav-*.amd64
     -> gstreamer1.0-plugins-bad-*.amd64
     Additionally, if you have enabled the i386 dpkg architecture on amd64:
     -> gstreamer1.0-libav-*.i386
     -> gstreamer1.0-plugins-bad-*.i386

  [ Where problems could occur ]

  The patch can only affect the behaviour of matching GStreamer capabilities.
  No other packagekit features are affected.
  Problems could manifest with `pkcon what-provides gstreamer1(...)` queries returning the wrong package names. This is verified in the test plan.

  [ Other info ]

  Specifically, the following is output by totem:

      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
      ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder)
      ** Message: 21:13:39.414: PackageKit: xid = 0
      ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
      ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
      ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder
      ** Message: 21:13:39.414: PackageKit: ignoring field named level
      ** Message: 21:13:39.414: PackageKit: ignoring field named profile
      ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit)
      ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
      ** Message: 21:13:39.441: No installation candidate for missing plugins found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions



From 2128350 at bugs.launchpad.net  Fri Oct 24 11:42:46 2025
From: 2128350 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 24 Oct 2025 11:42:46 -0000
Subject: [Bug 2128350] Re: Some desktop snaps are no longer visible in the
 apps menu
References: <176062998947.2963269.10879243361967771236.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176130616705.2606775.11135626361155994880.malone@juju-98d295-prod-launchpad-3>

Hello Alessandro, or anyone else affected,

Accepted malcontent into questing-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/malcontent/0.13.0-1ubuntu2.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-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. 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-questing

** Tags added: verification-needed-plucky

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

Title:
  Some desktop snaps are no longer visible in the apps menu

Status in malcontent package in Ubuntu:
  Fix Released
Status in malcontent source package in Jammy:
  In Progress
Status in malcontent source package in Noble:
  In Progress
Status in malcontent source package in Plucky:
  Fix Committed
Status in malcontent source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  Malcontent is a parental control mechanism implemented in GNOME Shell.
  It supports hiding applications from the application menu.

  Some desktop snaps like telegram-desktop are no longer visible in GNOME Shell when libmalcontent is installed, even without any filters applied. Which snaps are hidden depends on the numbers of command-line arguments they specify in the Exec line. If it's more than 2, then the snap will be hidden.
  For example, telegram-desktop uses:

  Exec=/snap/bin/telegram-desktop -- %U

  Ubuntu ships a patch in malcontent to allow filtering non-flatpak applications too.
  This patch assumed that a desktop snap Exec= line would always follow the format `Exec=env BAMF_DESKTOP_FILE_HINT=foo.desktop /snap/bin/foo arg1 arg2`, so it would interpret the third argument as the absolute binary path.

  That was changed in snapd version 2.72 to remove the
  BAMF_DESKTOP_FILE_HINT environment variable, so the Exec line now
  follows the format `Exec=/snap/bin/foo arg1 arg2`. The third argument
  is no longer the binary's absolute path, and things break.

  Malcontent needs to be adapted to not assume that the snap binary is
  always the third argument.

  [ Test Plan ]

  1. Install the `malcontent` deb package
     -> this is pre-installed on some OEM installs.
  2. Log-out, log-in again.
  3. Install snapd 2.72 or newer, available from the candidate channel:
     `sudo snap refresh snapd --candidate`
  4. Install the `telegram-desktop` snap
  5. Open the GNOME Shell application launcher
  6. Search for Telegram
  7. Verify that the Telegram app is listed.

  [ Where problems could occur ]

  Problems would manifest with applications being incorrectly filtered
  out or not filtered out.

  The patch should make sure that it is future-proof by not assuming the
  position of the binary path in the command-line a-priori.

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



From 2128350 at bugs.launchpad.net  Fri Oct 24 11:46:02 2025
From: 2128350 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 24 Oct 2025 11:46:02 -0000
Subject: [Bug 2128350] Please test proposed package
References: <176062998947.2963269.10879243361967771236.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176130636219.2833765.14722213311050784600.malone@juju-98d295-prod-launchpad-7>

Hello Alessandro, or anyone else affected,

Accepted malcontent into plucky-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/malcontent/0.13.0-1ubuntu1.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-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2128350

Title:
  Some desktop snaps are no longer visible in the apps menu

Status in malcontent package in Ubuntu:
  Fix Released
Status in malcontent source package in Jammy:
  In Progress
Status in malcontent source package in Noble:
  In Progress
Status in malcontent source package in Plucky:
  Fix Committed
Status in malcontent source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  Malcontent is a parental control mechanism implemented in GNOME Shell.
  It supports hiding applications from the application menu.

  Some desktop snaps like telegram-desktop are no longer visible in GNOME Shell when libmalcontent is installed, even without any filters applied. Which snaps are hidden depends on the numbers of command-line arguments they specify in the Exec line. If it's more than 2, then the snap will be hidden.
  For example, telegram-desktop uses:

  Exec=/snap/bin/telegram-desktop -- %U

  Ubuntu ships a patch in malcontent to allow filtering non-flatpak applications too.
  This patch assumed that a desktop snap Exec= line would always follow the format `Exec=env BAMF_DESKTOP_FILE_HINT=foo.desktop /snap/bin/foo arg1 arg2`, so it would interpret the third argument as the absolute binary path.

  That was changed in snapd version 2.72 to remove the
  BAMF_DESKTOP_FILE_HINT environment variable, so the Exec line now
  follows the format `Exec=/snap/bin/foo arg1 arg2`. The third argument
  is no longer the binary's absolute path, and things break.

  Malcontent needs to be adapted to not assume that the snap binary is
  always the third argument.

  [ Test Plan ]

  1. Install the `malcontent` deb package
     -> this is pre-installed on some OEM installs.
  2. Log-out, log-in again.
  3. Install snapd 2.72 or newer, available from the candidate channel:
     `sudo snap refresh snapd --candidate`
  4. Install the `telegram-desktop` snap
  5. Open the GNOME Shell application launcher
  6. Search for Telegram
  7. Verify that the Telegram app is listed.

  [ Where problems could occur ]

  Problems would manifest with applications being incorrectly filtered
  out or not filtered out.

  The patch should make sure that it is future-proof by not assuming the
  position of the binary path in the command-line a-priori.

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



From 2127792 at bugs.launchpad.net  Fri Oct 24 12:14:38 2025
From: 2127792 at bugs.launchpad.net (Alessandro Astone)
Date: Fri, 24 Oct 2025 12:14:38 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176130807853.2145666.18347471497333874253.launchpad@juju-98d295-prod-launchpad-2>

** Merge proposal unlinked:
   https://code.launchpad.net/~antoinelassagne/ubuntu/+source/gnome-remote-desktop/+git/gnome-remote-desktop/+merge/494354

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 24 13:15:27 2025
From: 2127792 at bugs.launchpad.net (Antoine Lassagne)
Date: Fri, 24 Oct 2025 13:15:27 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176131172775.2751559.15198150953645710102.malone@juju-98d295-prod-launchpad-3>

Hello Alessandro,

I just tested that again on the device I have.

> The login screen is not the only place where they get artifacts.
artifacts are everywhere. After the fix, everything is fine. I used the
Remmina edge snap, because stable does not work for me. The original
report uses mstsc.exe from windows, which works and uses NVENV too.

> About the groups, I'm not able to see a difference. The original
report mentioned that the group video and render were required. But I
don't see any crash, it actually works fine. Maybe it's because I've
enter a user that exists in the Remote Login panel? I'm asking the
original reporter to come and comment here.

> I'm not seeing that as well - headless works. But I've seen that
happens in the past with specific applications that requires monitors
(opengl, for example). People use clunky fake-monitor dongles in these
situations. But not here, it seems.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2124239 at bugs.launchpad.net  Fri Oct 24 13:49:40 2025
From: 2124239 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 24 Oct 2025 13:49:40 -0000
Subject: [Bug 2124239] Re: [SRU] 2.72
References: <175809378005.2374882.6087375139259954737.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176131379852.1476959.8704230028708697437.malone@scripts.lp.internal>

This bug was fixed in the package snapd - 2.72+ubuntu26.04.1

---------------
snapd (2.72+ubuntu26.04.1) resolute; urgency=medium

  * New upstream release, LP: #2124239
    - FDE: support replacing TPM protected keys at runtime via the
      /v2/system-volumes endpoint
    - FDE: support secboot preinstall check fix actions for 25.10+
      hybrid installs via the /v2/system/{label} endpoint
    - FDE: tweak polkit message to remove jargon
    - FDE: ensure proper sealing with kernel command line defaults
    - FDE: provide generic reseal function
    - FDE: support using OPTEE for protecting keys, as an alternative to
      existing fde-setup hooks (Ubuntu Core only)
    - Confdb: 'snapctl get --view' supports passing default values
    - Confdb: content sub-rules in confdb-schemas inherit their parent
      rule's "access"
    - Confdb: make confdb error kinds used in API more generic
    - Confdb: fully support lists and indexed paths (including unset)
    - Prompting: add notice backend for prompting types (unused for now)
    - Prompting: include request cgroup in prompt
    - Prompting: handle unsupported xattrs
    - Prompting: add permission mapping for the camera interface
    - Notices: read notices from state without state lock
    - Notices: add methods to get notice fields and create, reoccur, and
      deepcopy notice
    - Notices: add notice manager to coordinate separate notice backends
    - Notices: support draining notices from state when notice backend
      registered as producer of a particular notice type
    - Notices: query notice manager from daemon instead of querying
      state for notices directly
    - Packaging: Ubuntu | ignore .git directory
    - Packaging: FIPS | bump deb Go FIPS to 1.23
    - Packaging: snap | bump FIPS toolchain to 1.23
    - Packaging: debian | sync most upstream changes
    - Packaging: debian-sid | depends on libcap2-bin for postint
    - Packaging: Fedora | drop fakeroot
    - Packaging: snap | modify snapd.mk to pass build tags when running
      unit tests
    - Packaging: snap | modify snapd.mk to pass nooptee build tag
    - Packaging: modify Makefile.am to fix snap-confine install profile
      with 'make hack'
    - Packaging: modify Makefile.am to fix out-of-tree use of 'make
      hack'
    - LP: #2122054 Snap installation: skip snap icon download when
      running in a cloud or using a proxy store
    - Snap installation: add timeout to http client when downloading
      snap icon
    - Snap installation: use http(s) proxy for icon downloads
    - LP: #2117558 snap-confine: fix error message with /root/snap not
      accessible
    - snap-confine: fix non-suid limitation by switching to root:root to
      operate v1 freezer
    - core-initrd: do not use writable-paths when not available
    - core-initrd: remove debian folder
    - LP: #1916244 Interfaces: gpio-chardev | re-enable the gpio-chardev
      interface now with the more robust gpio-aggregator configfs kernel
      interface
    - Interfaces: gpio-chardev | exclusive snap connections, raise a
      conflict when both gpio-chardev and gpio are connected
    - Interfaces: gpio-chardev | fix gpio-aggregator module load order
    - Interfaces: ros-snapd-support | grant access to /v2/changes
    - Interfaces: uda-driver-libs, egl-driver-libs, gbm-driver-libs,
      opengl-driver-libs, opengles-driver-libs | new interfaces to
      support nvidia driver components
    - Interfaces: microstack-support | allow DPDK (hugepage related
      permissions)
    - Interfaces: system-observe | allow reading additional files in
      /proc, needed by node-exporter
    - Interfaces: u2f | add Cano Key, Thesis FIDO2 BioFP+ Security Key
      and Kensington VeriMark DT Fingerprint Key to device list
    - Interfaces: snap-interfaces-requests-control | allow shell API
      control
    - Interfaces: fwupd | allow access to Intel CVS sysfs
    - Interfaces: hardware-observe | allow read access to Kernel
      Samepage Merging (KSM)
    - Interfaces: xilinx-dma | support Multi Queue DMA (QDMA) IP
    - Interfaces: spi | relax sysfs permission rules to allow access to
      SPI device node attributes
    - Interfaces: content | introduce compatibility label
    - LP: #2121238 Interfaces: do not expose Kerberos tickets for
      classic snaps
    - Interfaces: ssh-public-keys | allow ro access to public host keys
      with ssh-key
    - Interfaces: Modify AppArmor template to allow listing systemd
      credentials and invoking systemd-creds
    - Interfaces: modify AppArmor template with workarounds for Go 1.35
      cgroup aware GOMAXPROCS
    - Interfaces: modify seccomp template to allow landlock_*
    - Prevent snap hooks from running while relevant snaps are unlinked
    - Make refreshes wait before unlinking snaps if running hooks can be
      affected
    - Fix systemd unit generation by moving "WantedBy=" from section
      "unit" to "install"
    - Add opt-in logging support for snap-update-ns
    - Unhide 'snap help' sign and export-key under Development category
    - LP: #2117121 Cleanly support socket activation for classic snap
    - Add architecture to 'snap version' output
    - Add 'snap debug api' option to disable authentication through
      auth.json
    - Show grade in notes for 'snap info --verbose'
    - Fix preseeding failure due to scan-disk issue on RPi
    - Support 'snap debug api' queries to user session agents
    - LP: #2112626 Improve progress reporting for snap install/refresh
    - Drop legacy BAMF_DESKTOP_FILE_HINT in desktop files
    - Fix /v2/apps error for root user when user services are present
    - LP: #2114704 Extend output to indicate when snap data snapshot was
      created during remove
    - Improve how we handle emmc volumes
    - Improve handling of system-user extra assertions

 -- Ernest Lotter <ernest.lotter at canonical.com>  Thu, 18 Sep 2025
10:00:54 +0200

** Changed in: snapd (Ubuntu Resolute)
       Status: In Progress => Fix Released

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

Title:
  [SRU] 2.72

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Jammy:
  Fix Committed
Status in snapd source package in Noble:
  Fix Committed
Status in snapd source package in Plucky:
  Fix Committed
Status in snapd source package in Questing:
  Fix Committed
Status in snapd source package in Resolute:
  Fix Released

Bug description:
  New Snapd release 2.72 is required for Jammy, Noble, Plucky and
  Questing.

  Snapd 2.72 is the latest upstream release. It follows the the previous
  Ubuntu release snapd 2.71.

  The Snapd package deviates from the standard SRU process. The
  following special SRU process was followed:
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  Snapd-Updates/. We are in the process of updating to refreshed
  documentation:
  https://docs.google.com/document/d/e/2PACX-1vTE088Am4f5SWhf3vIzA1vAIPLNrQ7JYWRO185SWmHED_e0msSahJSozArisSXezd1D8CugstKN27jx/pub
  (draft)

  Release preparation: https://github.com/canonical/snapd/pull/16000
  Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  Failure analysis: https://github.com/canonical/snapd/pull/16000#issuecomment-3311044430

  Release notes:
  https://github.com/canonical/snapd/pull/16000/files#diff-51920e95310ebfbc1ae31709f3b95f89afffbf4f1a6e38e8b2b406e2fb6197ea

  Please refer to snapd release notes documentation to understand how
  this is put together:
  https://docs.google.com/document/d/1do2TFwRIAzuOjLmteVuD0CRoJNO5vVcdUIwTHo4bYO4/edit?tab=t.0#heading=h.ablpjof536fg

  Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/2.72

  Content overview:
   - Full Disk Encryption (FDE)
   - Confdb
   - AppArmor Prompting
   - Notices
   - Many interface extensions including:
     - GPIO chardev interface as replacement for sysfs based GPIO
     - Multiple interfaces for different Nvidia driver components
   - Various LP bug fixes
   - Various packaging changes, only one minor change for Ubuntu

  Areas of potential regressions:
  - FDE just because it's complex, but risk is low given the level of integration tests in place

  Source packages on `ppa:snappy-dev/image` for upload to -proposed:
  - Resolute | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749185/+listing-archive-extra
  - Questing | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17749183/+listing-archive-extra
  - Plucky   | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598894/+listing-archive-extra
  - Noble    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598895/+listing-archive-extra
  - Jammy    | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+sourcepub/17598896/+listing-archive-extra

  Validation already completed:

  - Release preparation test results: https://github.com/canonical/snapd/actions/runs/17822196539/job/50712254868
  - QA Beta validation        https://warthogs.atlassian.net/browse/SNAPDENG-34861
  - Certification validation: https://test-observer.canonical.com/#/snaps/239942 (need VPN)

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



From 2127792 at bugs.launchpad.net  Fri Oct 24 13:53:19 2025
From: 2127792 at bugs.launchpad.net (Alessandro Astone)
Date: Fri, 24 Oct 2025 13:53:19 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176131399940.2813823.637050946141893362.malone@juju-98d295-prod-launchpad-3>

Ok, your evidence makes more sense to me than those comments upstream.
Let's go with this.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  In Progress
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 24 14:10:58 2025
From: 2127792 at bugs.launchpad.net (Alessandro Astone)
Date: Fri, 24 Oct 2025 14:10:58 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176131505891.2846945.11820316710656532159.launchpad@juju-98d295-prod-launchpad-3>

** Changed in: gnome-remote-desktop (Ubuntu Questing)
       Status: In Progress => Fix Committed

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 24 16:12:54 2025
From: 2127792 at bugs.launchpad.net (Keith Berger)
Date: Fri, 24 Oct 2025 16:12:54 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176132237468.3264745.5295101052883685856.malone@juju-98d295-prod-launchpad-7>

How did you test the groups issue? Using mstsc.exe we can easily see it
crash when you run LibreCalc. I can also try and LibreCalc.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 24 16:33:40 2025
From: 2127792 at bugs.launchpad.net (Antoine Lassagne)
Date: Fri, 24 Oct 2025 16:33:40 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176132362045.2557401.3339135476914648949.malone@juju-98d295-prod-launchpad-2>

I run remmina against a DGX Spark, with the noble version that is in the
above PPA. Without particular group tuning, I run a few apps... I don't
see any crash.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 24 20:07:31 2025
From: 2127792 at bugs.launchpad.net (Alessandro Astone)
Date: Fri, 24 Oct 2025 20:07:31 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176133645162.1283252.4754495461005477631.malone@juju-98d295-prod-launchpad-4>

> How did you test the groups issue? Using mstsc.exe we can easily see
it crash when you run LibreCalc. I can also try and LibreCalc.

Oh, I wonder if you're seeing bug 2127249. Could you try to confirm by matching the crash stacktrace?
Also let's try to keep that discussion in bug 2127249 and/or bug 2077538 if that turns out to be one way to reproduce.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127480 at bugs.launchpad.net  Mon Oct 27 11:19:50 2025
From: 2127480 at bugs.launchpad.net (Dariusz Gadomski)
Date: Mon, 27 Oct 2025 11:19:50 -0000
Subject: [Bug 2127480] Re: lshw incorrectly detects frame buffer devices
References: <176010375520.2147597.4447164906795993813.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176156399080.3565379.13509918229420044438.launchpad@juju-98d295-prod-launchpad-2>

** Also affects: lshw (Ubuntu Resolute)
   Importance: Undecided
       Status: New

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

Title:
  lshw incorrectly detects frame buffer devices

Status in lshw package in Ubuntu:
  New
Status in lshw source package in Focal:
  New
Status in lshw source package in Jammy:
  New
Status in lshw source package in Noble:
  New
Status in lshw source package in Plucky:
  New
Status in lshw source package in Questing:
  New
Status in lshw source package in Resolute:
  New

Bug description:
  [ Impact ]

   * Executing lshw can provide incorrect output for devices if frame
  buffer (fb) devices are present in the system.

   * Issue happens when lshw parses fb devices, internally it tries to look for a PCI device which matches a set of requirements (it's looking for iommu address ranges for device based on data from FB device IOCTL). If a device is matched it will append it's metadata to it and later print it.
  Problem is in logic used to detect fb devices metadata. As a result the first device on the list with iommu resource can be correlated with fb device.

   * In following example, fb metadata has been added to network adapter.
          *-network:0
               description: Ethernet interface
               product: Ethernet Controller XXV710 for 25GbE SFP28
               vendor: Intel Corporation
               physical id: 0
               bus info: pci at 0000:5e:00.0
               logical name: enp94s0f0
               logical name: /dev/fb0
               version: 02
               serial: 50:7c:6f:45:ca:23
               capacity: 25Gbit/s
               width: 64 bits
               clock: 33MHz
               capabilities: pm msi msix pciexpress vpd bus_master cap_list rom ethernet physical fibre 25000bt-fd autonegotiation fb
               configuration: autonegotiation=off broadcast=yes depth=32 driver=i40e driverversion=5.15.0-107-generic duplex=full firmware=9.50 0x8000f251 23.0.8 latency=0 link=yes mode=1024x768 multicast=yes slave=yes visual=truecolor xres=1024 yres=768
               resources: iomemory:38c00-38bff iomemory:38c00-38bff irq:36 memory:38c000000000-38c000ffffff memory:38c002800000-38c002807fff memory:b8800000-b887ffff memory:38c002000000-38c0023fffff memory:38c002810000-38c00290ffff

   * More discussion on the issue in [0]

  [ Test Plan ]

   * FB (/dev/fb0) device is required to reproduce the issue, then run
  "lshw" and check output of all devices.

  In my local local laptop fb data is added to 3D controller device:
             *-display
                  description: 3D controller
                  product: NVIDIA Corporation
                  vendor: NVIDIA Corporation
                  physical id: 0
                  bus info: pci at 0000:01:00.0
                  logical name: /dev/fb0
                  version: a1
                  width: 64 bits
                  clock: 33MHz
                  capabilities: pm msi pciexpress bus_master cap_list rom fb
                  configuration: depth=32 driver=nvidia latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
                  resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
          *-display
               description: VGA compatible controller
               product: Intel Corporation
               vendor: Intel Corporation
               physical id: 2
               bus info: pci at 0000:00:02.0
               logical name: /dev/fb0
               version: 04
               width: 64 bits
               clock: 33MHz
               capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
               configuration: depth=32 driver=i915 latency=0 resolution=1920,1200

  With fix:
             *-display
                  description: 3D controller
                  product: NVIDIA Corporation
                  vendor: NVIDIA Corporation
                  physical id: 0
                  bus info: pci at 0000:01:00.0
                  version: a1
                  width: 64 bits
                  clock: 33MHz
                  capabilities: pm msi pciexpress bus_master cap_list rom
                  configuration: driver=nvidia latency=0
                  resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
          *-display
               description: VGA compatible controller
               product: Intel Corporation
               vendor: Intel Corporation
               physical id: 2
               bus info: pci at 0000:00:02.0
               logical name: /dev/fb0
               version: 04
               width: 64 bits
               clock: 33MHz
               capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
               configuration: depth=32 driver=i915 latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
               resources: iomemory:620-61f iomemory:400-3ff irq:181 memory:6288000000-6288ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff

  
  [ Where problems could occur ]

   * Fix is written in a way that if new way of detecting fb metadata
  does not work it will fall back to previous method.

   * Worst case scenario is that fb data will not be printed

  [ Other Info ]

   * To workaround the problem disable fb detection by adding -disable
  fb

   * Upstream patches [1]

  [0] - https://github.com/lyonel/lshw/pull/106
  [1] - https://ezix.org/src/pkg/lshw/commits/branch/master af7c69e1b6 8798c9f1a2

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



From 2121623 at bugs.launchpad.net  Mon Oct 27 14:47:58 2025
From: 2121623 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 27 Oct 2025 14:47:58 -0000
Subject: [Bug 2121623] [NEW] [needs-packaging] rustc-1.89
References: <175641308106.667615.16419926783611633205.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176157647850.3937083.4892329488626261747.launchpad@juju-98d295-prod-launchpad-2>

You have been subscribed to a public bug by Max Gilmour (maxgmr):

Rust 1.89 was released on 7 August, 2025. A great deal of packages in
the Ubuntu archive rely on up-to-date versions of Rust in order to build
properly, and as time passes, the minimal supported Rust version (MSRV)
of crucial Rust-based packages increases. It is very important to keep
up with upstream Rust development to ensure that the latest Rust-based
Ubuntu packages can be built without issue.

Rust 1.89 also brings several fixes and new features, such as the full
stabilization of 128-bit integer support[1]. A full list of changes may
be consulted below[2].

As of 2 September 2025, 1.89.0 is the current stable Rust version.
Getting rustc-1.89 into the archive means that we will be fully caught
up with upstream.

[1]: https://github.com/rust-lang/rust/pull/138285
[2]: https://releases.rs/docs/1.89.0/

** Affects: ubuntu
     Importance: Wishlist
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress

** Affects: Ubuntu Resolute
     Importance: Wishlist
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress


** Tags: needs-packaging
-- 
[needs-packaging] rustc-1.89
https://bugs.launchpad.net/bugs/2121623
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2121623 at bugs.launchpad.net  Mon Oct 27 14:51:28 2025
From: 2121623 at bugs.launchpad.net (Max Gilmour)
Date: Mon, 27 Oct 2025 14:51:28 -0000
Subject: [Bug 2121623] Re: [needs-packaging] rustc-1.89
References: <175641308106.667615.16419926783611633205.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176157668901.3948535.15464889799531838833.malone@juju-98d295-prod-launchpad-2>

Ah right, thanks for the reminder.

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

Title:
  [needs-packaging] rustc-1.89

Status in Ubuntu:
  In Progress
Status in The Resolute Raccoon:
  In Progress

Bug description:
  Rust 1.89 was released on 7 August, 2025. A great deal of packages in
  the Ubuntu archive rely on up-to-date versions of Rust in order to
  build properly, and as time passes, the minimal supported Rust version
  (MSRV) of crucial Rust-based packages increases. It is very important
  to keep up with upstream Rust development to ensure that the latest
  Rust-based Ubuntu packages can be built without issue.

  Rust 1.89 also brings several fixes and new features, such as the full
  stabilization of 128-bit integer support[1]. A full list of changes
  may be consulted below[2].

  As of 2 September 2025, 1.89.0 is the current stable Rust version.
  Getting rustc-1.89 into the archive means that we will be fully caught
  up with upstream.

  [1]: https://github.com/rust-lang/rust/pull/138285
  [2]: https://releases.rs/docs/1.89.0/

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



From 2129955 at bugs.launchpad.net  Mon Oct 27 15:07:50 2025
From: 2129955 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 27 Oct 2025 15:07:50 -0000
Subject: [Bug 2129955] [NEW] [needs-packaging] vulkan-profiles
References: <176157758574.436446.1202103793448263585.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176157767034.440306.6393321283160621037.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Andreas Glinserer (aglinserer):

URL: https://github.com/KhronosGroup/Vulkan-Profiles
License: Apache-2.0, CC-BY-4.0
Notes: Vulkan Profiles contain a collection of components for Vulkan application developers to build portable Vulkan applications using predefined profiles. This makes it easier to ship Vulkan apps which target a specific set of GPU features across devices.

I wish to package vulkan-profiles for Ubuntu.

** Affects: ubuntu
     Importance: Undecided
         Status: New


** Tags: needs-packaging
-- 
[needs-packaging] vulkan-profiles
https://bugs.launchpad.net/bugs/2129955
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2129196 at bugs.launchpad.net  Mon Oct 27 17:06:06 2025
From: 2129196 at bugs.launchpad.net (Lena Voytek)
Date: Mon, 27 Oct 2025 17:06:06 -0000
Subject: [Bug 2129196] Re: mysql-server fails to install when an ext4 fs is
 mounted to /var/lib/mysql 
References: <176105583922.2334596.9944933464066925340.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176158476608.647872.17664295752574823225.malone@juju-98d295-prod-launchpad-3>

I will sponsor uploads after the new security update so SRU uploads are
not overridden

** Tags removed: server-triage-discuss

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

Title:
  mysql-server fails to install when an ext4 fs is mounted to
  /var/lib/mysql

Status in mysql-8.0 package in Ubuntu:
  New
Status in mysql-8.4 package in Ubuntu:
  New
Status in mysql-8.0 source package in Jammy:
  New
Status in mysql-8.0 source package in Noble:
  New
Status in mysql-8.4 source package in Plucky:
  New
Status in mysql-8.4 source package in Questing:
  New
Status in mysql-8.4 source package in Resolute:
  New

Bug description:
  [ Impact ]

   * The postinst script for mysql-server checks whether the
  `/var/lib/mysql` directory is empty before setting up the database
  state. When `/var/lib/mysql` is an ext4 filesystem, the `lost+found`
  directory causes this check to fail and the database is not properly
  set up.

   * Mounting a separate volume to hold the mysql state is a common
  pattern, and ext4 is extremely prevalent so this is likely to be a
  common pain point. Although workarounds are straightforward, it makes
  for bad UX.

   * This can be remedied by ignoring the lost+found directory in the
  check.

  [ Test Plan ]

   To ensure bug is fixed:
   * Create an empty ext4 volume and mount it to /var/lib/mysql
   * Install mysql-server
   * Check whether the installation succeeds

   To check that data is preserved:
   * Uninstall and reinstall mysql-server
   * Ensure that the data in /var/lib/mysql is not overwritten

  [ Where problems could occur ]

   * In this case, the only change is to the postinst script, so problems should be related to install.
   * If the check being done were incorrect it could lead to loss of user data.
     - We keep the change to script to a minimum to reduce the risk of this
     - Test plan includes confirming that user data is not overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2129196/+subscriptions



From 2129955 at bugs.launchpad.net  Mon Oct 27 23:55:03 2025
From: 2129955 at bugs.launchpad.net (Brian Murray)
Date: Mon, 27 Oct 2025 23:55:03 -0000
Subject: [Bug 2129955] Re: [needs-packaging] vulkan-profiles
References: <176157758574.436446.1202103793448263585.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176160930370.1314899.14366547348844679413.malone@juju-98d295-prod-launchpad-3>

*** 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.

** Changed in: ubuntu
   Importance: Undecided => Wishlist

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

Title:
  [needs-packaging] vulkan-profiles

Status in Ubuntu:
  New

Bug description:
  URL: https://github.com/KhronosGroup/Vulkan-Profiles
  License: Apache-2.0, CC-BY-4.0
  Notes: Vulkan Profiles contain a collection of components for Vulkan application developers to build portable Vulkan applications using predefined profiles. This makes it easier to ship Vulkan apps which target a specific set of GPU features across devices.

  I wish to package vulkan-profiles for Ubuntu.

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



From 2126737 at bugs.launchpad.net  Tue Oct 28 03:55:37 2025
From: 2126737 at bugs.launchpad.net (Tzu-Hsien Kao)
Date: Tue, 28 Oct 2025 03:55:37 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176162373809.1855814.16882300829648858788.launchpad@juju-98d295-prod-launchpad-7>

** Changed in: alsa-ucm-conf (Ubuntu Noble)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Noble)
     Assignee: (unassigned) => Tzu-Hsien Kao (tzuhsien-kao)

** Changed in: alsa-ucm-conf (Ubuntu Plucky)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Plucky)
     Assignee: (unassigned) => Tzu-Hsien Kao (tzuhsien-kao)

** Changed in: alsa-ucm-conf (Ubuntu Questing)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Questing)
     Assignee: (unassigned) => Tzu-Hsien Kao (tzuhsien-kao)

** Changed in: alsa-ucm-conf (Ubuntu Resolute)
       Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Resolute)
     Assignee: (unassigned) => Tzu-Hsien Kao (tzuhsien-kao)

** Changed in: alsa-ucm-conf (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu Plucky)
       Status: In Progress => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu Questing)
       Status: In Progress => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu Resolute)
       Status: In Progress => Fix Committed

** Description changed:

  [Impact]
  
  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK platforms
  based on the mt8365, mt8370, mt8390, and mt8395 SoCs.
  
  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.
  
  [Test Plan]
  
  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).
  
  To verify the fix:
  
  1. On a target EVK, install the updated package.
  
  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.
  
  3. Test audio playback and recording through all available devices.
  
  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.
  
  [Where problems could occur]
  
  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce unexpected
  conflicts. This would most likely manifest as a loss of audio
  functionality (e.g., missing input/output devices) on previously working
  hardware.
  
  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.
  
  [Other Info]
  
  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.
  
  Upstream commits:
  
  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2
- 
- **Affected Releases**
- 
- This bug has been filed against Noble Numbat (24.04 LTS) as the primary
- target for the SRU.
- 
- Following the SRU policy, this fix also needs to be verified in the
- development release. Could a bug triager please also mark this bug as
- affecting **`Ubuntu (Development)`**?

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf source package in Noble:
  Fix Committed
Status in alsa-ucm-conf source package in Plucky:
  Fix Committed
Status in alsa-ucm-conf source package in Questing:
  Fix Committed
Status in alsa-ucm-conf source package in Resolute:
  Fix Committed

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2120689 at bugs.launchpad.net  Tue Oct 28 04:31:04 2025
From: 2120689 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 28 Oct 2025 04:31:04 -0000
Subject: [Bug 2120689] [NEW] [SRU] Missing DeviceAllow for Intel's linux-lts
 6.12 tree's ipu6-psys
References: <175521695863.3172424.7969664374267313725.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176162586614.3720321.6563333878451658601.launchpad@juju-98d295-prod-launchpad-4>

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

[ SRU Justification ]

[ Impact ]

Missing DeviceAllow for Intel's linux-lts 6.12 tree's ipu6-psys. Since
v4l2-relayd version 0.1.5, systemd DeviceAllow is added to limit device
accesses for v4l2-relayd. The one added initially was for Intel IPU7,
and certainly IPU6 is required, too.

Without that, an error printed in v4l2-relayd's systemd logs:
```
$ systemctl status v4l2-relayd
......
sh[6920]: [10-28 03:49:39.560] CamHAL[ERR] Failed to open PSYS, error: Operation not permitted
```

[ Test Plan ]

1. Install v4l2-relayd from -proposed pocket.

2. Try to use webcam with:
   ```
   $ gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! autovideosink
   # Expect video streaming occurs
   ```

[ Where problems could occur ]

Trivial. That's the hardware access it needs in order to use the webcam
function.

[ Other Info ]

While this affects only v4l2-relayd >= 0.1.5, nominate only Resolute and
Questing. For Resolute, the fix has been included in 0.2.0, which is
being updated in bug 2116722.

========== original bug report ==========

The Intel's Linux LTS tree, which supports IPU6 out-of-the-box, uses
different character device class causing systemd rule packaged with
v4l2-relayd unable to access the device.

https://github.com/intel/linux-intel-
lts/blob/6.12/linux/drivers/media/pci/intel/ipu6/psys/ipu-psys.c#L63

I've confirmed adding "DeviceAllow=char-intel-ipu6-psys" fixes IPU6
support for v4l2-relayd.

** Affects: v4l2-relayd (Ubuntu)
     Importance: Critical
     Assignee: You-Sheng Yang (vicamo)
         Status: In Progress

** Affects: v4l2-relayd (Ubuntu Noble)
     Importance: Undecided
         Status: Invalid

** Affects: v4l2-relayd (Ubuntu Plucky)
     Importance: Undecided
         Status: Invalid

** Affects: v4l2-relayd (Ubuntu Questing)
     Importance: Critical
     Assignee: You-Sheng Yang (vicamo)
         Status: In Progress


** Tags: patch
-- 
[SRU] Missing DeviceAllow for Intel's linux-lts 6.12 tree's ipu6-psys
https://bugs.launchpad.net/bugs/2120689
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2116722 at bugs.launchpad.net  Tue Oct 28 04:31:19 2025
From: 2116722 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 28 Oct 2025 04:31:19 -0000
Subject: [Bug 2116722] [NEW] [SRU] Support multiple MIPI based camera devices
References: <175223546251.3395184.12132729931459807763.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176162587972.3719135.15997126193034960852.launchpad@juju-98d295-prod-launchpad-4>

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

To enable oem platforms with front/rear cameras both based on MIPI
technology.

** Affects: v4l2-relayd (Ubuntu)
     Importance: High
     Assignee: You-Sheng Yang (vicamo)
         Status: In Progress

** Affects: v4l2-relayd (Ubuntu Noble)
     Importance: High
     Assignee: You-Sheng Yang (vicamo)
         Status: In Progress

** Affects: v4l2-relayd (Ubuntu Plucky)
     Importance: Undecided
         Status: Won't Fix

** Affects: v4l2-relayd (Ubuntu Questing)
     Importance: Undecided
         Status: Won't Fix

** Affects: v4l2-relayd (Ubuntu Resolute)
     Importance: High
     Assignee: You-Sheng Yang (vicamo)
         Status: In Progress


** Tags: jira-somerville-3152 patch
-- 
[SRU] Support multiple MIPI based camera devices
https://bugs.launchpad.net/bugs/2116722
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2120689 at bugs.launchpad.net  Tue Oct 28 04:31:06 2025
From: 2120689 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Tue, 28 Oct 2025 04:31:06 -0000
Subject: [Bug 2120689] Re: [SRU] Missing DeviceAllow for Intel's linux-lts
 6.12 tree's ipu6-psys
References: <175521695863.3172424.7969664374267313725.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176162586695.1916278.9962348193381625721.malone@juju-98d295-prod-launchpad-7>

The attachment "v4l2-relayd_0.1.5-0ubuntu1.1.questing.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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2120689

Title:
  [SRU] Missing DeviceAllow for Intel's linux-lts 6.12 tree's ipu6-psys

Status in v4l2-relayd package in Ubuntu:
  In Progress
Status in v4l2-relayd source package in Noble:
  Invalid
Status in v4l2-relayd source package in Plucky:
  Invalid
Status in v4l2-relayd source package in Questing:
  In Progress

Bug description:
  [ SRU Justification ]

  [ Impact ]

  Missing DeviceAllow for Intel's linux-lts 6.12 tree's ipu6-psys. Since
  v4l2-relayd version 0.1.5, systemd DeviceAllow is added to limit
  device accesses for v4l2-relayd. The one added initially was for Intel
  IPU7, and certainly IPU6 is required, too.

  Without that, an error printed in v4l2-relayd's systemd logs:
  ```
  $ systemctl status v4l2-relayd
  ......
  sh[6920]: [10-28 03:49:39.560] CamHAL[ERR] Failed to open PSYS, error: Operation not permitted
  ```

  [ Test Plan ]

  1. Install v4l2-relayd from -proposed pocket.

  2. Try to use webcam with:
     ```
     $ gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! autovideosink
     # Expect video streaming occurs
     ```

  [ Where problems could occur ]

  Trivial. That's the hardware access it needs in order to use the
  webcam function.

  [ Other Info ]

  While this affects only v4l2-relayd >= 0.1.5, nominate only Resolute
  and Questing. For Resolute, the fix has been included in 0.2.0, which
  is being updated in bug 2116722.

  ========== original bug report ==========

  The Intel's Linux LTS tree, which supports IPU6 out-of-the-box, uses
  different character device class causing systemd rule packaged with
  v4l2-relayd unable to access the device.

  https://github.com/intel/linux-intel-
  lts/blob/6.12/linux/drivers/media/pci/intel/ipu6/psys/ipu-psys.c#L63

  I've confirmed adding "DeviceAllow=char-intel-ipu6-psys" fixes IPU6
  support for v4l2-relayd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l2-relayd/+bug/2120689/+subscriptions



From 2116722 at bugs.launchpad.net  Tue Oct 28 04:31:20 2025
From: 2116722 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Tue, 28 Oct 2025 04:31:20 -0000
Subject: [Bug 2116722] Re: [SRU] Support multiple MIPI based camera devices
References: <175223546251.3395184.12132729931459807763.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176162588017.1711727.5349022200564992623.malone@juju-98d295-prod-launchpad-3>

The attachment "v4l2-relayd_0.1.2-0ubuntu3.1.noble.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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2116722

Title:
  [SRU] Support multiple MIPI based camera devices

Status in v4l2-relayd package in Ubuntu:
  In Progress
Status in v4l2-relayd source package in Noble:
  In Progress
Status in v4l2-relayd source package in Plucky:
  Won't Fix
Status in v4l2-relayd source package in Questing:
  Won't Fix
Status in v4l2-relayd source package in Resolute:
  In Progress

Bug description:
  To enable oem platforms with front/rear cameras both based on MIPI
  technology.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l2-relayd/+bug/2116722/+subscriptions



From 2126737 at bugs.launchpad.net  Tue Oct 28 09:16:08 2025
From: 2126737 at bugs.launchpad.net (Tzu-Hsien Kao)
Date: Tue, 28 Oct 2025 09:16:08 -0000
Subject: [Bug 2126737] Re: [SRU] alsa-ucm-conf: Missing audio support for
 MediaTek Genio EVK platforms
References: <175947114567.3227894.14534524421909863561.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176164297031.2378779.7140912945341738881.launchpad@juju-98d295-prod-launchpad-7>

** Changed in: alsa-ucm-conf (Ubuntu Noble)
       Status: Fix Committed => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Plucky)
       Status: Fix Committed => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Resolute)
       Status: Fix Committed => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Questing)
       Status: Fix Committed => In Progress

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

Title:
  [SRU] alsa-ucm-conf: Missing audio support for MediaTek Genio EVK
  platforms

Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Noble:
  In Progress
Status in alsa-ucm-conf source package in Plucky:
  In Progress
Status in alsa-ucm-conf source package in Questing:
  In Progress
Status in alsa-ucm-conf source package in Resolute:
  In Progress

Bug description:
  [Impact]

  This update adds new ALSA UCM2 profiles to the alsa-ucm-conf package,
  specifically to enable audio on a range of MediaTek Genio EVK
  platforms based on the mt8365, mt8370, mt8390, and mt8395 SoCs.

  This is a crucial hardware enablement update necessary for out-of-the-
  box audio functionality on these specific development and reference
  boards. Without these profiles, audio playback, recording, and jack
  detection are non-functional.

  [Test Plan]

  This update requires testing on the specific MediaTek EVK hardware for
  which the profiles are intended (mt8365-evk, mt8370-evk, mt8390-evk,
  mt8395-evk).

  To verify the fix:

  1. On a target EVK, install the updated package.

  2. Confirm that audio devices (speakers, microphone, headset) are
  correctly detected in sound settings.

  3. Test audio playback and recording through all available devices.

  4. Verify that plugging in and unplugging a headset is correctly
  detected and that audio routes appropriately.

  [Where problems could occur]

  Regressions are unlikely but possible on other, existing platforms if
  the new configuration files cause parsing issues or introduce
  unexpected conflicts. This would most likely manifest as a loss of
  audio functionality (e.g., missing input/output devices) on previously
  working hardware.

  As a precaution, regression testing on a few non-MediaTek devices is
  recommended to ensure no existing functionality is broken.

  [Other Info]

  This update cherry-picks a series of 9 upstream commits that add the
  UCM2 profiles for the MediaTek EVK platforms.

  Upstream commits:

  * 0c4b859: https://github.com/alsa-project/alsa-ucm-conf/commit/0c4b859abcab
  * 03dd378: https://github.com/alsa-project/alsa-ucm-conf/commit/03dd37830b4b
  * 1b5de60: https://github.com/alsa-project/alsa-ucm-conf/commit/1b5de60bee2a
  * 35a3153: https://github.com/alsa-project/alsa-ucm-conf/commit/35a315312ffe
  * 3b81e60: https://github.com/alsa-project/alsa-ucm-conf/commit/3b81e602e222
  * ebdf9d1: https://github.com/alsa-project/alsa-ucm-conf/commit/ebdf9d1d8ffb
  * f293b31: https://github.com/alsa-project/alsa-ucm-conf/commit/f293b3149b8b
  * 63f161c: https://github.com/alsa-project/alsa-ucm-conf/commit/63f161cb8d65
  * c68ce7f: https://github.com/alsa-project/alsa-ucm-conf/commit/c68ce7f841d2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2126737/+subscriptions



From 2127480 at bugs.launchpad.net  Tue Oct 28 10:44:01 2025
From: 2127480 at bugs.launchpad.net (Robert Malz)
Date: Tue, 28 Oct 2025 10:44:01 -0000
Subject: [Bug 2127480] Re: lshw incorrectly detects frame buffer devices
References: <176010375520.2147597.4447164906795993813.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176164824129.93117.2347361906767827038.malone@juju-98d295-prod-launchpad-2>

resolute debdiff

** Patch added: "resolute.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/2127480/+attachment/5920866/+files/resolute.debdiff

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

Title:
  lshw incorrectly detects frame buffer devices

Status in lshw package in Ubuntu:
  New
Status in lshw source package in Focal:
  New
Status in lshw source package in Jammy:
  New
Status in lshw source package in Noble:
  New
Status in lshw source package in Plucky:
  New
Status in lshw source package in Questing:
  New
Status in lshw source package in Resolute:
  New

Bug description:
  [ Impact ]

   * Executing lshw can provide incorrect output for devices if frame
  buffer (fb) devices are present in the system.

   * Issue happens when lshw parses fb devices, internally it tries to look for a PCI device which matches a set of requirements (it's looking for iommu address ranges for device based on data from FB device IOCTL). If a device is matched it will append it's metadata to it and later print it.
  Problem is in logic used to detect fb devices metadata. As a result the first device on the list with iommu resource can be correlated with fb device.

   * In following example, fb metadata has been added to network adapter.
          *-network:0
               description: Ethernet interface
               product: Ethernet Controller XXV710 for 25GbE SFP28
               vendor: Intel Corporation
               physical id: 0
               bus info: pci at 0000:5e:00.0
               logical name: enp94s0f0
               logical name: /dev/fb0
               version: 02
               serial: 50:7c:6f:45:ca:23
               capacity: 25Gbit/s
               width: 64 bits
               clock: 33MHz
               capabilities: pm msi msix pciexpress vpd bus_master cap_list rom ethernet physical fibre 25000bt-fd autonegotiation fb
               configuration: autonegotiation=off broadcast=yes depth=32 driver=i40e driverversion=5.15.0-107-generic duplex=full firmware=9.50 0x8000f251 23.0.8 latency=0 link=yes mode=1024x768 multicast=yes slave=yes visual=truecolor xres=1024 yres=768
               resources: iomemory:38c00-38bff iomemory:38c00-38bff irq:36 memory:38c000000000-38c000ffffff memory:38c002800000-38c002807fff memory:b8800000-b887ffff memory:38c002000000-38c0023fffff memory:38c002810000-38c00290ffff

   * More discussion on the issue in [0]

  [ Test Plan ]

   * FB (/dev/fb0) device is required to reproduce the issue, then run
  "lshw" and check output of all devices.

  In my local local laptop fb data is added to 3D controller device:
             *-display
                  description: 3D controller
                  product: NVIDIA Corporation
                  vendor: NVIDIA Corporation
                  physical id: 0
                  bus info: pci at 0000:01:00.0
                  logical name: /dev/fb0
                  version: a1
                  width: 64 bits
                  clock: 33MHz
                  capabilities: pm msi pciexpress bus_master cap_list rom fb
                  configuration: depth=32 driver=nvidia latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
                  resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
          *-display
               description: VGA compatible controller
               product: Intel Corporation
               vendor: Intel Corporation
               physical id: 2
               bus info: pci at 0000:00:02.0
               logical name: /dev/fb0
               version: 04
               width: 64 bits
               clock: 33MHz
               capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
               configuration: depth=32 driver=i915 latency=0 resolution=1920,1200

  With fix:
             *-display
                  description: 3D controller
                  product: NVIDIA Corporation
                  vendor: NVIDIA Corporation
                  physical id: 0
                  bus info: pci at 0000:01:00.0
                  version: a1
                  width: 64 bits
                  clock: 33MHz
                  capabilities: pm msi pciexpress bus_master cap_list rom
                  configuration: driver=nvidia latency=0
                  resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
          *-display
               description: VGA compatible controller
               product: Intel Corporation
               vendor: Intel Corporation
               physical id: 2
               bus info: pci at 0000:00:02.0
               logical name: /dev/fb0
               version: 04
               width: 64 bits
               clock: 33MHz
               capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
               configuration: depth=32 driver=i915 latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
               resources: iomemory:620-61f iomemory:400-3ff irq:181 memory:6288000000-6288ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff

  
  [ Where problems could occur ]

   * Fix is written in a way that if new way of detecting fb metadata
  does not work it will fall back to previous method.

   * Worst case scenario is that fb data will not be printed

  [ Other Info ]

   * To workaround the problem disable fb detection by adding -disable
  fb

   * Upstream patches [1]

  [0] - https://github.com/lyonel/lshw/pull/106
  [1] - https://ezix.org/src/pkg/lshw/commits/branch/master af7c69e1b6 8798c9f1a2

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



From 2130010 at bugs.launchpad.net  Tue Oct 28 12:23:30 2025
From: 2130010 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 28 Oct 2025 12:23:30 -0000
Subject: [Bug 2130010] [NEW] Sync laserboy 2024.03.08+dfsg-3 (universe) from
 Debian unstable (main)
References: <176165420486.272529.16764589301594165484.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176165421056.337331.18377206694257196149.launchpad@juju-98d295-prod-launchpad-4>

You have been subscribed to a public bug by Mateus Rodrigues de Morais (mateus-morais):

Please sync laserboy 2024.03.08+dfsg-3 (universe) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * d/p/fix-boost-1.88-ftbfs.patch: fix FTBFS with boost 1.88 (LP: #2120885)

    The patch fixing FTBFS on Boost 1.88 has been included in Debian and delta
    is no longer necessary.

Changelog entries since current resolute version
2024.03.08+dfsg-2ubuntu1:

laserboy (2024.03.08+dfsg-3) unstable; urgency=medium

  * Add fix-boost-1.88-ftbfs.patch, fixing FTBFS with Boost 1.88.
    Thanks to Mateus Rodrigues de Morais for the patch (Closes: #1110627)

 -- Nicolas Schodet <nico at ni.fr.eu.org>  Mon, 27 Oct 2025 17:39:12 +0100

** Affects: laserboy (Ubuntu)
     Importance: Wishlist
         Status: New

-- 
Sync laserboy 2024.03.08+dfsg-3 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/2130010
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2127480 at bugs.launchpad.net  Tue Oct 28 13:37:05 2025
From: 2127480 at bugs.launchpad.net (Simon Chopin)
Date: Tue, 28 Oct 2025 13:37:05 -0000
Subject: [Bug 2127480] Re: lshw incorrectly detects frame buffer devices
References: <176010375520.2147597.4447164906795993813.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176165862544.407384.8541418617346572733.malone@juju-98d295-prod-launchpad-2>

Hi,

Thanks for the patches!

Please note that typically we wouldn't upload the fix to Focal, as it is
out of standard support.

** Tags added: dcr-incoming

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

Title:
  lshw incorrectly detects frame buffer devices

Status in lshw package in Ubuntu:
  New
Status in lshw source package in Focal:
  New
Status in lshw source package in Jammy:
  New
Status in lshw source package in Noble:
  New
Status in lshw source package in Plucky:
  New
Status in lshw source package in Questing:
  New
Status in lshw source package in Resolute:
  New

Bug description:
  [ Impact ]

   * Executing lshw can provide incorrect output for devices if frame
  buffer (fb) devices are present in the system.

   * Issue happens when lshw parses fb devices, internally it tries to look for a PCI device which matches a set of requirements (it's looking for iommu address ranges for device based on data from FB device IOCTL). If a device is matched it will append it's metadata to it and later print it.
  Problem is in logic used to detect fb devices metadata. As a result the first device on the list with iommu resource can be correlated with fb device.

   * In following example, fb metadata has been added to network adapter.
          *-network:0
               description: Ethernet interface
               product: Ethernet Controller XXV710 for 25GbE SFP28
               vendor: Intel Corporation
               physical id: 0
               bus info: pci at 0000:5e:00.0
               logical name: enp94s0f0
               logical name: /dev/fb0
               version: 02
               serial: 50:7c:6f:45:ca:23
               capacity: 25Gbit/s
               width: 64 bits
               clock: 33MHz
               capabilities: pm msi msix pciexpress vpd bus_master cap_list rom ethernet physical fibre 25000bt-fd autonegotiation fb
               configuration: autonegotiation=off broadcast=yes depth=32 driver=i40e driverversion=5.15.0-107-generic duplex=full firmware=9.50 0x8000f251 23.0.8 latency=0 link=yes mode=1024x768 multicast=yes slave=yes visual=truecolor xres=1024 yres=768
               resources: iomemory:38c00-38bff iomemory:38c00-38bff irq:36 memory:38c000000000-38c000ffffff memory:38c002800000-38c002807fff memory:b8800000-b887ffff memory:38c002000000-38c0023fffff memory:38c002810000-38c00290ffff

   * More discussion on the issue in [0]

  [ Test Plan ]

   * FB (/dev/fb0) device is required to reproduce the issue, then run
  "lshw" and check output of all devices.

  In my local local laptop fb data is added to 3D controller device:
             *-display
                  description: 3D controller
                  product: NVIDIA Corporation
                  vendor: NVIDIA Corporation
                  physical id: 0
                  bus info: pci at 0000:01:00.0
                  logical name: /dev/fb0
                  version: a1
                  width: 64 bits
                  clock: 33MHz
                  capabilities: pm msi pciexpress bus_master cap_list rom fb
                  configuration: depth=32 driver=nvidia latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
                  resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
          *-display
               description: VGA compatible controller
               product: Intel Corporation
               vendor: Intel Corporation
               physical id: 2
               bus info: pci at 0000:00:02.0
               logical name: /dev/fb0
               version: 04
               width: 64 bits
               clock: 33MHz
               capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
               configuration: depth=32 driver=i915 latency=0 resolution=1920,1200

  With fix:
             *-display
                  description: 3D controller
                  product: NVIDIA Corporation
                  vendor: NVIDIA Corporation
                  physical id: 0
                  bus info: pci at 0000:01:00.0
                  version: a1
                  width: 64 bits
                  clock: 33MHz
                  capabilities: pm msi pciexpress bus_master cap_list rom
                  configuration: driver=nvidia latency=0
                  resources: iomemory:600-5ff iomemory:620-61f irq:180 memory:be000000-beffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:3000(size=128)
          *-display
               description: VGA compatible controller
               product: Intel Corporation
               vendor: Intel Corporation
               physical id: 2
               bus info: pci at 0000:00:02.0
               logical name: /dev/fb0
               version: 04
               width: 64 bits
               clock: 33MHz
               capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
               configuration: depth=32 driver=i915 latency=0 mode=1920x1200 visual=truecolor xres=1920 yres=1200
               resources: iomemory:620-61f iomemory:400-3ff irq:181 memory:6288000000-6288ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff

  
  [ Where problems could occur ]

   * Fix is written in a way that if new way of detecting fb metadata
  does not work it will fall back to previous method.

   * Worst case scenario is that fb data will not be printed

  [ Other Info ]

   * To workaround the problem disable fb detection by adding -disable
  fb

   * Upstream patches [1]

  [0] - https://github.com/lyonel/lshw/pull/106
  [1] - https://ezix.org/src/pkg/lshw/commits/branch/master af7c69e1b6 8798c9f1a2

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



From 2122556 at bugs.launchpad.net  Tue Oct 28 14:37:10 2025
From: 2122556 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 28 Oct 2025 14:37:10 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176166223031.530646.13201477602647259266.malone@juju-98d295-prod-launchpad-2>

re #14: You're right! That commit is already included in Plucky, which
is unfortunately not obvious from the upstream repo:
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651
(1.2.5 does not show up in "Tags"). But trying to apply the patch
manually results in an empty commit

So I'll be sponsoring Plucky as-is!

$ dput ubuntu ../pipewire_1.2.7-1ubuntu5.2_source.changes
Uploading pipewire using ftp to ubuntu (host: upload.ubuntu.com; directory: /ubuntu)
running required-fields: check whether a field is present and non-empty in the changes file
running suite-mismatch: check the target distribution for common errors
running gpg: check GnuPG signatures before the upload
running ppaforppaonly: Stop uploads to the archive with or to ppa without ~ppa suffix.
running updatemaintainer: Stop if ubuntu changes are without ubuntu maintainer.
running checksum: verify checksums before uploading
running nobug: Stop if uploading without any bug reference.
running gitubuntu: Warn if uploading without git-ubuntu Vcs-* entries.
running placeholderbug: Stop if using common placeholder numbers as bug reference.
running releasemismatch: Warn about mismatching suffixesg e.g. focal with a XX.YY not being 20.04
running supported-distribution: check whether the target distribution is currently supported (using distro-info)
{'allowed': ['release', 'proposed', 'backports', 'security'], 'known': ['release', 'proposed', 'updates', 'backports', 'security']}
running badauthor: Stop if uploading with root@ or ubuntu@ email adresses.
running check-debs: makes sure the upload contains a binary package
Uploading pipewire_1.2.7-1ubuntu5.2.dsc
Uploading pipewire_1.2.7-1ubuntu5.2.debian.tar.xz
Uploading pipewire_1.2.7-1ubuntu5.2_source.buildinfo
Uploading pipewire_1.2.7-1ubuntu5.2_source.changes

** Changed in: pipewire (Ubuntu Plucky)
       Status: New => In Progress

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  In Progress

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2121623 at bugs.launchpad.net  Tue Oct 28 15:18:03 2025
From: 2121623 at bugs.launchpad.net (=?utf-8?q?Jeremy_B=C3=ADcha?=)
Date: Tue, 28 Oct 2025 15:18:03 -0000
Subject: [Bug 2121623] Re: [needs-packaging] rustc-1.89
References: <175641308106.667615.16419926783611633205.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176166468364.3058187.13273939868951036123.malone@juju-98d295-prod-launchpad-7>

Which version do you want uploaded? The version from git or the version
from the PPA (which has switched to llvm 21)?

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

Title:
  [needs-packaging] rustc-1.89

Status in Ubuntu:
  In Progress
Status in The Resolute Raccoon:
  In Progress

Bug description:
  Rust 1.89 was released on 7 August, 2025. A great deal of packages in
  the Ubuntu archive rely on up-to-date versions of Rust in order to
  build properly, and as time passes, the minimal supported Rust version
  (MSRV) of crucial Rust-based packages increases. It is very important
  to keep up with upstream Rust development to ensure that the latest
  Rust-based Ubuntu packages can be built without issue.

  Rust 1.89 also brings several fixes and new features, such as the full
  stabilization of 128-bit integer support[1]. A full list of changes
  may be consulted below[2].

  As of 2 September 2025, 1.89.0 is the current stable Rust version.
  Getting rustc-1.89 into the archive means that we will be fully caught
  up with upstream.

  [1]: https://github.com/rust-lang/rust/pull/138285
  [2]: https://releases.rs/docs/1.89.0/

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



From 2121623 at bugs.launchpad.net  Tue Oct 28 15:29:34 2025
From: 2121623 at bugs.launchpad.net (Max Gilmour)
Date: Tue, 28 Oct 2025 15:29:34 -0000
Subject: [Bug 2121623] Re: [needs-packaging] rustc-1.89
References: <175641308106.667615.16419926783611633205.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176166537421.128614.3650525179900368370.malone@juju-98d295-prod-launchpad-3>

Hi Jeremy, I'd just like the version from git please. The git version
built in a PPA but I tried an LLVM 21 build in the same PPA just for
testing.

I'll make sure this toolchain is eventually removed from devel so we can
drop the LLVM 20 dependency.

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

Title:
  [needs-packaging] rustc-1.89

Status in Ubuntu:
  In Progress
Status in The Resolute Raccoon:
  In Progress

Bug description:
  Rust 1.89 was released on 7 August, 2025. A great deal of packages in
  the Ubuntu archive rely on up-to-date versions of Rust in order to
  build properly, and as time passes, the minimal supported Rust version
  (MSRV) of crucial Rust-based packages increases. It is very important
  to keep up with upstream Rust development to ensure that the latest
  Rust-based Ubuntu packages can be built without issue.

  Rust 1.89 also brings several fixes and new features, such as the full
  stabilization of 128-bit integer support[1]. A full list of changes
  may be consulted below[2].

  As of 2 September 2025, 1.89.0 is the current stable Rust version.
  Getting rustc-1.89 into the archive means that we will be fully caught
  up with upstream.

  [1]: https://github.com/rust-lang/rust/pull/138285
  [2]: https://releases.rs/docs/1.89.0/

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



From 2122556 at bugs.launchpad.net  Tue Oct 28 16:33:29 2025
From: 2122556 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 28 Oct 2025 16:33:29 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176166921053.4151.4796526906090771235.launchpad@scripts-bzrsyncd.lp.internal>

** Merge proposal linked:
   https://code.launchpad.net/~slyon/ubuntu/+source/pipewire/+git/pipewire/+merge/495139

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  In Progress

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2121623 at bugs.launchpad.net  Tue Oct 28 16:33:10 2025
From: 2121623 at bugs.launchpad.net (=?utf-8?q?Jeremy_B=C3=ADcha?=)
Date: Tue, 28 Oct 2025 16:33:10 -0000
Subject: [Bug 2121623] Re: [needs-packaging] rustc-1.89
References: <175641308106.667615.16419926783611633205.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176166919016.55328.16756039309364434280.malone@juju-98d295-prod-launchpad-7>

I've uploaded and the source package was accepted. I'm unsubscribing
ubuntu-sponsors. Feel free to resubscribe if you have something else
that needs to be sponsored.

https://launchpad.net/ubuntu/+source/rustc-1.89/1.89.0+dfsg0ubuntu1-0ubuntu1

** Package changed: Ubuntu Resolute => rustc-1.89 (Ubuntu Resolute)

** Changed in: rustc-1.89 (Ubuntu Resolute)
       Status: In Progress => Fix Committed

** No longer affects: rustc-1.89 (Ubuntu Resolute)

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

Title:
  [needs-packaging] rustc-1.89

Status in rustc-1.89 package in Ubuntu:
  Fix Committed

Bug description:
  Rust 1.89 was released on 7 August, 2025. A great deal of packages in
  the Ubuntu archive rely on up-to-date versions of Rust in order to
  build properly, and as time passes, the minimal supported Rust version
  (MSRV) of crucial Rust-based packages increases. It is very important
  to keep up with upstream Rust development to ensure that the latest
  Rust-based Ubuntu packages can be built without issue.

  Rust 1.89 also brings several fixes and new features, such as the full
  stabilization of 128-bit integer support[1]. A full list of changes
  may be consulted below[2].

  As of 2 September 2025, 1.89.0 is the current stable Rust version.
  Getting rustc-1.89 into the archive means that we will be fully caught
  up with upstream.

  [1]: https://github.com/rust-lang/rust/pull/138285
  [2]: https://releases.rs/docs/1.89.0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc-1.89/+bug/2121623/+subscriptions



From 2122556 at bugs.launchpad.net  Tue Oct 28 16:40:42 2025
From: 2122556 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Tue, 28 Oct 2025 16:40:42 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176166964268.268957.8814608980105798948.malone@juju-98d295-prod-launchpad-3>

re #15, #12, #11: Thanks for your additional explanation! As stated,
it's a bit risky but might work out, especially if we use "block-
proposed-noble" until your internal verification is done and then maybe
do some slow phasing. But I'll leave the final decision (and discussion)
between you and the SRU team.

I did review the huge patch-series for Noble, including all of upstream
MR#1800 and it looks mostly good to me. All but 4 patches are cleanly
matching the upstream patches, the others have minor differences in
patch description of whitespace (but are not declared as "backport"). I
guess it would be OKish to upload Noble as-is, but if you'd be able to
cleanup my remarks this should allow for a smoother SRU review.

Please let me know how you want to proceed!

I've also prepared a draft MP/git-ubuntu branch, feel free to propose any changes against that branch for easier future review of your (potential) changes:
https://code.launchpad.net/~slyon/ubuntu/+source/pipewire/+git/pipewire/+merge/495139

Full range-diff of git-buildpackage patch-queue with your quilt patches applied
and the corresponding upstream range from MR#1800:
https://paste.ubuntu.com/p/5GhJ4hQMK4/

List of new quilt patches that are matching upstream ("OK") or show
slight differences ("WARN"):

UCM_updates/alsa-ucm-remove-extra-space-from-the-device.intended.patch - OK
UCM_updates/alsa-mixer-allow-to-re-attach-the-mixer-control-elem.patch - WARN
=> This seems to squash two commits from the upstream merge-proposal
   (with some random whitespace fixes in empty lines).
   Can you please either make it two clean cherry-picks or mention it's a "backport" instead of "upstream" inside the DEP-3 Origin-header and briefly explain the changes.
 2:  2afc6051c <  -:  --------- [PATCH 04/38] alsa-mixer: allow to re-attach the mixer control element
 -:  --------- >  2:  3177f41cb alsa-mixer: allow to re-attach the mixer control element
 -:  --------- >  3:  4066bbaf0 alsa-mixer: fix the re-attach code for the mixer control element

UCM_updates/alsa-mixer-extend-pa_alsa_mixer_find-with-the-subdev.patch - OK
UCM_updates/alsa-util-Add-more-standard-sample-rates.patch             - OK
UCM_updates/alsa-util-Dump-probed-rates.patch                          - OK
UCM_updates/alsa-util-Perform-format-and-rate-detection-before-s.patch - OK
UCM_updates/alsa-util-Fix-pa_alsa_get_supported_formats-fallback.patch - OK
UCM_updates/alsa-ucm-Fix-spurious-mixer-path-removal-on-initial-.patch - OK
UCM_updates/alsa-ucm-Always-create-device-conflicting-supported-.patch - OK
UCM_updates/alsa-ucm-Make-modifiers-track-conflicting-supported-.patch - OK
UCM_updates/alsa-ucm-Add-enable-disable-status-helpers-for-devic.patch - OK
UCM_updates/alsa-ucm-Set-profiles-by-their-struct-instance-not-t.patch - OK
UCM_updates/alsa-ucm-Let-profiles-know-their-associated-UCM-verb.patch - OK
UCM_updates/alsa-ucm-Stop-conflating-profile-name-with-UCM-verb-.patch - OK
UCM_updates/alsa-ucm-Make-mapping-creation-independent-from-indv.patch - OK
UCM_updates/alsa-ucm-Split-profile-creation-into-verb-and-profil.patch - OK
UCM_updates/acp-Add-idxset-comparison-and-reverse-search-operati.patch - OK
UCM_updates/alsa-ucm-Rewrite-conformant-device-group-generation-.patch - OK
UCM_updates/alsa-ucm-Fix-device-conformance-check.patch                - OK
UCM_updates/alsa-ucm-Split-out-helpers-for-device-set-name-descr.patch - OK
UCM_updates/alsa-ucm-Make-one-input-output-mapping-per-UCM-devic.patch - OK
UCM_updates/alsa-ucm-Remove-combination-port-generation-logic.patch    - OK
UCM_updates/alsa-ucm-Make-ports-store-only-one-device.patch            - OK
UCM_updates/alsa-ucm-Make-mapping-UCM-contexts-have-only-one-dev.patch - OK
UCM_updates/alsa-ucm-Make-mapping-UCM-contexts-have-only-one-mod.patch - WARN
=> nitpick: slight difference in commit message, can you make it a clean cherry-pick?
UCM_updates/alsa-ucm-Disable-old-devices-when-switching-profiles.patch - OK
UCM_updates/alsa-ucm-Create-multiple-profiles-per-verb-for-confl.patch - OK
UCM_updates/alsa-ucm-Add-enable-disable-status-helpers-for-modif.patch - OK
UCM_updates/alsa-ucm-Disable-old-modifiers-when-switching-profil.patch - OK
UCM_updates/alsa-ucm-Consider-devices-using-the-same-PCM-as-inco.patch - OK
UCM_updates/alsa-ucm-Fix-more-instances-of-profile-verb-conflati.patch - OK
UCM_updates/alsa-ucm-Check-UCM-verb-before-working-with-device-s.patch - OK
UCM_updates/alsa-ucm-Replace-port-device-UCM-context-assertion-w.patch - OK
UCM_updates/acp-Don-t-sync-hardware-volumes-while-UCM-device-is-.patch - OK
UCM_updates/acp-Disable-active-UCM-profile-before-enabling-Pro-A.patch - OK

lp2122556_0001-acp-sync-the-mixer-after-selecting-the-port.patch - WARN
=> nitpick: some minimal diff of whitespace in empty lines, can you make it a clean cherry-pick?

lp2122556_0002-spa-alsa-do-not-allow-setting-Route-that-is-not-in-c.patch - WARN
=> diff in patch context. Please mention it's a "backport" instead of "upstream" inside DEP-3 Origin-header and briefly explain the changes.

** Tags added: block-proposed-noble

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  In Progress

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2100266 at bugs.launchpad.net  Tue Oct 28 17:28:39 2025
From: 2100266 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 28 Oct 2025 17:28:39 -0000
Subject: [Bug 2100266] [NEW] Versioned cargo wrapper script points to default
 cargo
References: <174056282678.1063803.9344663968037281355.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176167252029.865691.8328095120858313962.launchpad@juju-98d295-prod-launchpad-2>

You have been subscribed to a public bug by Max Gilmour (maxgmr):

If you use the cargo wrapper script provided by a versioned cargo
package, e.g. /usr/lib/rust-1.80/share/cargo/bin/cargo, it will invoke
/usr/bin/cargo rather than /usr/lib/rust-1.80/bin/cargo.

** Affects: rustc-1.76 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: rustc-1.77 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: rustc-1.78 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: rustc-1.79 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: rustc-1.80 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: rustc-1.81 (Ubuntu)
     Importance: Undecided
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress

** Affects: rustc-1.82 (Ubuntu)
     Importance: Undecided
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress

** Affects: rustc-1.83 (Ubuntu)
     Importance: Undecided
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress

** Affects: rustc-1.84 (Ubuntu)
     Importance: High
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress

** Affects: rustc-1.85 (Ubuntu)
     Importance: Undecided
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress

** Affects: rustc-1.88 (Ubuntu)
     Importance: Undecided
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress

** Affects: rustc-1.76 (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: rustc-1.77 (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: rustc-1.78 (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: rustc-1.79 (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: rustc-1.80 (Ubuntu Focal)
     Importance: Undecided
         Status: New

** Affects: rustc-1.76 (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: rustc-1.77 (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: rustc-1.78 (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: rustc-1.79 (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: rustc-1.80 (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: rustc-1.76 (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: rustc-1.77 (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: rustc-1.78 (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: rustc-1.79 (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: rustc-1.80 (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: rustc-1.80 (Ubuntu Oracular)
     Importance: Undecided
         Status: Won't Fix

** Affects: rustc-1.81 (Ubuntu Oracular)
     Importance: Undecided
         Status: Won't Fix

** Affects: rustc-1.81 (Ubuntu Plucky)
     Importance: Undecided
         Status: New

** Affects: rustc-1.82 (Ubuntu Plucky)
     Importance: Undecided
         Status: New

** Affects: rustc-1.83 (Ubuntu Plucky)
     Importance: Undecided
         Status: New

** Affects: rustc-1.84 (Ubuntu Plucky)
     Importance: High
         Status: Triaged

** Affects: rustc-1.85 (Ubuntu Questing)
     Importance: Undecided
         Status: New

** Affects: rustc-1.88 (Ubuntu Questing)
     Importance: Undecided
         Status: New

** Affects: rustc-1.88 (Ubuntu Resolute)
     Importance: Undecided
     Assignee: Max Gilmour (maxgmr)
         Status: In Progress


** Tags: foundations-todo
-- 
Versioned cargo wrapper script points to default cargo
https://bugs.launchpad.net/bugs/2100266
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2100266 at bugs.launchpad.net  Tue Oct 28 17:30:28 2025
From: 2100266 at bugs.launchpad.net (Max Gilmour)
Date: Tue, 28 Oct 2025 17:30:28 -0000
Subject: [Bug 2100266] Re: Versioned cargo wrapper script points to default
 cargo
References: <174056282678.1063803.9344663968037281355.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176167262846.374763.13554323960606137643.malone@juju-98d295-prod-launchpad-3>

I've created fixes for several of the targeted versions. Their debdiffs
shall be included in future comments.

======
Before
======

root at plucky-bug:~# apt install -yU cargo cargo-1.82
[...]
root at plucky-bug:~# cargo --version
cargo 1.84.1 (66221abde 2024-11-19)
root at plucky-bug:~# /usr/lib/rust-1.82/share/cargo/bin/cargo --version
cargo 1.84.1 (66221abde 2024-11-19)

=====
After
=====

root at plucky-bug:~# add-apt-repository ppa:maxgmr/rustc-lp-2100266
[...]
root at plucky-bug:~# apt-cache policy cargo-1.82
cargo-1.82:
  Installed: 1.82.0+dfsg0ubuntu1-0ubuntu2
  Candidate: 1.82.0+dfsg0ubuntu1-0ubuntu3~ppa2
  Version table:
     1.82.0+dfsg0ubuntu1-0ubuntu3~ppa2 500
        500 https://ppa.launchpadcontent.net/maxgmr/rustc-lp-2100266/ubuntu plucky/main amd64 Packages
 *** 1.82.0+dfsg0ubuntu1-0ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu plucky/universe amd64 Packages
        100 /var/lib/dpkg/status
root at plucky-bug:~# apt install cargo-1.82
[...]
root at plucky-bug:~# cargo --version
cargo 1.84.1 (66221abde 2024-11-19)
root at plucky-bug:~# /usr/lib/rust-1.82/share/cargo/bin/cargo --version
cargo 1.82.0 (8f40fc59f 2024-08-21)

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

Title:
  Versioned cargo wrapper script points to default cargo

Status in rustc-1.76 package in Ubuntu:
  Invalid
Status in rustc-1.77 package in Ubuntu:
  Invalid
Status in rustc-1.78 package in Ubuntu:
  Invalid
Status in rustc-1.79 package in Ubuntu:
  Invalid
Status in rustc-1.80 package in Ubuntu:
  Invalid
Status in rustc-1.81 package in Ubuntu:
  In Progress
Status in rustc-1.82 package in Ubuntu:
  In Progress
Status in rustc-1.83 package in Ubuntu:
  In Progress
Status in rustc-1.84 package in Ubuntu:
  In Progress
Status in rustc-1.85 package in Ubuntu:
  In Progress
Status in rustc-1.88 package in Ubuntu:
  In Progress
Status in rustc-1.76 source package in Focal:
  New
Status in rustc-1.77 source package in Focal:
  New
Status in rustc-1.78 source package in Focal:
  New
Status in rustc-1.79 source package in Focal:
  New
Status in rustc-1.80 source package in Focal:
  New
Status in rustc-1.76 source package in Jammy:
  New
Status in rustc-1.77 source package in Jammy:
  New
Status in rustc-1.78 source package in Jammy:
  New
Status in rustc-1.79 source package in Jammy:
  New
Status in rustc-1.80 source package in Jammy:
  New
Status in rustc-1.76 source package in Noble:
  New
Status in rustc-1.77 source package in Noble:
  New
Status in rustc-1.78 source package in Noble:
  New
Status in rustc-1.79 source package in Noble:
  New
Status in rustc-1.80 source package in Noble:
  New
Status in rustc-1.80 source package in Oracular:
  Won't Fix
Status in rustc-1.81 source package in Oracular:
  Won't Fix
Status in rustc-1.81 source package in Plucky:
  New
Status in rustc-1.82 source package in Plucky:
  New
Status in rustc-1.83 source package in Plucky:
  New
Status in rustc-1.84 source package in Plucky:
  Triaged
Status in rustc-1.85 source package in Questing:
  New
Status in rustc-1.88 source package in Questing:
  New
Status in rustc-1.88 source package in Resolute:
  In Progress

Bug description:
  If you use the cargo wrapper script provided by a versioned cargo
  package, e.g. /usr/lib/rust-1.80/share/cargo/bin/cargo, it will invoke
  /usr/bin/cargo rather than /usr/lib/rust-1.80/bin/cargo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc-1.76/+bug/2100266/+subscriptions



From 2100266 at bugs.launchpad.net  Tue Oct 28 17:31:08 2025
From: 2100266 at bugs.launchpad.net (Max Gilmour)
Date: Tue, 28 Oct 2025 17:31:08 -0000
Subject: [Bug 2100266] Re: Versioned cargo wrapper script points to default
 cargo
References: <174056282678.1063803.9344663968037281355.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176167266856.206641.2135058023325277781.malone@juju-98d295-prod-launchpad-4>

** Patch added: "1-1.81.0+dfsg0ubuntu1-0ubuntu4.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/rustc-1.84/+bug/2100266/+attachment/5921273/+files/1-1.81.0+dfsg0ubuntu1-0ubuntu4.debdiff

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

Title:
  Versioned cargo wrapper script points to default cargo

Status in rustc-1.76 package in Ubuntu:
  Invalid
Status in rustc-1.77 package in Ubuntu:
  Invalid
Status in rustc-1.78 package in Ubuntu:
  Invalid
Status in rustc-1.79 package in Ubuntu:
  Invalid
Status in rustc-1.80 package in Ubuntu:
  Invalid
Status in rustc-1.81 package in Ubuntu:
  In Progress
Status in rustc-1.82 package in Ubuntu:
  In Progress
Status in rustc-1.83 package in Ubuntu:
  In Progress
Status in rustc-1.84 package in Ubuntu:
  In Progress
Status in rustc-1.85 package in Ubuntu:
  In Progress
Status in rustc-1.88 package in Ubuntu:
  In Progress
Status in rustc-1.76 source package in Focal:
  New
Status in rustc-1.77 source package in Focal:
  New
Status in rustc-1.78 source package in Focal:
  New
Status in rustc-1.79 source package in Focal:
  New
Status in rustc-1.80 source package in Focal:
  New
Status in rustc-1.76 source package in Jammy:
  New
Status in rustc-1.77 source package in Jammy:
  New
Status in rustc-1.78 source package in Jammy:
  New
Status in rustc-1.79 source package in Jammy:
  New
Status in rustc-1.80 source package in Jammy:
  New
Status in rustc-1.76 source package in Noble:
  New
Status in rustc-1.77 source package in Noble:
  New
Status in rustc-1.78 source package in Noble:
  New
Status in rustc-1.79 source package in Noble:
  New
Status in rustc-1.80 source package in Noble:
  New
Status in rustc-1.80 source package in Oracular:
  Won't Fix
Status in rustc-1.81 source package in Oracular:
  Won't Fix
Status in rustc-1.81 source package in Plucky:
  New
Status in rustc-1.82 source package in Plucky:
  New
Status in rustc-1.83 source package in Plucky:
  New
Status in rustc-1.84 source package in Plucky:
  Triaged
Status in rustc-1.85 source package in Questing:
  New
Status in rustc-1.88 source package in Questing:
  New
Status in rustc-1.88 source package in Resolute:
  In Progress

Bug description:
  If you use the cargo wrapper script provided by a versioned cargo
  package, e.g. /usr/lib/rust-1.80/share/cargo/bin/cargo, it will invoke
  /usr/bin/cargo rather than /usr/lib/rust-1.80/bin/cargo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rustc-1.76/+bug/2100266/+subscriptions



From 2122556 at bugs.launchpad.net  Tue Oct 28 21:44:12 2025
From: 2122556 at bugs.launchpad.net (Kai-Chuan Hsieh)
Date: Tue, 28 Oct 2025 21:44:12 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176168785294.615553.7557828367108215256.malone@juju-98d295-prod-launchpad-7>

@slyon

reply #17. Thanks for reviewing it. I made the MP [1] by following the
suggestion, please check if it is good to proceed.

[1]
https://code.launchpad.net/~kchsieh/ubuntu/+source/pipewire/+git/pipewire/+merge/495153

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  In Progress

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2130032 at bugs.launchpad.net  Wed Oct 29 09:50:16 2025
From: 2130032 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 29 Oct 2025 09:50:16 -0000
Subject: [Bug 2130032] [NEW] libbpf-tools is not available on s390x
References: <176166632794.159950.2089668575019926360.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176173141722.2450661.11116498538689576201.launchpad@juju-98d295-prod-launchpad-2>

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

Upstream libbpf-tools supports s390x, but it's not enabled in Ubuntu.

I've applied the following patches to bpfcc-0.31.0+ds (questing) and the
resulting debs worked:

--- debian/control.orig 2025-10-28 15:36:18.036218954 +0000
+++ debian/control      2025-10-28 15:34:44.981585267 +0000
@@ -99,7 +99,7 @@
  This package provides the command-line tools and examples
 
 Package: libbpf-tools
-Architecture: amd64 arm64
+Architecture: amd64 arm64 s390x
 Depends: ${misc:Depends},
  ${shlibs:Depends}
 Description: tools for BPF Compiler Collection based on libbpf (BTF and CO-RE)

--- debian/rules.orig   2025-10-28 15:39:44.563040889 +0000
+++ debian/rules        2025-10-28 15:39:49.668436889 +0000
@@ -8,7 +8,7 @@
 
 # for building libbpf-tools on selective architecture
 include /usr/share/dpkg/architecture.mk
-libbpf_tool_skip_arch := armhf s390x ppc64 riscv64
+libbpf_tool_skip_arch := armhf ppc64 riscv64
 
 # Disable tests as they require root to run
 export DEB_BUILD_MAINT_OPTIONS=nocheck

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


** Tags: dcr-incoming
-- 
libbpf-tools is not available on s390x
https://bugs.launchpad.net/bugs/2130032
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2122556 at bugs.launchpad.net  Wed Oct 29 11:36:49 2025
From: 2122556 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Wed, 29 Oct 2025 11:36:49 -0000
Subject: =?utf-8?q?=5BBug_2122556=5D_Re=3A_3=2E5mm_microphone_recognized_but_can=E2=80=99t_be_used_as_audio_input?=
References: <175756005578.1012427.7750653839967208635.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176173781006.2629578.16580949480031891817.malone@juju-98d295-prod-launchpad-2>

Thanks @kchsieh! With this I'm seeing clean cherry-picks for all of
upstream's MR#1800 in my git range-diff. It's still a huge change, but
I'm OK with sponsoring it for the reasons given above and added "block-
proposed-noble" for you to do the extra testing involved.

The final decision will be with the SRU team.


Sponsoring into the Noble unapproved queue!

$ dput ubuntu ../pipewire_1.0.5-1ubuntu3.2_source.changes
Uploading pipewire using ftp to ubuntu (host: upload.ubuntu.com; directory: /ubuntu)
running ppaforppaonly: Stop uploads to the archive with or to ppa without ~ppa suffix.
running updatemaintainer: Stop if ubuntu changes are without ubuntu maintainer.
running suite-mismatch: check the target distribution for common errors
running gpg: check GnuPG signatures before the upload
running releasemismatch: Warn about mismatching suffixesg e.g. focal with a XX.YY not being 20.04
running gitubuntu: Warn if uploading without git-ubuntu Vcs-* entries.
running badauthor: Stop if uploading with root@ or ubuntu@ email adresses.
running supported-distribution: check whether the target distribution is currently supported (using distro-info)
{'allowed': ['release', 'proposed', 'backports', 'security'], 'known': ['release', 'proposed', 'updates', 'backports', 'security']}
running required-fields: check whether a field is present and non-empty in the changes file
running nobug: Stop if uploading without any bug reference.
running check-debs: makes sure the upload contains a binary package
running placeholderbug: Stop if using common placeholder numbers as bug reference.
running checksum: verify checksums before uploading
Uploading pipewire_1.0.5-1ubuntu3.2.dsc
Uploading pipewire_1.0.5-1ubuntu3.2.debian.tar.xz
Uploading pipewire_1.0.5-1ubuntu3.2_source.buildinfo
Uploading pipewire_1.0.5-1ubuntu3.2_source.changes

** Changed in: pipewire (Ubuntu Noble)
       Status: New => In Progress

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

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  In Progress
Status in pipewire source package in Plucky:
  In Progress

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

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



From 2130010 at bugs.launchpad.net  Wed Oct 29 11:45:31 2025
From: 2130010 at bugs.launchpad.net (=?utf-8?q?Lukas_M=C3=A4rdian?=)
Date: Wed, 29 Oct 2025 11:45:31 -0000
Subject: [Bug 2130010] Re: Sync laserboy 2024.03.08+dfsg-3 (universe) from
 Debian unstable (main)
References: <176165420486.272529.16764589301594165484.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176173833208.2648973.9134997644889660583.malone@juju-98d295-prod-launchpad-2>

This bug was fixed in the package laserboy - 2024.03.08+dfsg-3
Sponsored for Mateus Rodrigues de Morais (mateus-morais)

---------------
laserboy (2024.03.08+dfsg-3) unstable; urgency=medium

  * Add fix-boost-1.88-ftbfs.patch, fixing FTBFS with Boost 1.88.
    Thanks to Mateus Rodrigues de Morais for the patch (Closes: #1110627)

 -- Nicolas Schodet <nico at ni.fr.eu.org>  Mon, 27 Oct 2025 17:39:12 +0100

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

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

Title:
  Sync laserboy 2024.03.08+dfsg-3 (universe) from Debian unstable (main)

Status in laserboy package in Ubuntu:
  Fix Released

Bug description:
  Please sync laserboy 2024.03.08+dfsg-3 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * d/p/fix-boost-1.88-ftbfs.patch: fix FTBFS with boost 1.88 (LP: #2120885)

      The patch fixing FTBFS on Boost 1.88 has been included in Debian and delta
      is no longer necessary.

  Changelog entries since current resolute version
  2024.03.08+dfsg-2ubuntu1:

  laserboy (2024.03.08+dfsg-3) unstable; urgency=medium

    * Add fix-boost-1.88-ftbfs.patch, fixing FTBFS with Boost 1.88.
      Thanks to Mateus Rodrigues de Morais for the patch (Closes: #1110627)

   -- Nicolas Schodet <nico at ni.fr.eu.org>  Mon, 27 Oct 2025 17:39:12
  +0100

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



From 2127792 at bugs.launchpad.net  Wed Oct 29 13:47:26 2025
From: 2127792 at bugs.launchpad.net (Nick Rosbrook)
Date: Wed, 29 Oct 2025 13:47:26 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176174564625.2229353.12785343667456552469.malone@juju-98d295-prod-launchpad-7>

Hello Antoine, or anyone else affected,

Accepted gnome-remote-desktop into questing-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/49.0-0ubuntu1.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-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. 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-questing

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap. This version supports NVENC, the .deb
  does not.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127925 at bugs.launchpad.net  Wed Oct 29 17:37:19 2025
From: 2127925 at bugs.launchpad.net (Ken VanDine)
Date: Wed, 29 Oct 2025 17:37:19 -0000
Subject: [Bug 2127925] Re: "policy: auto-activating connection" never occurs
 on adapter restart for networks where user entered incorrect password before
 correct password
References: <176053406915.105350.7511956944740384426.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176175943996.3298526.12904600338128622575.malone@juju-98d295-prod-launchpad-2>

This has been sponsored to resolute, questing, plucky, and noble

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

Title:
  "policy: auto-activating connection" never occurs on adapter restart
  for networks where user entered incorrect password before correct
  password

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Noble:
  New
Status in network-manager source package in Plucky:
  New
Status in network-manager source package in Questing:
  New
Status in network-manager source package in Resolute:
  New

Bug description:
  This bug was reported upstream:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1812

  And it got fixed with
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2295

  ---------------------------
  SRU Justification:

  [ Impact ]

   * When trying to connect to a wifi network, if one does cancel the
  credential popup, the network is gets an internal in-memory flag
  preventing its auto reconnection. If then the user succeeds to connect
  to it, this flag is not removed. As a result, if the user disable and
  re-enables wifi, the network will not reconnect automatically.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * Whenever the connection succeeds, the autoconnect blocker flag must
  be removed and reset correctly.

  [ Test Plan ]

   * Test network-manager without and with this fix:
  1. Forget all wifi networks
  2. Click on one on the gnome menubar
  3. Cancel the popup without entering credentials
  4. Check NM's logs to see if an autoconnection is attempted. No autoconnection should be attempted at this point.
  5. Click on this same network again, connect successfully.
  6. Disable and re-enable wifi.
  7. See if an automatic reconnection occurs.

  [ Where problems could occur ]

   * Given the nature of the fix (it's one line), I don't see how
  anything could go wrong here, given we properly run the test plan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2127925/+subscriptions



From 2127925 at bugs.launchpad.net  Wed Oct 29 17:50:18 2025
From: 2127925 at bugs.launchpad.net (Ken VanDine)
Date: Wed, 29 Oct 2025 17:50:18 -0000
Subject: [Bug 2127925] Re: "policy: auto-activating connection" never occurs
 on adapter restart for networks where user entered incorrect password before
 correct password
References: <176053406915.105350.7511956944740384426.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176176021946.2672107.12950078396744450317.launchpad@juju-98d295-prod-launchpad-7>

** Changed in: network-manager (Ubuntu Resolute)
       Status: New => Fix Committed

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

Title:
  "policy: auto-activating connection" never occurs on adapter restart
  for networks where user entered incorrect password before correct
  password

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Noble:
  New
Status in network-manager source package in Plucky:
  New
Status in network-manager source package in Questing:
  New
Status in network-manager source package in Resolute:
  Fix Committed

Bug description:
  This bug was reported upstream:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1812

  And it got fixed with
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2295

  ---------------------------
  SRU Justification:

  [ Impact ]

   * When trying to connect to a wifi network, if one does cancel the
  credential popup, the network is gets an internal in-memory flag
  preventing its auto reconnection. If then the user succeeds to connect
  to it, this flag is not removed. As a result, if the user disable and
  re-enables wifi, the network will not reconnect automatically.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * Whenever the connection succeeds, the autoconnect blocker flag must
  be removed and reset correctly.

  [ Test Plan ]

   * Test network-manager without and with this fix:
  1. Forget all wifi networks
  2. Click on one on the gnome menubar
  3. Cancel the popup without entering credentials
  4. Check NM's logs to see if an autoconnection is attempted. No autoconnection should be attempted at this point.
  5. Click on this same network again, connect successfully.
  6. Disable and re-enable wifi.
  7. See if an automatic reconnection occurs.

  [ Where problems could occur ]

   * Given the nature of the fix (it's one line), I don't see how
  anything could go wrong here, given we properly run the test plan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2127925/+subscriptions



From 2127792 at bugs.launchpad.net  Wed Oct 29 20:35:13 2025
From: 2127792 at bugs.launchpad.net (Mitchell Augustin)
Date: Wed, 29 Oct 2025 20:35:13 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176177011360.3606285.5215529223150428257.malone@juju-98d295-prod-launchpad-2>

@Antoine I did need to `sudo chmod 666 /dev/dri/renderD128` to reproduce
this issue on Questing (since it's required to allow RDP to use the
GPU), just FYI. I'll update the test plan accordingly.

** Description changed:

  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.
  
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263
  
  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346
  
  ---------------------------
  SRU Justification:
  
  [ Impact ]
  
   * This is a hardware enablement SRU.
  
   * gnome-remote-desktop, when used alongside NVENC for video streaming,
  simply does not work, because the image is broken.
  
   * With the above, the streaming is fixed.
  
  [ Fix ]
  
   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.
  
  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.
  
  [ Test Plan ]
  
  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)
  
  2. Enable Remote Login from the Gnome Settings on the DUT with a monitor
  plugged in.
  
- 3. Install Reminna from Snap. This version supports NVENC, the .deb does
- not.
+ 3. Install Reminna from Snap (via the edge channel) on your client. This
+ version supports NVENC, the .deb does not. On the server, run `sudo
+ chmod 666 /dev/dri/renderD128` to enable GPU acceleration with RDP.
  
  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon` and
  observing an encoder activity >0%. The repro only occurs when the NVENC
  path is used. CPU encoding path or non-H264 streaming is unaffected
  
  5. Run the same test without a monitor plugged in to the DUT.
  
  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)
  
  [ Where problems could occur ]
  
   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap (via the edge channel) on your client.
  This version supports NVENC, the .deb does not. On the server, run
  `sudo chmod 666 /dev/dri/renderD128` to enable GPU acceleration with
  RDP.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2120689 at bugs.launchpad.net  Thu Oct 30 08:09:21 2025
From: 2120689 at bugs.launchpad.net (Timo Aaltonen)
Date: Thu, 30 Oct 2025 08:09:21 -0000
Subject: [Bug 2120689] Re: [SRU] Missing DeviceAllow for Intel's linux-lts
 6.12 tree's ipu6-psys
References: <175521695863.3172424.7969664374267313725.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176181176145.4120046.2837041313390926763.malone@juju-98d295-prod-launchpad-4>

does the distro kernel have the same issue?

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

Title:
  [SRU] Missing DeviceAllow for Intel's linux-lts 6.12 tree's ipu6-psys

Status in v4l2-relayd package in Ubuntu:
  In Progress
Status in v4l2-relayd source package in Noble:
  Invalid
Status in v4l2-relayd source package in Plucky:
  Invalid
Status in v4l2-relayd source package in Questing:
  In Progress

Bug description:
  [ SRU Justification ]

  [ Impact ]

  Missing DeviceAllow for Intel's linux-lts 6.12 tree's ipu6-psys. Since
  v4l2-relayd version 0.1.5, systemd DeviceAllow is added to limit
  device accesses for v4l2-relayd. The one added initially was for Intel
  IPU7, and certainly IPU6 is required, too.

  Without that, an error printed in v4l2-relayd's systemd logs:
  ```
  $ systemctl status v4l2-relayd
  ......
  sh[6920]: [10-28 03:49:39.560] CamHAL[ERR] Failed to open PSYS, error: Operation not permitted
  ```

  [ Test Plan ]

  1. Install v4l2-relayd from -proposed pocket.

  2. Try to use webcam with:
     ```
     $ gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! autovideosink
     # Expect video streaming occurs
     ```

  [ Where problems could occur ]

  Trivial. That's the hardware access it needs in order to use the
  webcam function.

  [ Other Info ]

  While this affects only v4l2-relayd >= 0.1.5, nominate only Resolute
  and Questing. For Resolute, the fix has been included in 0.2.0, which
  is being updated in bug 2116722.

  ========== original bug report ==========

  The Intel's Linux LTS tree, which supports IPU6 out-of-the-box, uses
  different character device class causing systemd rule packaged with
  v4l2-relayd unable to access the device.

  https://github.com/intel/linux-intel-
  lts/blob/6.12/linux/drivers/media/pci/intel/ipu6/psys/ipu-psys.c#L63

  I've confirmed adding "DeviceAllow=char-intel-ipu6-psys" fixes IPU6
  support for v4l2-relayd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l2-relayd/+bug/2120689/+subscriptions



From 2128350 at bugs.launchpad.net  Thu Oct 30 10:29:44 2025
From: 2128350 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 30 Oct 2025 10:29:44 -0000
Subject: [Bug 2128350] Re: Some desktop snaps are no longer visible in the
 apps menu
References: <176062998947.2963269.10879243361967771236.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176182018450.729398.16665745435777362286.malone@juju-98d295-prod-launchpad-2>

Tested in Ubuntu 25.04:

$ snap info snapd | grep installed:
installed:          2.72                         (25577) 53MB snapd

$ apt policy libmalcontent-0-0
libmalcontent-0-0:
  Installed: 0.13.0-1ubuntu1.2
  Candidate: 0.13.0-1ubuntu1.2

Telegram desktop is visible again in GNOME's applications menu.

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

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

Title:
  Some desktop snaps are no longer visible in the apps menu

Status in malcontent package in Ubuntu:
  Fix Released
Status in malcontent source package in Jammy:
  In Progress
Status in malcontent source package in Noble:
  In Progress
Status in malcontent source package in Plucky:
  Fix Committed
Status in malcontent source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  Malcontent is a parental control mechanism implemented in GNOME Shell.
  It supports hiding applications from the application menu.

  Some desktop snaps like telegram-desktop are no longer visible in GNOME Shell when libmalcontent is installed, even without any filters applied. Which snaps are hidden depends on the numbers of command-line arguments they specify in the Exec line. If it's more than 2, then the snap will be hidden.
  For example, telegram-desktop uses:

  Exec=/snap/bin/telegram-desktop -- %U

  Ubuntu ships a patch in malcontent to allow filtering non-flatpak applications too.
  This patch assumed that a desktop snap Exec= line would always follow the format `Exec=env BAMF_DESKTOP_FILE_HINT=foo.desktop /snap/bin/foo arg1 arg2`, so it would interpret the third argument as the absolute binary path.

  That was changed in snapd version 2.72 to remove the
  BAMF_DESKTOP_FILE_HINT environment variable, so the Exec line now
  follows the format `Exec=/snap/bin/foo arg1 arg2`. The third argument
  is no longer the binary's absolute path, and things break.

  Malcontent needs to be adapted to not assume that the snap binary is
  always the third argument.

  [ Test Plan ]

  1. Install the `malcontent` deb package
     -> this is pre-installed on some OEM installs.
  2. Log-out, log-in again.
  3. Install snapd 2.72 or newer, available from the candidate channel:
     `sudo snap refresh snapd --candidate`
  4. Install the `telegram-desktop` snap
  5. Open the GNOME Shell application launcher
  6. Search for Telegram
  7. Verify that the Telegram app is listed.

  [ Where problems could occur ]

  Problems would manifest with applications being incorrectly filtered
  out or not filtered out.

  The patch should make sure that it is future-proof by not assuming the
  position of the binary path in the command-line a-priori.

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



From 2128350 at bugs.launchpad.net  Thu Oct 30 10:36:40 2025
From: 2128350 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 30 Oct 2025 10:36:40 -0000
Subject: [Bug 2128350] Re: Some desktop snaps are no longer visible in the
 apps menu
References: <176062998947.2963269.10879243361967771236.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176182060022.126838.6582404691009014991.malone@juju-98d295-prod-launchpad-7>

Tested in Ubuntu 25.10:

$ snap info snapd | grep installed:
installed:          2.72                         (25577) 53MB snapd

$ apt policy libmalcontent-0-0
libmalcontent-0-0:
  Installed: 0.13.0-1ubuntu2.1
  Candidate: 0.13.0-1ubuntu2.1

Telegram desktop is visible again in GNOME's applications menu.

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

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

Title:
  Some desktop snaps are no longer visible in the apps menu

Status in malcontent package in Ubuntu:
  Fix Released
Status in malcontent source package in Jammy:
  In Progress
Status in malcontent source package in Noble:
  In Progress
Status in malcontent source package in Plucky:
  Fix Committed
Status in malcontent source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  Malcontent is a parental control mechanism implemented in GNOME Shell.
  It supports hiding applications from the application menu.

  Some desktop snaps like telegram-desktop are no longer visible in GNOME Shell when libmalcontent is installed, even without any filters applied. Which snaps are hidden depends on the numbers of command-line arguments they specify in the Exec line. If it's more than 2, then the snap will be hidden.
  For example, telegram-desktop uses:

  Exec=/snap/bin/telegram-desktop -- %U

  Ubuntu ships a patch in malcontent to allow filtering non-flatpak applications too.
  This patch assumed that a desktop snap Exec= line would always follow the format `Exec=env BAMF_DESKTOP_FILE_HINT=foo.desktop /snap/bin/foo arg1 arg2`, so it would interpret the third argument as the absolute binary path.

  That was changed in snapd version 2.72 to remove the
  BAMF_DESKTOP_FILE_HINT environment variable, so the Exec line now
  follows the format `Exec=/snap/bin/foo arg1 arg2`. The third argument
  is no longer the binary's absolute path, and things break.

  Malcontent needs to be adapted to not assume that the snap binary is
  always the third argument.

  [ Test Plan ]

  1. Install the `malcontent` deb package
     -> this is pre-installed on some OEM installs.
  2. Log-out, log-in again.
  3. Install snapd 2.72 or newer, available from the candidate channel:
     `sudo snap refresh snapd --candidate`
  4. Install the `telegram-desktop` snap
  5. Open the GNOME Shell application launcher
  6. Search for Telegram
  7. Verify that the Telegram app is listed.

  [ Where problems could occur ]

  Problems would manifest with applications being incorrectly filtered
  out or not filtered out.

  The patch should make sure that it is future-proof by not assuming the
  position of the binary path in the command-line a-priori.

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



From 2127792 at bugs.launchpad.net  Thu Oct 30 13:54:15 2025
From: 2127792 at bugs.launchpad.net (Mitchell Augustin)
Date: Thu, 30 Oct 2025 13:54:15 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176183245527.723505.16744557742770353722.malone@juju-98d295-prod-launchpad-3>

This still is not getting pulled from questing-proposed for me when I
try to install it via apt, but I did verify that it works as expected on
DGX Spark when I install the deb from
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/49.0-0ubuntu1.1/+build/31444535/+files/gnome-remote-
desktop_49.0-0ubuntu1.1_arm64.deb.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap (via the edge channel) on your client.
  This version supports NVENC, the .deb does not. On the server, run
  `sudo chmod 666 /dev/dri/renderD128` to enable GPU acceleration with
  RDP.

  4. Test gnome-remote-desktop with and without the fix. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon`
  and observing an encoder activity >0%. The repro only occurs when the
  NVENC path is used. CPU encoding path or non-H264 streaming is
  unaffected

  5. Run the same test without a monitor plugged in to the DUT.

  6. Run the same tests (with and without monitors) on an older GPU
  generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2128350 at bugs.launchpad.net  Thu Oct 30 14:34:35 2025
From: 2128350 at bugs.launchpad.net (Alessandro Astone)
Date: Thu, 30 Oct 2025 14:34:35 -0000
Subject: [Bug 2128350] Re: Some desktop snaps are no longer visible in the
 apps menu
References: <176062998947.2963269.10879243361967771236.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176183487582.555661.12778735049992603030.launchpad@juju-98d295-prod-launchpad-7>

** Changed in: malcontent (Ubuntu Noble)
       Status: In Progress => Fix Committed

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

Title:
  Some desktop snaps are no longer visible in the apps menu

Status in malcontent package in Ubuntu:
  Fix Released
Status in malcontent source package in Jammy:
  In Progress
Status in malcontent source package in Noble:
  Fix Committed
Status in malcontent source package in Plucky:
  Fix Committed
Status in malcontent source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  Malcontent is a parental control mechanism implemented in GNOME Shell.
  It supports hiding applications from the application menu.

  Some desktop snaps like telegram-desktop are no longer visible in GNOME Shell when libmalcontent is installed, even without any filters applied. Which snaps are hidden depends on the numbers of command-line arguments they specify in the Exec line. If it's more than 2, then the snap will be hidden.
  For example, telegram-desktop uses:

  Exec=/snap/bin/telegram-desktop -- %U

  Ubuntu ships a patch in malcontent to allow filtering non-flatpak applications too.
  This patch assumed that a desktop snap Exec= line would always follow the format `Exec=env BAMF_DESKTOP_FILE_HINT=foo.desktop /snap/bin/foo arg1 arg2`, so it would interpret the third argument as the absolute binary path.

  That was changed in snapd version 2.72 to remove the
  BAMF_DESKTOP_FILE_HINT environment variable, so the Exec line now
  follows the format `Exec=/snap/bin/foo arg1 arg2`. The third argument
  is no longer the binary's absolute path, and things break.

  Malcontent needs to be adapted to not assume that the snap binary is
  always the third argument.

  [ Test Plan ]

  1. Install the `malcontent` deb package
     -> this is pre-installed on some OEM installs.
  2. Log-out, log-in again.
  3. Install snapd 2.72 or newer, available from the candidate channel:
     `sudo snap refresh snapd --candidate`
  4. Install the `telegram-desktop` snap
  5. Open the GNOME Shell application launcher
  6. Search for Telegram
  7. Verify that the Telegram app is listed.

  [ Where problems could occur ]

  Problems would manifest with applications being incorrectly filtered
  out or not filtered out.

  The patch should make sure that it is future-proof by not assuming the
  position of the binary path in the command-line a-priori.

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



From 2130347 at bugs.launchpad.net  Thu Oct 30 14:59:38 2025
From: 2130347 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 30 Oct 2025 14:59:38 -0000
Subject: [Bug 2130347] [NEW] trash banner active 'Empty Trash' button
References: <176183612155.645418.17670435522354474893.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176183637891.840983.16845436374694370439.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Andreas Glinserer (aglinserer):

[ Impact ]

 * The bug is a confusing banner shown in the `Trash` section in nautilus. The
   banner is active and conveys that files are there to be removed even when
   the trash is empty.

 * Our partner nvidia has reported this bug and sees this as a UX
problem.

[ Test Plan ]

 * Visit `Trash` on your system. There you have now two main scenarios:
   - Trash is empty: The banner on top suggests that you can remove files.
	 Clicking on it triggers a dialog box to confirm. The whole operation does
     nothing.
   - Trash has files in it: Banner shows the option to remove trash and
     clicking on it and confirming does empty the trash. Now you are at the
     `Trash is empty` state.

 * With the patch applied, visiting an empty `Trash` does not show the banner.
   If files are in the trash, the banner becomes active.

[ Where problems could occur ]

 * If the monitoring of `Trash` does fail, the banner could show up even if not
   intended or being hidden. In the case of it being hidden, users are still
   left with the option to delete files from `Trash` by rightclick.

[ Other Info ]

 * This has been merged upstream with
https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1633 .

 * This patch/fix is already present in plucky and newer.

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

-- 
trash banner active 'Empty Trash' button
https://bugs.launchpad.net/bugs/2130347
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2125145 at bugs.launchpad.net  Thu Oct 30 18:11:35 2025
From: 2125145 at bugs.launchpad.net (Bryan Fraschetti)
Date: Thu, 30 Oct 2025 18:11:35 -0000
Subject: [Bug 2125145] Re: [SRU] Makedumpfile: Errors and Page Exclusions When
 Opening Kernel Crashdump Files Generated on the Latest HWE Kernel
References: <175821630447.1842424.14764010785335167964.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176184789558.1003763.14862637027322348689.malone@juju-98d295-prod-launchpad-4>

Thanks Dariusz for fixing the missing colon typo and pointing me to
update-maintainer tool

Also thanks Andreas for taking a look. I agree that it doesn't make
sense to accept the makedumpfile upload into -proposed until the
corresponding crash changes are also accepted on Noble through Resolute.
The patched crash and makedumpfile should be tested together otherwise
reading the dumpfile is only partially functional and the broken
features vary across architectures.

It looks like crash has landed in Resolute:
https://launchpad.net/ubuntu/resolute/+source/crash

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

Title:
  [SRU] Makedumpfile: Errors and Page Exclusions When Opening Kernel
  Crashdump Files Generated on the Latest HWE Kernel

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in crash source package in Noble:
  New
Status in makedumpfile source package in Noble:
  New
Status in crash source package in Plucky:
  New
Status in makedumpfile source package in Plucky:
  Fix Released
Status in crash source package in Questing:
  New
Status in makedumpfile source package in Questing:
  Fix Released
Status in crash source package in Resolute:
  Confirmed
Status in makedumpfile source package in Resolute:
  Fix Released

Bug description:
  Note: Original description is at the bottom of this report

  [Impact]

  The current versions of Makedumpfile and Crash in the -updates pocket
  on Noble do not support the latest hardware enablement kernel for that
  platform, which is 6.14. There are several architecture-dependent and
  kernel flavor-dependent behaviours that I will outline below, but the
  steps to reproduce are the same.

  Reproducer steps:
  -----------------

  Boot into a hardware enablement kernel. For example, on arm64 use the
  6.14.0-1008-nvidia-64k kernel:

  KERNEL_VERSION=6.14.0-1008-nvidia-64k
  DISTRO=noble

  sudo apt update
  sudo apt install ubuntu-dbgsym-keyring
  echo "deb http://ddebs.ubuntu.com ${DISTRO} main restricted universe multiverse
  deb http://ddebs.ubuntu.com ${DISTRO}-updates main restricted universe multiverse | \
    sudo tee /etc/apt/sources.list.d/ddebs.list
  sudo apt update
  sudo apt install linux-image-${KERNEL_VERSION}
  sudo apt install linux-image-unsigned-${KERNEL_VERSION}-dbgsym

  Modify grub's cmdline to specify a crashkernel: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=512M" # Or similar
  sudo update-grub
  sudo apt install kexec-tools kdump-tools crash makedumpfile
  sudo systemctl enable kdump-tools
  sudo systemctl start kdump-tools
  sudo reboot

  echo c | sudo tee /proc/sysrq-trigger

  After the machine recovers,

  crash /usr/lib/debug/boot/<kernel-dbgsym> /var/crash/<dump-dir>/<dump-
  file>

  Results on Arm64
  ----------------

  crash 8.0.4
  Copyright (C) 2002-2022  Red Hat, Inc.
  ...
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  please wait... (gathering task table data)
  crash: page excluded: kernel virtual address: ffff07ffa042d8e0  type: "xa_node.slots[off]"

  Results on amd64
  ----------------

  On an amd64 machine, using a kernel such as linux-
  image-6.14.0-29-generic results in crash failing to open. No error is
  printed but we don't obtain the prompt:

  crash 8.0.4
  ...
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  # Program exits and no prompt is presented

  [Test Plan]

  * Ensure that with the proposed combination of makedumpfile and crash is capable of generating and subsequently opening crashdumps on the HWE and GA kernels available for that platform. Here is the mapping ATOW:
  Noble GA: 6.8
  Noble HWE: 6.14
  Plucky (interim release, no HWE): 6.14
  Questing (interim release, no HWE): 6.17
  Resolute (development): 6.17 (as of Oct. 14th 2025)

  * Ensure all of crash's commands produce the expected output (eg. ps,
  mount, files, vm, vtop, runq, etc.)

  * If bugs are found in generating and reading crashdumps on the HWE
  kernel on other architectures (s390x, etc.), this test plan can be
  expanded to include those.

  [Where Problems Could Occur]
  * Crash and Makedumpfile are designed to be backwards-compatible, so the risk of regression when backporting a commit is low - however, not zero. This is why it will be important to ensure that the proposed combination of Makedumpfile and crash does not break existing environments - eg. the GA kernel

  * The matrix of hardware and kernel versions (including derivative /
  cloud kernels) to test again is extensive. It's possible that the
  commits identified to solve the known problems will not be
  comprehensive. For example, cpu architectures and kernels not in the
  test matrix may require additional commits to be backported.

  [Other Info]

  * Support/SEG are currently having conversations with the kernel team
  about the potential to proactively SRU / MRE the latest upstream crash
  version, and potentially Makedumpfile as well, alongside -hwe kernel
  releases to avoid this sort of regression in the future. Though, we
  understand this would require an SRUExceptionPolicy to be approved and
  published.

  [Investigation and summary of changes]

  We have identified that on the Makedumpfile at least two commits are needed:
  [1] https://github.com/makedumpfile/makedumpfile/commit/985e575253f1c2de8d6876cfe685c68a24ee06e1
  [2] https://github.com/makedumpfile/makedumpfile/commit/bad2a7c4fa75d37a41578441468584963028bdda

  These are patches to compensate for a change in the kernel's mapping
  of memory. Using the patched Makedumpfile helps, but it is not
  sufficient. Including the patches in Makedumpfile (or using the tip of
  upstream master), but opening with the currently distributed crash
  results in the following errors:

  eg. Patched Makedumpfile with crash 8.0.4 on Arm64:
  ---------------------------------------------------
  ...
  WARNING: cannot determine starting stack frame for task ffffd574e21b4800

  WARNING: cannot determine starting stack frame for task
  ffff07ff83296300

  WARNING: cannot determine starting stack frame for task
  ffff07ff83293f80

  WARNING: cannot determine starting stack frame for task
  ffff07ff83a04700

  WARNING: cannot determine starting stack frame for task ffff08010507c400
        KERNEL: /usr/lib/debug/boot/vmlinux-6.14.0-1008-nvidia-64k
      DUMPFILE: /var/crash/patched_mdf/dump.202509191531  [PARTIAL DUMP]
          CPUS: 128 [OFFLINE: 127]
          DATE: Thu Jan  1 00:00:00 UTC 1970
        UPTIME: 00:13:38
  LOAD AVERAGE: 0.12, 0.16, 0.10
         TASKS: 1573
      NODENAME: penguru
       RELEASE: 6.14.0-1008-nvidia-64k
       VERSION: #8-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 26 02:43:53 UTC 2025
       MACHINE: aarch64  (unknown Mhz)
        MEMORY: 63.8 GB
         PANIC: "Kernel panic - not syncing: sysrq triggered crash"
           PID: 7886
       COMMAND: "tee"
          TASK: ffff08010507c400  [THREAD_INFO: ffff08010507c400]
           CPU: 85
         STATE: TASK_RUNNING (PANIC)

  On Amd64
  --------
  Crash still fails to open.

  Therefore, in addition to the above Makedumpfile commits, crash
  requires some patching. With the above two commits to Makedumpfile I
  did a bisect on crash on amd64 and arm64.

  On the amd64 crash side, I have identified that [3] applied in isolation (cherry-picked) is sufficient on amd64
  [3] https://github.com/crash-utility/crash/commit/6752571d8d782d07537a258a1ec8919ebd1308ad

  I have also found that cherry-picking [4] and [5] resolves the issue on arm64 hardware in testflinger (using the machine agent penguru)
  [4] https://github.com/crash-utility/crash/commit/3879e9104826d5ae14a0824ec47ab60056a249a7
  [5] https://github.com/crash-utility/crash/commit/968debd0d5979dd9ddca3af0766bad714dbd51e3

  At this point, crash's commands such as mount, files, vm, etc. were
  still broken. To resolve this, [6] and [7] are needed

  [6] https://github.com/crash-utility/crash/commit/3d60d9d40457239683a5f20b01437db94f964fb8
  [7] https://github.com/crash-utility/crash/commit/2795136a515446b798ebbfa257c97f0ca6ecb8ec

  To SRU for Noble, crash must also be work on Plucky, Questing, and Resolute. The current version of makedumpfile on all of those series was found to be sufficient and so no SRU for makedumpfile is required on those. However for crash:
  * Plucky uses the 6.14 kernel, so no additional commits are needed - in fact due to the newer version available on Plucky, only [7] is needed.
  * Questing uses the 6.17 kernel. No issues other than [7] were observed on arm, but on amd64, an infinite loop while gdb loaded module symbols was observed, This is fixed in [8].
  * Resolute will ship with a newer kernel than 6.17, but as of October 14th, 2025 is currently based on 6.17. Currently the package in Debian unstable, which will autosync to Resolute does not contain the required fixes and so it will also require SRU with [7] and [8] unless superceded by an upstream (Debian) version bump.

  [8] https://github.com/crash-
  utility/crash/commit/e44a9a9d808c83fb846060f65e5aaa9d30b6e2c4

  PPA with all of the packages built (except resolute):
  https://launchpad.net/~bryanfraschetti/+archive/ubuntu/lp2125145

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

  Original Description:
  =====================

  24.04 LTS,
  Linux 6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 14 16:52:50 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  Problem Description:
  crash utility is crashing (error code 1) when attempting to analyze kernel crash dumps.

  Setup kdump & generated kernel panic using “echo 1 >
  /proc/sys/kernel/sysrq” but, crash cannot access it:

  # crash /usr/lib/debug/boot/vmlinux-6.14.0-29-generic
  dump.202509161821

  crash 8.0.4
  Copyright (C) 2002-2022  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2022  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-pc-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
      <http://www.gnu.org/software/gdb/documentation/>.

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...

  # echo $?
  1

  running as root user and file is readable fine:

  $ :/var/crash/202509161821# ls -l
  total 299144
  -rw------- 1 root whoopsie    119627 Sep 16 18:21 dmesg.202509161821
  -rw-r--r-- 1 root whoopsie 306200163 Sep 16 18:21 dump.202509161821

  symbol file is there:

  # ls -l /usr/lib/debug/boot/vmlinux-6.14.0-29-generic*
  -rw-r--r-- 1 root root 450705920 Aug 14 18:02 /usr/lib/debug/boot/vmlinux-6.14.0-29-generic

  tail of strace:

  14:06:20.661240 rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661281 rt_sigaction(SIGINT, {sa_handler=0x5ec383cbceb0, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661322 rt_sigaction(SIGSEGV, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER|SA_NODEFER, sa_restorer=0x7b0841845330}, NULL, 8) = 0 <0.000008>
  14:06:20.661360 write(1, "\n", 1
  )       = 1 <0.000119>
  14:06:20.661579 lseek(3, 10312, SEEK_SET) = 10312 <0.000010>
  14:06:20.661617 read(3, "OSRELEASE=6.14.0-29-generic\nBUIL"..., 3276) = 3276 <0.000011>
  14:06:20.661748 unlink("/var/tmp/ramdump_elf_XXXXXX") = -1 ENOENT (No such file or directory) <0.002921>
  14:06:20.664817 exit_group(1)           = ?
  14:06:20.690105 +++ exited with 1 +++

  full crash strace https://filebin.net/custom-bin/crash.strace.1

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: crash 8.0.4-1ubuntu2
  ProcVersionSignature: Ubuntu 6.14.0-29.29~24.04.1-generic 6.14.8
  Uname: Linux 6.14.0-29-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Sep 18 20:21:26 2025
  InstallationDate: Installed on 2025-09-04 (14 days ago)
  InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: crash
  UpgradeStatus: No upgrade log present (probably fresh install)

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



From 2127792 at bugs.launchpad.net  Thu Oct 30 19:59:37 2025
From: 2127792 at bugs.launchpad.net (Mitchell Augustin)
Date: Thu, 30 Oct 2025 19:59:37 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176185437800.1365663.12124690106565625979.malone@juju-98d295-prod-launchpad-3>

I'm not sure why there's such a long publisher delay with this one, but
it still is not appearing to apt in questing-proposed on any of my
machines. Regardless, I also completed step 6 by installing the deb from
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/49.0-0ubuntu1.1/+build/31444533/+files/gnome-remote-
desktop_49.0-0ubuntu1.1_amd64.deb manually on my older generation nvidia
machine (ASUS ROG Zephryus G15 with Nvidia RTX 3060 (Ampere).)

Based on Alessandro's point in
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-
desktop/+bug/2127792/comments/5, I am going to change step 5 of the test
plan from "Run the same test without a monitor plugged in to the DUT" to
"Run the same test using software rendering, or with the monitor
unplugged (which should have the same impact)", and switch the order (so
that people can do it before chmod'ing the descriptor). This seems more
precisely tuned to the real impact of that part of the test, and will
allow for a less troublesome reproducer for those without physical
hardware access.


With that said, I think we can mark this verified as soon as it starts getting pulled from proposed via apt. (but let me know if we're good to do it now).

** Description changed:

  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.
  
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263
  
  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346
  
  ---------------------------
  SRU Justification:
  
  [ Impact ]
  
   * This is a hardware enablement SRU.
  
   * gnome-remote-desktop, when used alongside NVENC for video streaming,
  simply does not work, because the image is broken.
  
   * With the above, the streaming is fixed.
  
  [ Fix ]
  
   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.
  
  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.
  
  [ Test Plan ]
  
  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)
  
  2. Enable Remote Login from the Gnome Settings on the DUT with a monitor
  plugged in.
  
  3. Install Reminna from Snap (via the edge channel) on your client. This
- version supports NVENC, the .deb does not. On the server, run `sudo
- chmod 666 /dev/dri/renderD128` to enable GPU acceleration with RDP.
+ version supports NVENC, the .deb does not.
  
- 4. Test gnome-remote-desktop with and without the fix. Make sure which
+ 4. On the server with a Blackwell GPU, test gnome-remote-desktop with
+ and without the fix using software rendering, or with the monitor
+ unplugged (which should have the same impact)
+ 
+ 5. On the server with a Blackwell GPU, run `sudo chmod 666
+ /dev/dri/renderD128` to enable GPU acceleration with RDP.
+ 
+ 4. Run the same test, now with GPU acceleration enabled. Make sure which
  backend is in use. This can be checked by running `nvidia-smi dmon` and
  observing an encoder activity >0%. The repro only occurs when the NVENC
  path is used. CPU encoding path or non-H264 streaming is unaffected
  
- 5. Run the same test without a monitor plugged in to the DUT.
- 
- 6. Run the same tests (with and without monitors) on an older GPU
- generation (Maxwell, ideally)
+ 6. Run the same tests (with and without software rendering) on an older
+ GPU generation (Maxwell, ideally)
  
  [ Where problems could occur ]
  
   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap (via the edge channel) on your client.
  This version supports NVENC, the .deb does not.

  4. On the server with a Blackwell GPU, test gnome-remote-desktop with
  and without the fix using software rendering, or with the monitor
  unplugged (which should have the same impact)

  5. On the server with a Blackwell GPU, run `sudo chmod 666
  /dev/dri/renderD128` to enable GPU acceleration with RDP.

  4. Run the same test, now with GPU acceleration enabled. Make sure
  which backend is in use. This can be checked by running `nvidia-smi
  dmon` and observing an encoder activity >0%. The repro only occurs
  when the NVENC path is used. CPU encoding path or non-H264 streaming
  is unaffected

  6. Run the same tests (with and without software rendering) on an
  older GPU generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2130385 at bugs.launchpad.net  Fri Oct 31 00:12:37 2025
From: 2130385 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 31 Oct 2025 00:12:37 -0000
Subject: [Bug 2130385] [NEW] amd64v3: No Contents in the cache with the given
 restrictions
References: <176186252237.1418748.9064343818732088207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176186955744.1751945.8071287559716276553.launchpad@juju-98d295-prod-launchpad-3>

You have been subscribed to a public bug by Heinrich Schuchardt (xypron):

apt-file does not support the amd64v3 architecture variant:

With arch variant disabled in /etc/apt/apt.conf.d/99enable-amd64v3
$ apt-file update
$ apt-file search riscv64-linux-gnu-gcc-15
gcc-15-riscv64-linux-gnu: /usr/bin/riscv64-linux-gnu-gcc-15
gcc-15-riscv64-linux-gnu: /usr/share/man/man1/riscv64-linux-gnu-gcc-15.1.gz

With arch variant enabled in /etc/apt/apt.conf.d/99enable-amd64v3
$ apt-file update
$ apt-file search riscv64-linux-gnu-gcc-15
Finding relevant cache files to search ...E: No Contents in the cache with the given restrictions
--- 
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: Ubuntu 26.04
InstallationDate: Installed on 2025-06-20 (132 days ago)
InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Daily amd64 (20250607)
NonfreeKernelModules: zfs
Package: apt-file 3.3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 6.17.0-6.6-generic 6.17.1
Tags: resolute
Uname: Linux 6.17.0-6-generic x86_64
UpgradeStatus: Upgraded to resolute on 2025-10-30 (0 days ago)
UserGroups: N/A
_MarkForUpload: True

** Affects: apt-file (Ubuntu)
     Importance: Undecided
     Assignee: Heinrich Schuchardt (xypron)
         Status: In Progress


** Tags: apport-collected resolute
-- 
amd64v3: No Contents in the cache with the given restrictions
https://bugs.launchpad.net/bugs/2130385
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


From 2130385 at bugs.launchpad.net  Fri Oct 31 00:12:41 2025
From: 2130385 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Fri, 31 Oct 2025 00:12:41 -0000
Subject: [Bug 2130385] Re: amd64v3: No Contents in the cache with the given
 restrictions
References: <176186252237.1418748.9064343818732088207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176186956244.1757116.14006642072347788335.launchpad@juju-98d295-prod-launchpad-3>

** Changed in: apt-file (Ubuntu)
       Status: In Progress => Confirmed

** Changed in: apt-file (Ubuntu)
     Assignee: Heinrich Schuchardt (xypron) => (unassigned)

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

Title:
  amd64v3: No Contents in the cache with the given restrictions

Status in apt-file package in Ubuntu:
  Confirmed

Bug description:
  apt-file does not support the amd64v3 architecture variant:

  With arch variant disabled in /etc/apt/apt.conf.d/99enable-amd64v3
  $ apt-file update
  $ apt-file search riscv64-linux-gnu-gcc-15
  gcc-15-riscv64-linux-gnu: /usr/bin/riscv64-linux-gnu-gcc-15
  gcc-15-riscv64-linux-gnu: /usr/share/man/man1/riscv64-linux-gnu-gcc-15.1.gz

  With arch variant enabled in /etc/apt/apt.conf.d/99enable-amd64v3
  $ apt-file update
  $ apt-file search riscv64-linux-gnu-gcc-15
  Finding relevant cache files to search ...E: No Contents in the cache with the given restrictions
  --- 
  ProblemType: Bug
  ApportVersion: 2.33.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 26.04
  InstallationDate: Installed on 2025-06-20 (132 days ago)
  InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Daily amd64 (20250607)
  NonfreeKernelModules: zfs
  Package: apt-file 3.3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 6.17.0-6.6-generic 6.17.1
  Tags: resolute
  Uname: Linux 6.17.0-6-generic x86_64
  UpgradeStatus: Upgraded to resolute on 2025-10-30 (0 days ago)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-file/+bug/2130385/+subscriptions



From 2130385 at bugs.launchpad.net  Fri Oct 31 00:23:50 2025
From: 2130385 at bugs.launchpad.net (Heinrich Schuchardt)
Date: Fri, 31 Oct 2025 00:23:50 -0000
Subject: [Bug 2130385] Re: amd64v3: No Contents in the cache with the given
 restrictions
References: <176186252237.1418748.9064343818732088207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176187023041.1767079.388807931097490931.launchpad@juju-98d295-prod-launchpad-3>

** Bug watch added: Debian Bug tracker #1119710
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119710

** Also affects: apt-file via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119710
   Importance: Unknown
       Status: Unknown

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

Title:
  amd64v3: No Contents in the cache with the given restrictions

Status in Apt File:
  Unknown
Status in apt-file package in Ubuntu:
  Confirmed

Bug description:
  apt-file does not support the amd64v3 architecture variant:

  With arch variant disabled in /etc/apt/apt.conf.d/99enable-amd64v3
  $ apt-file update
  $ apt-file search riscv64-linux-gnu-gcc-15
  gcc-15-riscv64-linux-gnu: /usr/bin/riscv64-linux-gnu-gcc-15
  gcc-15-riscv64-linux-gnu: /usr/share/man/man1/riscv64-linux-gnu-gcc-15.1.gz

  With arch variant enabled in /etc/apt/apt.conf.d/99enable-amd64v3
  $ apt-file update
  $ apt-file search riscv64-linux-gnu-gcc-15
  Finding relevant cache files to search ...E: No Contents in the cache with the given restrictions
  --- 
  ProblemType: Bug
  ApportVersion: 2.33.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 26.04
  InstallationDate: Installed on 2025-06-20 (132 days ago)
  InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Daily amd64 (20250607)
  NonfreeKernelModules: zfs
  Package: apt-file 3.3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 6.17.0-6.6-generic 6.17.1
  Tags: resolute
  Uname: Linux 6.17.0-6-generic x86_64
  UpgradeStatus: Upgraded to resolute on 2025-10-30 (0 days ago)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt-file/+bug/2130385/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 31 04:01:51 2025
From: 2127792 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Fri, 31 Oct 2025 04:01:51 -0000
Subject: [Bug 2127792] Autopkgtest regression report
 (gnome-remote-desktop/49.0-0ubuntu1.1)
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <20251031040151.29656FC05A@ubuntu-archive-toolbox.internal>

All autopkgtests for the newly accepted gnome-remote-desktop (49.0-0ubuntu1.1) for questing have finished running.
The following regressions have been reported in tests triggered by the package:

gnome-remote-desktop/49.0-0ubuntu1.1 (amd64, arm64, s390x)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/questing/update_excuses.html#gnome-remote-desktop

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  In Progress
Status in gnome-remote-desktop source package in Plucky:
  In Progress
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap (via the edge channel) on your client.
  This version supports NVENC, the .deb does not.

  4. On the server with a Blackwell GPU, test gnome-remote-desktop with
  and without the fix using software rendering, or with the monitor
  unplugged (which should have the same impact)

  5. On the server with a Blackwell GPU, run `sudo chmod 666
  /dev/dri/renderD128` to enable GPU acceleration with RDP.

  4. Run the same test, now with GPU acceleration enabled. Make sure
  which backend is in use. This can be checked by running `nvidia-smi
  dmon` and observing an encoder activity >0%. The repro only occurs
  when the NVENC path is used. CPU encoding path or non-H264 streaming
  is unaffected

  6. Run the same tests (with and without software rendering) on an
  older GPU generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2130385 at bugs.launchpad.net  Fri Oct 31 08:42:40 2025
From: 2130385 at bugs.launchpad.net (Bug Watch Updater)
Date: Fri, 31 Oct 2025 08:42:40 -0000
Subject: [Bug 2130385] Re: amd64v3: No Contents in the cache with the given
 restrictions
References: <176186252237.1418748.9064343818732088207.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176190016167.1584242.12735887243120001137.launchpad@scripts.lp.internal>

** Changed in: apt-file
       Status: Unknown => New

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

Title:
  amd64v3: No Contents in the cache with the given restrictions

Status in Apt File:
  New
Status in apt-file package in Ubuntu:
  Confirmed

Bug description:
  apt-file does not support the amd64v3 architecture variant:

  With arch variant disabled in /etc/apt/apt.conf.d/99enable-amd64v3
  $ apt-file update
  $ apt-file search riscv64-linux-gnu-gcc-15
  gcc-15-riscv64-linux-gnu: /usr/bin/riscv64-linux-gnu-gcc-15
  gcc-15-riscv64-linux-gnu: /usr/share/man/man1/riscv64-linux-gnu-gcc-15.1.gz

  With arch variant enabled in /etc/apt/apt.conf.d/99enable-amd64v3
  $ apt-file update
  $ apt-file search riscv64-linux-gnu-gcc-15
  Finding relevant cache files to search ...E: No Contents in the cache with the given restrictions
  --- 
  ProblemType: Bug
  ApportVersion: 2.33.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 26.04
  InstallationDate: Installed on 2025-06-20 (132 days ago)
  InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Daily amd64 (20250607)
  NonfreeKernelModules: zfs
  Package: apt-file 3.3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 6.17.0-6.6-generic 6.17.1
  Tags: resolute
  Uname: Linux 6.17.0-6-generic x86_64
  UpgradeStatus: Upgraded to resolute on 2025-10-30 (0 days ago)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt-file/+bug/2130385/+subscriptions



From 2130347 at bugs.launchpad.net  Fri Oct 31 12:33:31 2025
From: 2130347 at bugs.launchpad.net (Mitchell Augustin)
Date: Fri, 31 Oct 2025 12:33:31 -0000
Subject: [Bug 2130347] Re: trash banner active 'Empty Trash' button
References: <176183612155.645418.17670435522354474893.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176191401153.2981135.1103580120507524423.launchpad@juju-98d295-prod-launchpad-3>

** Also affects: nautilus (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Changed in: nautilus (Ubuntu Noble)
       Status: New => In Progress

** Changed in: nautilus (Ubuntu Noble)
     Assignee: (unassigned) => Andreas Glinserer (aglinserer)

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

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

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

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

Title:
  trash banner active 'Empty Trash' button

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Noble:
  In Progress

Bug description:
  [ Impact ]

   * The bug is a confusing banner shown in the `Trash` section in nautilus. The
     banner is active and conveys that files are there to be removed even when
     the trash is empty.

   * Our partner nvidia has reported this bug and sees this as a UX
  problem.

  [ Test Plan ]

   * Visit `Trash` on your system. There you have now two main scenarios:
     - Trash is empty: The banner on top suggests that you can remove files.
  	 Clicking on it triggers a dialog box to confirm. The whole operation does
       nothing.
     - Trash has files in it: Banner shows the option to remove trash and
       clicking on it and confirming does empty the trash. Now you are at the
       `Trash is empty` state.

   * With the patch applied, visiting an empty `Trash` does not show the banner.
     If files are in the trash, the banner becomes active.

  [ Where problems could occur ]

   * If the monitoring of `Trash` does fail, the banner could show up even if not
     intended or being hidden. In the case of it being hidden, users are still
     left with the option to delete files from `Trash` by rightclick.

  [ Other Info ]

   * This has been merged upstream with
  https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1633 .

   * This patch/fix is already present in plucky and newer.

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



From 2120689 at bugs.launchpad.net  Fri Oct 31 12:55:35 2025
From: 2120689 at bugs.launchpad.net (You-Sheng Yang)
Date: Fri, 31 Oct 2025 12:55:35 -0000
Subject: [Bug 2120689] Re: [SRU] Missing DeviceAllow for Intel's linux-lts
 6.12 tree's ipu6-psys
References: <175521695863.3172424.7969664374267313725.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176191533545.2842784.15893383052980960624.malone@juju-98d295-prod-launchpad-7>

@tjaalton, This is about the PSYS device for Intel IPU6/IPU7, and the
in-tree drivers has only ISYS so far. This doesn't affect any
Upstream/Ubuntu kernel.

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

Title:
  [SRU] Missing DeviceAllow for Intel's linux-lts 6.12 tree's ipu6-psys

Status in v4l2-relayd package in Ubuntu:
  In Progress
Status in v4l2-relayd source package in Noble:
  Invalid
Status in v4l2-relayd source package in Plucky:
  Invalid
Status in v4l2-relayd source package in Questing:
  In Progress

Bug description:
  [ SRU Justification ]

  [ Impact ]

  Missing DeviceAllow for Intel's linux-lts 6.12 tree's ipu6-psys. Since
  v4l2-relayd version 0.1.5, systemd DeviceAllow is added to limit
  device accesses for v4l2-relayd. The one added initially was for Intel
  IPU7, and certainly IPU6 is required, too.

  Without that, an error printed in v4l2-relayd's systemd logs:
  ```
  $ systemctl status v4l2-relayd
  ......
  sh[6920]: [10-28 03:49:39.560] CamHAL[ERR] Failed to open PSYS, error: Operation not permitted
  ```

  [ Test Plan ]

  1. Install v4l2-relayd from -proposed pocket.

  2. Try to use webcam with:
     ```
     $ gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! autovideosink
     # Expect video streaming occurs
     ```

  [ Where problems could occur ]

  Trivial. That's the hardware access it needs in order to use the
  webcam function.

  [ Other Info ]

  While this affects only v4l2-relayd >= 0.1.5, nominate only Resolute
  and Questing. For Resolute, the fix has been included in 0.2.0, which
  is being updated in bug 2116722.

  ========== original bug report ==========

  The Intel's Linux LTS tree, which supports IPU6 out-of-the-box, uses
  different character device class causing systemd rule packaged with
  v4l2-relayd unable to access the device.

  https://github.com/intel/linux-intel-
  lts/blob/6.12/linux/drivers/media/pci/intel/ipu6/psys/ipu-psys.c#L63

  I've confirmed adding "DeviceAllow=char-intel-ipu6-psys" fixes IPU6
  support for v4l2-relayd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l2-relayd/+bug/2120689/+subscriptions



From 2130347 at bugs.launchpad.net  Fri Oct 31 14:26:43 2025
From: 2130347 at bugs.launchpad.net (Alessandro Astone)
Date: Fri, 31 Oct 2025 14:26:43 -0000
Subject: [Bug 2130347] Re: trash banner active 'Empty Trash' button
References: <176183612155.645418.17670435522354474893.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176192080427.3558372.4113695184053075169.launchpad@juju-98d295-prod-launchpad-2>

** Changed in: nautilus (Ubuntu Noble)
    Milestone: None => noble-updates

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

Title:
  trash banner active 'Empty Trash' button

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Noble:
  In Progress

Bug description:
  [ Impact ]

   * The bug is a confusing banner shown in the `Trash` section in nautilus. The
     banner is active and conveys that files are there to be removed even when
     the trash is empty.

   * Our partner nvidia has reported this bug and sees this as a UX
  problem.

  [ Test Plan ]

   * Visit `Trash` on your system. There you have now two main scenarios:
     - Trash is empty: The banner on top suggests that you can remove files.
  	 Clicking on it triggers a dialog box to confirm. The whole operation does
       nothing.
     - Trash has files in it: Banner shows the option to remove trash and
       clicking on it and confirming does empty the trash. Now you are at the
       `Trash is empty` state.

   * With the patch applied, visiting an empty `Trash` does not show the banner.
     If files are in the trash, the banner becomes active.

  [ Where problems could occur ]

   * If the monitoring of `Trash` does fail, the banner could show up even if not
     intended or being hidden. In the case of it being hidden, users are still
     left with the option to delete files from `Trash` by rightclick.

  [ Other Info ]

   * This has been merged upstream with
  https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1633 .

   * This patch/fix is already present in plucky and newer.

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



From 2128350 at bugs.launchpad.net  Fri Oct 31 14:53:13 2025
From: 2128350 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 31 Oct 2025 14:53:13 -0000
Subject: [Bug 2128350] Re: Some desktop snaps are no longer visible in the
 apps menu
References: <176062998947.2963269.10879243361967771236.malonedeb@juju-98d295-prod-launchpad-7>
Message-ID: <176192239386.3608456.3548142720448874352.malone@juju-98d295-prod-launchpad-2>

Hello Alessandro, or anyone else affected,

Accepted malcontent into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/malcontent/0.11.1-1ubuntu1.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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 removed: verification-done
** Tags added: verification-needed verification-needed-noble

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

Title:
  Some desktop snaps are no longer visible in the apps menu

Status in malcontent package in Ubuntu:
  Fix Released
Status in malcontent source package in Jammy:
  In Progress
Status in malcontent source package in Noble:
  Fix Committed
Status in malcontent source package in Plucky:
  Fix Committed
Status in malcontent source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  Malcontent is a parental control mechanism implemented in GNOME Shell.
  It supports hiding applications from the application menu.

  Some desktop snaps like telegram-desktop are no longer visible in GNOME Shell when libmalcontent is installed, even without any filters applied. Which snaps are hidden depends on the numbers of command-line arguments they specify in the Exec line. If it's more than 2, then the snap will be hidden.
  For example, telegram-desktop uses:

  Exec=/snap/bin/telegram-desktop -- %U

  Ubuntu ships a patch in malcontent to allow filtering non-flatpak applications too.
  This patch assumed that a desktop snap Exec= line would always follow the format `Exec=env BAMF_DESKTOP_FILE_HINT=foo.desktop /snap/bin/foo arg1 arg2`, so it would interpret the third argument as the absolute binary path.

  That was changed in snapd version 2.72 to remove the
  BAMF_DESKTOP_FILE_HINT environment variable, so the Exec line now
  follows the format `Exec=/snap/bin/foo arg1 arg2`. The third argument
  is no longer the binary's absolute path, and things break.

  Malcontent needs to be adapted to not assume that the snap binary is
  always the third argument.

  [ Test Plan ]

  1. Install the `malcontent` deb package
     -> this is pre-installed on some OEM installs.
  2. Log-out, log-in again.
  3. Install snapd 2.72 or newer, available from the candidate channel:
     `sudo snap refresh snapd --candidate`
  4. Install the `telegram-desktop` snap
  5. Open the GNOME Shell application launcher
  6. Search for Telegram
  7. Verify that the Telegram app is listed.

  [ Where problems could occur ]

  Problems would manifest with applications being incorrectly filtered
  out or not filtered out.

  The patch should make sure that it is future-proof by not assuming the
  position of the binary path in the command-line a-priori.

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



From 2127792 at bugs.launchpad.net  Fri Oct 31 15:03:54 2025
From: 2127792 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 31 Oct 2025 15:03:54 -0000
Subject: [Bug 2127792] Re: Images are corrupted on blackwell GPUs
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176192303478.3114440.14825356938765128005.malone@juju-98d295-prod-launchpad-4>

Hello Antoine, or anyone else affected,

Accepted gnome-remote-desktop into plucky-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/48.0-1ubuntu0.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-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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-remote-desktop (Ubuntu Plucky)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-plucky

** Changed in: gnome-remote-desktop (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-noble

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

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  Fix Committed
Status in gnome-remote-desktop source package in Plucky:
  Fix Committed
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap (via the edge channel) on your client.
  This version supports NVENC, the .deb does not.

  4. On the server with a Blackwell GPU, test gnome-remote-desktop with
  and without the fix using software rendering, or with the monitor
  unplugged (which should have the same impact)

  5. On the server with a Blackwell GPU, run `sudo chmod 666
  /dev/dri/renderD128` to enable GPU acceleration with RDP.

  4. Run the same test, now with GPU acceleration enabled. Make sure
  which backend is in use. This can be checked by running `nvidia-smi
  dmon` and observing an encoder activity >0%. The repro only occurs
  when the NVENC path is used. CPU encoding path or non-H264 streaming
  is unaffected

  6. Run the same tests (with and without software rendering) on an
  older GPU generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127792 at bugs.launchpad.net  Fri Oct 31 15:04:36 2025
From: 2127792 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 31 Oct 2025 15:04:36 -0000
Subject: [Bug 2127792] Please test proposed package
References: <176036370328.3969345.10411964742737576923.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176192307622.3246210.17161446904207100902.malone@juju-98d295-prod-launchpad-3>

Hello Antoine, or anyone else affected,

Accepted gnome-remote-desktop into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/46.3-0ubuntu1.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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2127792

Title:
  Images are corrupted on blackwell GPUs

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Noble:
  Fix Committed
Status in gnome-remote-desktop source package in Plucky:
  Fix Committed
Status in gnome-remote-desktop source package in Questing:
  Fix Committed
Status in gnome-remote-desktop source package in Resolute:
  Fix Released

Bug description:
  There is image distorsion in gnome-remote-desktop when a Blackwell GPU
  is in use and NVENC is responsible for the video streaming.

  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/issues/263

  A fix was just released by nvidia upstream, and also backported to GNOME 48: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/344
  https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/346

  ---------------------------
  SRU Justification:

  [ Impact ]

   * This is a hardware enablement SRU.

   * gnome-remote-desktop, when used alongside NVENC for video
  streaming, simply does not work, because the image is broken.

   * With the above, the streaming is fixed.

  [ Fix ]

   * Nvidia devices never supported `NV_ENC_PARAMS_FRAME_FIELD_MODE_MBAFF`.
  Though the code worked for past, it causes interlaced line artifacts on
  Blackwell GPUs.

  * Using `NV_ENC_PARAMS_FRAME_FIELD_MODE_FRAME` and changing
  `grd-cuda-avc-utils` to produce progressive frames works on
  Blackwell and on older GPU generations.

  [ Test Plan ]

  1. Use a DUT that has a Blackwell GPU
  (https://en.wikipedia.org/wiki/Blackwell_(microarchitecture)#Blackwell_dies)

  2. Enable Remote Login from the Gnome Settings on the DUT with a
  monitor plugged in.

  3. Install Reminna from Snap (via the edge channel) on your client.
  This version supports NVENC, the .deb does not.

  4. On the server with a Blackwell GPU, test gnome-remote-desktop with
  and without the fix using software rendering, or with the monitor
  unplugged (which should have the same impact)

  5. On the server with a Blackwell GPU, run `sudo chmod 666
  /dev/dri/renderD128` to enable GPU acceleration with RDP.

  4. Run the same test, now with GPU acceleration enabled. Make sure
  which backend is in use. This can be checked by running `nvidia-smi
  dmon` and observing an encoder activity >0%. The repro only occurs
  when the NVENC path is used. CPU encoding path or non-H264 streaming
  is unaffected

  6. Run the same tests (with and without software rendering) on an
  older GPU generation (Maxwell, ideally)

  [ Where problems could occur ]

   * Given the nature of the fix, it should not impact non-nvidia machines.
   * Also, the  fix comes from nvidia themsleves, and it's in GNOME 48 and 49 already, so it's pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2127792/+subscriptions



From 2127925 at bugs.launchpad.net  Fri Oct 31 15:45:57 2025
From: 2127925 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 31 Oct 2025 15:45:57 -0000
Subject: [Bug 2127925] Re: "policy: auto-activating connection" never occurs
 on adapter restart for networks where user entered incorrect password before
 correct password
References: <176053406915.105350.7511956944740384426.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176192555760.3318905.18163097045776632927.malone@juju-98d295-prod-launchpad-3>

Hello Antoine, or anyone else affected,

Accepted network-manager into plucky-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.52.0-1ubuntu1.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-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. 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: network-manager (Ubuntu Plucky)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-plucky

** Changed in: network-manager (Ubuntu Noble)
       Status: New => Fix Committed

** Tags added: verification-needed-noble

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

Title:
  "policy: auto-activating connection" never occurs on adapter restart
  for networks where user entered incorrect password before correct
  password

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Noble:
  Fix Committed
Status in network-manager source package in Plucky:
  Fix Committed
Status in network-manager source package in Questing:
  Fix Committed
Status in network-manager source package in Resolute:
  Fix Committed

Bug description:
  This bug was reported upstream:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1812

  And it got fixed with
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2295

  ---------------------------
  SRU Justification:

  [ Impact ]

   * When trying to connect to a wifi network, if one does cancel the
  credential popup, the network is gets an internal in-memory flag
  preventing its auto reconnection. If then the user succeeds to connect
  to it, this flag is not removed. As a result, if the user disable and
  re-enables wifi, the network will not reconnect automatically.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * Whenever the connection succeeds, the autoconnect blocker flag must
  be removed and reset correctly.

  [ Test Plan ]

   * Test network-manager without and with this fix:
  1. Forget all wifi networks
  2. Click on one on the gnome menubar
  3. Cancel the popup without entering credentials
  4. Check NM's logs to see if an autoconnection is attempted. No autoconnection should be attempted at this point.
  5. Click on this same network again, connect successfully.
  6. Disable and re-enable wifi.
  7. See if an automatic reconnection occurs.

  [ Where problems could occur ]

   * Given the nature of the fix (it's one line), I don't see how
  anything could go wrong here, given we properly run the test plan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2127925/+subscriptions



From 2127925 at bugs.launchpad.net  Fri Oct 31 15:46:36 2025
From: 2127925 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 31 Oct 2025 15:46:36 -0000
Subject: [Bug 2127925] Please test proposed package
References: <176053406915.105350.7511956944740384426.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176192559645.3153108.11566688105465034018.malone@juju-98d295-prod-launchpad-7>

Hello Antoine, or anyone else affected,

Accepted network-manager into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.46.0-1ubuntu2.4 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: network-manager (Ubuntu Questing)
       Status: New => Fix Committed

** Tags added: verification-needed-questing

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

Title:
  "policy: auto-activating connection" never occurs on adapter restart
  for networks where user entered incorrect password before correct
  password

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Noble:
  Fix Committed
Status in network-manager source package in Plucky:
  Fix Committed
Status in network-manager source package in Questing:
  Fix Committed
Status in network-manager source package in Resolute:
  Fix Committed

Bug description:
  This bug was reported upstream:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1812

  And it got fixed with
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2295

  ---------------------------
  SRU Justification:

  [ Impact ]

   * When trying to connect to a wifi network, if one does cancel the
  credential popup, the network is gets an internal in-memory flag
  preventing its auto reconnection. If then the user succeeds to connect
  to it, this flag is not removed. As a result, if the user disable and
  re-enables wifi, the network will not reconnect automatically.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * Whenever the connection succeeds, the autoconnect blocker flag must
  be removed and reset correctly.

  [ Test Plan ]

   * Test network-manager without and with this fix:
  1. Forget all wifi networks
  2. Click on one on the gnome menubar
  3. Cancel the popup without entering credentials
  4. Check NM's logs to see if an autoconnection is attempted. No autoconnection should be attempted at this point.
  5. Click on this same network again, connect successfully.
  6. Disable and re-enable wifi.
  7. See if an automatic reconnection occurs.

  [ Where problems could occur ]

   * Given the nature of the fix (it's one line), I don't see how
  anything could go wrong here, given we properly run the test plan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2127925/+subscriptions



From 2127925 at bugs.launchpad.net  Fri Oct 31 15:47:24 2025
From: 2127925 at bugs.launchpad.net (Timo Aaltonen)
Date: Fri, 31 Oct 2025 15:47:24 -0000
Subject: [Bug 2127925] Please test proposed package
References: <176053406915.105350.7511956944740384426.malonedeb@juju-98d295-prod-launchpad-3>
Message-ID: <176192564500.3318760.12513577002458694183.malone@juju-98d295-prod-launchpad-3>

Hello Antoine, or anyone else affected,

Accepted network-manager into questing-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.52.0-1ubuntu3.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-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. 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, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2127925

Title:
  "policy: auto-activating connection" never occurs on adapter restart
  for networks where user entered incorrect password before correct
  password

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Noble:
  Fix Committed
Status in network-manager source package in Plucky:
  Fix Committed
Status in network-manager source package in Questing:
  Fix Committed
Status in network-manager source package in Resolute:
  Fix Committed

Bug description:
  This bug was reported upstream:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1812

  And it got fixed with
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2295

  ---------------------------
  SRU Justification:

  [ Impact ]

   * When trying to connect to a wifi network, if one does cancel the
  credential popup, the network is gets an internal in-memory flag
  preventing its auto reconnection. If then the user succeeds to connect
  to it, this flag is not removed. As a result, if the user disable and
  re-enables wifi, the network will not reconnect automatically.

   * With the above, the reconnection is fixed.

  [ Fix ]

   * Whenever the connection succeeds, the autoconnect blocker flag must
  be removed and reset correctly.

  [ Test Plan ]

   * Test network-manager without and with this fix:
  1. Forget all wifi networks
  2. Click on one on the gnome menubar
  3. Cancel the popup without entering credentials
  4. Check NM's logs to see if an autoconnection is attempted. No autoconnection should be attempted at this point.
  5. Click on this same network again, connect successfully.
  6. Disable and re-enable wifi.
  7. See if an automatic reconnection occurs.

  [ Where problems could occur ]

   * Given the nature of the fix (it's one line), I don't see how
  anything could go wrong here, given we properly run the test plan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2127925/+subscriptions



From 2130347 at bugs.launchpad.net  Fri Oct 31 16:37:16 2025
From: 2130347 at bugs.launchpad.net (Alessandro Astone)
Date: Fri, 31 Oct 2025 16:37:16 -0000
Subject: [Bug 2130347] Re: trash banner active 'Empty Trash' button
References: <176183612155.645418.17670435522354474893.malonedeb@juju-98d295-prod-launchpad-4>
Message-ID: <176192863754.3246430.4685910085533066476.launchpad@juju-98d295-prod-launchpad-7>

** Changed in: nautilus (Ubuntu Noble)
       Status: In Progress => Fix Committed

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

Title:
  trash banner active 'Empty Trash' button

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

   * The bug is a confusing banner shown in the `Trash` section in nautilus. The
     banner is active and conveys that files are there to be removed even when
     the trash is empty.

   * Our partner nvidia has reported this bug and sees this as a UX
  problem.

  [ Test Plan ]

   * Visit `Trash` on your system. There you have now two main scenarios:
     - Trash is empty: The banner on top suggests that you can remove files.
  	 Clicking on it triggers a dialog box to confirm. The whole operation does
       nothing.
     - Trash has files in it: Banner shows the option to remove trash and
       clicking on it and confirming does empty the trash. Now you are at the
       `Trash is empty` state.

   * With the patch applied, visiting an empty `Trash` does not show the banner.
     If files are in the trash, the banner becomes active.

  [ Where problems could occur ]

   * If the monitoring of `Trash` does fail, the banner could show up even if not
     intended or being hidden. In the case of it being hidden, users are still
     left with the option to delete files from `Trash` by rightclick.

  [ Other Info ]

   * This has been merged upstream with
  https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1633 .

   * This patch/fix is already present in plucky and newer.

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



From 2127243 at bugs.launchpad.net  Fri Oct 31 23:05:14 2025
From: 2127243 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 31 Oct 2025 23:05:14 -0000
Subject: [Bug 2127243] [NEW]  [needs-packaging] spirv-reflect
References: <176008368998.1624766.844184339739748034.malonedeb@juju-98d295-prod-launchpad-2>
Message-ID: <176195191449.237750.13101881272743027116.launchpad@juju-98d295-prod-launchpad-2>

You have been subscribed to a public bug by Antoine Lassagne (antoinelassagne):

URL: https://github.com/KhronosGroup/SPIRV-Reflect
License: Apache-2.0
Notes: SPIRV-Reflect is a lightweight library that provides a C/C++ reflection API for SPIR-V shader bytecode in Vulkan applications.

I wish to package spirv-reflect for Ubuntu.

** Affects: ubuntu
     Importance: Wishlist
         Status: New


** Tags: needs-packaging
-- 
 [needs-packaging] spirv-reflect
https://bugs.launchpad.net/bugs/2127243
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.


