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: z
** 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.
https://bug
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
alread
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 Rele
i wonder if things work fine if called with pkexec.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1958055
Title:
sudo apport-kde is in a different design (stripped
XDG_CUR
** Description changed:
+ [Impact]
+
+ * Optimization features included in jammy cause atypical alignment of
+ LOAD ELF sections. This in turn causes failure to execute binaries on
+ WSL1. Upstream have since integrated the optimization features included
+ in jammy, but also reverted alignment t
Used systemd packaging repo's ./debian/git-cherry-pick and gbp dch + gbp
tag to convert the cherry-pick request into a typical looking systemd
sru backport.
Submitted merge proposal to https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/+git/systemd/+merge/429491
will ask for revi
I can add maintainer script to check and remove expired copies of
0xC8CAB6595FDFF622 and then like print a message that one needs to
install ubuntu-dbgsym-keyring
Unfortunately, I cannot automatically ask apt to install ubuntu-dbgsym-
keyring if expired dbgsym key is detected on disk =/
--
You r
** 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 D
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: signingTi
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
timestamp
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_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)
Import
@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 done
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
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:
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 rec
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 3.0
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 s
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)
Importance:
** 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.
https://bugs
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 seed
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
Tit
> 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 all
** 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 flashke
** 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
** 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
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)
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 recommen
** 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
Stat
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, w
** 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 cowbuilder
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 rece
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 rec
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 de
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 `/etc/apt/trusted.gpg.d/webupd8team-tor-browse
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 s
** 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 ea
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
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.
Af
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 t
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
I am glad that this worked out fine now.
I am not sure there is time to fix this in 20.10, as it has only a few
months of support left. I hope that having libffi7 in 21.04 is enough.
** Changed in: pyopenssl (Ubuntu Groovy)
Status: Incomplete => Invalid
** Changed in: pyopenssl (Ubuntu)
My understanding of resilient boot is that there are multiple ESPs
trying to boot the same raid device.
If there is only one rootfs filesystem, boot that one. Which in case of
raid, there will be only one.
I'm more concerned about the case of two ubuntu-server preinstalled
images on two usb stick
I've rebuilt all the packages mentioned above in bileto ppa against
security pocket and pushed them to focal-proposed queue, ready for sru
review and accept.
All, but openafs which ftbfs now, and will need to be fixed up for v5.11
anyway. So it will be rebuild in security pocket with v5.11 fixes l
debdiffs are on https://bileto.ubuntu.com/#/ticket/4543
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1914279
Title:
linux from security may force reboots without complete dk
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf,
arm64) -> is a false negative. virtualbox-hwe is only supported on amd64
i thought.
https://autopkgtest.ubuntu.com/packages/v/virtualbox
https://autopkgtest.ubuntu.com/packages/v/virtualbox-hwe
Suggests that to be the case.
--
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 re
** 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
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
[Impact]
* openssl fails to talk to letsencrypt website past September 2021,
despite trusting the letsencrypt root certificate.
[Test Plan]
* Import staging cert equivalent to ISRG Root X1
https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem
* Import expire
** Information type changed from Public to Public Security
** Tags removed: letsencrypt
** Tags added: letsencryptexpiry
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/19289
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
--
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/1931725
Title:
initramfs-tools: use zstd
dpkg patch looks good to me.
did lintian patch locally and started to run the regression test suite
locally to see if anything else is tripped up.
working on reprepro changes too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Summary changed:
- initramfs-tools: use zstd as the default compression method
+ initramfs-tools & kernel: use zstd as the default compression method
** Description changed:
Turns out that loading is always the slow part in loading initramfs into
memory and decompressing it since decompre
@ IBM can you please review the upstream patch and merge it into the the
s390 tree ?
https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u
** Description changed:
Turns out that loading is always the slow part in loading initramfs into
memory and decompr
Vasily Gorbik is reviewing this patch.
--
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/1931725
Title:
initramfs-tools & kernel: use zstd as the default compression
lintian should be good in impish-proposed, but we should migrate it
first.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by
I wonder if this is ADT cloud failure.
--
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/1932354
Title:
systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
(T
The following packages have unmet dependencies:
systemd-tests : Depends: libsystemd0 (= 247.3-3ubuntu3.1) but 247.3-3ubuntu3
is to be installed
Depends: systemd (= 247.3-3ubuntu3.1)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Retrying these once.
--
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/1932354
Title:
systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
(Test dependencies a
** Also affects: hello (Ubuntu)
Importance: Undecided
Status: New
** Tags added: block-proposed-impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
I am told it is an apt bug, due to systemd package being phased.
See https://launchpad.net/bugs/1925745
--
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/1932354
Title:
syst
Public bug reported:
[Impact]
* initramfs-tools in impish has changed default initrd compression to
zstd. To allow compressing and uncompressing such initrds on Focal LTS
release we should backport zstd support in the mkinitramfs &
unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinit
** Changed in: initramfs-tools (Ubuntu Focal)
Status: New => In Progress
** Tags added: zstd
--
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/1932542
Title:
** Tags removed: block-proposed-impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib p
@sil2100 zstd depends was added in the devel series. Historically, we
only had the depends on the tool that is needed at a time for a given
series... ie. gzip, xz, lz4, zstd.
Given that zstd compressed initrds are not supported by the linux GA
kernel in Focal, I am hesitant to impose zstd dependen
http://launchpadlibrarian.net/543778464/initramfs-
tools_0.140ubuntu5_0.140ubuntu6.diff.gz for the depends change in
impish.
--
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
# mkinitramfs -czstd -o /boot/initrd.img-5.4.0-76-generic 5.4.0-76-generic
# unmkinitramfs /boot/initrd.img-5.4.0-76-generic foo
# ls foo/
bin conf etc init lib lib64 run sbin scripts usr
# dpkg-query -W initramfs-tools zstd
initramfs-tools 0.136ubuntu6.6
zstd1.4.4+dfsg-3ubuntu0.1
#
Public bug reported:
kmod add zstd support
* v27+ needs patches cherrypicked from v28
* v28+ needs new build-time deps adjusted
** Affects: kmod (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
decompression speed only needs to be faster than i/o speed, once that is
reached the best compression ratio results in the fastest bootspped.
for kernel image zstd is used with -22 --ultra, thus I can compare it
with zlib -9.
--
You received this bug notification because you are a member of Ubun
@cborntra
v5.13 ubuntu kernel's s390 configuration with zstd -22 --ultra
compression is 8.5 MB, whereas gzip -9 is 11M.
Thus for gzip to win at bootspeed the decompression speed has to
compensate for 2.5M of i/o and be faster than zstd.
Unaccelerated decompression comparison still gives me faste
** Also affects: initramfs-tools (Ubuntu Bionic)
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/1932542
Title:
Add supp
** Description changed:
[Impact]
- * openssl fails to talk to letsencrypt website past September 2021,
+ * openssl fails to talk to letsencrypt website past September 2021,
despite trusting the letsencrypt root certificate.
[Test Plan]
- * Import staging cert equivalent to ISRG R
** Patch added: "lp1928989.patch"
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1928989/+attachment/5507665/+files/lp1928989.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://
** Tags added: rls-ii-incoming
** Tags added: rls-jj-incoming
--
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/1965293
Title:
systemd/248.3-1ubuntu8.2 ADT test failure (tes
** Changed in: iptables (Ubuntu Impish)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incor
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-meta (Ubuntu)
Milestone: None => ubuntu-22.04
** Tags added: rls-ff-incoming
** Tags removed: rls-ff-incoming
** T
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 a
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
Ob
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
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net
# 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:
The newly enabled autopkgtest appears to regress on i386 =/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with i
And s390x =(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with iptables-nft
Status in iptables package in
** 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 syst
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
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https
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
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
o
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:
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 stde
** 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 fail
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 co
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 →
/lib/syst
** 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
Touch seeded packages, wh
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
Touch seeded packages, whi
** 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
uploaded into unapproved queue
--
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/1958904
Title:
autopkgtest is failing on jammy with "no space left on device"
Status
@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 b
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 when
** 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 parity,
** 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 linux
Assignee: 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 affe
1 - 100 of 2765 matches
Mail list logo
