*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
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
** 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
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:
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
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
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
** 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.
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
** 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
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
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
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 <
** 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
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
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
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
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
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
** 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
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
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.
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
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:
** 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
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.
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
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.
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
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.
) => 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 t
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
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
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
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");
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:
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
** 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
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
# 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
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.
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:
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
# 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:
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
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:
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
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
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
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
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
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
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
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
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
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.
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
** 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
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
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
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
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
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
** 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
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
** 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
** 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:
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
** 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
** 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
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
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.
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
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
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
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
** 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
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
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
** 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
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:
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:
** 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
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:
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
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
/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 =>
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
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
** 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 =>
** 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.
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.
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
** 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
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
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
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
** 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.
** 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
** 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
1 - 100 of 9454 matches
Mail list logo
