** 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
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
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:
i guess rebuilding gnome snaps with proposed on arm64 and testing that
new gnome snap on mantic for pi5 & x1s would help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604
Can you please explain how all of this is handled during dist-upgrades?
Have all the packages with affected profiles have versioned depends
added?
Is the featured _not_ turned on during dist-upgrade from jammy hwe to
noble, but only after reboot? (as the kernel is compatible, yet during
upgrade
my expectation is that udev should be running (somewhere, not sure if it
needs to be both the host and the lxd guest) and that it should process
the device using locks https://systemd.io/BLOCK_DEVICE_LOCKING/.
After that is done, the device should be safe to operate on, in a
consistent manner.
can you please move such updates into esm-proposed instead?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1813581
Title:
gpgme1.0 ftbfs in 18.04 LTS
Status in gpgme1.0
** Changed in: ubuntu-keyring (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1801762
Title:
Dual-signed things should be
something is wrong with your install
gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team-sublime-text-2.gpg':
resource limit
gpg: keyblock resource `/etc/apt/trusted.gpg.d/webupd8team-sublime-text-3.gpg':
resource limit
gpg: keyblock resource
it seems maybe incompatible gnupg was installed on the system?
gpg: fatal: /etc/apt/trustdb.gpg: invalid trustdb
** Changed in: ubuntu-keyring (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Something is broken with these files:
gpg: /etc/apt/trusted.gpg.d/webupd8team-y-ppa-manager.gpg: recurso de bloqueo
de claves: límite de recurso
gpg: /etc/apt/trusted.gpg.d/wine-wine-builds.gpg: recurso de bloqueo de claves:
límite de recurso
gpg: /etc/apt/trusted.gpg.d/yorba-ppa.gpg: recurso
something is wrong with your installation
gpg: invalid key resource URL `/etc/apt/trusted.gpg.d/home:osmc.gpg'
unrelated to this package
** Changed in: ubuntu-keyring (Ubuntu)
Status: New => Won't Fix
** Changed in: ubuntu-keyring (Ubuntu)
Status: Won't Fix => Invalid
--
You
SRU of debian keyring is also somehow counter productive. Most likely
usecase is to debootstrap unstable chroot. And for that to be done
correctly, often enough most recent debootstrap from debian is required
as otherwise the debootstrap might not complete, or complete incorrectly
(see all the
** Changed in: ubuntu-keyring (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1776329
Title:
apport-cli and
I think UEFI spec says to not check timestamps against current time. But
I am not sure it says it is ok to have signature time to be outside of
the cert validity. Which violates pkcs7 signature spec.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: bluez (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2041496
Title:
btmgmt --index broken in Mantic
Public bug reported:
[ Impact ]
* ubuntu-seeds were changed since last meta update
* to ensure correct upgrades; regenerate ubuntu-meta with contents / changes
done before release
[ Test Plan ]
* Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to
mantic install newly
Public bug reported:
Consistent naming of onboard NIC on all Pi on all Ubuntu
We should have the one distro config, to force consistent oboard NIC naming on
all Pi on all Ubuntu in the one place.
Let's find all the puzzle pieces and do it onces, and for all
** Affects: linux-raspi (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Invalid
** Changed in: apparmor (Ubuntu Lunar)
Status: Confirmed => Invalid
** Changed in: maas
Status: Fix Committed => Fix Released
** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received
** Changed in: ubuntu-cdimage
Status: New => Fix Committed
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Milestone: None => mantic-updates
--
You received this bug notification because you are a member of Ubuntu
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2038903
Title:
X13s didn't run
** Changed in: util-linux (Ubuntu Mantic)
Status: New => Triaged
** Changed in: util-linux (Ubuntu Mantic)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu Mantic)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete =>
Fix under review https://lists.ubuntu.com/archives/kernel-
team/2023-October/146015.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2038567
Title:
Disable
** Summary changed:
- Mantic 6.5.0-7 kernel causes regression in LXD container usage
+ Disable restricting unprivileged change_profile by default, due to LXD
latest/snap not yet compatible with this new apparmor feature
** Changed in: lxd (Ubuntu)
Importance: Undecided => High
** Changed
@rpocase please check internally I believe we have multiple azure & Aws
affected customers as per previous Salesforce escalations.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
** Changed in: util-linux (Ubuntu Mantic)
Milestone: None => ubuntu-23.10
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Current suspects are out of date apparmor features in livecd-rootfs
pending https://launchpad.net/ubuntu/+source/livecd-rootfs/23.10.55
kernel, apparmor, snapd, lxd, snapd again having fits about all of them
because of:
..
Make
@foundations & EDM can we have this backported all the way to trusty?
Xenial for sure.
** Tags added: rls-mm-incoming
** Information type changed from Public to Public Security
** Also affects: cloud-images
Importance: Undecided
Status: New
** Changed in: cloud-images
Importance:
ubuntu kernel team does not handle which drivers do or do not get
included in the initrd.
Since this is stuff that affects generic, these should be added by
default for modules=most mode by initramfs-tools.
please contact ubuntu foundations team about this.
** Package changed: linux (Ubuntu) =>
libcamera is not shipped on the images, and will be SRUed once tested.
** Changed in: pipewire (Ubuntu)
Status: Triaged => Invalid
** Changed in: libcamera (Ubuntu)
Milestone: None => mantic-updates
--
You received this bug notification because you are a member of Ubuntu
Touch
I believe reproducer is:
wget
https://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/ga-23.10/generic/boot-kernel
wget
https://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/ga-23.10/generic/boot-initrd
qemu-system-x86_64 -m 4G -smp 2 -nic
analysis at https://github.com/canonical/cloud-init/issues/4451
identified systemd regression that is affecting mantic
the kernel workaround is here for virtio-net, but not for all other NIC types,
i.e. e1000
and will likely affect other users too, not just cloud-init use case.
Request to
I request this to be considered release critical, as this prevents all
kernel team & certification team deployments of mantic systems,
inhibiting our ability to test SRUs on all architectures.
** Tags added: rls-mm-incoming
--
You received this bug notification because you are a member of
Does this have FFe?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1923363
Title:
Grant access to hardware (UARTs, I2C, etc.) via custom udev rules
Status in
I cannot tell if
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1923363 has FFe
or not for the uaccess addition on udev rules.
** Changed in: mesa (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I wonder if this is duplicate of
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202
And if the workaround in
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/2037202/comments/1 can keep us going
--
You received this bug notification because you are a member of
Public bug reported:
[ Impact ]
* HWE for Raspberry Pi 5 https://raspberrypi.com/5
[ Test Plan ]
* Private builds tested on all existing/supported Raspberry Pi SKUs in
armhf & arm64 variants
* No regressions on any existing SKUs
* Test that Raspberry Pi 5 boards work
[ Where problems
** Changed in: ubuntu-meta (Ubuntu Mantic)
Milestone: None => ubuntu-23.10
** Tags added: rls-mm-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2037425
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2037417
Title:
mantic arm64 images are
dracut-install has these options:
-P --mod-filter-nopathExclude kernel modules by path regexp
-N --mod-filter-nonameExclude kernel modules by name regexp
I'm more thinking along the lines of:
rm_modules_dir()
rm_modules()
Which would apply mod-filter-nopath / mod-filter-noname,
** Description changed:
please add api to repack initramfs
- from the results of unpackinitramfs, including all early & main dirs
+ from the results of unpackinitramfs, including all early & main dirs.
+
+ Userstory: i want to tweak my initrd in-place by replacing broken
+ libc.so.6 with a
** Description changed:
Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
almost seven weeks past it's original release date. But at least we have
an rc3 which is "only" two weeks old. Yes, we are getting close to
mantic release but this series is something we want for
** Description changed:
Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
almost seven weeks past it's original release date. But at least we have
an rc3 which is "only" two weeks old. Yes, we are getting close to
mantic release but this series is something we want for
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2036885
Title:
please add API to
Public bug reported:
please add api to repack initramfs
from the results of unpackinitramfs, including all early & main dirs
** Affects: initramfs-tools (Ubuntu)
Importance: Wishlist
Status: New
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Wishlist
--
You
Public bug reported:
Please add API to exclude things
It would be useful on Pi to say "yes include all graphics" but do
exclude "amdgpu, nvidia" drivers and firmware related to those.
Something along the lines of a "exclude filter list" for drivers &
firmware.
** Affects: initramfs-tools
software-properties (0.99.39) mantic; urgency=medium
* Add cjwatson patch to use getArchiveSubscriptionURL() for private PPAs
* Fix getArchiveSubscriptionURL() API call and tests
* Resolve adding private PPAs, which do not yet have a token LP: #1991553
-- Dimitri John Ledkov Fri, 25 Aug
** Also affects: firmware-sof (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1942260
Title:
compress firmware
** Changed in: linux-firmware (Ubuntu)
Milestone: None => ubuntu-23.10-beta
** Changed in: linux-firmware-raspi2 (Ubuntu)
Milestone: None => ubuntu-23.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
moving linux tasks to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
[ Impact ]
* orphan_file ext4 feature is available in Jammy v5.15 GA kernel
* It is to be enabled by default in Mantic
* fsck utility in jammy doesn't support orphan_file feature
* as part of forwards-compatibility support it would be useful for Jammy 22.04
LTS to be
Note this is still an issue, we just marked the given test case as
ignored on s390x going forward.
The https://launchpad.net/ubuntu/+source/iptables/1.8.7-1ubuntu6 upload:
* disabled 0002-ebtables-save-restore_0 on x86
* disabled 0009-needless-bitwise_0 on s390x
See the diff at
Given new incompatible RO and RW features in ext4 that v5.15 kernels
support, imho we should SRU backport of e2fsprogs on HWE grounds.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
** Description changed:
After installation of the FDE image, the system fails to boot due to
e2fsck failing with:
Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
feature(s): FEATURE_C12
this means that Jammy fsck fails against mantic created ext4
** Also affects: e2fsprogs (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2025339
Title:
FDE image fails to
** Description changed:
After installation of the FDE image, the system fails to boot due to
e2fsck failing with:
- Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
feature(s): FEATURE_C12
- Jun 21 12:48:19 ubuntu systemd-fsck[268]: e2fsck: Get a newer version of
All done, updated states and dropped sponsors subscribers
** Changed in: lxc (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
cross test of lxd fails, but i386 is not supported under ESM and i'm not
sure if i386 cross-arch autopkgtest is valid at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
autopkgteest & general usage of lxc 3.0.3-0ubuntu1~18.04.3 works with
host kernels on bionic's GA kernel and on hwe v5.4 kernels now.
verification done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received
cross test of lxd fails, but i386 is not supported under ESM and i'm not
sure if i386 cross-arch autopkgtest is valid at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
autopkgteest & general usage of lxc 3.0.3-0ubuntu1~18.04.3 works with
host kernels on bionic's GA kernel and on hwe v5.4 kernels now.
verification done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received
cross test of lxd fails, but i386 is not supported under ESM and i'm not
sure if i386 cross-arch autopkgtest is valid at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
autopkgteest & general usage of lxc 3.0.3-0ubuntu1~18.04.3 works with
host kernels on bionic's GA kernel and on hwe v5.4 kernels now.
verification done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received
it must be released in bionic-updates.
bionic-proposed is insufficient.
this follows the previous SRUs that fixed adt only, which were awaiting on "an
end-user visible sru to come in the future" which never has.
autopkgtest infrastructure has no ability to always test against proposed
pocket, a
I thought as part of this work we agreed to always unpack tar with
xattrs, but i'm not sure how to check if this was done or in place. will
investigate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
it does feel too many that it should be included by default, not sure
why the rest of the tty/serial drivers are not included, or how come
this one is not scoped under usb/hid, it is fairly small, and built on
arm64 only i think, thus it is useful to include by default - as at best
it is unlikely
Public bug reported:
$ snap connections --all | grep gnome
content -
gnome-3-28-1804:gnome-3-28-1804 -
content -
I'm not too sure if updates from sed1991s above are correct
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991975
Title:
dev file system is mounted without nosuid or
Public bug reported:
Enter code on ubuntu.com/pro/attach is not a clickable url.
however ubuntu.com/pro and "register new account" are.
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Screenshot from 2023-04-26 12-05-00.png"
vmlinuz-6.2.0-18-generic is good, so regression introduced in 6.2.0-19
abi, suspecting new apparmor stack
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012136
** Also affects: apparmor
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
alexsander-souza - if you can make this on per-distro basis that would
be great. Indeed empty (thus apparmor=1) should work on jammy and up,
but yes we can never know. And having it for lunar onwards would be
super nice, because yes overlayfs apparmor things got fixed a while back
and are expected
Lunar kernel will need SRU to be fixed up.
And separately, we could check if we can get rid of apparmor=0 for all
supported releases or not, in next mass release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Now about those bugs, it is true that apparmor and overlayfs used to not
play along.
Depending on support matrix we can attempt to turn apparmor back on.
Equally it is buggy that Ubuntu kernel does not work with apparmor
turned off.
It would be nice to investigate if we can at least enable
** Description changed:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which I
don't believe was part of the 20230319 serial. I don't have access to
the maas server, so I can't directly check any log
horay i managed to reproduce it locally.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2016908
I am annoyed that i cannot reproduce this locally outside of MAAS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2016908
Title:
Unable to deploy hosts with lunar images
@brian
I'm sorry, but with block-proposed-focal set it means that affected
users on riscv64 don't have uptodata pulseaudio.
can we please release this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
> The syslog-ng profile needs flags=(attach_disconnected) added to it
I failed to reproduce this with syslog-ng, but i guess i didn't
configure syslog-ng correctly to attempt attaching to /dev/log
I am also not sure of os-prober usage of logger is correct, and if it
actually wants to use that
Steps i can reproduce:
wget https://bugs.launchpad.net/ubuntu/+source/os-
prober/+bug/1826294/+attachment/5652492/+files/reproducer.sh
chmod +x reproducer.sh
sudo journalctl -f -e &
clear
sudo ./reproducer.sh
--
You received this bug notification because you are a member of Ubuntu
Touch
This is Ubuntu desktop install. rsyslog.service is active and running,
systemd-journald-dev-log.socket is running.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294
** Attachment added: "reproducer.sh"
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1826294/+attachment/5652492/+files/reproducer.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
yeah i get apparmor="DENIED" info="Failed name loookup - disconnected
path", which breaks os-prober.
** Changed in: os-prober (Ubuntu)
Importance: Undecided => Critical
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Changed in: rsyslog (Ubuntu)
Public bug reported:
Updating base-files at point releases is pointless, misleading, and
causes confusing and anxiety
Can we please stop updating base-files at point releases?
Building new installer media, and calling it with a new .N number is
good, and helps to differentiate what the initial
sponsored into unapproved queue
** Changed in: lxc (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc
One should use ubuntu-drivers CLI or Additional Drivers GUI to install
or switch nvidia graphics stacks from one major series to another. It
ensures that correct matching pre-signed kernel drivers are installed
together with the right userspace (with and without gui stacks, as
needed).
--
You
we ought to sponosr
http://launchpadlibrarian.net/453184210/lxc_3.0.4-0ubuntu1_3.0.4-0ubuntu2.diff.gz
into bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
Public bug reported:
apt source exact-source-package doesn't download the right source
package
when specifying source package, i expect the exact source package to be
downloaded.
example:
$ apt source linux-lowlatency => incorrectly downloads linux-meta-lowlatency
$ apt source --only-source
@sil2100 marked out test case in the bug report more clearly.
** Description changed:
This is *probably* the wrong package, but it's the best I can figure for
this, so here goes.
Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5,
UEFI, no secure boot. Testing
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=ubiquity
** Also affects: ubiquity (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Jammy)
Importance:
The best we can do, is to take notAfter time of the signing certificate
and add that as the signingTime, which will then be used by the Sign
command as given.
This will ensure the signature is within valid time-series.
I don't see an easy openssl API to sign things without any signature
setting PKCS7_NOATTR is not enough, as that only removes the smime
capabilities signed attribute, whilst signature timestamp remains.
--- ./regular.text 2023-01-23 11:42:49.992929526 +
+++ noattr.text 2023-01-23 11:42:59.288981639 +
@@ -128,7 +128,7 @@
object:
** Changed in: snapd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1993318
Title:
ZFS + Encryption installations of Ubuntu
In the triggered logs
PASS: test-execute
is present with new kernel and new systemd
-env=ADT_TEST_TRIGGERS=linux-meta-hwe-5.15/5.15.0.53.59~20.04.21 linux-
hwe-5.15/5.15.0-53.59~20.04.1 linux-signed-hwe-5.15/5.15.0-53.59~20.04.1
systemd/245.4-4ubuntu3.19'
all autopkgtests now pass https://people.canonical.com/~ubuntu-
archive/proposed-migration/focal/update_excuses.html#systemd
now testing if the new testcase is fixed with v5.15 kernels in focal.
Test request submitted.
Result history
https://autopkgtest.ubuntu.com/packages/systemd/focal/amd64
imho focal users on riscv64 deserve new pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1973734
Title:
FTBFS on riscv64 in focal
Status in pulseaudio
build successful
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.14/+build/23853226
** 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
https://code.launchpad.net/~xnox/ubiquity/+git/ubiquity/+merge/431831
should solve first boot post-install.
However, I don't think that will solve booting snapshot, or whenever on-
disk cached is missing/corrupted/out of date, and one tries to boot.
Seems quite scary.
--
You received this bug
on first boot /etc/zfs/zfs-list.cache/rboot /etc/zfs/zfs-
list.cache/bpool are either missing or empty.
this causes daemon-reload to go bananzas, as zfs generator runs for the
first time and generates many essential mount units. After that if cache
is populated, generators on boot & daemon-reload
subsequent boots are fine.
i wonder if we have a race somewhere, for example. On first boot zfs
cache is out of date. And zfs mount generator doesn't generate mounts
for all the mounted file systems.
then the first daemon-reload ever, will happen after zfs cache is
populated and the zfs volumes
1) doing first boot of encrypted zfs kinetic, edit boot cmdline to
include:
systemd.mask=snapd.service systemd.snapd.seeded.service
systemd.mask=snapd.socket
crutially this prevents snapd seeding to complete which calls systemctl
daemon-relaod.
system boots normally
2) login into tty and check
** Attachment added: "system.journal"
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1993318/+attachment/5624966/+files/system.journal
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status:
1 - 100 of 2744 matches
Mail list logo
