[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
Hello You-Sheng, or anyone else affected, Accepted ipu6-drivers into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ipu6-drivers/0~git202404110253.97c94720-0ubuntu1 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: ipu6-drivers (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 Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-oem-6.8 package in Ubuntu: Triaged Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: Triaged Status in linux-meta-oem-6.8 source package in Noble: Triaged Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060852] Re: nvidia-driver-550-open fails with secure boot enabled
linux-restricted-modules providing 550 is now available, so closing this blocking bug. ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-550 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu. https://bugs.launchpad.net/bugs/2060852 Title: nvidia-driver-550-open fails with secure boot enabled Status in nvidia-graphics-drivers-550 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-550-server package in Ubuntu: Fix Released Bug description: I switched to the 550-open driver to test this out but the module fails to load with secureboot enabled. The key is rejected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nvidia-kernel-source-550-open 550.67-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 13:45:43 2024 Dependencies: InstallationDate: Installed on 2023-04-10 (366 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-550 UpgradeStatus: Upgraded to noble on 2024-04-10 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-12-15T17:01:26.953508 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2060852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060852] Re: nvidia-driver-550-open fails with secure boot enabled
I believe this also applies to 550-open and 550-server, so demoting these also. ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu. https://bugs.launchpad.net/bugs/2060852 Title: nvidia-driver-550-open fails with secure boot enabled Status in nvidia-graphics-drivers-550 package in Ubuntu: New Status in nvidia-graphics-drivers-550-server package in Ubuntu: New Bug description: I switched to the 550-open driver to test this out but the module fails to load with secureboot enabled. The key is rejected. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nvidia-kernel-source-550-open 550.67-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 13:45:43 2024 Dependencies: InstallationDate: Installed on 2023-04-10 (366 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-550 UpgradeStatus: Upgraded to noble on 2024-04-10 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-12-15T17:01:26.953508 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2060852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059001] [NEW] proposed-migration for nvidia-settings 510.47.03-0ubuntu2
Public bug reported: nvidia-settings 510.47.03-0ubuntu2 is built in -proposed but not on armhf. This will not block migration because armhf binaries are being removed from the release pocket, but unless addressed will regress armhf availability of this package in 24.04 LTS. ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: time-t update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/2059001 Title: proposed-migration for nvidia-settings 510.47.03-0ubuntu2 Status in nvidia-settings package in Ubuntu: New Bug description: nvidia-settings 510.47.03-0ubuntu2 is built in -proposed but not on armhf. This will not block migration because armhf binaries are being removed from the release pocket, but unless addressed will regress armhf availability of this package in 24.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/2059001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed
You say "recent kernel or local kernel." What Ubuntu-provided kernel for Ubuntu 22.04 LTS do you see this with? ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057808 Title: [LTS] cryptsetup-initramfs fails when kernel modules are compressed Status in cryptsetup package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cryptsetup source package in Jammy: New Status in linux source package in Jammy: Incomplete Bug description: This is the same cause as the Mantic bug "cryptsetup autopkgtest fails with zstd compressed kernel modules" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120 where hooks/cryptroot::add_modules() needs postfix wildcards after $glob.ko on 2 lines. It affects 22.04 LTS with recent kernel or local kernel built with CONFIG_MODULE_COMPRESS_* I think the fix needs cherry-picking into LTS release(s). https://salsa.debian.org/cryptsetup- team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750 At boot-time it results in the cryptic (pun intended) messages: device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT) device-mapper: ioctl: error adding target to table device-mapper: reload ioctl on luks_os (253:0) failed: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed
It is not clear that this is a behavior change in the kernel that should have been included as part of the hwe backports. cryptsetup may not be the only package affected. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: cryptsetup (Ubuntu) Importance: Undecided => Critical ** Also affects: cryptsetup (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: cryptsetup (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: cryptsetup (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057808 Title: [LTS] cryptsetup-initramfs fails when kernel modules are compressed Status in cryptsetup package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cryptsetup source package in Jammy: New Status in linux source package in Jammy: New Bug description: This is the same cause as the Mantic bug "cryptsetup autopkgtest fails with zstd compressed kernel modules" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120 where hooks/cryptroot::add_modules() needs postfix wildcards after $glob.ko on 2 lines. It affects 22.04 LTS with recent kernel or local kernel built with CONFIG_MODULE_COMPRESS_* I think the fix needs cherry-picking into LTS release(s). https://salsa.debian.org/cryptsetup- team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750 At boot-time it results in the cryptic (pun intended) messages: device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT) device-mapper: ioctl: error adding target to table device-mapper: reload ioctl on luks_os (253:0) failed: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056178] [NEW] Please link linux-perf against libopencsd-dev
Public bug reported: Hello, For Arm platforms it is possible to capture Coresight Trace information with Linux perf. A library libopencsd-dev is then used to decode the coresight trace information. On Debian, we already have perf linking against libopencsd-dev, this was addressed by: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895131 Could we please have a similar change applied to the Ubuntu perf executables? To implement this change one would need to: 1) Add libopencsd-dev to the build-deps, 2) Add CORESIGHT=1 to the make flags for perf. Note that it would be beneficial for all architectures to link against libopencsd-dev (not just arm64) as this would allow users to decode coresight trace information on their local machine. Cheers, -- Steve Capper ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056178 Title: Please link linux-perf against libopencsd-dev Status in linux package in Ubuntu: New Bug description: Hello, For Arm platforms it is possible to capture Coresight Trace information with Linux perf. A library libopencsd-dev is then used to decode the coresight trace information. On Debian, we already have perf linking against libopencsd-dev, this was addressed by: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895131 Could we please have a similar change applied to the Ubuntu perf executables? To implement this change one would need to: 1) Add libopencsd-dev to the build-deps, 2) Add CORESIGHT=1 to the make flags for perf. Note that it would be beneficial for all architectures to link against libopencsd-dev (not just arm64) as this would allow users to decode coresight trace information on their local machine. Cheers, -- Steve Capper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049689] Re: partprobe is broken on empty loopback device
** Summary changed:
- partproke is broken on empty loopback device
+ partprobe is broken on empty loopback device
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
partprobe is broken on empty loopback device
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
SRU Justification:
[Impact]
* BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
but now returns EINVAL, breaking partprobe due to commit
"block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
introduced in mantic 6.5.0-17 and jammy 5.15.0-94.
[Fix]
* backport commit
"block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"
[Test Plan]
* dd if=/dev/zero of=/tmp/foo bs=1M count=50
* partprobe $(losetup --find --show /tmp/foo)
Before the fix this fails.
After the fix it should work.
[Where problems could occur]
* We may see issues on disk partitions operations.
Old description:
This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic
5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
/dev/loop2 have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a
result, the old partition(s) will remain in use. You should reboot
now before making further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to
land soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054439] Re: RM obsolete binaries from noble to allow linux to migrate
this appears to have been done, none of these packages are present in noble or noble-proposed. ** Changed in: linux (Ubuntu Noble) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054439 Title: RM obsolete binaries from noble to allow linux to migrate Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: currently linux is stuck from migrating because of * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04 - splitting the component into single items and retrying them ipu6 / ivsc are curretnly broken and will be re-introduced once fixed. nvidia-440 and nvidia-450 are obsolete and remove from the archive and so is oem-20.04 kernel flavour which stopped being a thing in jammy. Please remove all of those packages from noble & noble-proposed to allow linux to migrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055162] Re: linux-headers package not being pulled in with linux-image-generic
linux-headers-generic is not a dependency of linux-image-generic. It IS a dependency of linux-generic, which is what ubiquity installs. But any mismatches here are likely in the kernel dependencies, not the installer. ** Package changed: ubiquity (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055162 Title: linux-headers package not being pulled in with linux-image-generic Status in linux package in Ubuntu: New Bug description: linux-image-5.15.0-97-generic definitely exists in Ubuntu and it does not pull in the correct linux-header package which is required to rebuilt nvidia kernel modules. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136 Uname: Linux 5.15.0-97-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Feb 27 08:29:48 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2023-06-16 (256 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
** Tags removed: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-450-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-470 source package in Jammy: Invalid Status in nvidia-graphics-drivers-470-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-525 source package in Jammy: Invalid Status in nvidia-graphics-drivers-525-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
I have confirmed that with the 6.5.0-25.25 kernel in mantic-proposed,
shared libraries for 32bit binaries are loaded with some randoness;
specifically, we are back to 7 bits of randomness with this kernel
update:
$ cat /proc/version_signature
Ubuntu 6.5.0-25.25-generic 6.5.13
$ for ((i = 0 ; i < 5; i++ )) ; do ./aslr32 --report libs ; done
0xe8a86e80
0xf4a86e80
0xf2886e80
0xf2a86e80
0xf1686e80
# report the number of distinct values we get:
$ for ((i = 0 ; i < 1; i++ )) ; do ./aslr32 --report libs ; done | sort |
uniq -c | wc -l
129
For reference, on the 6.5.0-17.17 kernel, we had no randomness
whatsoever:
$ cat /proc/version_signature
Ubuntu 6.5.0-17.17-generic 6.5.8
$ for ((i = 0 ; i < 1; i++ )) ; do ./aslr32 --report libs ; done | sort |
uniq -c
1 0xf7c86e80
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Status in QA Regression Testing:
Invalid
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Won't Fix
Status in linux-oem-6.1 source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.1 source package in Mantic:
New
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.1 source package in Noble:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906067] Re: Boot from ISO - exFAT support missing
You've filed a bug in debian against software which is not used in Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-515-server 515.105.01-0ubuntu2 in noble libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-common-510-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-common-510-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-common-510-server 515.105.01-0ubuntu2 in noble armhf libnvidia-common-510-server 515.105.01-0ubuntu2 in noble i386 libnvidia-common-510-server 515.105.01-0ubuntu2 in noble ppc64el libnvidia-common-510-server 515.105.01-0ubuntu2 in noble riscv64 libnvidia-common-510-server 515.105.01-0ubuntu2 in noble s390x libnvidia-common-515-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-common-515-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-common-515-server 515.105.01-0ubuntu2 in noble armhf libnvidia-common-515-server 515.105.01-0ubuntu2 in noble i386 libnvidia-common-515-server 515.105.01-0ubuntu2 in noble ppc64el libnvidia-common-515-server 515.105.01-0ubuntu2 in noble riscv64 libnvidia-common-515-server 515.105.01-0ubuntu2 in noble s390x libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble i386 libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble i386 libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble i386 libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble i386 libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble i386 libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble amd64 libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble arm64 libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble i386 nvidia-compute-utils-510-server 515.105.01-0ubuntu2 in noble amd64 nvidia-compute-utils-510-server 515.105.01-0ubuntu2 in noble arm64 nvidia-dkms-510-server 515.105.01-0ubuntu2 in noble amd64 nvidia-dkms-510-server 515.105.01-0ubuntu2 in noble arm64 nvidia-driver-510-server 515.105.01-0ubuntu2 in noble amd64 nvidia-driver-510-server 515.105.01-0ubuntu2 in noble arm64 nvidia-headless-510-server 515.105.01-0ubuntu2 in noble amd64 nvidia-headless-510-server 515.105.01-0ubuntu2 in noble arm64 nvidia-headless-no-dkms-510-server 515.105.01-0ubuntu2 in noble amd64 nvidia-headless-no-dkms-510-server 515.105.01-0ubuntu2 in noble arm64 nvidia-kernel-common-510-server 515.105.01-0ubuntu2 in noble amd64 nvidia-kernel-common-510-server 515.105.01-0ubuntu2 in noble arm64 nvidia-kernel-source-510-server 515.105.01-0ubuntu2 in noble amd64 nvidia-kernel-source-510-server 515.105.01-0ubuntu2 in noble arm64 nvidia-utils-510-server 515.105.01-0ubuntu2 in noble amd64 nvidia-utils-510-server 515.105.01-0ubuntu2 in noble arm64 xserver-xorg-video-nvidia-510-server 515.105.01-0ubuntu2 in noble amd64 xserver-xorg-video-nvidia-510-server 515.105.01-0ubuntu2 in noble arm64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-515-server (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-460 460.91.03-0ubuntu1 in noble libnvidia-cfg1-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-cfg1-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-common-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-common-450 460.91.03-0ubuntu1 in noble arm64 libnvidia-common-450 460.91.03-0ubuntu1 in noble armhf libnvidia-common-450 460.91.03-0ubuntu1 in noble i386 libnvidia-common-450 460.91.03-0ubuntu1 in noble ppc64el libnvidia-common-450 460.91.03-0ubuntu1 in noble riscv64 libnvidia-common-450 460.91.03-0ubuntu1 in noble s390x libnvidia-common-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-common-455 460.91.03-0ubuntu1 in noble arm64 libnvidia-common-455 460.91.03-0ubuntu1 in noble armhf libnvidia-common-455 460.91.03-0ubuntu1 in noble i386 libnvidia-common-455 460.91.03-0ubuntu1 in noble ppc64el libnvidia-common-455 460.91.03-0ubuntu1 in noble riscv64 libnvidia-common-455 460.91.03-0ubuntu1 in noble s390x libnvidia-common-460 460.91.03-0ubuntu1 in noble amd64 libnvidia-common-460 460.91.03-0ubuntu1 in noble arm64 libnvidia-common-460 460.91.03-0ubuntu1 in noble armhf libnvidia-common-460 460.91.03-0ubuntu1 in noble i386 libnvidia-common-460 460.91.03-0ubuntu1 in noble ppc64el libnvidia-common-460 460.91.03-0ubuntu1 in noble riscv64 libnvidia-common-460 460.91.03-0ubuntu1 in noble s390x libnvidia-compute-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-compute-450 460.91.03-0ubuntu1 in noble i386 libnvidia-compute-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-compute-455 460.91.03-0ubuntu1 in noble i386 libnvidia-decode-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-decode-450 460.91.03-0ubuntu1 in noble i386 libnvidia-decode-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-decode-455 460.91.03-0ubuntu1 in noble i386 libnvidia-encode-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-encode-450 460.91.03-0ubuntu1 in noble i386 libnvidia-encode-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-encode-455 460.91.03-0ubuntu1 in noble i386 libnvidia-extra-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-extra-450 460.91.03-0ubuntu1 in noble i386 libnvidia-extra-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-extra-455 460.91.03-0ubuntu1 in noble i386 libnvidia-fbc1-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-fbc1-450 460.91.03-0ubuntu1 in noble i386 libnvidia-fbc1-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-fbc1-455 460.91.03-0ubuntu1 in noble i386 libnvidia-gl-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-gl-450 460.91.03-0ubuntu1 in noble i386 libnvidia-gl-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-gl-455 460.91.03-0ubuntu1 in noble i386 libnvidia-ifr1-450 460.91.03-0ubuntu1 in noble amd64 libnvidia-ifr1-450 460.91.03-0ubuntu1 in noble i386 libnvidia-ifr1-455 460.91.03-0ubuntu1 in noble amd64 libnvidia-ifr1-455 460.91.03-0ubuntu1 in noble i386 nvidia-compute-utils-450 460.91.03-0ubuntu1 in noble amd64 nvidia-compute-utils-455 460.91.03-0ubuntu1 in noble amd64 nvidia-dkms-450 460.91.03-0ubuntu1 in noble amd64 nvidia-dkms-455 460.91.03-0ubuntu1 in noble amd64 nvidia-driver-450 460.91.03-0ubuntu1 in noble amd64 nvidia-driver-455 460.91.03-0ubuntu1 in noble amd64 nvidia-headless-450 460.91.03-0ubuntu1 in noble amd64 nvidia-headless-455 460.91.03-0ubuntu1 in noble amd64 nvidia-headless-no-dkms-450 460.91.03-0ubuntu1 in noble amd64 nvidia-headless-no-dkms-455 460.91.03-0ubuntu1 in noble amd64 nvidia-kernel-common-450 460.91.03-0ubuntu1 in noble amd64 nvidia-kernel-common-455 460.91.03-0ubuntu1 in noble amd64 nvidia-kernel-source-450 460.91.03-0ubuntu1 in noble amd64 nvidia-kernel-source-455 460.91.03-0ubuntu1 in noble amd64 nvidia-utils-450 460.91.03-0ubuntu1 in noble amd64 nvidia-utils-455 460.91.03-0ubuntu1 in noble amd64 xserver-xorg-video-nvidia-450 460.91.03-0ubuntu1 in noble amd64 xserver-xorg-video-nvidia-455 460.91.03-0ubuntu1 in noble amd64 Comment:
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Same for 515-server: $ reverse-depends src:nvidia-graphics-drivers-515-server Reverse-Depends === * libnvidia-decode-510-server (for libnvidia-decode-515-server) * libnvidia-encode-510-server (for libnvidia-encode-515-server) Packages without architectures listed are reverse-dependencies in: amd64, arm64, i386 $ ** Changed in: nvidia-graphics-drivers-515-server (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
All older source packages listed in this bug report have been removed, and yet: $ reverse-depends src:nvidia-graphics-drivers-460 Reverse-Depends === * libnvidia-decode-455 (for libnvidia-decode-460) * libnvidia-encode-455 (for libnvidia-encode-460) * nvidia-headless-455 [amd64] (for nvidia-headless-460) * nvidia-kernel-common-455 [amd64] Packages without architectures listed are reverse-dependencies in: amd64, i386 $ ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048782] Re: RM obsolete auxiliary packages for removed nvidia server ERD drivers
Removing packages from noble: fabric-manager-515 515.105.01-0ubuntu1 in noble cuda-drivers-fabricmanager-510 515.105.01-0ubuntu1 in noble amd64 nvidia-fabricmanager-510 515.105.01-0ubuntu1 in noble amd64 nvidia-fabricmanager-dev-510 515.105.01-0ubuntu1 in noble amd64 Comment: Auxiliary package for obsolete driver version; LP: #2048782 ** Changed in: fabric-manager-515 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048782] Re: RM obsolete auxiliary packages for removed nvidia server ERD drivers
Removing packages from noble: libnvidia-nscq-515 515.105.01-0ubuntu1 in noble libnvidia-nscq-510 515.105.01-0ubuntu1 in noble amd64 Comment: Auxiliary package for obsolete driver version; LP: #2048782 1 package successfully removed. ** Changed in: libnvidia-nscq-515 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048782] Re: RM obsolete auxiliary packages for removed nvidia server ERD drivers
Removing packages from noble: libnvidia-nscq-510 510.85.02-0ubuntu2 in noble Comment: Auxiliary package for obsolete driver version; LP: #2048782 1 package successfully removed. ** Changed in: libnvidia-nscq-510 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048782] Re: RM obsolete auxiliary packages for removed nvidia server ERD drivers
Removing packages from noble: libnvidia-nscq-460 460.106.00-0ubuntu1 in noble Comment: Auxiliary package for obsolete driver version; LP: #2048782 1 package successfully removed. ** Changed in: libnvidia-nscq-460 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048782] Re: RM obsolete auxiliary packages for removed nvidia server ERD drivers
Removing packages from noble: fabric-manager-450 450.248.02-0ubuntu1 in noble cuda-drivers-fabricmanager-450 450.248.02-0ubuntu1 in noble amd64 nvidia-fabricmanager-450 450.248.02-0ubuntu1 in noble amd64 nvidia-fabricmanager-dev-450 450.248.02-0ubuntu1 in noble amd64 Comment: Auxiliary package for obsolete driver version; LP: #2048782 1 package successfully removed. ** Changed in: fabric-manager-450 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048782] Re: RM obsolete auxiliary packages for removed nvidia server ERD drivers
Removing packages from noble: fabric-manager-510 510.85.02-0ubuntu2 in noble Comment: Auxiliary package for obsolete driver version; LP: #2048782 1 package successfully removed. ** Changed in: fabric-manager-510 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048782] Re: RM obsolete auxiliary packages for removed nvidia server ERD drivers
Removing packages from noble: libnvidia-nscq-450 450.248.02-0ubuntu1 in noble libnvidia-nscq-450 450.248.02-0ubuntu1 in noble amd64 Comment: Auxiliary package for obsolete driver version; LP: #2048782 1 package successfully removed. ** Changed in: libnvidia-nscq-450 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048782] Re: RM obsolete auxiliary packages for removed nvidia server ERD drivers
Removing packages from noble: fabric-manager-460 460.106.00-0ubuntu1 in noble Comment: Auxiliary package for obsolete driver version; LP: #2048782 1 package successfully removed. ** Changed in: fabric-manager-460 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in fabric-manager-510 package in Ubuntu: Fix Released Status in fabric-manager-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-510 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-450 450.119.03-0ubuntu1 in noble libnvidia-cfg1-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-common-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-common-440 450.119.03-0ubuntu1 in noble arm64 libnvidia-common-440 450.119.03-0ubuntu1 in noble armhf libnvidia-common-440 450.119.03-0ubuntu1 in noble i386 libnvidia-common-440 450.119.03-0ubuntu1 in noble ppc64el libnvidia-common-440 450.119.03-0ubuntu1 in noble riscv64 libnvidia-common-440 450.119.03-0ubuntu1 in noble s390x libnvidia-common-450 450.119.03-0ubuntu1 in noble amd64 libnvidia-common-450 450.119.03-0ubuntu1 in noble arm64 libnvidia-common-450 450.119.03-0ubuntu1 in noble armhf libnvidia-common-450 450.119.03-0ubuntu1 in noble i386 libnvidia-common-450 450.119.03-0ubuntu1 in noble ppc64el libnvidia-common-450 450.119.03-0ubuntu1 in noble riscv64 libnvidia-common-450 450.119.03-0ubuntu1 in noble s390x libnvidia-compute-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-compute-440 450.119.03-0ubuntu1 in noble i386 libnvidia-decode-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-decode-440 450.119.03-0ubuntu1 in noble i386 libnvidia-encode-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-encode-440 450.119.03-0ubuntu1 in noble i386 libnvidia-extra-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-extra-440 450.119.03-0ubuntu1 in noble i386 libnvidia-fbc1-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-fbc1-440 450.119.03-0ubuntu1 in noble i386 libnvidia-gl-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-gl-440 450.119.03-0ubuntu1 in noble i386 libnvidia-ifr1-440 450.119.03-0ubuntu1 in noble amd64 libnvidia-ifr1-440 450.119.03-0ubuntu1 in noble i386 nvidia-compute-utils-440 450.119.03-0ubuntu1 in noble amd64 nvidia-dkms-440 450.119.03-0ubuntu1 in noble amd64 nvidia-driver-440 450.119.03-0ubuntu1 in noble amd64 nvidia-headless-440 450.119.03-0ubuntu1 in noble amd64 nvidia-headless-no-dkms-440 450.119.03-0ubuntu1 in noble amd64 nvidia-kernel-common-440 450.119.03-0ubuntu1 in noble amd64 nvidia-kernel-source-440 450.119.03-0ubuntu1 in noble amd64 nvidia-utils-440 450.119.03-0ubuntu1 in noble amd64 xserver-xorg-video-nvidia-440 450.119.03-0ubuntu1 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-440 440.100-0ubuntu1 in noble libnvidia-cfg1-430 440.100-0ubuntu1 in noble amd64 libnvidia-common-430 440.100-0ubuntu1 in noble amd64 libnvidia-common-430 440.100-0ubuntu1 in noble arm64 libnvidia-common-430 440.100-0ubuntu1 in noble armhf libnvidia-common-430 440.100-0ubuntu1 in noble i386 libnvidia-common-430 440.100-0ubuntu1 in noble ppc64el libnvidia-common-430 440.100-0ubuntu1 in noble riscv64 libnvidia-common-430 440.100-0ubuntu1 in noble s390x libnvidia-common-440 440.100-0ubuntu1 in noble amd64 libnvidia-common-440 440.100-0ubuntu1 in noble arm64 libnvidia-common-440 440.100-0ubuntu1 in noble armhf libnvidia-common-440 440.100-0ubuntu1 in noble i386 libnvidia-common-440 440.100-0ubuntu1 in noble ppc64el libnvidia-common-440 440.100-0ubuntu1 in noble riscv64 libnvidia-common-440 440.100-0ubuntu1 in noble s390x libnvidia-compute-430 440.100-0ubuntu1 in noble amd64 libnvidia-compute-430 440.100-0ubuntu1 in noble i386 libnvidia-decode-430 440.100-0ubuntu1 in noble amd64 libnvidia-decode-430 440.100-0ubuntu1 in noble i386 libnvidia-encode-430 440.100-0ubuntu1 in noble amd64 libnvidia-encode-430 440.100-0ubuntu1 in noble i386 libnvidia-fbc1-430 440.100-0ubuntu1 in noble amd64 libnvidia-fbc1-430 440.100-0ubuntu1 in noble i386 libnvidia-gl-430 440.100-0ubuntu1 in noble amd64 libnvidia-gl-430 440.100-0ubuntu1 in noble i386 libnvidia-ifr1-430 440.100-0ubuntu1 in noble amd64 libnvidia-ifr1-430 440.100-0ubuntu1 in noble i386 nvidia-compute-utils-430 440.100-0ubuntu1 in noble amd64 nvidia-dkms-430 440.100-0ubuntu1 in noble amd64 nvidia-driver-430 440.100-0ubuntu1 in noble amd64 nvidia-headless-430 440.100-0ubuntu1 in noble amd64 nvidia-headless-no-dkms-430 440.100-0ubuntu1 in noble amd64 nvidia-kernel-common-430 440.100-0ubuntu1 in noble amd64 nvidia-kernel-source-430 440.100-0ubuntu1 in noble amd64 nvidia-utils-430 440.100-0ubuntu1 in noble amd64 xserver-xorg-video-nvidia-430 440.100-0ubuntu1 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-515 515.105.01-0ubuntu3 in noble Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-530 530.41.03-0ubuntu2 in noble Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
The other packages in this listed are reported by reverse-depends to have non-empty revdeps. However it looks like these all come from other packages that have just been removed. Rather than tracing this manually and possibly making a mistake, I'll let the others sit for another round. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-455 455.45.01-0ubuntu1 in noble libnvidia-cfg1-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-common-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-common-435 455.45.01-0ubuntu1 in noble arm64 libnvidia-common-435 455.45.01-0ubuntu1 in noble armhf libnvidia-common-435 455.45.01-0ubuntu1 in noble i386 libnvidia-common-435 455.45.01-0ubuntu1 in noble ppc64el libnvidia-common-435 455.45.01-0ubuntu1 in noble riscv64 libnvidia-common-435 455.45.01-0ubuntu1 in noble s390x libnvidia-common-455 455.45.01-0ubuntu1 in noble amd64 libnvidia-common-455 455.45.01-0ubuntu1 in noble arm64 libnvidia-common-455 455.45.01-0ubuntu1 in noble armhf libnvidia-common-455 455.45.01-0ubuntu1 in noble i386 libnvidia-common-455 455.45.01-0ubuntu1 in noble ppc64el libnvidia-common-455 455.45.01-0ubuntu1 in noble riscv64 libnvidia-common-455 455.45.01-0ubuntu1 in noble s390x libnvidia-compute-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-compute-435 455.45.01-0ubuntu1 in noble i386 libnvidia-decode-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-decode-435 455.45.01-0ubuntu1 in noble i386 libnvidia-encode-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-encode-435 455.45.01-0ubuntu1 in noble i386 libnvidia-fbc1-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-fbc1-435 455.45.01-0ubuntu1 in noble i386 libnvidia-gl-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-gl-435 455.45.01-0ubuntu1 in noble i386 libnvidia-ifr1-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-ifr1-435 455.45.01-0ubuntu1 in noble i386 nvidia-compute-utils-435 455.45.01-0ubuntu1 in noble amd64 nvidia-dkms-435 455.45.01-0ubuntu1 in noble amd64 nvidia-driver-435 455.45.01-0ubuntu1 in noble amd64 nvidia-headless-435 455.45.01-0ubuntu1 in noble amd64 nvidia-headless-no-dkms-435 455.45.01-0ubuntu1 in noble amd64 nvidia-kernel-common-435 455.45.01-0ubuntu1 in noble amd64 nvidia-kernel-source-435 455.45.01-0ubuntu1 in noble amd64 nvidia-utils-435 455.45.01-0ubuntu1 in noble amd64 xserver-xorg-video-nvidia-435 455.45.01-0ubuntu1 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-510 510.108.03-0ubuntu3 in noble libnvidia-cfg1-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-common-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-common-495 510.108.03-0ubuntu3 in noble arm64 libnvidia-common-495 510.108.03-0ubuntu3 in noble armhf libnvidia-common-495 510.108.03-0ubuntu3 in noble i386 libnvidia-common-495 510.108.03-0ubuntu3 in noble ppc64el libnvidia-common-495 510.108.03-0ubuntu3 in noble riscv64 libnvidia-common-495 510.108.03-0ubuntu3 in noble s390x libnvidia-common-510 510.108.03-0ubuntu3 in noble amd64 libnvidia-common-510 510.108.03-0ubuntu3 in noble arm64 libnvidia-common-510 510.108.03-0ubuntu3 in noble armhf libnvidia-common-510 510.108.03-0ubuntu3 in noble i386 libnvidia-common-510 510.108.03-0ubuntu3 in noble ppc64el libnvidia-common-510 510.108.03-0ubuntu3 in noble riscv64 libnvidia-common-510 510.108.03-0ubuntu3 in noble s390x libnvidia-compute-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-compute-495 510.108.03-0ubuntu3 in noble i386 libnvidia-decode-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-decode-495 510.108.03-0ubuntu3 in noble i386 libnvidia-encode-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-encode-495 510.108.03-0ubuntu3 in noble i386 libnvidia-extra-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-extra-495 510.108.03-0ubuntu3 in noble i386 libnvidia-fbc1-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-fbc1-495 510.108.03-0ubuntu3 in noble i386 libnvidia-gl-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-gl-495 510.108.03-0ubuntu3 in noble i386 nvidia-compute-utils-495 510.108.03-0ubuntu3 in noble amd64 nvidia-dkms-495 510.108.03-0ubuntu3 in noble amd64 nvidia-driver-495 510.108.03-0ubuntu3 in noble amd64 nvidia-headless-495 510.108.03-0ubuntu3 in noble amd64 nvidia-headless-no-dkms-495 510.108.03-0ubuntu3 in noble amd64 nvidia-kernel-common-495 510.108.03-0ubuntu3 in noble amd64 nvidia-kernel-source-495 510.108.03-0ubuntu3 in noble amd64 nvidia-utils-495 510.108.03-0ubuntu3 in noble amd64 xserver-xorg-video-nvidia-495 510.108.03-0ubuntu3 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-435 435.21-0ubuntu8 in noble Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Triaged Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-340 340.108-0ubuntu8 in noble libcuda1-340 340.108-0ubuntu8 in noble amd64 libcuda1-340 340.108-0ubuntu8 in noble armhf nvidia-340 340.108-0ubuntu8 in noble amd64 nvidia-340 340.108-0ubuntu8 in noble armhf nvidia-340-dev 340.108-0ubuntu8 in noble amd64 nvidia-340-dev 340.108-0ubuntu8 in noble armhf nvidia-340-uvm 340.108-0ubuntu8 in noble amd64 nvidia-340-uvm 340.108-0ubuntu8 in noble armhf nvidia-libopencl1-340 340.108-0ubuntu8 in noble amd64 nvidia-opencl-icd-340 340.108-0ubuntu8 in noble amd64 Comment: Unsupported driver version; LP: #2048087 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Triaged Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-430 430.50-0ubuntu3 in noble libnvidia-cfg1-418 430.50-0ubuntu3 in noble amd64 libnvidia-common-418 430.50-0ubuntu3 in noble amd64 libnvidia-common-418 430.50-0ubuntu3 in noble arm64 libnvidia-common-418 430.50-0ubuntu3 in noble armhf libnvidia-common-418 430.50-0ubuntu3 in noble i386 libnvidia-common-418 430.50-0ubuntu3 in noble ppc64el libnvidia-common-418 430.50-0ubuntu3 in noble riscv64 libnvidia-common-418 430.50-0ubuntu3 in noble s390x libnvidia-common-430 430.50-0ubuntu3 in noble amd64 libnvidia-common-430 430.50-0ubuntu3 in noble arm64 libnvidia-common-430 430.50-0ubuntu3 in noble armhf libnvidia-common-430 430.50-0ubuntu3 in noble i386 libnvidia-common-430 430.50-0ubuntu3 in noble ppc64el libnvidia-common-430 430.50-0ubuntu3 in noble riscv64 libnvidia-common-430 430.50-0ubuntu3 in noble s390x libnvidia-compute-418 430.50-0ubuntu3 in noble amd64 libnvidia-compute-418 430.50-0ubuntu3 in noble i386 libnvidia-decode-418 430.50-0ubuntu3 in noble amd64 libnvidia-decode-418 430.50-0ubuntu3 in noble i386 libnvidia-encode-418 430.50-0ubuntu3 in noble amd64 libnvidia-encode-418 430.50-0ubuntu3 in noble i386 libnvidia-fbc1-418 430.50-0ubuntu3 in noble amd64 libnvidia-fbc1-418 430.50-0ubuntu3 in noble i386 libnvidia-gl-418 430.50-0ubuntu3 in noble amd64 libnvidia-gl-418 430.50-0ubuntu3 in noble i386 libnvidia-ifr1-418 430.50-0ubuntu3 in noble amd64 libnvidia-ifr1-418 430.50-0ubuntu3 in noble i386 nvidia-compute-utils-418 430.50-0ubuntu3 in noble amd64 nvidia-dkms-418 430.50-0ubuntu3 in noble amd64 nvidia-driver-418 430.50-0ubuntu3 in noble amd64 nvidia-headless-418 430.50-0ubuntu3 in noble amd64 nvidia-headless-no-dkms-418 430.50-0ubuntu3 in noble amd64 nvidia-kernel-common-418 430.50-0ubuntu3 in noble amd64 nvidia-kernel-source-418 430.50-0ubuntu3 in noble amd64 nvidia-utils-418 430.50-0ubuntu3 in noble amd64 xserver-xorg-video-nvidia-418 430.50-0ubuntu3 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Triaged Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2046082] Re: zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Normally, changing a conffile in an SRU is iffy because this may result
in conffile prompts for the user on upgrade, and will cause unattended-
upgrades to hold the package back.
In this case we're fixing a regression in a conffile that was introduced
already in -updates. So, ok.
** Changed in: zfs-linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2046082
Title:
zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[Impact]
* There's a typo in user-visible option (/etc/zfs/zed.d/zed.rc)
ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT introduced upstream
in 2.2.0-rc4 and SRU-ed to Mantic with 2.2.0-0ubuntu1~23.10.
* This could be fixed in Ubuntu before users start adopting it.
[Test Plan]
* Check whether /etc/zfs/zed.d/zed.rc ships the correct option.
* Actual:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
* Expected:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
[Regression Potential]
* Users of Mantic who upgraded to zfs-linux 2.2.0-0ubuntu1~23.10
(published to mantic-updates on 2023-12-08) _and_ enabled the
option (with typo) would have such functionality disabled.
[Other Info]
* This option (with typo) was introduced in commit d19304ffeec5
("zed: Add zedlet to power off slot when drive is faulted"),
and is present in:
- ZFS 2.2: zfs-2.2.0-rc4 (mantic-updates)
- ZFS 2.1: zfs-2.1.13
* It affects Ubuntu Noble and Mantic, but not Lunar or older.
* Fixed upstream with commit 3c7650491b9a ("zed: fix typo in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046082] Please test proposed package
Hello Mauricio, or anyone else affected,
Accepted zfs-linux into mantic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.2.0-0ubuntu1~23.10.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-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. 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 Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2046082
Title:
zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[Impact]
* There's a typo in user-visible option (/etc/zfs/zed.d/zed.rc)
ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT introduced upstream
in 2.2.0-rc4 and SRU-ed to Mantic with 2.2.0-0ubuntu1~23.10.
* This could be fixed in Ubuntu before users start adopting it.
[Test Plan]
* Check whether /etc/zfs/zed.d/zed.rc ships the correct option.
* Actual:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
* Expected:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
[Regression Potential]
* Users of Mantic who upgraded to zfs-linux 2.2.0-0ubuntu1~23.10
(published to mantic-updates on 2023-12-08) _and_ enabled the
option (with typo) would have such functionality disabled.
[Other Info]
* This option (with typo) was introduced in commit d19304ffeec5
("zed: Add zedlet to power off slot when drive is faulted"),
and is present in:
- ZFS 2.2: zfs-2.2.0-rc4 (mantic-updates)
- ZFS 2.1: zfs-2.1.13
* It affects Ubuntu Noble and Mantic, but not Lunar or older.
* Fixed upstream with commit 3c7650491b9a ("zed: fix typo in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers
The usbio-drivers package that was uploaded to the noble NEW queue has been rejected due to an incorrect debian/copyright. The upstream copyright declarations all indicate that they are GPL 2.0, not GPL 2.0 or any later version. The debian/copyright uses the correct short name for the actual license, but includes "or any later version" text in the body of the license statement, which is incorrect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041800 Title: [needs-packaging] usbio-drivers Status in Ubuntu: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in The Jammy Jellyfish: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in Noble: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice AIC This package provides kernel drivers for MIPI cameras through the Intel IPU6 on Intel MeteoLake platform with Lattice AIC. Upstream URL: https://github.com/intel/usbio-drivers Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms (to request usd-import after created) License: GPL v2 PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2031412. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2041800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
LP: #2048087 has been opened with a superset of removal requests, so marking invalid the tasks here in favor of that separate bug with independent history. ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-460 package in Ubuntu: Invalid Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
I actually agree that we should aim to remove these packages entirely, rather than merely demoting them. I think removal of the server is a clear-cut case. Nobody should need to run a pptp server nowadays on Ubuntu, and if anyone is, forcing them to migrate to a better VPN solution on upgrade (or maintaining their own pptpd without Ubuntu support) is IMHO reasonable. Removing the client, I think, is less clear-cut. If you don't have a pptp server to talk to, then shipping the client is harmless. If you DO have a pptp server to talk to, then the client is essential. Anyone running a PPTP server on Windows these days should upgrade... but dropping the client support from Ubuntu doesn't give the Ubuntu users any more leverage to make their server admin upgrade, it just makes Ubuntu unusable in such an environment. So I think we should remove pptpd from the archive for noble, but that we should propose removal of the clients via discussion with the Debian maintainers. ** Changed in: pptpd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
Removing packages from noble: pptpd 1.4.0-12build2 in noble bcrelay 1.4.0-12build2 in noble amd64 bcrelay 1.4.0-12build2 in noble arm64 bcrelay 1.4.0-12build2 in noble armhf bcrelay 1.4.0-12build2 in noble ppc64el bcrelay 1.4.0-12build2 in noble riscv64 bcrelay 1.4.0-12build2 in noble s390x pptpd 1.4.0-12build2 in noble amd64 pptpd 1.4.0-12build2 in noble arm64 pptpd 1.4.0-12build2 in noble armhf pptpd 1.4.0-12build2 in noble ppc64el pptpd 1.4.0-12build2 in noble riscv64 pptpd 1.4.0-12build2 in noble s390x Comment: server implementation of an obsolete insecure protocol; LP: #2041751 1 package successfully removed. ** Changed in: pptpd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
** Description changed: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. - IPSec OpenVPN Strongswan are much better alternatives. + Current Windows versions natively support IPSec and L2TP as much better + alternatives. + + https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- + configuration#how-to-use-wfp-to-configure-ipsec-policies + + https://learn.microsoft.com/en-US/troubleshoot/windows- + server/networking/configure-l2tp-ipsec-server-behind-nat-t-device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: New Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046116] Re: bluetooth device connected but not recognised as output device
** Tags added: regression-security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
>From the linked page: However, that doesn't mean people don't accept the risks. There are many corporations and individuals using PPTP with full knowledge of these risks. Some use mitigating controls, and some don't. No one has ever run pptp on Linux, as either a client or server, because they thought it was a good protocol. It was used because compatibility was required with the other end. > IPSec OpenVPN Strongswan are much better alternatives. What is the compatibility story for these on Windows? The page you link also says: > Microsoft promote something else. What, specifically, and what is the Linux compatibility story with that "something else"? It should be clear in this removal bug what users should be using instead of pptp as a Windows-compatible VPN. ** Changed in: pptpd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Incomplete Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
Oh. To the question of whether there was a systemd change in this window: yes absolutely, because this is the point at which the riscv64 builders moved from lgw manually-operated qemu with a 20.04 guest image, to bos03 openstack-operated qemu with a 22.04 guest image. Which is also why we've moved from 5.13.0-1019-generic to 5.19.0-1021-generic. But again, it was my understanding that these devices are supposed to be created synchronously WITHOUT the involvement of udev. In fact, we had to make launchpad-buildd changes to make use of these devices at all because udev would NOT set them up for us. So if these are now being set up via udev, that's a significant departure from expectations and it's not clear we even CAN have synchronous behavior given that they would be set up by the host udev and not the udev in the lxd container! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
On Sat, Dec 09, 2023 at 05:13:28PM -, Andy Whitcroft wrote: > Was there any systemd/udev change in this timeframe? As the device > files are very much connected to those. My understanding is that these devices are supposed to be created directly by the kernel on devtmpfs and NOT via udev, which is part of how we expected to fix the earlier races. And systemd did not change in this time frame in any release. If there was a change to the HOST udev in this timeframe causing a regression because a new base image was published that includes a newer udev, we don't have visibility on it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/544490 is a log from a build with a new livecd-rootfs that spits out more debugging info on failure. + sgdisk binary/boot/disk-uefi.ext4 --print Disk binary/boot/disk-uefi.ext4: 9437184 sectors, 4.5 GiB Sector size (logical): 512 bytes Disk identifier (GUID): CD1DD3AE-E4C8-4C5F-BD64-9236C39B9824 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 9437150 Partitions will be aligned on 2-sector boundaries Total free space is 0 sectors (0 bytes) Number Start (sector)End (sector) Size Code Name 1 235520 9437150 4.4 GiB 8300 12 227328 235519 4.0 MiB 8300 CIDATA 13 342081 1024.0 KiB loader1 142082 10239 4.0 MiB loader2 15 10240 227327 106.0 MiB EF00 + mount_image binary/boot/disk-uefi.ext4 1 + trap clean_loops EXIT + backing_img=binary/boot/disk-uefi.ext4 + local rootpart=1 ++ losetup --show -f -P -v binary/boot/disk-uefi.ext4 + loop_device=/dev/loop5 + '[' '!' -b /dev/loop5 ']' + rootfs_dev_mapper=/dev/loop5p1 + '[' '!' -b /dev/loop5p1 ']' + echo '/dev/loop5p1 is not a block device' /dev/loop5p1 is not a block device + ls -l /dev/loop5p1 /dev/loop5p12 brw--- 1 root root 259, 2 Dec 9 04:16 /dev/loop5p1 brw--- 1 root root 259, 3 Dec 9 04:16 /dev/loop5p12 + exit 1 This clearly shows that: - there are 5 partitions on the image being passed to losetup - after losetup exits, /dev/loop5p1 is not present - after this check fails, an ls of /dev/loop5p* shows devices present for two of the partitions - including /dev/loop5p1 that we were looking for in the first place - but not all 5. So this definitely means we have a race after calling losetup -P. Is this the expected behavior from the kernel? How do we make this race-free? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
Hello You-Sheng, or anyone else affected,
Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
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: firmware-sof (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf
[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms
Hello Chris, or anyone else affected, Accepted firmware-sof into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware- sof/2.0-1ubuntu4.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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: firmware-sof (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2044330 Title: Update soundwire topology files for Intel RPL platforms Status in firmware-sof package in Ubuntu: Fix Released Status in firmware-sof source package in Jammy: Fix Committed Status in firmware-sof source package in Mantic: Fix Committed Bug description: [Impact] Old RPL soundwire topology files are found to be muted when doing audio capture on left channel. [Fix] The commit from https://github.com/thesofproject/sof-bin/ is required. * https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d (Update v2.2.8 topology files for Intel RPL platforms) [Test Case] Test audio functions on Dell MayaBay RTL platforms. [Where problems could occur] Most topology files for Intel RPL are updated. Need more confirmation on Intel RPL platforms. [Other info] Lunar is skipped, as it'll be EOL soon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2044330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
Hello You-Sheng, or anyone else affected,
Accepted firmware-sof into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.2.6-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-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. 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: firmware-sof (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
In Progress
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms
Hello Chris, or anyone else affected, Accepted firmware-sof into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware- sof/2.2.6-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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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: firmware-sof (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2044330 Title: Update soundwire topology files for Intel RPL platforms Status in firmware-sof package in Ubuntu: Fix Released Status in firmware-sof source package in Jammy: In Progress Status in firmware-sof source package in Mantic: Fix Committed Bug description: [Impact] Old RPL soundwire topology files are found to be muted when doing audio capture on left channel. [Fix] The commit from https://github.com/thesofproject/sof-bin/ is required. * https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d (Update v2.2.8 topology files for Intel RPL platforms) [Test Case] Test audio functions on Dell MayaBay RTL platforms. [Where problems could occur] Most topology files for Intel RPL are updated. Need more confirmation on Intel RPL platforms. [Other info] Lunar is skipped, as it'll be EOL soon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2044330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
zfs-linux (2.2.2-0ubuntu1~23.10) mantic; urgency=medium * New upstream release. LP: #2044657 - Address potential data corruption I'm assuming the plan for fixing it on earlier releases does not involve updating to 2.2.2. And this does not fall under a hardware enablement exception. AND there are packaging changes under debian/. The diff for this new upstream release is 9kloc. I would expect a cherry-picked fix here for mantic, not a full upstream backport - just as will be required for releases prior to mantic. ** Changed in: zfs-linux (Ubuntu Mantic) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Committed Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
Failing build had kernel Kernel version: Linux bos03-riscv64-014 5.19.0-1021-generic #23~22.04.1-Ubuntu SMP Thu Jun 22 12:49:35 UTC 2023 riscv64 The build immediately before the first failure had kernel Kernel version: Linux riscv64-qemu-lgw01-069 5.13.0-1019-generic #21~20.04.1-Ubuntu SMP Thu Mar 24 22:36:01 UTC 2022 riscv64 So maybe this is a kernel regression? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
November 16 was 2 days after livecd-rootfs 24.04.4 landed in the noble release pocket, superseding 24.04.2. The code delta between 24.04.2 and 24.04.4 includes removal of support for "legacy" images (SUBPROJECT=legacy) which doesn't apply here; and some reorganization of code related to "preinstalled" images which could affect the riscv64+generic image, that is a preinstalled image using the cpc project, but there were no code changes touching any of the image partitioning code so it's unclear how those code changes could have introduced this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045586] [NEW] livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
Public bug reported: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Hello You-Sheng, or anyone else affected, Accepted ivsc-driver into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ivsc- driver/0~git202212210258.94ecb88b-0ubuntu0.23.10.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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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: ivsc-driver (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: In Progress Status in ivsc-driver source package in Mantic: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
I'd really recommend not open new bug tasks for further source packages on a bug like this; we clearly aren't going to remove any of those other packages from mantic now... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
Hello Chris, or anyone else affected, Accepted firmware-sof into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware- sof/2.2.4+2.2.6-0ubuntu0.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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. 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: firmware-sof (Ubuntu Lunar) Status: Triaged => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Fix Committed Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11
Hello Chris, or anyone else affected, Accepted firmware-sof into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware- sof/2.2.6-1ubuntu1.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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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: firmware-sof (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038263 Title: Add SoF topology support on Intel RaptorLake DELL SKU 0C11 Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Won't Fix Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support audio functions on RPL Dell SKU 0C11, it requires the topology file from sof-tplg-v2.2.7 [Fix] Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Test Case] Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the audio function. 1. Install the firmware-sof on platform(RPL) Dell SKU 0C11 2. Make sure the audio output/input devices are not dummy in audio settings. [Where problems could occur] New firmware is only for the RPL platforms which requires the specific topology file. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Impact] Audio play/capture are not functional on specific Dell machines of Intel RPL platforms [Fix] Backport the fix from Intel in https://github.com/thesofproject/linux [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy` shown on the Audio output/input option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041741] Re: Fan speed Control not working on RASPERRY PI 5 RUNNING UBUNTU 23.10
** Package changed: ubuntu => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2041741 Title: Fan speed Control not working on RASPERRY PI 5 RUNNING UBUNTU 23.10 Status in linux-raspi package in Ubuntu: New Bug description: The fan speed control when running Ubuntu 23.10 on a Raspberry Pi 5 does not appear to be working. The fan runs at near maximum speed all the time and the cur_state in /sys/class/thermal/cooling_device0/ is stuck at the value of 4 no matter what the CPU temperature. I suspect it is related to this fault reported on Raspberry Pi OS: https://forums.raspberrypi.com/viewtopic.php?t=356881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2041741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Thanks for investigating this, Cascardo. I agree that option 3 is likely
the best path forward, either via changing our kernel config defaults or
adjusting the sysctl defaults via the procps package. For reference the
adjustable sysctl setting is vm.mmap_rnd_compat_bits.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Status in QA Regression Testing:
New
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux source package in Kinetic:
Incomplete
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039379] Re: boot issue, rollout 1.8 to Lunar or remove 1.7
*** This bug is a duplicate of bug 2038745 *** https://bugs.launchpad.net/bugs/2038745 Thank you for highlighting this. I have released the update now to lunar as well. Marking this as a duplicate of LP: #2038745. ** This bug has been marked a duplicate of bug 2038745 NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2039379 Title: boot issue, rollout 1.8 to Lunar or remove 1.7 Status in linux-firmware package in Ubuntu: New Bug description: I pulled updates very early this morning (Oct 15) and system was no longer booting. Turns out linux-firmware 1.7 (Oct 9) fails to boot on RX 7900 series: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745 Fixed with linux-firmware 1.8 (Oct 10) and deployed to Jammy (Oct 12) but it is Oct 15th and Lunar -updates is still serving 1.7, a broken package that breaks boot for users??? How is this not critical? Fixed by booting into recovery and manually applying the linux- firmware 1.8 deb in -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
This has been marked as fixed in mantic, but this bug does not say what the plan is for lunar, which is still the supported upgrade path from jammy. ** Changed in: gdm3 (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Incomplete Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031302] Re: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)
Paolo's merge request has been applied in qa-regression-testing, thanks! ** Changed in: qa-regression-testing Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031302 Title: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore) Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: New Bug description: This test requires HARDENED_USERCOPY to be unset. Test log: Running 'python3 ./test-kernel-security.py -v KernelSecurityConfigTest.test_290_config_hardened_usercopy' Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: '6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest) Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY depends on the allocator and strict devmem) FAIL == FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest) Ensure CONFIG_HARDENED_USERCOPY is set -- Traceback (most recent call last): File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 2724, in test_290_config_hardened_usercopy self.assertKernelConfigUnset(config_name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 223, in assertKernelConfigUnset self.assertFalse(self._test_config(name), AssertionError: True is not false : HARDENED_USERCOPY option was expected to be unset in the kernel config -- Ran 1 test in 0.007s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
The firmware-sof upload in lunar-proposed contains a sha256sum.txt with the checksums of all the firmware. But every line of this file is different from every line in the previous version, because the version number is encoded. Likewise, the file paths within the package encode the version. This makes it very difficult to review this package using a debdiff. Can you suggest a method of reviewing the package that confirms we have only firmware file additions here, and not changes to existing firmware files that could cause a regression? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
** Description changed: - SRU Jusitification for firmware-sof + SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038292] Re: nvidia-graphics-drivers-535{, -server} lower than in lunar & jammy
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2038292
Title:
nvidia-graphics-drivers-535{,-server} lower than in lunar & jammy
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Invalid
Bug description:
nvidia-graphics-drivers-535 and nvidia-graphics-drivers-535-server are
lower than in lunar
meaning we need to sru 535.113 into mantic, before turning on
upgrades.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2038292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
This does not appear to be a blocker for Ubuntu 23.10; removing the milestone. ** Changed in: linux (Ubuntu Mantic) Milestone: ubuntu-23.10 => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029905 Title: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Bug description: This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
** Changed in: linux-firmware-raspi (Ubuntu Mantic) Milestone: ubuntu-23.10 => mantic-updates ** Changed in: linux-firmware-raspi (Ubuntu Mantic) Milestone: mantic-updates => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1942260 Title: compress firmware in /lib/firmware Status in firmware-sof package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in firmware-sof source package in Mantic: Fix Released Status in initramfs-tools source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware-raspi source package in Mantic: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038292] Re: nvidia-graphics-drivers-535{, -server} lower than in lunar & jammy
My understanding is this will be able to go into the mantic release
pocket with the kernel respin currently in progress, so should not need
to be an SRU.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2038292
Title:
nvidia-graphics-drivers-535{,-server} lower than in lunar & jammy
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Fix Committed
Status in ubuntu-release-upgrader package in Ubuntu:
Invalid
Bug description:
nvidia-graphics-drivers-535 and nvidia-graphics-drivers-535-server are
lower than in lunar
meaning we need to sru 535.113 into mantic, before turning on
upgrades.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2038292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
marking this fix committed for linux, version 6.5.0-9.9 in mantic- proposed should contain the fix. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Removing packages from mantic: nvidia-graphics-drivers-450-server 450.248.02-0ubuntu2 in mantic libnvidia-cfg1-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-cfg1-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic arm64 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic armhf libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic ppc64el libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic riscv64 libnvidia-common-440-server 450.248.02-0ubuntu2 in mantic s390x libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic arm64 libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic armhf libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic ppc64el libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic riscv64 libnvidia-common-450-server 450.248.02-0ubuntu2 in mantic s390x libnvidia-compute-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-compute-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-compute-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-compute-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-decode-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-decode-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-decode-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-decode-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-encode-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-encode-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-encode-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-encode-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-extra-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-extra-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-extra-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-extra-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-fbc1-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-fbc1-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-fbc1-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-fbc1-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-gl-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-gl-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-gl-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-gl-450-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-ifr1-440-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-ifr1-440-server 450.248.02-0ubuntu2 in mantic i386 libnvidia-ifr1-450-server 450.248.02-0ubuntu2 in mantic amd64 libnvidia-ifr1-450-server 450.248.02-0ubuntu2 in mantic i386 nvidia-compute-utils-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-compute-utils-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-dkms-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-dkms-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-driver-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-driver-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-headless-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-headless-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-headless-no-dkms-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-headless-no-dkms-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-kernel-common-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-kernel-common-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-kernel-source-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-kernel-source-450-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-utils-440-server 450.248.02-0ubuntu2 in mantic amd64 nvidia-utils-450-server 450.248.02-0ubuntu2 in mantic amd64 xserver-xorg-video-nvidia-440-server 450.248.02-0ubuntu2 in mantic amd64
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Now: $ reverse-depends src:nvidia-graphics-drivers-450-server Reverse-Depends === * libnvidia-decode-440-server (for libnvidia-decode-450-server) * libnvidia-encode-440-server (for libnvidia-encode-450-server) * libnvidia-fbc1-440-server (for libnvidia-fbc1-450-server) * libnvidia-ifr1-440-server (for libnvidia-ifr1-450-server) Packages without architectures listed are reverse-dependencies in: amd64, i386 $ And these are false-positives because built from this source. (I wonder if the server implementation has trouble parsing the Sources file for this, because the Binary: field is strangely split across lines...) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
418 is clean. $ reverse-depends src:nvidia-graphics-drivers-418-server No reverse dependencies found $ reverse-depends src:nvidia-graphics-drivers-418-server -a source No reverse dependencies found $ Removing packages from mantic: nvidia-graphics-drivers-418-server 418.226.00-0ubuntu5 in mantic libnvidia-cfg1-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic arm64 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic armhf libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic ppc64el libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic riscv64 libnvidia-common-418-server 418.226.00-0ubuntu5 in mantic s390x libnvidia-compute-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-compute-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-decode-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-decode-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-encode-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-encode-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-fbc1-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-fbc1-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-gl-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-gl-418-server 418.226.00-0ubuntu5 in mantic i386 libnvidia-ifr1-418-server 418.226.00-0ubuntu5 in mantic amd64 libnvidia-ifr1-418-server 418.226.00-0ubuntu5 in mantic i386 nvidia-compute-utils-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-dkms-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-driver-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-headless-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-headless-no-dkms-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-kernel-common-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-kernel-source-418-server 418.226.00-0ubuntu5 in mantic amd64 nvidia-utils-418-server 418.226.00-0ubuntu5 in mantic amd64 xserver-xorg-video-nvidia-418-server 418.226.00-0ubuntu5 in mantic amd64 Comment: EOL and obsolete; LP: #2035189 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Removing packages from mantic: nvidia-graphics-drivers-440-server 440.95.01-0ubuntu2 in mantic Comment: EOL, obsolete source package; LP: #2035189 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-440-server (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
The reason for adding bumblebee is that Recommends and alternative Depends on removed packages can cause them to be retained on end user systems after upgrade. Better to remove the references than to try to work out if nvidia would manage to not be affected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Ok, on the correct package reverse-depends now shows: $ reverse-depends src:nvidia-graphics-drivers-450-server Reverse-Depends === * libnvidia-decode-440-server (for libnvidia-decode-450-server) * libnvidia-encode-440-server (for libnvidia-encode-450-server) * libnvidia-fbc1-440-server (for libnvidia-fbc1-450-server) * libnvidia-ifr1-440-server (for libnvidia-ifr1-450-server) * linux-modules-nvidia-450-server-6.5.0-1004-azure [amd64] * linux-modules-nvidia-450-server-6.5.0-1004-gcp [amd64] * linux-modules-nvidia-450-server-6.5.0-1005-aws [amd64] * linux-modules-nvidia-450-server-6.5.0-1005-oracle [amd64] * linux-modules-nvidia-450-server-6.5.0-5-generic [amd64] * linux-modules-nvidia-450-server-6.5.0-5-lowlatency [amd64] * linux-modules-nvidia-450-server-aws [amd64] * linux-modules-nvidia-450-server-azure [amd64] * linux-modules-nvidia-450-server-gcp [amd64] * linux-modules-nvidia-450-server-generic [amd64] * linux-modules-nvidia-450-server-generic-hwe-22.04 [amd64] * linux-modules-nvidia-450-server-generic-hwe-22.04-edge [amd64] * linux-modules-nvidia-450-server-lowlatency [amd64] * linux-modules-nvidia-450-server-lowlatency-hwe-22.04 [amd64] * linux-modules-nvidia-450-server-lowlatency-hwe-22.04-edge [amd64] * linux-modules-nvidia-450-server-oracle [amd64] Packages without architectures listed are reverse-dependencies in: amd64, i386 $ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
$ reverse-depends src:nvidia-graphics-drivers-450 Reverse-Depends === * libnvidia-cfg1-430 [amd64](for libnvidia-cfg1-440) * libnvidia-common-430 (for libnvidia-common-440) * libnvidia-compute-430 [amd64 i386] * libnvidia-decode-430 [amd64 i386] * libnvidia-encode-430 [amd64 i386] * libnvidia-fbc1-430 [amd64 i386] * libnvidia-gl-430 [amd64 i386] * libnvidia-ifr1-430 [amd64 i386] * nvidia-compute-utils-430 [amd64] * nvidia-dkms-430 [amd64] (for nvidia-dkms-440) * nvidia-driver-430 [amd64] (for nvidia-driver-440) * nvidia-headless-430 [amd64] (for nvidia-headless-440) * nvidia-headless-no-dkms-430 [amd64] * nvidia-kernel-common-430 [amd64] * nvidia-kernel-source-430 [amd64] * nvidia-utils-430 [amd64] (for nvidia-utils-440) * xserver-xorg-video-nvidia-430 [amd64] Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ It looks like nvidia-graphics-drivers-430 would also have to be removed first? ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
Removing packages from mantic: nvidia-graphics-drivers-390 390.157-0ubuntu8 in mantic libcuda1-384 390.157-0ubuntu8 in mantic amd64 libnvidia-cfg1-390 390.157-0ubuntu8 in mantic amd64 libnvidia-common-390 390.157-0ubuntu8 in mantic amd64 libnvidia-common-390 390.157-0ubuntu8 in mantic arm64 libnvidia-common-390 390.157-0ubuntu8 in mantic armhf libnvidia-common-390 390.157-0ubuntu8 in mantic i386 libnvidia-common-390 390.157-0ubuntu8 in mantic ppc64el libnvidia-common-390 390.157-0ubuntu8 in mantic riscv64 libnvidia-common-390 390.157-0ubuntu8 in mantic s390x libnvidia-compute-390 390.157-0ubuntu8 in mantic amd64 libnvidia-compute-390 390.157-0ubuntu8 in mantic i386 libnvidia-decode-390 390.157-0ubuntu8 in mantic amd64 libnvidia-decode-390 390.157-0ubuntu8 in mantic i386 libnvidia-encode-390 390.157-0ubuntu8 in mantic amd64 libnvidia-encode-390 390.157-0ubuntu8 in mantic i386 libnvidia-fbc1-390 390.157-0ubuntu8 in mantic amd64 libnvidia-fbc1-390 390.157-0ubuntu8 in mantic i386 libnvidia-gl-390 390.157-0ubuntu8 in mantic amd64 libnvidia-gl-390 390.157-0ubuntu8 in mantic i386 libnvidia-ifr1-390 390.157-0ubuntu8 in mantic amd64 libnvidia-ifr1-390 390.157-0ubuntu8 in mantic i386 nvidia-384 390.157-0ubuntu8 in mantic amd64 nvidia-384-dev 390.157-0ubuntu8 in mantic amd64 nvidia-compute-utils-390 390.157-0ubuntu8 in mantic amd64 nvidia-dkms-390 390.157-0ubuntu8 in mantic amd64 nvidia-driver-390 390.157-0ubuntu8 in mantic amd64 nvidia-headless-390 390.157-0ubuntu8 in mantic amd64 nvidia-headless-no-dkms-390 390.157-0ubuntu8 in mantic amd64 nvidia-kernel-common-390 390.157-0ubuntu8 in mantic amd64 nvidia-kernel-source-390 390.157-0ubuntu8 in mantic amd64 nvidia-libopencl1-384 390.157-0ubuntu8 in mantic amd64 nvidia-opencl-icd-384 390.157-0ubuntu8 in mantic amd64 nvidia-utils-390 390.157-0ubuntu8 in mantic amd64 xserver-xorg-video-nvidia-390 390.157-0ubuntu8 in mantic amd64 Comment: EOL and obsolete; LP: #2035189 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
$ reverse-depends src:nvidia-graphics-drivers-390 Reverse-Depends === * bumblebee-nvidia (for nvidia-driver-390) $ bumblebee should be updated to drop the reference, so that any users who still have this installed don't have it kept installed as a result of this dependency. ** Also affects: bumblebee (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020469] Re: Package ppc64el/s390x signing certs
https://git.launchpad.net/~ubuntu-cdimage/debian- cd/+git/ubuntu/commit/?id=3b282009dc2eda1d450b88699d338b001ad43651 Result confirmed in https://cdimage.ubuntu.com/ubuntu-server/daily- live/20230928.5/mantic-live-server-s390x.list. ** Changed in: ubuntu-cdimage Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2020469 Title: Package ppc64el/s390x signing certs Status in Ubuntu CD Images: Fix Released Status in Ubuntu on IBM z Systems: In Progress Status in linux-signed package in Ubuntu: Fix Committed Status in s390-tools-signed package in Ubuntu: Fix Released Bug description: Package ppc64el/s390x signing certs For ease of using signed boot on opal & sipl platforms, package and expose the signing certificate in .pem format in the .deb packages and on the isos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2020469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Triaged Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Triaged Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
On Wed, Sep 27, 2023 at 11:16:52PM -, Brian Murray wrote: > However, using software-properties-gtk to install the proprietary driver > (broadcom-sta-dkms) worked and the b43 driver was blacklisted and I was > able to connect to a wireless network. Does this mean the driver was not offered to you automatically through ubuntu-drivers-common? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036951] Re: unblock request: please migrate dkms from proposed
it's in the release pocket now. ** Changed in: dkms (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2036951 Title: unblock request: please migrate dkms from proposed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Mantic: Fix Released Bug description: Kernels now use zstd compressed modules. dkms autopkgtest was not expecting that correctly. autopkgtest was adjusted, and uploaded to proposed but did not migrate prior to feature freeze. Please unblock dkms to migrate, to resolve all ongoing dkms failures. The upload in question is https://launchpad.net/ubuntu/+source/dkms/3.0.11-1ubuntu10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2036951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037305] Re: installed nvidia-kernel-common-535 package post-installation script subprocess returned error exit status 1
** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided => Critical ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Mantic) Importance: Critical Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2037305 Title: installed nvidia-kernel-common-535 package post-installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535 source package in Mantic: New Bug description: Installing nvidia-driver-535 in a minimal schroot environment fails: ``` $ schroot-wrapper -p linux-headers-generic,linux-image-generic,initramfs-tools,zstd,xserver-xorg-core -c mantic -u root (mantic)root@host:~# apt-get install --no-install-recommends nvidia-driver-535 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: cpp-12 dkms gcc-12 gcc-12-base libgcc-12-dev libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 libnvidia-decode-535 libnvidia-encode-535 libnvidia-extra-535 libnvidia-fbc1-535 libnvidia-gl-535 lsb-release nvidia-compute-utils-535 nvidia-dkms-535 nvidia-firmware-535-535.104.05 nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535 xserver-xorg-video-nvidia-535 Suggested packages: gcc-12-locales cpp-12-doc menu gcc-12-multilib gcc-12-doc Recommended packages: sudo nvidia-settings nvidia-prime libnvidia-compute-535:i386 libnvidia-decode-535:i386 libnvidia-encode-535:i386 libnvidia-fbc1-535:i386 libnvidia-gl-535:i386 The following NEW packages will be installed: cpp-12 dkms gcc-12 gcc-12-base libgcc-12-dev libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 libnvidia-decode-535 libnvidia-encode-535 libnvidia-extra-535 libnvidia-fbc1-535 libnvidia-gl-535 lsb-release nvidia-compute-utils-535 nvidia-dkms-535 nvidia-driver-535 nvidia-firmware-535-535.104.05 nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535 xserver-xorg-video-nvidia-535 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. Need to get 359 MB of archives. After this operation, 924 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 lsb-release all 12.0-2 [6564 B] Get:2 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 gcc-12-base amd64 12.3.0-9ubuntu1 [43.5 kB] Get:3 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 cpp-12 amd64 12.3.0-9ubuntu1 [10.7 MB] Get:4 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 libgcc-12-dev amd64 12.3.0-9ubuntu1 [2574 kB] Get:5 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 gcc-12 amd64 12.3.0-9ubuntu1 [21.6 MB] Get:6 http://de.archive.ubuntu.com/ubuntu mantic/main amd64 dkms all 3.0.11-1ubuntu10 [51.3 kB] Get:7 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-cfg1-535 amd64 535.104.05-0ubuntu4 [108 kB] Get:8 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-common-535 all 535.104.05-0ubuntu4 [15.4 kB] Get:9 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-compute-535 amd64 535.104.05-0ubuntu4 [40.2 MB] Get:10 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-decode-535 amd64 535.104.05-0ubuntu4 [1886 kB] Get:11 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-encode-535 amd64 535.104.05-0ubuntu4 [97.4 kB] Get:12 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-extra-535 amd64 535.104.05-0ubuntu4 [72.0 kB] Get:13 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-fbc1-535 amd64 535.104.05-0ubuntu4 [55.6 kB] Get:14 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 libnvidia-gl-535 amd64 535.104.05-0ubuntu4 [194 MB] Get:15 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-compute-utils-535 amd64 535.104.05-0ubuntu4 [122 kB] Get:16 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-kernel-source-535 amd64 535.104.05-0ubuntu4 [45.0 MB] Get:17 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-firmware-535-535.104.05 amd64 535.104.05-0ubuntu4 [39.5 MB] Get:18 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-kernel-common-535 amd64 535.104.05-0ubuntu4 [209 kB] Get:19 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-dkms-535 amd64 535.104.05-0ubuntu4 [35.9 kB] Get:20 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 nvidia-utils-535 amd64 535.104.05-0ubuntu4 [403 kB] Get:21 http://de.archive.ubuntu.com/ubuntu mantic/restricted amd64 xserver-xorg-video-nvidia-535 amd64 535.104.05-0ubuntu4 [1587 kB] Get:22
[Kernel-packages] [Bug 2036287] Re: 6.2.0-32 kernel doesn't work with Asus Vivobook
On Medion Laptop S15549 (similar Hardware) the same problem occurs. After upgrading under Linux Mint 21.2 from kernel 6.2.0-31 to kernel 6.2.0-32 (and now -33) the boot stops right after the Medion picture shows on the screen during boot in very early stage. Details are described here, including some pictures of the screen at boot in kernel 6.2.0-33 secure boot. https://forums.linuxmint.com/viewtopic.php?t=403618 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036287 Title: 6.2.0-32 kernel doesn't work with Asus Vivobook Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: I have both kernel 6.2.0-32 and 6.2.0-26 installed on my Asus Vivobook. Since 6.2.0-32 install boot has been impossible. I think this may be a common problem as I'm seeing issues with Ubuntu: https://ubuntuforums.org/showthread.php?t=2490616 and Linux Mint: https://forums.linuxmint.com/viewtopic.php?t=403618 https://askubuntu.com/questions/1485350/booting-ubuntu-22-with- kernel-6-2-0-32-is-impossible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 20:38:11 2023 InstallationDate: Installed on 2023-01-20 (238 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036951] Re: unblock request: please migrate dkms from proposed
Bug description does not describe a beta-critical issue, only autopkgtest failures. Should be unblocked after Beta is released. ** Changed in: dkms (Ubuntu Mantic) Milestone: ubuntu-23.10-beta => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2036951 Title: unblock request: please migrate dkms from proposed Status in dkms package in Ubuntu: New Status in dkms source package in Mantic: New Bug description: Kernels now use zstd compressed modules. dkms autopkgtest was not expecting that correctly. autopkgtest was adjusted, and uploaded to proposed but did not migrate prior to feature freeze. Please unblock dkms to migrate, to resolve all ongoing dkms failures. The upload in question is https://launchpad.net/ubuntu/+source/dkms/3.0.11-1ubuntu10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2036951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035285] Re: nft cannot load certain rulesets after kernel upgrade
I have prepared an nftables upload for lunar in the ubuntu-security-
proposed ppa https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/ for people to test and confirm that it
addresses the issue; additional work needs to be done for jammy as
naively applying the commits results in an nft that segfaults on the
0041chain_binding_0 testcase.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035285
Title:
nft cannot load certain rulesets after kernel upgrade
Status in linux package in Ubuntu:
Won't Fix
Status in nftables package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in nftables source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in nftables source package in Lunar:
New
Bug description:
[Impact]
After kernel fixes for CVE-2023-4147/CVE-2023-3995 were applied, the kernel
nftables module does not accept certain bogus rules that were built by the nft
tool. A fix for nft was provided to produce rules as now expected by the kernel.
[Test case]
Running nftables testcase 0041chain_binding_0 on linux-5.15.0-83-generic or
linux-6.2.0-32-generic will will show the following error:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
W: [FAILED] ./testcases/chains/0041chain_binding_0: got 1
/dev/stdin:5:25-95: Error: Could not process rule: Operation not supported
ip saddr { 127.0.0.0/8, 172.23.0.0/16,
192.168.13.0/24 } counter accept
^^^
/dev/stdin:6:25-56: Error: Could not process rule: Operation not supported
ip6 saddr ::1/128 counter accept
I: results: [OK] 0 [FAILED] 1 [TOTAL] 1
The expected result is:
ubuntu@jammy2:~/nftables-1.0.2/tests/shell$ sudo NFT=/usr/sbin/nft
./run-tests.sh -g ./testcases/chains/0041chain_binding_0
I: using nft command: /usr/sbin/nft
I: [OK] ./testcases/chains/0041chain_binding_0
I: results: [OK] 1 [FAILED] 0 [TOTAL] 1
Another test case is trying to run nft -f test.nft with the following
contents on test.nft:
#!/usr/sbin/nft -f
flush ruleset
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw;
tcp flags syn jump {
tcp option maxseg size 1-500 counter drop
tcp sport 0 counter drop
}
rt type 0 counter drop
}
}
A broken nft will produce:
./test.nft:10:4-44: Error: Could not process rule: Operation not supported
tcp option maxseg size 1-500 counter drop
^
./test.nft:11:4-27: Error: Could not process rule: Operation not supported
tcp sport 0 counter drop
A fixed nft will produce no output, but a following 'nft list ruleset'
command will show:
table inet filter {
chain PREROUTING_RAW {
type filter hook prerouting priority raw; policy accept;
tcp flags syn jump {
tcp option maxseg size 1-500 counter packets 0 bytes
0 drop
tcp sport 0 counter packets 0 bytes 0 drop
}
rt type 0 counter packets 0 bytes 0 drop
}
}
[Potential regressions]
Users rulesets may fail to load or produce incorrect results, like allowing
or denying certain packages in their firewall, for example.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035285/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Update Released
The verification of the Stable Release Update for glibc 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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2011421 Title: TDX azure instances crash during boot because of glibc bug Status in glibc package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: Won't Fix Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: New Bug description: [IMPACT] Glibc in jammy and kinetic is affected by the following bug : https://sourceware.org/bugzilla/show_bug.cgi?id=29953 When cpuid reports no information on a shared cache, the x86_non_temporal_threshold will be set to zero, causing memcpy/memset to behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates that the minimum value must be 0x4040, but this is not enforced for the default value. The issue was reported because jammy tdx instances are failing to boot (crashing) on azure. The bug has been resolved upstream in https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b [TEST CASE] Test case requires an azure tdx instance. Microsoft has tested a test package with the above commit and confirmed that instances boot successfully. [REGRESSION POTENTIAL] The patches have been accepted upstream. They modify code for x86 architecture, so any potential regression would affect x86. [OTHER] Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953 Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037 In jammy we need 2 commits : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b In kinetic we just need : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2011421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026863] Proposed package upload rejected
An upload of zfs-linux to jammy-proposed has been rejected from the upload queue for the following reason: "no response from uploader to incomplete bug status for >1m". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2026863 Title: zfs-linux SRU build support against hwe kernels Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Incomplete Bug description: [ Impact ] * hwe kernels keep on changing * jammy zfs-linux 2.1.5 upstream releases + cherry-picks is quite old, thus a jump to 2.1.12 or 2.2 has potential to break userspace * Instead cherry-pick patches that continue to enable building zfs-dkms against hwe kernels, if one desires to use dkms from the archive, rather than prebuilt modules that all of Ubuntu kernels ship. * the cherry-picks area gainst config/* code (autoconf/m4) and kernel code (module/ & include/), without any changes to userspace tooling or fixes. [ Test Plan ] * verify zfs-dkms module builds from source against v5.15, v5.19, v6.2, v6.3 kernels on jammy * verify existing zsys installs continue to work * verify kernel team zfs tests-suites continue to work with v5.15 kernel [ Where problems could occur ] * majority of diff is in config macros to detect different compatible kernel APIs and ABIs and use an appropriate one. there are changes to uidmap handling for v6.3 kernels, however it is mostly ignored by userspace without intruducing new feature. LXD will need to be double checked, as it may assume this driver version seems to accept uidmap mount options - which it then ignores. * Note this is still at feature parity with Lunar's upload 2.1.9-2ubuntu1.1, despite having partial kernel driver only build compat with v6.3 - as v6.3 kernels are not expected to land in lunar, and will not land in jammy until after mantic release. Mantic already has much newer 2.2.x series zfs-linux. [ Other Info ] * This is similar to previous zfs-linux SRUs we have performed in the past. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2026863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033923] Re: latest xububtu jammy daily isos fail to install on asus, lenovo & msi
the zfs dependency in question is systemd-udev-settle. Sep 1 17:49:20 xubuntu udevadm[1064]: systemd-udev-settle.service is deprecated. Please fix zfs-load-module.service, zfs-import-cache.service not to pull it in. (heh) Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: start operation timed out. Terminating. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: State 'stop-sigterm' timed out. Killing. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Killing process 1064 (udevadm) with signal SIGKILL. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Processes still around after SIGKILL. Ignoring. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: State 'final-sigterm' timed out. Killing. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Killing process 1064 (udevadm) with signal SIGKILL. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Processes still around after final SIGKILL. Entering failed mode. Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: Failed with result 'timeout'. Opening tasks on systemd and zfsutils-linux, since these packages need to fight it out wrt the "deprecation". And opening a task on the kernel, because a udevadm process that doesn't die with SIGKILL means it's hung in the kernel. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-cdimage Status: New => Invalid ** Summary changed: - latest xububtu jammy daily isos fail to install on asus, lenovo & msi + latest xubuntu jammy daily isos fail to install on asus, lenovo & msi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033923 Title: latest xubuntu jammy daily isos fail to install on asus, lenovo & msi Status in Ubuntu CD Images: Invalid Status in linux-hwe-6.2 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: Hi, I downloaded the latest xubuntu jammy images 20230901 (and previous ones, verified them) On a Mac all went well with a fresh install, however on a Lenovo, Asus, MSI the installer fails... udev startup job hangs and is restarted several times with 3 minutes increments I get several different errors: Dependency failed for Install ZFS kernel module Dependency failed for Import ZFS,... Failing start job without limit! Load Kernel Module efi_pstore Thank you for sorting this out Kind regards Otto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2033923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032963] Re: NBS clean up in focal-proposed for wrong variant
$ rmadison -s focal-proposed linux-ibm-lts-20.04 linux-ibm-lts-20.04 | 5.4.0.1056.85 | focal-proposed | amd64 $ It looks like the last request is superseded: ** Changed in: linux-meta-ibm-5.15 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-ibm-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2032963 Title: NBS clean up in focal-proposed for wrong variant Status in linux-meta-ibm-5.15 package in Ubuntu: Fix Released Bug description: # apt-cache policy linux-ibm-lts-20.04 linux-ibm-lts-20.04: Installed: (none) Candidate: 5.15.0.1035.38~20.04.6 Version table: 5.15.0.1035.38~20.04.6 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 5.4.0.1053.79 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages -lts-20.04 variant was incorrectly added on the linux-meta-ibm-5.15 when it was supposed to be added on linux-meta-ibm package only. this package did not go out of proposed, but we require NBS cleanup removal to roll back linux-ibm-lts-20.04 to 5.4.0. the errours package was already dropped in the 20.04.7 upload of linux-meta-ibm-5.15 which has otherwise migrated. Dear archive admins please drop this binary package: $ ./remove-package -A ubuntu -s focal-proposed -a amd64 --binary -m "NBS cleanup of incorrect variant, which will be moved back to src:linux-meta-ibm" linux-ibm-lts-20.04 -e 5.15.0.1035.38~20.04.6 Removing packages from focal-proposed: linux-ibm-lts-20.04 5.15.0.1035.38~20.04.6 in focal amd64 Comment: NBS cleanup of incorrect variant, which will be moved back to src:linux-meta-ibm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-ibm-5.15/+bug/2032963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
