sru-release comments: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf, arm64) -> autopkgtest failures are a false negative. It only is built and supported on amd64
sysdig/riscv64 - ftbfs is not a regression, never built on riscv64 in focal zfs-linux/riscv64 - ftbfs is not a regression, never built on riscv64 in focal iptables-netflow - needs 3 more days to age Thus everything is ready to be released to -updates & -security ** Changed in: acpi-call (Ubuntu) Status: New => Fix Released ** Changed in: backport-iwlwifi-dkms (Ubuntu) Status: New => Fix Released ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released ** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Released ** Changed in: virtualbox (Ubuntu) Status: New => Fix Released ** Changed in: v4l2loopback (Ubuntu) Status: New => Fix Released ** Changed in: sysdig (Ubuntu) Status: New => Fix Released ** Changed in: rtl8812au (Ubuntu) Status: New => Fix Released ** Changed in: r8168 (Ubuntu) Status: New => Fix Released ** Changed in: oss4 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Fix Released ** Changed in: lttng-modules (Ubuntu) Status: New => Fix Released ** Changed in: lime-forensics (Ubuntu) Status: New => Fix Released ** Changed in: liblzf (Ubuntu) Status: New => Fix Released ** Changed in: iptables-netflow (Ubuntu) Status: New => Fix Released ** Changed in: gost-crypto (Ubuntu) Status: New => Fix Released ** Changed in: evdi (Ubuntu) Status: New => Fix Released ** Changed in: dm-writeboost (Ubuntu) Status: New => Fix Released ** Changed in: dahdi-linux (Ubuntu) Status: New => Fix Released ** Changed in: bcmwl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot..... which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp