[Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
*should be changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
I think release upgrader settings changed. To do deb2snap transitions first before upgrade happens. Because during upgrade, packages are inconsistent, and snap hooks must be deffered until they are safe to execute on the system. Note all other deb2snap transitions were always graceful and would attempt transition later if snap configuration fails during upgrade. See old LXD deb2snap .deb logic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: firefox (Ubuntu) Milestone: None => ubuntu-24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055426] [NEW] busybox wget with https crashes
Public bug reported: $ busybox wget https://start.ubuntu.com Floating point exception (core dumped) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: busybox (not installed) ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 29 13:55:07 2024 InstallationDate: Installed on 2024-02-20 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240219) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: busybox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055426 Title: busybox wget with https crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2055426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052967] Re: Provide all available pkcs11 userspace binaries for container consumption
535-server is verified on focal and up; it contains correctly two pkcs11 .so libraries. 535 will be fixed with next new upstream release. ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052967 Title: Provide all available pkcs11 userspace binaries for container consumption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2052967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] Re: no change rebuild to get security update out on riscv64
There was another security upload on 27th of may which is built on all arches, thus this rebuild is no longer needed. please reject cups from focal unapproved. ** Changed in: cups (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: cups (Ubuntu Focal) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] Re: no change rebuild to get security update out on riscv64
Ah - is it that the same version is now built and published in Groovy and we can't safely copy the binary backwards? => correct. I didn't check if we can or cannot safely copy the binary backwards, but imho we should not. This is not going via focal-security, because the security issue has already been fixed on all other arches, and riscv64 currently has best effort security support. I don't want to trigger cups security upgrade for $everyone, just because of the fix missing on riscv64 only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975580] Re: Enable StarFive VisionFive board
** Also affects: linux-riscv (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-riscv (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975580 Title: Enable StarFive VisionFive board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1975580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976287] Re: casper: qemu instances too small during autopkgtest (potential OOM failures)
Although this is autopkgtest change only, it affects testing of kernels, thus it would be nice to publish this SRU without keeping it in -proposed only. ** Changed in: casper (Ubuntu Focal) Status: New => In Progress ** Changed in: casper (Ubuntu Jammy) Status: New => In Progress ** Changed in: casper (Ubuntu Kinetic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976287 Title: casper: qemu instances too small during autopkgtest (potential OOM failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976287] Re: casper: qemu instances too small during autopkgtest (potential OOM failures)
** Merge proposal linked: https://code.launchpad.net/~arighi/casper/+git/casper/+merge/423639 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976287 Title: casper: qemu instances too small during autopkgtest (potential OOM failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642368] Re: linux: Staging modules should be unsigned
Re-fixing this issue again may result in users observing regression - i.e. previously something worked with secureboot which used staging drivers, but now cannot be loaded. For example some of the android related staging drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642368 Title: linux: Staging modules should be unsigned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498862] Re: autopkgtest: rebuild test should not run when testing ourselves
Multiple people in the team now believe the implementation of this fix is buggy and should be revisited. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498862 Title: autopkgtest: rebuild test should not run when testing ourselves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976281] [NEW] snapd autopkgtest tests impossible combination of things
Public bug reported: snapd autopkgtest tests impossible combination of things In debian/tests/integrationtests snapd without reexec is enforced # ensure we always run from the deb that is currently tested export SNAP_REEXEC=0 mkdir -p /etc/systemd/system/snapd.service.d cat < /etc/systemd/system/snapd.service.d/no-reexec.conf [Service] Environment=SNAP_REEXEC=$SNAP_REEXEC EOF systemctl daemon-reload systemctl restart snapd In those tests https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/s/snapd/20220525_161731_b567f@/log.gz installation of core22 is attempted + snap install --edge core22 error: cannot install "core22": snap "core22" assumes unsupported features: snapd2.55.5 (try to refresh snapd) Which now requires snapd 2.55.5 which is not available in stable updates in any releases, maximum is 2.55.3 Please rollback core22 requiring 2.55.5, or ship updates to snapd deb to skip that test case when running with older snapd debs (i.e. make it dependent on 2.55.5+), or please mark snapd autopkgtests of snapd as currently broken in britney & adt-matrix hints. ** Affects: snapd Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: rls-jj-incoming ** Tags added: rls-jj-incoming ** Also affects: snapd Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976281 Title: snapd autopkgtest tests impossible combination of things To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1976281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976248] Re: Revert PPC get_user workaround
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976248 Title: Revert PPC get_user workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976248] [NEW] Revert PPC get_user workaround
Public bug reported: [Impact] * A change of kernel symbol license allows to drop a PPC specific workaround in zfs-dkms to use the regular (better) code paths. * See details in: https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009242 [Test Plan] * linux: apply https://github.com/torvalds/linux/commit/d9e5c3e9e75162f845880535957b7fd0b4637d23 * zfs-dkms: revert https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch * Build on kernel with zfs module on ppc * Ensure that zfs.ko successfully loads and works * Test that root on zfs installations work on ppc (however, Ubuntu currently doesn't provide an installation method to achieve this, so this bit of verification might be hard to complete) [Where problems could occur] * linux: the patch only changes the symbol licensing and the potential tainteness status of the kernel, without any observable user or kernel space impacts * zfs-dkms: The PPC workaround patch is known to be buggy, and the new arch-independent codepath may now use optimized codepaths inside kernel resulting in a different behavior as observed by user-space (operation successful, EFAULT not returned) matching the behavior of all other architectures. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - * A change of kernel symbol license allows to drop a PPC specific + * A change of kernel symbol license allows to drop a PPC specific workaround in zfs-dkms to use the regular (better) code paths. - * See details in: + * See details in: https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009242 - [Test Plan] - * linux: apply https://github.com/torvalds/linux/commit/d9e5c3e9e75162f845880535957b7fd0b4637d23 - - * zfs-dkms: revert https://git.launchpad.net/ubuntu/+source/zfs-linux/tree/debian/patches/4900-ppc-get-user-workaround.patch + * linux: apply + https://github.com/torvalds/linux/commit/d9e5c3e9e75162f845880535957b7fd0b4637d23 - * Build on kernel with zfs module on ppc + * zfs-dkms: revert https://git.launchpad.net/ubuntu/+source/zfs- + linux/tree/debian/patches/4900-ppc-get-user-workaround.patch - * Ensure that zfs.ko successfully loads and works + * Build on kernel with zfs module on ppc - * Test that root on zfs installations work on ppc (however, Ubuntu + * Ensure that zfs.ko successfully loads and works + + * Test that root on zfs installations work on ppc (however, Ubuntu currently doesn't provide an installation method to achieve this, so this bit of verification might be hard to complete) [Where problems could occur] - * The PPC workaround patch is known to be buggy, and the new arch- - independent codepath may now use optimized codepaths inside kernel + * linux: the patch only changes the symbol licensing and the potential + tainteness status of the kernel, without any observable user or kernel + space impacts + + * zfs-dkms: The PPC workaround patch is known to be buggy, and the new + arch-independent codepath may now use optimized codepaths inside kernel resulting in a different behavior as observed by user-space (operation successful, EFAULT not returned) matching the behavior of all other architectures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976248 Title: Revert PPC get_user workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975592] [NEW] Enable Nezha board
Public bug reported: Enable Nezha board Apply relevant patches to linux-riscv-5.17 kernel to enable nezha kernel flavour. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975592 Title: Enable Nezha board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1975592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975580] [NEW] Enable StarFive VisionFive board
Public bug reported: Enable StarFive VisionFive board Apply relevant patches to linux-riscv-5.17 kernel to enable visionfive kernel flavour. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975580 Title: Enable StarFive VisionFive board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1975580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930454] Re: support for .ko.hash signatures or .o -> ko -> detached signatures
Investigating this further .ko signatures are CMS signatures, which are ANS.1 structures. THey are tested, such that SignedData is a wrapper, around DigestedData, which is a wrapper around ContentInfo, which is a warapper around raw binary input. The nice property of DigestedData is that it contains version, hash algo, and digest fields, and the raw binary data is actually optional. Meaning, one can Create CMS ANS.1 DER encoded DigestedData object, with raw binary data discarded. Transfer that to the signing service, which should be able to produce detached signatures. Original desire to make large data optional, is in case the data to be signed is a very large stream / tape, which is impossible or impractical to hold in memory; and yet one still wants to generate signatures for it. None of the existing APIs to work CMS appear to trivially support creating / serializing DigestedData, then deserialize it to sign it and produce detached signatures. Ideally this should be done in DER encoding such that it is platform/architecture independent. I am pondering to add more APIs to OpenSSL or extend some of the available CMS golang or rust libraries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930454 Title: support for .ko.hash signatures or .o -> ko -> detached signatures To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1930454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969482] Re: zfs-2.1.4+ sru
Hi, the verification you have performed is incorrect. You installed kernel and using zfs.ko as built into the kernel, which vendors zfs.ko from release/updates pockets only. To test, zfs.ko from proposed, one has to install the dkms package, build it, enroll MOK (if secureboot is on, and MOK key is not already enrolled), and reboot. ** Tags removed: verification-failed-jammy ** Tags added: verification-needed-jammy ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969482 Title: zfs-2.1.4+ sru To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974056] Re: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-bitwise_0 fails on s390x
** Tags added: rls-kk-incoming ** Description changed: In Ubuntu, we execute the full iptables shell testcases across all architectures. They seem to all pass everywhere, however iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 is currently failing on s390x like so: command17FAIL stderr: W: [FAILED] ././testcases/nft- only/0009-needless-bitwise_0: expected 0 but got 1 i wonder if there is some endian bug, as this is currently Ubuntu's only big-endian architecture. + + this can be reproduced with: + + pull-lp-source iptables + cd iptables-1.8.7/ + chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 + cd iptables/tests/shell + sudo ./run-tests.sh --host -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974056 Title: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 fails on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1974056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974056] [NEW] iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-bitwise_0 fails on s390x
Public bug reported: In Ubuntu, we execute the full iptables shell testcases across all architectures. They seem to all pass everywhere, however iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 is currently failing on s390x like so: command17FAIL stderr: W: [FAILED] ././testcases/nft- only/0009-needless-bitwise_0: expected 0 but got 1 i wonder if there is some endian bug, as this is currently Ubuntu's only big-endian architecture. ** Affects: iptables Importance: Unknown Status: Unknown ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Tags: s390x ** Bug watch added: bugzilla.netfilter.org/ #1606 http://bugzilla.netfilter.org/show_bug.cgi?id=1606 ** Also affects: iptables via http://bugzilla.netfilter.org/show_bug.cgi?id=1606 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974056 Title: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 fails on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1974056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973734] [NEW] FTBFS on riscv64 in focal
Public bug reported: [Impact] * FTBFS on riscv64 in focal in unittest of volume test * Disable that unit test, as later releases do not run unittests on riscv64, and it's better to have up to date pulseaudio on riscv64 (with many security fixes), even if it doesn't completely correctly work. [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * volume-test probably indicates that one can't set volume correctly on riscv64 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973734 Title: FTBFS on riscv64 in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1973734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] [NEW] no change rebuild to get security update out on riscv64
Public bug reported: no change rebuild to get riscv64 build out [Impact] * riscv64 build of cups security update failed, and then succeeded in groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 * do a no change rebuild of cups as an SRU to get updated cups package out on focal [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * As usual, no change rebuilds of packages may introduce miss builds. [Other Info] * currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64. ** Affects: cups (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: cups (Ubuntu Focal) Importance: Undecided Status: In Progress ** Summary changed: - no change rebuild to get riscv64 build out + no change rebuild to get security update out on riscv64 ** Also affects: cups (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Status: New => Fix Released ** Description changed: no change rebuild to get riscv64 build out [Impact] - * riscv64 build of cups security update failed, and then succeeded in groovy - * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 - * do a no change rebuild of cups as an SRU to get updated cups package out on focal + * riscv64 build of cups security update failed, and then succeeded in groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 + * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 + * do a no change rebuild of cups as an SRU to get updated cups package out on focal [Test Plan] - * autopkgtests pass - * riscv64 build is successful + * autopkgtests pass + * riscv64 build is successful [Where problems could occur] - * As usual, no change rebuilds of packages may introduce miss builds. + * As usual, no change rebuilds of packages may introduce miss builds. [Other Info] - - * currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64. + + * currently snap review tooling reports that cups has CVEs on riscv64 + when one builds base:core20 snaps for riscv64. ** Changed in: cups (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
v1 upstream got rejected, submitted v2 now https://lore.kernel.org/linux- bluetooth/20220516103329.516952-1-dimitri.led...@canonical.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973012] [NEW] v4l2loopback.ko should be shipped in modules-extras
Public bug reported: v4l2loopback.ko is shipped in the wrong place it is built after module-inclusion is processed, and installed directly into the linux-modules package however, it depends on modules that are split into modules-extras, thus it should be shipped in the modules-extras package. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - v4l2loopback.ko is shipped in the wrong place + v4l2loopback.ko should be shipped in modules-extras -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973012 Title: v4l2loopback.ko should be shipped in modules-extras To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967721] Re: Laptop never resuming from standby
We were trying to debug this issues with sparkiegeek too, and we have had inconclusive test results. Where the same kernel with/without power attached behaved differently and did/didn't come back from suspend. When testing v5.13 kernel on jammy, could you please confirm that suspend/resume works in both cases 1) power attached and charging 2) power not attached Similarly, when trying to build v5.13/v5.14 kernels with a more recent jammy kernel config we seemed to have been hitting suspend/resume failure more often. So I am hoping that we can figure out the kernel config differences that is causing this behavior regression. It always helps to use fwupdate manager to install all available firmware upgrades. In general, these are likely to have multiple security vulnerability and stability fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967721 Title: Laptop never resuming from standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972899] Re: [Regression] Real-time Kernel Build Failure
Given this is SRU paperwork for Ubuntu linux package, moving the bug report over to Ubuntu linux package where it belongs. ** Project changed: ubuntu-realtime => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972899 Title: [Regression] Real-time Kernel Build Failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] Re: xenial systemd fails to start if unified-only (non-hybrid) cgroup2 is mounted on jammy hosts
I've attempted to prepare naive SRUs and it doesn't get me far yet. The issue is that unified cgroups2 support in xenial's systemd is rudimental, and falls apart very quickly with none of the xenial userspace expecting or able to work correctly with unified cgroups2 setup. I fear that it will not be practical to SRU systemd into xenial to resolve this. And users on Jammy that need to launch xenial containers should continue to switch their systems to hybrid cgroups setup by using `systemd.unified_cgroup_hierarchy=false` kernel command line option on their hosts. ** Summary changed: - xenial systemd fails to start if cgroup2 is mounted + xenial systemd fails to start if unified-only (non-hybrid) cgroup2 is mounted on jammy hosts ** Description changed: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, - so this is fixed already in b and later. + so this is fixed already in b and later. However that patch alone is + insufficient, does not implement hybrid group setup, and breaks a lot of + xenial userspace expectations. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. - - [backported patch] - - the backported patch adds support to mount cgroup2 (new way) in addition - to the old way (cgroup + __DEVEL_ option) and also adds a fallback to do - that when mounting cgroups1 fails (because host is already using non- - hybrid v2 cgroups). This way the default behaviour remains the same, - apart from when trying to boot xenial on latest kernels and userspace - that opts into using cgroups2-only. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if unified-only (non-hybrid) cgroup2 is mounted on jammy hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
Usually we try to avoid using embedded copies of code. Is it at all possible to convert some of the affected packages to use/reuse a shared library instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961427 Title: zlib: compressBound() returns an incorrect result on z15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
Can affected users please try kernel from https://launchpad.net/~xnox/+snap/xnox-pc-kernel/+build/1757817 ? and see if that helps to resolve the issue for them? Static analysis shows that all intel/ibt-* firmware files are now included. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
https://lists.ubuntu.com/archives/kernel-team/2022-May/130086.html in review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
Separately will work on submitting that to our kernels. Separately will work on trying to workaround this bug in our trim- firmware scripts for kernel snaps. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
https://lore.kernel.org/linux- bluetooth/20220509163259.1513242-1-dimitri.led...@canonical.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
drivers/bluetooth/btintel.c only declares
MODULE_AUTHOR("Marcel Holtmann ");
MODULE_DESCRIPTION("Bluetooth support for Intel devices ver " VERSION);
MODULE_VERSION(VERSION);
MODULE_LICENSE("GPL");
MODULE_FIRMWARE("intel/ibt-11-5.sfi");
MODULE_FIRMWARE("intel/ibt-11-5.ddc");
MODULE_FIRMWARE("intel/ibt-12-16.sfi");
MODULE_FIRMWARE("intel/ibt-12-16.ddc");
thus during snap build we strip it, and it doesn't get included in the snap.
i wonder if we should adjust the MODULE_FIRMWARE to mention more things,
or mentioned them with regexp. Such that we don't strip it and include
them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970819
Title:
5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file
intel/ibt-17-16-1.sfi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970819/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971978] Re: Driver binaries fail to load on arm64 through LXD
Separately i'm failing to get even as far as the bug description gets, as i get failures on missing newuidmap binary and what not: $ lxc info --show-log local:evident-oyster Name: evident-oyster Status: STOPPED Type: container Architecture: aarch64 Created: 2022/05/09 15:41 UTC Last Used: 2022/05/09 15:42 UTC Log: lxc evident-oyster 20220509154201.159 WARN conf - conf.c:lxc_map_ids:3592 - newuidmap binary is missing lxc evident-oyster 20220509154201.160 WARN conf - conf.c:lxc_map_ids:3598 - newgidmap binary is missing lxc evident-oyster 20220509154201.165 WARN conf - conf.c:lxc_map_ids:3592 - newuidmap binary is missing lxc evident-oyster 20220509154201.165 WARN conf - conf.c:lxc_map_ids:3598 - newgidmap binary is missing lxc evident-oyster 20220509154201.271 ERRORconf - conf.c:run_buffer:321 - Script exited with status 1 lxc evident-oyster 20220509154201.271 ERRORconf - conf.c:lxc_setup:4400 - Failed to run mount hooks lxc evident-oyster 20220509154201.271 ERRORstart - start.c:do_start:1275 - Failed to setup container "evident-oyster" lxc evident-oyster 20220509154201.271 ERRORsync - sync.c:sync_wait:34 - An error occurred in another process (expected sequence number 4) lxc evident-oyster 20220509154201.278 WARN network - network.c:lxc_delete_network_priv:3617 - Failed to rename interface with index 0 from "eth0" to its initial name "veth9d667e66" lxc evident-oyster 20220509154201.278 ERRORlxccontainer - lxccontainer.c:wait_on_daemonized_start:877 - Received container state "ABORTING" instead of "RUNNING" lxc evident-oyster 20220509154201.278 ERRORstart - start.c:__lxc_start:2074 - Failed to spawn container "evident-oyster" lxc evident-oyster 20220509154201.278 WARN start - start.c:lxc_abort:1039 - No such process - Failed to send SIGKILL via pidfd 17 for process 5868 lxc evident-oyster 20220509154206.359 WARN conf - conf.c:lxc_map_ids:3592 - newuidmap binary is missing lxc evident-oyster 20220509154206.359 WARN conf - conf.c:lxc_map_ids:3598 - newgidmap binary is missing lxc 20220509154206.394 ERRORaf_unix - af_unix.c:lxc_abstract_unix_recv_fds_iov:218 - Connection reset by peer - Failed to receive response lxc 20220509154206.394 ERRORcommands - commands.c:lxc_cmd_rsp_recv_fds:127 - Failed to receive file descriptors for command "get_state" As a precaution, can we double check and compare how different lxd snaps are between x86_64 and aarch64 builds? For example to exclude differences in staged binaries / packages / etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971978 Title: Driver binaries fail to load on arm64 through LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971978] Re: Driver binaries fail to load on arm64 through LXD
It would be worth checking with lxd team if the lxd snap is building compatible container nvidia bits on arm64. Cause it looks like maybe one needs lxd based on core22 base to have this all work. or like wait for us to provide 510 nvidia drivers on arm64 on focal; and use that with focal based lxd snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971978 Title: Driver binaries fail to load on arm64 through LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
** Description changed: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. - [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. + [backported patch] + + the backported patch adds support to mount cgroup2 (new way) in addition + to the old way (cgroup + __DEVEL_ option) and also adds a fallback to do + that when mounting cgroups1 fails (because host is already using non- + hybrid v2 cgroups). This way the default behaviour remains the same, + apart from when trying to boot xenial on latest kernels and userspace + that opts into using cgroups2-only. + [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if cgroup2 is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964510] Re: [SRU] enable signing riscv64 binaries in bionic
root@ethical-catfish:~# dpkg-query -W sbsigntool sbsigntool 0.9.2-2ubuntu1~18.04.2 root@ethical-catfish:~# sbverify --cert db.crt test-arm64.efi.signed warning: data remaining[5112 vs 6104]: gaps between PE/COFF sections? Signature verification OK root@ethical-catfish:~# sbverify --cert db.crt test-riscv64.efi.signed warning: data remaining[5112 vs 6128]: gaps between PE/COFF sections? Signature verification OK root@ethical-catfish:~# faketime 'Thu May 5 13:35:03 CEST' sbsign --key ./db.key --cert ./db.crt test-arm64.efi warning: data remaining[3584 vs 4576]: gaps between PE/COFF sections? Signing Unsigned original image root@ethical-catfish:~# faketime 'Thu May 5 13:35:03 CEST' sbsign --key ./db.key --cert ./db.crt test-riscv64.efi warning: data remaining[3584 vs 4600]: gaps between PE/COFF sections? Signing Unsigned original image The signatures produced are identical to those made with impish tooling. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964510 Title: [SRU] enable signing riscv64 binaries in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1964510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964510] Re: [SRU] enable signing riscv64 binaries in bionic
# dpkg-query -W sbsigntool sbsigntool 0.9.2-2ubuntu1.1 # sbverify --cert ./db.crt test-arm64.efi.signed warning: data remaining[5112 vs 6104]: gaps between PE/COFF sections? Signature verification OK # sbverify --cert ./db.crt test-riscv64.efi.signed warning: data remaining[5112 vs 6128]: gaps between PE/COFF sections? Signature verification OK # faketime 'Thu May 5 13:35:03 CEST' sbsign --key db.key --cert db.crt ./test-arm64.efi warning: data remaining[3584 vs 4576]: gaps between PE/COFF sections? Signing Unsigned original image # faketime 'Thu May 5 13:35:03 CEST' sbsign --key db.key --cert db.crt ./test-riscv64.efi warning: data remaining[3584 vs 4600]: gaps between PE/COFF sections? Signing Unsigned original image Signing is successful and produces identical output, matching impish results. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964510 Title: [SRU] enable signing riscv64 binaries in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1964510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics
I have completed regression testing with this zfs update in proposed, on focal ga v5.4 kernel, including stress tests and zsys tests. It appears to be stable and working correctly. We should release this sru, even though I personally cannot reproduce and confirm that the stated issue is fixed. (i.e. https://github.com/openzfs/zfs/issues/10642 / bug description) $ cat /sys/module/zfs/version 0.8.3-1ubuntu12.14 $ uname -r 5.4.0-110-generic Note that testing hwe kernels is not interesting as they have zfs module of newer versions built-in. ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946686 Title: Fix zfs_get_data access to files with wrong generation causing panics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft
And s390x =( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949603 Title: iptables-save -c shows incorrect counters with iptables-nft To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1949603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft
The newly enabled autopkgtest appears to regress on i386 =/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949603 Title: iptables-save -c shows incorrect counters with iptables-nft To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1949603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933491] Re: kmod add zstd support
# dpkg-query -W kmod kmod27-1ubuntu2 # modinfo ./zstd.ko.zst modinfo: ERROR: Module alias ./zstd.ko.zst not found. upgraded to new kmod: # dpkg-query -W kmod kmod27-1ubuntu2.1 # modinfo ./zstd.ko.zst filename: /lib/modules/5.4.0-109-generic/kernel/crypto/./zstd.ko.zst alias: crypto-zstd alias: zstd description:Zstd Compression Algorithm license:GPL srcversion: C007A20DBED7E012AF5A0A8 depends:zstd_compress retpoline: Y intree: Y name: zstd vermagic: 5.4.0-109-generic SMP mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:2E:88:51:F0:25:CE:CD:BB:F2:FC:76:4E:F5:71:F2:A4:3F:3E:DC:F3 sig_hashalgo: sha512 signature: 62:91:50:E8:5F:FA:96:05:E8:CA:F4:9F:03:0A:5A:56:04:02:37:2D: 06:56:A8:A7:40:02:95:61:78:5F:F3:73:8B:EB:EA:FB:62:F6:B1:B7: 68:4F:A7:87:88:44:E1:85:41:C9:ED:BB:CD:34:02:A1:3E:7A:9A:E8: D8:24:84:94:64:D3:9F:FE:A7:3A:91:10:F3:90:B1:E7:71:25:26:BA: B8:CE:B8:59:E1:B9:DD:C0:0C:82:E3:9B:96:CF:E5:DB:BD:8F:77:11: 87:E4:BB:BC:84:57:49:A3:D8:CE:D6:33:25:86:35:50:67:B5:0A:13: 26:08:4D:66:E9:97:70:B5:F6:87:69:D2:89:EA:2A:40:38:30:88:AA: AD:ED:6C:0A:51:1E:62:E4:F1:13:47:8F:0B:AF:FB:53:A9:74:82:52: 78:53:F2:8D:4D:DB:15:5C:76:4F:9A:77:C0:7F:6E:87:16:B3:DB:FD: C7:D6:C6:8E:14:D1:A6:F0:0B:03:4C:33:68:E8:75:29:93:E6:4F:AE: 43:6D:90:4D:32:4B:A1:42:C1:AD:99:7C:C3:E2:B9:48:E6:F5:0D:DF: 2F:09:C2:46:A6:98:55:47:16:92:EF:28:AB:41:9E:4D:E8:03:2C:21: AF:21:CD:13:1D:C5:A3:FE:03:99:12:03:88:9E:65:1A:82:85:2B:71: DD:EB:F8:7E:C3:B8:84:A1:AD:25:25:DC:FD:58:77:1A:CE:EA:F8:04: C2:E1:DF:AB:A1:17:00:26:96:E5:FA:3F:84:CC:98:ED:31:E2:A0:2F: E6:7D:20:13:D1:57:8C:AA:74:2D:04:7C:48:34:E0:7B:DF:3C:F6:66: 4D:7A:E9:EF:5D:ED:66:7D:87:D6:98:2F:F7:92:3F:C7:CD:16:7B:D0: CE:B4:5B:A3:D9:9A:79:72:23:47:49:E0:69:B2:ED:44:E8:7F:7C:D6: 12:BB:66:A7:5E:F6:0D:2C:9B:7B:DA:8E:76:A9:66:B1:71:44:12:30: 83:DB:09:EE:4C:28:93:BD:50:51:E5:67:C3:B3:79:1C:27:86:82:02: 21:B9:EB:59:54:99:A9:93:02:D3:32:F5:D0:43:05:62:ED:C6:E9:4B: F9:09:9D:40:A2:83:74:25:65:30:BF:59:3A:42:64:28:94:9C:34:79: 42:59:81:22:CE:D0:80:56:A4:65:F8:A0:11:20:0F:A9:F2:F6:52:8C: D1:04:F6:D8:09:D0:D4:66:6E:21:12:AB:68:FD:34:1C:59:AF:9F:E9: AD:5C:A5:6F:AC:51:80:41:4C:62:28:A1:51:5B:C9:E0:C1:17:44:F1: A2:92:1E:39:00:07:96:E6:90:D9:CC:94 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933491 Title: kmod add zstd support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1933491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960169] Re: rtl8812au fails to build on focal with linux hwe 5.15
1) launched focal lxd VM, removed kvm kernel, installed v5.15 hwe-20.04-edge kernel. 2) checked that existing module fails to install Setting up rtl8812au-dkms (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3) ... Loading new rtl8812au-4.3.8.12175.20140902+dfsg DKMS files... Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/rtl8812au-dkms.0.crash' Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log for more informati on. dpkg: error processing package rtl8812au-dkms (--configure): installed rtl8812au-dkms package post-installation script subprocess returned error exit s tatus 10 Errors were encountered while processing: rtl8812au-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) 3) checked that new package installs correctly Unpacking rtl8812au-dkms (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4) over (4.3.8.12175.20 140902+dfsg-0ubuntu13~20.04.3) ... Setting up rtl8812au-dkms (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4) ... Loading new rtl8812au-4.3.8.12175.20140902+dfsg DKMS files... Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Can't load /var/lib/shim-signed/mok/.rnd into RNG 140687348028736:error:2406F079:random number generator:RAND_load_file:Cannot open file:../c rypto/rand/randfile.c:98:Filename=/var/lib/shim-signed/mok/.rnd Generating a RSA private key ... .+ ..+ writing new private key to '/var/lib/shim-signed/mok/MOK.priv' - Done. 8812au.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ depmod... DKMS: install completed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960169 Title: rtl8812au fails to build on focal with linux hwe 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1960169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933491] Re: kmod add zstd support
initramfs-tools ADT test passed on retry. the kernel tests mentioned above are now for EOL kernels that have since all rolled to 5.13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933491 Title: kmod add zstd support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1933491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960165] Re: lttng-modules-dkms fails to build on focal with linux hwe 5.15
1) launched focal lxd container 2) enabled proposed 3) installed the v5.15 based kernel apt install linux-generic-hwe-20.04-edge 4) disabled proposed 5) observed that it fails to install Setting up lttng-modules-dkms (2.12.5-1ubuntu2~20.04.1) ... Loading new lttng-modules-2.12.5 DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/lttng-modules/2.12.5/build/make.log for more information. dpkg: error processing package lttng-modules-dkms (--configure): installed lttng-modules-dkms package post-installation script subprocess returned error ex it status 10 6) enabled proposed once again 7) observed that from proposed installs & builds fine Setting up lttng-modules-dkms (2.12.5-1ubuntu2~20.04.2) ... Loading new lttng-modules-2.12.5 DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Done. lttng-lib-ring-buffer.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-ring-buffer-client-discard.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-ring-buffer-client-mmap-discard.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-ring-buffer-client-mmap-overwrite.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-ring-buffer-client-overwrite.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-ring-buffer-metadata-client.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-ring-buffer-metadata-mmap-client.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-clock.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-statedump.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-tracer.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-wrapper.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-probe-9p.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-probe-asoc.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-probe-block.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-probe-compaction.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-probe-gpio.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-probe-irq.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-probe-jbd2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ lttng-probe-kmem.ko: Running
[Bug 1951608] Re: ddcci-driver-linux: build error with linux 5.15 on jammy
1) launched focal lxd container 2) enabled proposed 3) installed the v5.15 based kernel apt install linux-generic-hwe-20.04-edge 4) disabled proposed 5) observed that it fails to install Loading new ddcci-0.3.3 DKMS files... BACKLIGHT_CLASS_DEVICE disabled in this kernel, not building module. It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/ddcci-dkms.0.crash' Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/ddcci/0.3.3/build/make.log for more information. dpkg: error processing package ddcci-dkms (--configure): installed ddcci-dkms package post-installation script subprocess returned error exit statu s 10 Errors were encountered while processing: ddcci-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) 6) enabled proposed once again 7) observed that from proposed installs & builds fine Setting up ddcci-dkms (0.3.3-1ubuntu0.1) ... Loading new ddcci-0.3.3 DKMS files... BACKLIGHT_CLASS_DEVICE disabled in this kernel, not building module. It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Done. ddcci.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ ddcci-backlight.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ depmod... DKMS: install completed. ** Tags added: verification-done verification-focal-done ** Tags removed: verification-focal-done ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951608 Title: ddcci-driver-linux: build error with linux 5.15 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1951608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960170] Re: rtl8821ce-dkms build failure on focal with linux hwe 5.15
1) launched focal lxd container 2) enabled proposed 3) installed the v5.15 based kernel apt install linux-generic-hwe-20.04-edge 4) disabled proposed 5) observed that it fails to install Setting up rtl8821ce-dkms (5.5.2.1-0ubuntu4~20.04.4) ... Loading new rtl8821ce-5.5.2.1 DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/rtl8821ce/5.5.2.1/build/make.log for more information. dpkg: error processing package rtl8821ce-dkms (--configure): installed rtl8821ce-dkms package post-installation script subprocess returned error exit s tatus 10 Errors were encountered while processing: rtl8821ce-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) 6) enabled proposed once again 7) observed that from proposed installs & builds fine Unpacking rtl8821ce-dkms (5.5.2.1-0ubuntu4~20.04.5) over (5.5.2.1-0ubuntu4~20.04.4) ... Setting up rtl8821ce-dkms (5.5.2.1-0ubuntu4~20.04.5) ... Loading new rtl8821ce-5.5.2.1 DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Done. rtl8821ce.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ /etc/modprobe.d/dkms.conf: added 'blacklist rtw88_8821ce' depmod... DKMS: install completed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960170 Title: rtl8821ce-dkms build failure on focal with linux hwe 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1960170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960169] Re: rtl8812au fails to build on focal with linux hwe 5.15
Opened bug report about the dkms.conf bug at https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1970635 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960169 Title: rtl8812au fails to build on focal with linux hwe 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1960169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970635] [NEW] dkms module is built against host kernel, when asking to build against a chroot kernel
Public bug reported: I was validating https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1960169 in a focal chroot on an impish host. despite only having v5.15 kernel in a chroot, the dkms module was attempted to be built against the host kernel, which failed. dkms modules should respect the kernel version dkms is asking the module to built against. Setting up rtl8812au-dkms (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4) ... Loading new rtl8812au-4.3.8.12175.20140902+dfsg DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/rtl8812au-dkms.0.crash' Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log for more informati on. dpkg: error processing package rtl8812au-dkms (--configure): installed rtl8812au-dkms package post-installation script subprocess returned error exit s tatus 10 dmesg: read kernel buffer failed: Operation not permitted Errors were encountered while proc essing: rtl8812au-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) root@normal-snake:~# cat /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log DKMS make.log for rtl8812au-4.3.8.12175.20140902+dfsg for kernel 5.15.0-25-generic (x86_64) Wed Apr 27 15:22:31 UTC 2022 make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.13.0-40-generic/build M=/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build modules make[1]: *** /lib/modules/5.13.0-40-generic/build: No such file or directory. Stop. make: *** [Makefile:1457: modules] Error 2 Note how make file is inconsistent with the dkms output. ** Affects: rtl8812au (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970635 Title: dkms module is built against host kernel, when asking to build against a chroot kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1970635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960168] Re: openafs build failures with linux-hwe 5.15 on focal
1) launched focal lxd container 2) enabled proposed 3) installed the v5.15 based kernel apt install linux-generic-hwe-20.04-edge 4) disabled proposed 5) observed that it fails to install apt install openafs-modules-dkms Setting up openafs-modules-dkms (1.8.4~pre1-1ubuntu2.3) ... Loading new openafs-1.8.4pre1 DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/openafs/1.8.4pre1/build/make.log for more information. dpkg: error processing package openafs-modules-dkms (--configure): installed openafs-modules-dkms package post-installation script subprocess returned error ex it status 10 6) enabled proposed once again 7) observed that iptables-netflow-dkms from proposed installs & builds fine Setting up openafs-modules-dkms (1.8.4~pre1-1ubuntu2.4) ... Loading new openafs-1.8.4pre1 DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Done. openafs.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ depmod... DKMS: install completed. Setting up openafs-modules-source (1.8.4~pre1-1ubuntu2.4) ... ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960168 Title: openafs build failures with linux-hwe 5.15 on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1960168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960169] Re: rtl8812au fails to build on focal with linux hwe 5.15
1) launched focal lxd container 2) enabled proposed 3) installed the v5.15 based kernel apt install linux-generic-hwe-20.04-edge 4) disabled proposed 5) observed that it fails to install # apt install rtl8812au-dkms=4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: rtl8812au-dkms 0 upgraded, 1 newly installed, 0 to remove and 34 not upgraded. Need to get 1116 kB of archives. After this operation, 8906 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 rtl8812au-dkms all 4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 [1116 kB] Fetched 1116 kB in 1s (1761 kB/s) Selecting previously unselected package rtl8812au-dkms. (Reading database ... 79023 files and directories currently installed.) Preparing to unpack .../rtl8812au-dkms_4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3_all.deb ... Unpacking rtl8812au-dkms (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3) ... Setting up rtl8812au-dkms (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3) ... Loading new rtl8812au-4.3.8.12175.20140902+dfsg DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log for more informati on. dpkg: error processing package rtl8812au-dkms (--configure): installed rtl8812au-dkms package post-installation script subprocess returned error exit s tatus 10 Errors were encountered while processing: rtl8812au-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) 6) enabled proposed once again 7) observed that from proposed does not build and install fine it seems that despite being in a chroot and requesting to build against v5.15 kernel it tries to build against the host kernel: Unpacking rtl8812au-dkms (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4) over (4.3.8.12175.20 140902+dfsg-0ubuntu13~20.04.3) ... Setting up rtl8812au-dkms (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4) ... Loading new rtl8812au-4.3.8.12175.20140902+dfsg DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/rtl8812au-dkms.0.crash' Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log for more informati on. dpkg: error processing package rtl8812au-dkms (--configure): installed rtl8812au-dkms package post-installation script subprocess returned error exit s tatus 10 dmesg: read kernel buffer failed: Operation not permitted Errors were encountered while proc essing: rtl8812au-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) root@normal-snake:~# cat /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log DKMS make.log for rtl8812au-4.3.8.12175.20140902+dfsg for kernel 5.15.0-25-generic (x86_64) Wed Apr 27 15:22:31 UTC 2022 make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.13.0-40-generic/build M=/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build modules make[1]: *** /lib/modules/5.13.0-40-generic/build: No such file or directory. Stop. make: *** [Makefile:1457: modules] Error 2 this needs to be verified in a VM. And the bug that dkms module is not built against requested kernel version should be filed and fixed separately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960169 Title: rtl8812au fails to build on focal with linux hwe 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1960169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960164] Re: iptables-netflow dkms build error on focal with linux hwe 5.15
1) launched focal lxd container 2) enabled proposed 3) installed the v5.15 based kernel apt install linux-generic-hwe-20.04-edge 4) disabled proposed 5) observed that apt install iptables-netflow-dkms fails to install Setting up iptables-netflow-dkms (2.4-2ubuntu0.4) ... Loading new ipt-netflow-2.4 DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic ERROR (dkms apport): kernel package linux-headers-5.15.0-25-generic is not supported Error! Bad return status for module build on kernel: 5.15.0-25-generic (x86_64) Consult /var/lib/dkms/ipt-netflow/2.4/build/make.log for more information. 6) enabled proposed once again 7) observed that iptables-netflow-dkms from proposed installs & builds fine Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 iptables-netflow-dkms amd64 2.4-2ubuntu0.5 [70.5 kB] Fetched 70.5 kB in 0s (202 kB/s) (Reading database ... 76722 files and directories currently installed.) Preparing to unpack .../iptables-netflow-dkms_2.4-2ubuntu0.5_amd64.deb ... -- Deleting module version: 2.4 completely from the DKMS tree. -- Done. Unpacking iptables-netflow-dkms (2.4-2ubuntu0.5) over (2.4-2ubuntu0.4) ... Setting up iptables-netflow-dkms (2.4-2ubuntu0.5) ... Loading new ipt-netflow-2.4 DKMS files... It is likely that 5.13.0-40-generic belongs to a chroot's host Building for 5.15.0-25-generic Building initial module for 5.15.0-25-generic Done. ipt_NETFLOW.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-25-generic/updates/dkms/ depmod... DKMS: install completed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960164 Title: iptables-netflow dkms build error on focal with linux hwe 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1960164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940528] Re: curl 7.68 does not init OpenSSL correctly
1) downgraded openssl to 1.1.1f-1ubuntu2.9 such that it doesn't have double free fix that was released in https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.10 2) installed old pka module from commit b0f32fa05298bf9e3997ea43fc1c11b90e0d662f 3) installed focal-updates version of curl Observed double free core dump: # dpkg-query -W | grep -e 1.1.1f -e curl -e pka curl7.68.0-1ubuntu2.7 libcurl3-gnutls:arm64 7.68.0-1ubuntu2.7 libcurl4:arm64 7.68.0-1ubuntu2.7 libpka1:arm64 1.3-1 libssl-dev:arm641.1.1f-1ubuntu2.9 libssl1.1:arm64 1.1.1f-1ubuntu2.9 openssl 1.1.1f-1ubuntu2.9 # curl -o /dev/null https://start.ubuntu.com/connectivity-check.html % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 576 100 5760 0 2117 0 --:--:-- --:--:-- --:--:-- 2117 double free or corruption (out) Aborted (core dumped) Upgraded to new curl: # dpkg-query -W | grep -e 1.1.1f -e curl -e pka curl7.68.0-1ubuntu2.8 libcurl3-gnutls:arm64 7.68.0-1ubuntu2.8 libcurl4:arm64 7.68.0-1ubuntu2.8 libpka1:arm64 1.3-1 libssl-dev:arm641.1.1f-1ubuntu2.9 libssl1.1:arm64 1.1.1f-1ubuntu2.9 openssl 1.1.1f-1ubuntu2.9 # curl -o /dev/null https://start.ubuntu.com/connectivity-check.html % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 576 100 5760 0 1894 0 --:--:-- --:--:-- --:--:-- 1888 Observed success without any double-free or segfault in openssl. Although this particular issue has already been fixed in openssl, it still makes sense to release this update of curl which includes correct openssl engine API usage. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940528 Title: curl 7.68 does not init OpenSSL correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965878] Re: touchpad dosen't be detected asus f553m
Is touchpad otherwise enabled in the BIOS settings? and with the hardware Fn keyboard key to enable/disable touchpad? It is odd that it seems as if no touchpads are present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965878 Title: touchpad dosen't be detected asus f553m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1965878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965878] Re: touchpad dosen't be detected asus f553m
if Fn+F6 doesn't bring it up. then you should try to install updated firmware via Windows Asus driver updater, or attempting to use fwupd: sudo fwupdmgr refresh sudo fwupdmgr update But given no touchpad appears visible, i'm not sure how to figure out which one it is, and what is missing to support it. Do you know the full touchpad vendor and model number? I.e. from windows info, or from bios settings / hardware spec sheets? ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965878 Title: touchpad dosen't be detected asus f553m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1965878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
** Changed in: zfs-linux (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969482] Re: zfs-2.1.4+ sru
Regression & zsys testing passed out of bileto PPA, submitting for SRU. ** Description changed: [Impact] - * Upstream stable point release update with bugfixes, performance - fixes, and newer kernel support as will be needed in the future hwe - kernels. + * Upstream stable point release update with bugfixes, performance + fixes, and newer kernel support as needed already in the OEM kernel and + will be needed in the future HWE kernels. [Test Plan] - * autopkgtest pass - - * kernel regression zfs testsuite pass + * autopkgtest pass - * zsys integration test pass + * kernel regression zfs testsuite pass + + * zsys integration test pass [Where problems could occur] - * The stable branches maintain api/abi. Certain bugfixes do change + * The stable branches maintain api/abi. Certain bugfixes do change userspace visible behavior of either succeeeding (when previously operations failed), or return errors when previously succeeding in error. For example there are changes when unlinking files in full volumes; changes to fallocate behaviour, etc. Overall they are minor corner cases, and bugfixes to correct the bahaviour to what is universally expected and how things behave on other filesystems (i.e. ext4). ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969482 Title: zfs-2.1.4+ sru To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970225] [NEW] should default to parallel build
Public bug reported: dkms should default to parallel builds if dkms packages fail to parallel build we should fix them; or override them one by one do single thread builds. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970225 Title: should default to parallel build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1970225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959971] Re: [FFE] increase /boot partition size
ZFS installation using ubiquity still uses smaller 1GiB sized bpool (equivalent of /boot on zfs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959971 Title: [FFE] increase /boot partition size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1959971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969940] [NEW] RM oss4 paolo says we should it kill it
Public bug reported: RM oss4 paolo says we should it kill it as far as I can tell it's ancient, unused and not helpful. Please use pipewire, pulseaudio, jack, alsa. Do not use oss4. ** Affects: oss4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969940 Title: RM oss4 paolo says we should it kill it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure
In unapproved. ** Changed in: oss4 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969752 Title: oss4-dkms '-mfloat-abi=hard' build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969632] Re: demote ntfs-3g
** Description changed: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. but there is still a lot of useful ntfs-3g tooling in the ntfs-3g package. For example, maybe we should drop the ntfs-3g initramfs hooks and drop mount.ntfs-3g utilities, in favor of using ntfs3 kernel module. But otherwise keep all other ntfs-3g package utils in place? + + or forexample maybe we should drop fuse portions of ntfs-3g, and keep + tooling + mounting using ntfs3 kernel module only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969632 Title: demote ntfs-3g To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1969632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
I've picked up the PR into a bileto ppa https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4831 it seems to work for me correctly. If one has MOK dkms key enrolled or secureboot disabled, one can use zfs-dkms package from the above ppa as a solution. Please test it and let me know. I will try to SRU that, but it may take a kernel sru cycle to fully land. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969632] Re: demote ntfs-3g
** Description changed: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. + + but there is still a lot of useful ntfs-3g tooling in the ntfs-3g + package. + + For example, maybe we should drop the ntfs-3g initramfs hooks and drop + mount.ntfs-3g utilities, in favor of using ntfs3 kernel module. But + otherwise keep all other ntfs-3g package utils in place? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969632 Title: demote ntfs-3g To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1969632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969632] Re: demote ntfs-3g
** Also affects: curtin Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969632 Title: demote ntfs-3g To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1969632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969632] [NEW] demote ntfs-3g
Public bug reported: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu-seeds/+git/platform/+merge/419962 ** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu-seeds/+merge/419961 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969632 Title: demote ntfs-3g To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1969632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** Description changed: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed. However, while we need secureboot to be enabled on these platforms, backport-iwlwifi-dkms must also be signed somehow. There are two possible method to achieve this, too. One, to prebuild this dkms as zfs and v4l2loopback does. However, while backport-iwlwifi-dkms generates kernel modules with exactly the same name as the in-tree ones, when prebuilt, they'll be available directly from the linux-modules package and therefore overrides the in-tree ones always, turning the in-tree driver completely useless and risk the stability of all other generic installations. The second one is to build backport-iwlwifi-dkms as nvidia graphic drivers in the linux-restricted-modules source package. In this way, affected platforms may install the corresponding packages when needed without interfering others. However, l-r-m is for restricted modules that needs special care of redistribution of its binaries, and backport-iwlwifi-dkms is GPL licensed. Here a similar but simpler process in the main kernel tree is re-implemented. Two additional packages, linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package linux-modules-MODULE-FLAVOUR will be created. [Test Case] Test builds: ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb [Where problems could occur] The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails to build under this proposed process. Debdiff attached to the same bug. Different from nvidia packages built from l-r-m, the generated package names do not carry an additional short version string, e.g. nvidia-410, as there is no such necessity to build multiple versions of iwlwifi. The modules are installed to /lib/modules//kernel/iwlwifi, not iwlwifi-9858/. - == original bug report == + == backport-iwlwifi-dkms SRU == + + Fix FTBFS with non-standard build directory layout, as executed by dkms + build with a sourcedir setting, as will be done by the above kernel + built-in dkms packages. [backport-iwlwifi-dkms] Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build --kernelsourcedir ...` and yet the dkms make command in this package has: MAKE="'make' -j$(num_cpu_cores) KLIB=/lib/modules/$kernelver" ** Description changed: [SRU Justfication] [Impact] Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress, and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16. Not reproducible on every platform with AX211 installed, and the chances of such failures vary from one to another. [Fix] A few solutions were considered. The very first one is to ask Intel to fix -64 firmware directly, and the answer is a solid no claimed -64 is not the planned production version of AX211. It's also possible to backport FW API from v5.16, but while iwlwifi FW API is more or less a black box to us and the new FW APIs also depends on updates on the wireless stack, this is going to be very risky and actually we had regressions before after such backports. The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on the effected platforms. This means oem-5.14 and its migration target, hwe-5.15 will not be able to drive this piece of hw flawlessly without backport-iwlwifi-dkms installed.
[Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
** Changed in: mysql-8.0 (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969482] [NEW] zfs-2.1.4+ sru
Public bug reported: [Impact] * Upstream stable point release update with bugfixes, performance fixes, and newer kernel support as will be needed in the future hwe kernels. [Test Plan] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass [Where problems could occur] * The stable branches maintain api/abi. Certain bugfixes do change userspace visible behavior of either succeeeding (when previously operations failed), or return errors when previously succeeding in error. For example there are changes when unlinking files in full volumes; changes to fallocate behaviour, etc. Overall they are minor corner cases, and bugfixes to correct the bahaviour to what is universally expected and how things behave on other filesystems (i.e. ext4). ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969482 Title: zfs-2.1.4+ sru To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
yeap that's bad. ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: zfs-linux (Ubuntu) Importance: Wishlist => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install
It seems that view, as provided by vim.tiny now attempts to load defaults.vim, which is shipped in the large vim-runtime package. All vims depend on vim-common. It would seem to me that we should move defaults.vim from vim-runtime to vim-common. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968912 Title: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
imho, mysql should still gain zfs specific knowledge that doing fallocate on CoW filesystems doesn't do what one expects it to do. ** Changed in: mysql-8.0 (Ubuntu) Status: Invalid => Triaged ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
However there is now also this: https://github.com/openzfs/zfs/pull/13338/files which seems to indicate that my / zfs understanding of the fallocate kernel flags are not what is done on other filesystems (and expected by stuff). If needed, we can look into pulling in https://github.com/openzfs/zfs/pull/13338/files Please let me know if setting zfs_fallocate_reserve_percent=0 is a workaround for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
given how zfs works, to me this is normal and expected. Also this is expected on btrfs, and on xfs with cow turned on. zfs is copy on write filesystem, thus calling fallocate to "reserve" a large amount of free space doesn't make sense. As the created file is immutable in zfs, and any writes to it will be written to a newly allocated quota in the zvol. There is an option to tune the behaviour of fallocate https://manpages.ubuntu.com/manpages/jammy/en/man4/zfs.4.html zfs_fallocate_reserve_percent=110% (uint) Since ZFS is a copy-on-write filesystem with snapshots, blocks cannot be preallocated for a file in order to guarantee that later writes will not run out of space. Instead, fallocate(2) space preallocation only checks that sufficient space is currently available in the pool or the user's project quota allocation, and then creates a sparse file of the requested size. The requested space is multiplied by zfs_fallocate_reserve_percent to allow additional space for indirect blocks and other internal metadata. Setting this to 0 disables support for fallocate(2) and causes it to return EOPNOTSUPP. This functionality / behaviour was added in zfs-0.8.0-847-gf734301d22 upstream, this is why you don't see it with bionic GA kernel, but do observe this new behaviour with bionic HWE kernels or newer. If things are using fallocate, on top of zfs, they should be aware that fallocate on zfs proofs that the there is enough quota in the zvol pool. Thus mysql needs to gain zfs specific knowledge w.r.t. this. Alternatively, you can disable fallocate support on your system by adding modprobe.d snippet to set zfs module option zfs_fallocate_reserve_percent to zero. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968886] Re: Provide pid_max namespace support
** Description changed:
[Impact]
- * Allow setting lower pid_max on per namespace basis, to support legacy
+ * Allow setting lower pid_max on per namespace basis, to support legacy
workloads on modern hosts.
- * Cherrypick patches from
+ * Cherrypick patches from
https://gitlab.com/brauner/linux/-/commits/pid_max_namespacing/
[Test Plan]
- * Launch lxd container and lower pid_max in the container by doing echo
- 65536 > /path/to/proc/in/c0/mnt/namespace/proc/sys/kernel/pid_max from
- outside of the container
+ Setup:
- * Observe that pid_max is lowered inside the container relative the
- host
+ cat < "\${LXC_ROOTFS_MOUNT}"/proc/sys/kernel/pid_max
+ EOF
+
+ sudo chmod +x /var/snap/lxd/common/set-pid-max
+
+ echo "lxc.hook.mount=\$SNAP_COMMON/set-pid-max" | sudo tee
+ /var/snap/lxd/common/set-pid-max.config
+
+ lxc launch -c raw.lxc="lxc.include = /var/snap/lxd/common/set-pid-
+ max.config" ubuntu-daily:jammy
+
+ lxc launch -c raw.lxc="lxc.include = /var/snap/lxd/common/set-pid-
+ max.config" ubuntu-daily:jammy small-pid-container
+
+ == Test Results ==
+ Large value on the host:
+
+ sudo sysctl -a | grep pid_max
+ kernel.pid_max = 4194304
+
+ Small value in the container:
+ lxc exec small-pid-container -- sysctl -a 2>/dev/null | grep pid_max
+ Expected value: kernel.pid_max = 65536
[Where problems could occur]
- * These are out-of-the-tree sauce patches not yet applied upstream,
+ * These are out-of-the-tree sauce patches not yet applied upstream,
there appear to be permissions issues inside user namespaces of being
able to self-lower the limit without being cap_sysadmin in the parent
namespace. Implementation upstream may change, with different
permissions and semantics. By default, currently pid_max is very large,
and thus it shouldn't be needed to lower that at all on the host.
** Description changed:
[Impact]
* Allow setting lower pid_max on per namespace basis, to support legacy
workloads on modern hosts.
* Cherrypick patches from
https://gitlab.com/brauner/linux/-/commits/pid_max_namespacing/
[Test Plan]
Setup:
- cat < "\${LXC_ROOTFS_MOUNT}"/proc/sys/kernel/pid_max
EOF
sudo chmod +x /var/snap/lxd/common/set-pid-max
echo "lxc.hook.mount=\$SNAP_COMMON/set-pid-max" | sudo tee
/var/snap/lxd/common/set-pid-max.config
-
- lxc launch -c raw.lxc="lxc.include = /var/snap/lxd/common/set-pid-
- max.config" ubuntu-daily:jammy
lxc launch -c raw.lxc="lxc.include = /var/snap/lxd/common/set-pid-
max.config" ubuntu-daily:jammy small-pid-container
== Test Results ==
Large value on the host:
sudo sysctl -a | grep pid_max
kernel.pid_max = 4194304
Small value in the container:
lxc exec small-pid-container -- sysctl -a 2>/dev/null | grep pid_max
Expected value: kernel.pid_max = 65536
-
[Where problems could occur]
* These are out-of-the-tree sauce patches not yet applied upstream,
there appear to be permissions issues inside user namespaces of being
able to self-lower the limit without being cap_sysadmin in the parent
namespace. Implementation upstream may change, with different
permissions and semantics. By default, currently pid_max is very large,
and thus it shouldn't be needed to lower that at all on the host.
** Description changed:
[Impact]
* Allow setting lower pid_max on per namespace basis, to support legacy
workloads on modern hosts.
* Cherrypick patches from
https://gitlab.com/brauner/linux/-/commits/pid_max_namespacing/
[Test Plan]
Setup:
cat < "\${LXC_ROOTFS_MOUNT}"/proc/sys/kernel/pid_max
EOF
sudo chmod +x /var/snap/lxd/common/set-pid-max
echo "lxc.hook.mount=\$SNAP_COMMON/set-pid-max" | sudo tee
/var/snap/lxd/common/set-pid-max.config
lxc launch -c raw.lxc="lxc.include = /var/snap/lxd/common/set-pid-
max.config" ubuntu-daily:jammy small-pid-container
== Test Results ==
Large value on the host:
sudo sysctl -a | grep pid_max
kernel.pid_max = 4194304
Small value in the container:
lxc exec small-pid-container -- sysctl -a 2>/dev/null | grep pid_max
- Expected value: kernel.pid_max = 65536
+ kernel.pid_max = 65536
[Where problems could occur]
* These are out-of-the-tree sauce patches not yet applied upstream,
there appear to be permissions issues inside user namespaces of being
able to self-lower the limit without being cap_sysadmin in the parent
namespace. Implementation upstream may change, with different
permissions and semantics. By default, currently pid_max is very large,
and thus it shouldn't be needed to lower that at all on the host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968886
Title:
Provide pid_max namespace support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968886/+subscriptions
[Bug 1968886] Re: Provide pid_max namespace support
Entering mount & pid namespace, as initial namespace root does not let me set pid_max inside the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968886 Title: Provide pid_max namespace support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968886] Re: Provide pid_max namespace support
Changing pid_max on the host to a lower value, kept high value in the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968886 Title: Provide pid_max namespace support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on H/F-riscv
** No longer affects: linux-riscv (Ubuntu Jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909422 Title: ubuntu_ftrace_smoke_test timeout on H/F-riscv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969090] [NEW] ubuntu_stress_smoke_test permission errors on jammy
Public bug reported: Failing in jammy now, and it has: 09:57:20 INFO | ERROR ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-test timestamp=1649325440 localtime=Apr 07 09:57:20 Unhandled OSError: [Errno 1] Operation not permitted: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/tmp-stress-ng-chattr-20900-0/stress-ng-chattr-20900-0-0' 219 Traceback (most recent call last): 220 File "/home/ubuntu/autotest/client/shared/test.py", line 387, in _exec 221 *p_args, **p_dargs) 222 File "/home/ubuntu/autotest/client/shared/utils.py", line 829, in update_version 223 shutil.rmtree(srcdir) 224 File "/usr/lib/python2.7/shutil.py", line 270, in rmtree 225 rmtree(fullname, ignore_errors, onerror) 226 File "/usr/lib/python2.7/shutil.py", line 270, in rmtree 227 rmtree(fullname, ignore_errors, onerror) 228 File "/usr/lib/python2.7/shutil.py", line 275, in rmtree 229 onerror(os.remove, fullname, sys.exc_info()) 230 File "/usr/lib/python2.7/shutil.py", line 273, in rmtree 231 os.remove(fullname) 232 OSError: [Errno 1] Operation not permitted: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/tmp-stress-ng-chattr-20900-0/stress-ng-chattr-20900-0-0' 233 as if unclean machine. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: 5.8 jammy riscv riscv64 ubuntu-stress-smoke-test ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 5.8 jammy riscv riscv64 ubuntu-stress-smoke-test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969090 Title: ubuntu_stress_smoke_test permission errors on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1969090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on H/F-riscv
Failing in jammy now, and it has: 09:57:20 INFO | ERROR ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-testtimestamp=1649325440 localtime=Apr 07 09:57:20Unhandled OSError: [Errno 1] Operation not permitted: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/tmp-stress-ng-chattr-20900-0/stress-ng-chattr-20900-0-0' 219 Traceback (most recent call last): 220 File "/home/ubuntu/autotest/client/shared/test.py", line 387, in _exec 221 *p_args, **p_dargs) 222 File "/home/ubuntu/autotest/client/shared/utils.py", line 829, in update_version 223 shutil.rmtree(srcdir) 224 File "/usr/lib/python2.7/shutil.py", line 270, in rmtree 225 rmtree(fullname, ignore_errors, onerror) 226 File "/usr/lib/python2.7/shutil.py", line 270, in rmtree 227 rmtree(fullname, ignore_errors, onerror) 228 File "/usr/lib/python2.7/shutil.py", line 275, in rmtree 229 onerror(os.remove, fullname, sys.exc_info()) 230 File "/usr/lib/python2.7/shutil.py", line 273, in rmtree 231 os.remove(fullname) 232 OSError: [Errno 1] Operation not permitted: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/tmp-stress-ng-chattr-20900-0/stress-ng-chattr-20900-0-0' 233 as if unclean machine. ** Also affects: linux-riscv (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909422 Title: ubuntu_ftrace_smoke_test timeout on H/F-riscv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920774] Re: v5.11 kernel seems to sometimes hang on unmatched board
** Changed in: linux-riscv (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920774 Title: v5.11 kernel seems to sometimes hang on unmatched board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1920774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929594] Re: linux-image-5.11.0-1008-generic: cannot read initrd via EFI_LOAD_FILE2_PROTOCOL
Has this been resolved now? Jammy is booting fine, right? ** Changed in: linux-riscv (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929594 Title: linux-image-5.11.0-1008-generic: cannot read initrd via EFI_LOAD_FILE2_PROTOCOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1929594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966978] Re: microchip/microchip-mpfs-icicle-kit.dtb missing
I think first kernel that had it in jammy was: 2022-04-01 01:11:33 BST Superseded Jammy release maindevel 5.15.0-1004.4 Given bug filing date & the migration date of that kernel, it was not there at the time the bug was filed, but it is available now. ** Changed in: linux-riscv (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966978 Title: microchip/microchip-mpfs-icicle-kit.dtb missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1966978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937868] Re: linux-riscv: booting the kernel via the EFI stub with large initrd fails
included in v5.15 ** Changed in: linux-riscv (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937868 Title: linux-riscv: booting the kernel via the EFI stub with large initrd fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1937868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966978] Re: microchip/microchip-mpfs-icicle-kit.dtb missing
/lib/firmware/5.15.0-1007-generic/device-tree/microchip/microchip-mpfs- icicle-kit.dtb Is shipped by linux- modules-5.15.0-1007-generic_5.15.0-1007.7_riscv64.deb and probably earlier. Is something wrong with its presence or location? ** Changed in: linux-riscv (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966978 Title: microchip/microchip-mpfs-icicle-kit.dtb missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1966978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968886] [NEW] Provide pid_max namespace support
Public bug reported: [Impact] * Allow setting lower pid_max on per namespace basis, to support legacy workloads on modern hosts. * Cherrypick patches from https://gitlab.com/brauner/linux/-/commits/pid_max_namespacing/ [Test Plan] * Launch lxd container and lower pid_max in the container by doing echo 65536 > /path/to/proc/in/c0/mnt/namespace/proc/sys/kernel/pid_max from outside of the container * Observe that pid_max is lowered inside the container relative the host [Where problems could occur] * These are out-of-the-tree sauce patches not yet applied upstream, there appear to be permissions issues inside user namespaces of being able to self-lower the limit without being cap_sysadmin in the parent namespace. Implementation upstream may change, with different permissions and semantics. By default, currently pid_max is very large, and thus it shouldn't be needed to lower that at all on the host. ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968886 Title: Provide pid_max namespace support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968175] Re: Allow runtime configuration of pkcs11 modules through config file
In other distributions opensc by default is configured to use: PKCS11 default provider: /usr/lib64/opensc-pkcs11.so PKCS11 onepin provider: /usr/lib64/onepin-opensc-pkcs11.so which we do on Ubuntu as well, but with multiarch paths. However, I see that other distributions ship .module files to allow using opensc-pkcs11 via p11-kit proxy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968175 Title: Allow runtime configuration of pkcs11 modules through config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libp11/+bug/1968175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu) Milestone: None => ubuntu-22.04 ** Changed in: grub2-signed (Ubuntu) Milestone: None => ubuntu-22.04 ** Changed in: grub2-unsigned (Ubuntu) Milestone: None => ubuntu-22.04 ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967130] Re: rcu_sched detected stalls on CPUs/tasks
** Changed in: linux-riscv (Ubuntu) Status: Triaged => Fix Committed ** Changed in: linux-riscv (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967130 Title: rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968175] Re: Allow runtime configuration of pkcs11 modules through config file
I see that in Fedora opensc provides a p11kit module to allow using opensc-pkcs11.so via p11-kit's proxy module https://src.fedoraproject.org/rpms/opensc/blob/rawhide/f/opensc.module -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968175 Title: Allow runtime configuration of pkcs11 modules through config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libp11/+bug/1968175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968175] Re: Allow runtime configuration of pkcs11 modules through config file
libp11 in Ubuntu uses p11-kit-proxy.so by default already, so I don't believe it needs changing does it? Focal: https://launchpad.net/ubuntu/+source/libp11/0.4.10-1 https://launchpad.net/ubuntu/+source/libp11/0.4.10-1/+build/17239024 https://launchpadlibrarian.net/432332202/buildlog_ubuntu-eoan-amd64.libp11_0.4.10-1_BUILDING.txt.gz Default PKCS11 module: /usr/lib/x86_64-linux-gnu/p11-kit-proxy.so Jammy: https://launchpad.net/ubuntu/+source/libp11/0.4.11-1build3 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4813-deletedppa/+build/23497085 https://launchpadlibrarian.net/592757435/buildlog_ubuntu-jammy-amd64.libp11_0.4.11-1build3_BUILDING.txt.gz Default PKCS11 module: /usr/lib/x86_64-linux-gnu/p11-kit-proxy.so ** Changed in: libp11 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968175 Title: Allow runtime configuration of pkcs11 modules through config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libp11/+bug/1968175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968175] Re: Allow runtime configuration of pkcs11 modules through config file
** Description changed: - To be able to switch modules at runtime via configuration file change the default module from opensc-pkcs11 to p11-proxy module, which by default loads opensc-pkcs11 module unless configured by administrator to use something else. - This also allows configuration where multiple modules can be used together through the p11-proxy module. + [Impact] - This aligns Ubuntu closer with other distributions, and allows using the - same builds of opensc in embedded configurations on Ubuntu Core with + * To be able to switch modules at runtime via configuration file change + the default module from opensc-pkcs11 to p11-proxy module, which by + default loads opensc-pkcs11 module unless configured by administrator to + use something else. + + * This also allows configuration where multiple modules can be used + together through the p11-proxy module. + + * This aligns Ubuntu closer with other distributions, and allows using + the same builds of opensc in embedded configurations on Ubuntu Core with specialized modules - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: opensc 0.20.0-3 - ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 - Uname: Linux 5.4.0-107-generic aarch64 - NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp prl_fs_freeze prl_fs prl_tg - ApportVersion: 2.20.11-0ubuntu27.21 - Architecture: arm64 - Date: Thu Apr 7 14:50:08 2022 - InstallationDate: Installed on 2021-11-08 (150 days ago) - InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release arm64 (20210824) - SourcePackage: opensc - UpgradeStatus: No upgrade log present (probably fresh install) + [Test Plan] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + * if other testing is appropriate to perform before landing this update, +this should also be described here. + + [Where problems could occur] + + * Think about what the upload changes in the software. Imagine the change is +wrong or breaks something else: how would this show up? + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This must '''never''' be "None" or "Low", or entirely an argument as to why +your upload is low risk. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance ** Changed in: opensc (Ubuntu) Status: Confirmed => Incomplete ** Changed in: libp11 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968175 Title: Allow runtime configuration of pkcs11 modules through config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libp11/+bug/1968175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
I believe this is still related to lack of rhboot upstreaming patches to grub to use highmem allocations; such that lowmem remains unused; and thus SEV/SWIOTLB can be used "normally". It is likely the difference you see is due to fedora's grub patches. It would be interesting, if you could unpack & use fedora's kernel with ubuntu's grub, and see if fedora's kernel starts failing when booted via ubuntu's grub? Or vice-versa; unpack and use ubuntu's kernel on fedora with fedora's grub to observe it working fine. That would help eliminate differences of grub between the distros with the same kernels. ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968320] [NEW] Please support self-compressed kernel images on arm64
Public bug reported: arm64 is currently the only kernel architecture that does not support self-compressed kernel images, instead it states that "external" things should decompress the kernel image if it is so desired. this hinders adoption of arm64, reduces feature parity with other architectures, and makes it harder to have optimal kernels on arm64. For example: - sd-boot stub as used in Ubuntu Core does not support uncompressing .vmlinuz section in https://systemd.io/BOOT_LOADER_SPECIFICATION/ type 2 binary - firmware on RaspberryPi doesn't support compressed kernel images, or only supports a subset of compression algorithms - vmlinuz can be booted directly as an EFI app which also doesn't support compression, or doesn't support all compression algorithms It would be extremely nice to be able to compress vmlinuz on arm64 with modern compression algorithms (zstd, lz4, xz) and be able to boot them the same way one can boot armhf / x86_64 kernels in EFI contexts. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968320 Title: Please support self-compressed kernel images on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2
Please note that in jammy we ship cherrypicks of stable branch updates up to zfs-2.1.2-27-g1009e60992 meaning we do have v5.17 kernel support availabe in jammy. Upgrading to complete 2.1.3 / 2.1.4 is something very useful to do, but not sure it can be achieved in time for 22.04 LTS GA, but hopefully will be able to deliver it as an SRU. ** Changed in: zfs-linux (Ubuntu) Milestone: None => jammy-updates ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.4, jammy has 2.1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964484] Re: upgrade dkms autopkgtest to handle build-excludes correctly
** Changed in: dahdi-linux (Ubuntu) Status: New => Fix Released ** Changed in: rtl8821ce (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964484 Title: upgrade dkms autopkgtest to handle build-excludes correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1964484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968297] Re: FTBFS on kernels without wifi or v5.17+ based
** Summary changed: - FTBFS on kernels without wifi + FTBFS on kernels without wifi or v5.17+ based ** Description changed: FTBFS on kernels without wifi this dkms module attempts to build itself for kernels that do not support wifi (i.e. linux-kvm) adapt dkms.conf such that a build is not attempted on wifi-less kernels, and such combinations are skipped. This improves end user experience, and makes autopkgtestest pass. + + FTBFS on v5.17+ kernels + + cherrypick upstream patch to fix compat with v5.17. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968297 Title: FTBFS on kernels without wifi or v5.17+ based To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1968297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964484] Re: upgrade dkms autopkgtest to handle build-excludes correctly
** Changed in: v4l2loopback (Ubuntu) Status: New => Fix Committed ** Changed in: rtl8821ce (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964484 Title: upgrade dkms autopkgtest to handle build-excludes correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1964484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
