** Changed in: kdump-tools (Ubuntu)
Status: Invalid => 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/1877533
Title:
[20.10 FEAT] Increase the crashkernel setting if the root
systemd stuff did either partition or fs but not both.
we used the cloud initramfs implementation on the desktop, because yes,
it doesn't do cloud-init.
probably moving that out of the common seed will help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
This prevents installing OEM kernels with nvidia, offline, from Ubuntu
Desktop Focal point release media.
Note this package is in the ship-live .debs archive pool only.
--
Resolution
** Description changed:
Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
This prevents installing OEM kernels with nvidia, offline, from Ubuntu
Desktop Focal point release media.
Note this package is in the ship-live .debs archive pool only.
--
Resolution
Public bug reported:
Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
This prevents installing OEM kernels with nvidia, offline, from Ubuntu
Desktop Focal point release media.
Note this package is in the ship-live .debs archive pool only.
--
Resolution of this bug report
Downloaded the iso today doesn't mean the iso was built today, or if it
contains this update.
jammy installer iso are attempted to be built daily, but are only
published once they pass automated smoke testing and validation. The
last image that passed that was built on 2nd of February. And builds
Fix was released in busybox 1:1.30.1-7ubuntu3 and requires initramfs
rebuild
your screenshot clearly shows version number 1:1.30.1-7ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960083
Made an untested merge-proposal linked, please test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955671
Title:
support for rocky linux UEFI
To manage notifications about this bug go to:
Command: ['unshare', '--fork', '--pid', '--', 'chroot',
'/tmp/tmpqkhzgamy/target', 'grub2-mkconfig', '-o',
'/boot/efi/EFI/redhat/grub.cfg']
does not look correct, given that rocky edition of grub2 ships:
/boot/efi/EFI/rocky/grub.cfg
/boot/efi/EFI/rocky/grubenv
/boot/efi/EFI/rocky/grubx64.efi
Also, ubuntu_lxc fails on jammy now; even though it is still using
impish branch of tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960094
Title:
lxc/1:4.0.6-0ubuntu1~20.04.1 undefined
vers are built on arches for which both the
driver and kernel-flavour exist.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received t
To be fair we don't need the empty pthread in the initramfs, we only
need the non-empty dynamically opened libgcc_s, but it shouldn't hurt
either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958594
** Changed in: initramfs-tools (Ubuntu Jammy)
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/1950996
Title:
Missing all modules for usb nics in initrd
** Changed in: initramfs-tools (Ubuntu Jammy)
Status: Confirmed => 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/1958594
Title:
Boot error: libgcc_s.so.1 must be installed for
With above, when testing I now get:
Adding binary /usr/lib/initramfs-tools/bin/gcc_s1-stub
Adding binary /lib/x86_64-linux-gnu/libgcc_s.so.1
Adding binary /lib/x86_64-linux-gnu/libc.so.6
Adding binary-link /usr/lib64/ld-linux-x86-64.so.2
Adding binary
$ gcc -Wl,--no-as-needed -shared -l:libpthread.so.0 -l:libgcc_s.so.1 -o
bla
$ ldd bla
linux-vdso.so.1 (0x7ffe0e7e6000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7feeeaa32000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
With that branch rebased, and typpos fixed up testing locally does
produce this:
Adding binary /usr/lib/initramfs-tools/bin/gcc_s1-stub
Adding binary /lib/x86_64-linux-gnu/libgcc_s.so.1
Adding binary /lib/x86_64-linux-gnu/libc.so.6
Adding binary-link /usr/lib64/ld-linux-x86-64.so.2
Adding binary
** Changed in: initramfs-tools (Ubuntu Jammy)
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/1950996
Title:
Missing all modules for usb nics in initrd which
We have been bitten by this before. And Last time I did proposed to do
this:
- create a stub binary tha tis linked with pthread and libgcc_s
- copy_exec that into the initramfs
https://code.launchpad.net/~xnox/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/385243
This ensures that
** Description changed:
There is a new more efficient debug format enabled via
CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need
packaging in the .ddeb before we can enable this. Evaluate whether the
other tooling we have will handle it before doing so.
--
* all
** Description changed:
There is a new more efficient debug format enabled via
CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need
packaging in the .ddeb before we can enable this. Evaluate whether the
other tooling we have will handle it before doing so.
+
+ --
+
+ * all
I wonder if zfs-initramfs should actually add a harmless copy-exec
dirname => which should either do nothing (in case busybox-initramfs
provides dirname) or copy the coreutils implementation. Without breaks.
And I think I will take this upstream as well, as it seems to me that
the upstream hook
although it seems to be a regression introduced by zfs-linux =>
previously it would copy the coreutils dirname into the initramfs as a
binary. Which seems to have been dropped in the most recent upload in
jammy. I kind of agree that busybox providing dirname applet is better,
but it still feels
$ dput ssh-ubuntu busybox_1.30.1-7ubuntu3_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: /tmp/busybox_1.30.1-7ubuntu3_source.changes: Valid signature from
9B8EC849D5EF70ED
Checking signature on .dsc
gpg: /tmp/busybox_1.30.1-7ubuntu3.dsc: Valid signature from
Installed encrypted zsys impish system, enabled proposed, and applied
all updates.
$ dpkg-query -W zfs-initramfs
zfs-initramfs 2.0.6-1ubuntu2.1
Created zsys snapshot and booted into it successfully.
Downgraded all zfs packages back to 2.0.6-1ubuntu2, to check that I can
reproduce original
@fheimes @iii-i
thank you for this, we will include that patch into our kernels. Do you
expect that the toolchain change may have affected any other binaries
(ie. userspace binaries)? Or should we re-apply the reverted patch back
in our gcc-11 (given the improvements that it brings)?
--
You
** Description changed:
bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev
PPA and installed in pi-kernel snaps.
Some of the firmware files shipped in bluez-firmware are not present in
neither src:linux-firmware nor src:linux-firmware-raspi
It seems like it is
Public bug reported:
bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev
PPA and installed in pi-kernel snaps.
Some of the firmware files shipped in bluez-firmware are not present in
neither src:linux-firmware nor src:linux-firmware-raspi
It seems like it is an oversight, and
Autopkgtests completed successfully on both impish and focal.
** Tags removed: verification-needed verification-needed-focal
verification-needed-impish
** Tags added: verification-done verification-done-focal
verification-done-impish
--
You received this bug notification because you are a
Public bug reported:
RM linux-firmware-raspi2 from jammy 5-0ubuntu1
renamed to https://launchpad.net/ubuntu/+source/linux-firmware-raspi
** Affects: linux-firmware-raspi2 (Ubuntu)
Importance: Undecided
Status: Triaged
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status:
@sil2100
--disable-test-modules \
override_dh_auto_test:
+ dh_auto_test --builddir=build-deb
are needed together to enable building and running unittests during
build.
Note previously focal builds did not run unittests at all.
The autoconf help text for the option says "disable
** Bug watch added: Debian Bug tracker #990092
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990092
** Also affects: kmod (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990092
Importance: Unknown
Status: Unknown
--
You received this bug notification because
It feels like we should just copy libgcc_s.so.1 and libpthread always.
It is tiny in size and something is bound to use them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958594
Title:
Boot
: Dimitri John Ledkov (xnox)
Status: In Progress
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Impish)
** No longer affects: linux
** Description changed:
+ -- initramfs-tools
+
+ [Impact]
+
+ * linux supports xz compressed linux-firmware which saves disk space.
+ In focal, initramfs-tools only knows how to included uncompressed
+ firmware files (even when kernel supports loading compressed ones).
+ Newer releases of
** Description changed:
- kmod add zstd support
+ [Impact]
- * v27+ needs patches cherrypicked from v28
+ * To safe diskspace, upcoming devel series / hwe kernels may turn on
+ zstd kernel module compression. Kmod since impish support zstd support.
+ But in order to keep hwe kernels at
I wonder if I should have included feature backports to support
compressed kernel modules & coompressed firmware files
https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8
This would be actually useful, and would allow us to enable compressed
kernel modules for jammy and hwe-5.15
uploaded into unapproved queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958904
Title:
autopkgtest is failing on jammy with "no space left on device"
To manage notifications about this bug go
@brian-murray
Unfortunately, it would mean that kernel-teams adt-matrix would still
need to be hinted, as it does strict adt test runs against each kernel
flavour, against packages in updates only, and enforces that every
kernel flavour is tested. However, I also think that this adt test may
not
Doing test builds in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4769/+packages
** Changed in: dwarves (Ubuntu)
Status: Fix Released => Fix Committed
** Tags added: block-proposed-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
1.22-2ubuntu1 is not a fix but a revert back to 1.21 codebase
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958959
Title:
pahole v1.22-2 segfaults when building a Linux kernel
To manage
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Critical
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug not
For focal this appears to be required and fixes things for people
https://github.com/openzfs/zfs/issues/10642
I will rerun regression suites on focal with latest kernel, and if that
passes, will mark this as verification done.
--
You received this bug notification because you are a member of
riscv64 ftbfs is not a regression, as we don't build it in updates
either.
** Bug watch added: github.com/openzfs/zfs/issues #10642
https://github.com/openzfs/zfs/issues/10642
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
- regression tests s390x
- autopkgtests all arches
- regression tests ppc64el (on focal userspace)
- double check focal userspace with hwe-kernel new zfs-dkms
- regression tests arm64
-
I guess i can modify init-system-helpers again, to dump journal from the
build such that we can see what is going on.
** Also affects: launchpad-buildd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Summary changed:
- Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
+ error: too early for operation, device not yet seeded or device model not
acknowledged Install failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
- regression tests s390x
- autopkgtests all arches
- regression tests ppc64el (on focal userspace)
- double check focal userspace with hwe-kernel new zfs-dkms
- regression tests arm64
+ -
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
- regression tests s390x
- autopkgtests all arches
- regression tests ppc64el (on focal userspace)
- double check focal userspace with hwe-kernel new zfs-dkms
+ - regression tests arm64
even with reverted init-system-helps snapd units fail to start during
launchpad-buildd
https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650698
Setting up snapd (2.54.2+22.04ubuntu1) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/snapd.apparmor.service →
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
- regression tests s390x
- autopkgtests all arches
+ - regression tests ppc64el (on focal userspace)
+ - double check focal userspace with hwe-kernel new zfs-dkms
TODO
- - double check
Public bug reported:
https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565
New deb-systemd-invoke added functionality for systemd v250 which ubuntu
does not have yet. But it also appears to break postinst calls to deb-
systemd-invoke, at least as seen during snap builds in lxd
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
+ - regression tests s390x
- autopkgtests all arches
-
TODO
- double check focal userspace with hwe-kernel new zfs-dkms
- zsys in jammy on amd64
- - regression tests s390x
-
: zfs-linux (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: In Progress
** Affects: zfs-linux (Ubuntu Jammy)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: In Progress
** Tags: block-proposed-jammy
** Tags added
Public bug reported:
port zsys generator changes from shell to C
new zfs has ported zfs mount generator from shell to C, meaning we need
to rewrite zsys specific functionality that we patch into said generator
from shell to C.
** Affects: zfs-linux (Ubuntu)
Importance: Wishlist
@arighi
Explicit nack on zfs-linux patches, that is incomplete merge that drops
ubuntu delta & zsys support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954676
Title:
jammy 5.15 kernel soft
@ilja
Now this is starting to be more fun then. Note our mainframe is z13 2964
and we have reproduced the bug in both LPAR and KVM. I'll try to package
up a more concrete reproducer (to the point of tarring up a full chroot
with all the deps).
--
You received this bug notification because you
More useful filenames would be those the embeded the EFI architecute
tag. For example see grub:
http://archive.ubuntu.com/ubuntu/dists/jammy/main/uefi/grub2-amd64/current/
http://ports.ubuntu.com/dists/jammy/main/uefi/grub2-arm64/current/
The amd64 one is called grubx64.efi and for arm64 it is
Hi, modules built with gcc-11 14ubuntu1 toolchain have the gcc-11 stable
ibmz PLT patch already reverted to make things work again.
One needs to downgrade gcc-11 to 13ubuntu1 to experience the breakage.
You can fetch older gcc-11 from
The revert of the gcc-11 patch mentioned above results in working kernel
builds, which load zfs.ko built-into-kernel and built via zfs-dkms as
well.
** Description changed:
[Impact]
Installing zfs-dkms seems to trigger a soft lockup issue as soon as
zfs.ko is loaded. When the soft
Note above patches causes regression with SEV feature, which has been
subsequently fixed. See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4754/+packages build 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/1954676
Title:
jammy 5.15 kernel soft lockup when zfs.ko
We are suspecting
https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7
and trying to do builds with it reverted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954676
@ubuntu-archive please promote firwmare-sof from multiverse to
restricted. As blobs are now removed from linux-firmware in favor of
shipping them in firmware-sof.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: firmware-sof (Ubuntu Jammy)
Status: Triaged => 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/1930868
Title:
[SRU][Jammy]Package firmware-sof-signed (not
1) firmware-sof is good; note that breaks/replaces versions will need to
be adjusted to the correct versions for every series upon every upload
of this change, if it is SRUed.
2) the matching linux-firmware changes are good as well.
--
You received this bug notification because you are a member
** Changed in: bbswitch (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/1951583
Title:
bbswitch dkms build failure with 5.15 on armhf and ppc64el
Idea: move the strict `nvidia-kernel-common-N (<= N)` from the `linux-
modules-nvidia-N-ABI` package to the meta packages `linux-modules-
nvidia-N-kernelflavour`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The dependencies are intentionally very strict, to ensure that kernel /
nvidia drivers / nvidia userspace are all installed and are compatible
with each other.
However, it was intended to be upgradable unattended. And since one can
have up to three kernel ABIs on disk, one should in theory be
** Also affects: backport-iwlwifi-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/1951580
Title:
backport-iwlwifi-dkms fails to build with
sorry, i synced it, without noticing this bug report.
** Changed in: openafs (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/1952075
Title:
Sync openafs
** Changed in: ddcci-driver-linux (Ubuntu Jammy)
Status: Confirmed => 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/1951608
Title:
ddcci-driver-linux: build error with linux
Fixed in https://github.com/snapcore/snapd/pull/11090
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952224
Title:
snapd.apparmor.service uses apparmor_parser from base, instead of
snapd snap
To
Public bug reported:
snapd.apparmor.service uses apparmor_parser from base, instead of snapd
snap
$ /snap/snapd/current/usr/lib/snapd/apparmor_parser --preprocess <
Nov 25 12:32:34 ubuntu snapd-apparmor[2264]: AppArmor parser error for
/var/lib/snapd/apparmor/profiles/snap-confine.snapd.14091
** Changed in: rtl8812au (Ubuntu)
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/1951621
Title:
rtl8812au dkms broken with jammy 5.15
To manage notifications
** Description changed:
[Impact]
- * Engine crashes when loading the configuration more than once
+ * Engine crashes when loading the configuration more than once
- * Upstream started to avoid loading engines twice by using dynamic ids
+ * Upstream started to avoid loading engines
What about merging 2.6 from debian too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951611
Title:
iptables-netflow dkms build error on 5.15 jammy
To manage notifications about this bug go to:
doing forced sync from debian to bring in v2.6, then will upload the
proposed v5.15 patch on top.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951611
Title:
iptables-netflow dkms build error on
** Changed in: iptables (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/1949603
Title:
iptables-save -c shows incorrect counters with iptables-nft
ddcci-driver-linux (0.4.1-2) unstable; urgency=medium
* Adjust to build with kernel 5.15. Closes: #1000357.
-- Stephen Kitt Mon, 22 Nov 2021 18:24:42 +0100
** Changed in: ddcci-driver-linux (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are
Do you have full reproducer and example?
Because it is possible that subprojects vendor incompatible and obsolete
cmake files, as it is often been discovered to be the case.
** Changed in: cmake (Ubuntu)
Status: New => Incomplete
** Changed in: boost1.71 (Ubuntu)
Status: New =>
I'm not sure why we still have boost1.71 in jammy still, as everything
should have moved to boost1.74.
boost1.71 is still the default one in focal.
** Also affects: cmake (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
On Tue, Nov 23, 2021 at 1:40 PM Jason A. Donenfeld
<1892...@bugs.launchpad.net> wrote:
>
> I think he meant to post this on
> https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317
>
That makes a lot more sense. Commented my opinion there about the need
for key generation tooling.
My personal opinion is that we do need tools to setup and configure
wireguard from start to finish in Main. That does include tooling to
generate the keys.
It would be nice to further develop wireguard package such that by
default it integrates with the default Ubuntu networking stack
@ahasenack I feel a bit lost here. This bug report is about how one
should or shouldn't propagate DNS servers after establishing a wireguard
based connection.
This has nothing to do w.r.t. creating keys.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for working with OpenSSL upstream, explaining the issue at
hand, for everyone to eventually understand what is going on, and
finally coming up with a solution on the OpenSSL side of the APIs that
is accepted by upstream into development v3 branch and stable 1.1.1
branch.
I have started
Public bug reported:
[Impact]
* Engine crashes when loading the configuration more than once
* Upstream started to avoid loading engines twice by using dynamic ids
to track the loaded engines correctly
* OpenSSL 3 merge https://github.com/openssl/openssl/pull/17073 (bugfix
& testcase)
*
Public bug reported:
BUILD & CLEAN scripts should support DESTDIR option
When paths are mangled in the BUILD & CLEAN scripts it would be nice if
it injected DESTDIR variable support. Such that one could BUILD/CLEAN
modules in a different target directory when the bits directory is read
only.
**
Public bug reported:
Ubuntu kernel modules are stripped prior to signing:
$(build_cd) $(kmake) $(build_O) $(conc_level) modules_install $(vdso) \
INSTALL_MOD_STRIP=1 INSTALL_MOD_PATH=$(pkgdir)/ \
INSTALL_FW_PATH=$(pkgdir)/lib/firmware/$(abi_release)-$*
Public bug reported:
grep nv-interface.o -r .
./CLEAN:rm -f nvidia/nv-interface.o
./BUILD:/usr/bin/ld.bfd -r -o nvidia/nv-interface.o nvidia/nv.o nvidia/nv-pci.o
nvidia/nv-acpi.o nvidia/nv-cray.o nvidia/nv-dma.o nvidia/nv-i2c.o
nvidia/nv-mmap.o nvidia/nv-p2p.o nvidia/nv-pat.o nvidia/nv-procfs.o
> Do we even know for sure this krb5-k5tls is enough for fips
compliance, and that it replaces *all* crypto code in kerberos with
openssl calls?
No it does not. But intention is to make the over the network
communications with TLS to be FIPS-TLS compliant which is cheaper to
certify when reusing
Autopkgtests have now all passed.
--
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:
Netrome smartnic is 10x the price of RPi. It is unlikely that one will
run ovs on armhf successfully. And i think even arm64 variants of RPi
may be overwhelmed by ovs as well.
Imho it makes sense to disable Netrome smartnic driver in the raspi
kernel flavour and also remove/filter netrome
@arighi suggests used to be installed when one used to provide "needs-
suggests" restrictions or some such, but that got deprecated, so no
suggests are not getting installed by default.
However, we have a multi year MIR to seed and install nftables by
default let me check the status of that
https://media.giphy.com/media/FoH28ucxZFJZu/giphy.gif
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887187
Title:
[MIR] nftables
To manage notifications about this bug go to:
@chaoqin
In https://bugs.launchpad.net/intel/+bug/1842239, the glibc patches
point at https://gitlab.com/x86-glibc/glibc/-/commits/users/hjl/cet/2.31
which we have been applying. Currently we ship them as a backported
patch see
Public bug reported:
Can't cd to (debian/ubuntu-core-initramfs/usr/share/doc/ubuntu-core-initramfs/)
changelog: Not a directory
at /usr/bin/dh_strip_nondeterminism line 86.
dh_compress -a -O--buildsystem=meson\+ninja
-O--sourcedirectory=vendor/systemd
cd debian/ubuntu-core-initramfs
** Changed in: initramfs-tools (Ubuntu)
Status: New => Triaged
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Also affects: initramfs-tools (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: initramfs
@ Chao Qin (chaoqin) @anthonywong
Do we also need to patch glibc to turn on CET support? Most of Ubuntu
binaries have CET enabled, but I thought there was still a patch needed
to turn the CET support on due to changes in the CET patches done as per
kernel upstream feedback. Or is this patch
$ less pc-kernel_5.4.0-90.101.1_amd64.snap | grep regulatory
-rw-r--r-- root/root 4160 2021-08-29 20:49 /firmware/regulatory.db
-rw-r--r-- root/root 1182 2021-08-29 20:49
/firmware/regulatory.db.p7s
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
201 - 300 of 9162 matches
Mail list logo
