Oh wait, we've been through something very like this before
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
a judicious application of flock may be the most correct solution
available.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Here is a backport of the partial fix to jammy
https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-
rootfs/+merge/460729
I'm not sure I am best placed to update this bug description to match
the SRU template though -- I'm not sure which builds are being affected
in practice and so shoul
** Description changed:
- In mantic, we migrated livecd-rootfs to use losetup -P instead of
- kpartx, with the expectation that this would give us a reliable, race-
- free way of loop-mounting partitions from a disk image during image
- build.
+ [impact]
+ In mantic, we migrated livecd-rootfs to u
FWIW there is some discussion upstream in these two issues:
https://gitlab.gnome.org/GNOME/folks/-/issues/140
https://gitlab.gnome.org/GNOME/glib/-/issues/3316
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3316
https://gitlab.gnome.org/GNOME/glib/-/issues/3316
--
You received thi
Public bug reported:
If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can access
the boot image as /dev/pmem0. But this is not accessible in the initrd;
presumably some modules are missing. Dimitri added some modules that are
Ah yes that was it, thanks so much!
--
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/1981385
Title:
initrd lacks modules to mount boot image from http boot
Status i
The version of subiquity in 22.04.1 supports this now.
** Changed in: subiquity
Status: Triaged => Fix Released
--
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/187
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Fix Released
** Changed in: livecd-rootfs (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a memb
I tweaked the version numbers slightly (ubuntu1 -> ubuntu0.1) and
uploaded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1999104
Title:
arm64: broken c++ exception han
> Is only asking kernel to scan the device; to then generate "kernel udev"
> events; for then udev to wakeup and process/emit "udev udev" events; and
> create the required device nodes.
>
It's not udev that creates nodes like /dev/loop1p1 though is it? That's
devtmpfs surely.
--
You received thi
Amazing debugging Dann. Until we can get a kernel fix, what's the way
forward here? Run losetup without -P, run udevadm settle, run partprobe
on the device (then maybe run udevadm settle again??)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Here's my workaround then https://code.launchpad.net/~mwhudson/livecd-
rootfs/+git/livecd-rootfs/+merge/459380
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045586
Titl
This looks mostly ok but the merge doesn't seem to account for the
apport hooks being in debian now -- the changelog still lists it as a
difference, the package-hooks dir is in the .dirs files twice, and I
think they might be installed twice.
--
You received this bug notification because you are
Verified:
root@focal-vm:~# dpkg -l locales | grep ^ii
ii locales2.31-0ubuntu9.7 all GNU C Library: National
Language (locale) data [support]
root@focal-vm:~# cp /etc/default/locale /tmp/locale
root@focal-vm:~# update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8
root@f
Verified:
root@146e5ef6a792:/# dpkg -l libc6
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=
Verified that the new version does not generated bogus lines on bionic:
root@lp-1892825-bionic:~# cp /etc/default/locale /tmp/locale
root@lp-1892825-bionic:~# update-locale --locale-file /tmp/locale LANG = C.UTF-8
root@lp-1892825-bionic:~# diff -u /etc/default/locale /tmp/locale
--- /etc/default/l
Oh heh Gunnar had done that already :) Doubly verified then.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1892825
Title:
update-locale not perform correctly sanity checks
S
Verified:
root@focal:~# dpkg-query -W libc6
libc6:amd64 2.31-0ubuntu9.2
root@focal:~# cp /etc/default/locale /tmp/locale
root@focal:~# update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8
root@focal:~# diff -u /etc/default/locale /tmp/locale
--- /etc/default/locale 2019-10-21 18:01:0
"so this is fixed already in f and later" - think you mean "b and later"
here?
--
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/1962332
Title:
xenial systemd fails to start
** Changed in: glibc (Ubuntu)
Status: New => 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/1942113
Title:
systemd unit test regression in autopkgtest (oomd
** Description changed:
[impact]
A simple typo using the update-locale script can render a system inoperable
without booting into single user mode or similar:
$ sudo update-locale LANGUAGE = en_US.UTF-8
$ sudo -s
sudo: pam_open_session: Bad item passed to pam_*_item()
sudo: policy
** Changed in: initramfs-tools (Ubuntu)
Importance: Medium => High
--
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/1958148
Title:
mkinitramfs is too slow
Status
Are using the docker packages from the Ubuntu archive? It doesn't quite
look like it but I'm not completely sure how to tell.
--
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/1
I should say here that I don't really know what changes to subiquity are
desirable here. I don't really like the idea of subiquity always using
set-name, that just feels wrong, but I can see the problem here too.
--
You received this bug notification because you are a member of Ubuntu
Touch seede
Adding a pam task, pam_env does some sanity checking of the input (e.g.
%=1 in /etc/default/locale gets ignored) so I don't see why an empty
variable name should cause a total failure. But will fix the update-
locale script too.
** Also affects: pam (Ubuntu)
Importance: Undecided
Status:
** Also affects: glibc (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Focal)
Importance:
Fwiw I reported this as a pam bug too https://github.com/linux-
pam/linux-pam/issues/395
** Bug watch added: github.com/linux-pam/linux-pam/issues #395
https://github.com/linux-pam/linux-pam/issues/395
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
** Description changed:
+ [impact]
+ A simple typo using the update-locale script can render a system inoperable
without booting into single user mode or similar:
+
+ $ sudo update-locale LANGUAGE = en_US.UTF-8
+ $ sudo -s
+ sudo: pam_open_session: Bad item passed to pam_*_item()
+ sudo: policy
I don't see an upload for focal either in the unapproved queue or in
proposed. Am I confused? resetting the status for focal to in progress
in any case.
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a membe
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Tags added: foundations-todo
--
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/1989969
Title:
autopkgtest TE
Ioanna are you going to take care of preparing patches for fixing the
stable releases? I marked the overall/kinetic task as fix released as
you say the bug is no longer present there.
** Changed in: lsb (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification becau
** Changed in: gdb (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1971474
Title:
SRU: Update gdb to the final 12.1 release in 22.0
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474 tracks the
update of gdb to the 12.1 final release. You could try installing gdb
from jammy-proposed and see if that helps?
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch se
It's unclear to me how the comment about the kernel panic and the
openssh upgrade failing are related to me, I'm afraid.
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
Argh that shouldn't have happened. I've retried both the builds (it
looks like they failed because of infrastructure issues), hopefully that
will fix it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://b
** Tags added: foundations-todo
** Changed in: vim (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1989973
Title:
focal: Vim 2:8.
Could you try the gdb from proposed? I think it should help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1990729
Title:
gdb crashes when run from VSCode
Status in gdb pack
Oh yikes I'm sorry for giving you incomplete advice. These are the
instructions to follow: https://wiki.ubuntu.com/Testing/EnableProposed
-- no building from source required!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb
This just needs to be backported to Jammy now?
--
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/1992688
Title:
firefox deb not installed
Status in firefox package in Ub
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
** Changed in: apport (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bu
I think the issue here is that snaps (with cgroupsv2) require a systemd
user session and some desktop environments do not set this up? It's not
clear to me what needs to change here -- should snapd be more tolerant
of this situation or should the other desktop environments change to set
the necessa
Kinetic has 12.1?
** Changed in: gdb (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1959832
Title:
new version available upst
fontconfig 2.13.1-4.4ubuntu1 built successfully for me in a kinetic
sbuild so I think this can be closed.
** Changed in: fontconfig (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
I think your /boot ran out of space during the upgrade.
--
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/1992727
Title:
package linux-image-5.15.0-50-generic 5.15.0-
There is a new version of gdb in jammy-proposed that might help. Can you
try that? (some pointers on how to do this at
https://wiki.ubuntu.com/Testing/EnableProposed)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubun
** Tags added: foundations-triage-discuss
--
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/1992979
Title:
kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
lintian errors do not count as a build failure. You could file this as a
bug in Debian if you like -- we'll pick up the fix from there in due
course.
** Changed in: fontconfig (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch se
I think we're going to need more output that than to help you debug
this.
** Changed in: krb5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.ne
Hi, this looks mostly very good! I have some tiny nitpicks:
1) It's good to mention the patches that are being dropped in the changelog
entry.
2) There are some whitespace changes in the bottom of the changelog that you
could drop if you felt like it.
--
You received this bug notification beca
Thanks, this looks good to me but out of an abundance of caution (this
is sudo, after all), I'm going to get Marc from the security team to
take a look -- it seems the upstream fixes for the CVE are a bit
different from the ones currently in Ubuntu and I'd like him to verify
that we think upstream
The upstream bug request has a PR that seems to fix the issue already. I
guess if it gets accepted upstream we can think about backporting the
fix to stable releases in the fullness of time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
That said, we could fix this issue in curtin by searching for a device
with specified serial by just looking through the udev db directly
rather than by globbing in /dev/disk/by-id. In fact I thought we already
did that! But apparently not.
--
You received this bug notification because you are a
These seem to have both passed on retry...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1891486
Title:
vim ftbfs in focal (armhf, ppc64el)
Status in vim package in Ubuntu:
So I don't have the faintest idea what caused this to start failing but
the issue here is in mir:
int (*real_open)(char const *path, int flags, mode_t mode);
*(void **)(&real_open) = dlsym(RTLD_NEXT, "open");
return (*real_open)(path, flags, mode);
The declaration for real_open here
Martin, right I thought I'd said that in my comment too about the
prototype in the header but apparently I only thought it really loudly,
or something :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
http
Simon, no fix has been uploaded yet?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1934995
Title:
Broken on ppc64el (toolchain bug?)
Status in glibc package in Ubuntu:
At a very quick glance, Simon's patch looks a bit closer to the pull
request than the one in comment #4, so if you could test that soon that
would be good.
Simon, aside from debian/patches/lp1932010-ibm-z-add-vectorized-
crc32-implementation.patch which I'm not sure I'm competent to review
beyond
I made the changes iii suggested and uploaded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1932010
Title:
[21.10 FEAT] zlib CRC32 optimization for s390x
Status in Ubuntu
Public bug reported:
diffutils ftbfs with glibc 2.34 because of gnulib issues around SIGSTKSZ
no longer being constant. diffutils 3.8 was released with an updated
gnulib and builds fine with glibc 2.34
(https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=diffutils)
s
Is this only seen with glibc 2.34?
--
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/1940635
Title:
systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on
armhf
We must be hitting this line, right?
https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/convert_scm_timestamps.c;h=00c934c4135f0d4256068adcf23a3de024fadd43;hb=HEAD#l87
IOW, ddstreet was right in comment #10.
--
You received this bug notification because you are a member of
So what is going on is this:
In icmp6_receive systemd passes a buffer for control messages to recvmsg
that is only big enough for the messages it expects to receive. glibc
now attempts to append an extra control message to the buffer
(translating SO_TIMESTAMP / COMPAT_SO_TIMESTAMP_OLD to SO_TIMEST
I filed a bug in systemd (although I'm not really sure it's systemd's
bug) https://github.com/systemd/systemd/issues/20564 and uploaded a
simple workaround (in systemd) that passed systemd armhf autopkgtests in
my PPA. Fingers crossed!
We should come back and review this fix after glibc has migrat
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
--
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/1940635
Title:
systemd-networkd failing to acquire a DHC
The difference I can see between the passing and failing run is that in
the failing run, systemd and glibc are upgraded before the "rebooting
testbed after setup commands that affected boot" and in the passing run
they are upgraded after that step. That doesn't make a lot of sense but
maybe the tes
So yes, that is what matters. When a system is booted with systemd
248.3-1ubuntu3, it sets up the cgroups in "hybrid" mode. systemd
248.3-1ubuntu5 defaults to "unified" mode but simply upgrading the
package does not redo this setup -- the system remains in hybrid mode.
The test cases that are faili
Hmm something is off here: I'm pretty sure containers inherit their
cgroups mode from the host, so the default hierarchy changing in the
systemd in the archive shouldn't affect anything. I can reproduce the
failure of this report by adding systemd.unified_cgroup_hierarchy=1 to
the kernel command li
So it turns out that if you have security.nesting=true set on the
container, then the systemd in proposed manages to set up a unified
hierarchy and the test fails. This is the difference between the
production test runs and mine.
I filed a bug upstream https://github.com/systemd/systemd/issues/205
Sigh yes it does look like you found amd fixed the same bug. Oh well at
least I learnt some things yesterday.
--
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/1942113
Title:
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1940505
Title:
monero FTBFS on riscv64
Status in binutils:
Fix Released
Status in binutils
Public bug reported:
Reported upstream as https://gitlab.gnome.org/GNOME/gcr/-/issues/84.
Looks like it might be a flaky test?
** Affects: gcr (Ubuntu)
Importance: Undecided
Status: New
** Tags: ftbfs update-excuse
--
You received this bug notification because you are a member o
(I confirmed by bind mount shenanigans that putting the libgcc_s.so.1
from the core snapd into the snapd snap makes this work)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/
So what is going on here is that libc is trying to load libgcc_s.so.1
and as it is not in the snap it ends up loading it from the host.
Apparently in all releases from xenial through to hirsute this has
worked but for whatever reason it does not work on impish. I think the
appropriate fix is for th
https://github.com/snapcore/snapd/pull/10757
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1943077
Title:
snapd fails to autopkgtest on mksquashfs, which is looking for
Did the patch ever get sent to libc-alpha?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1940996
Title:
test failure - test-regex
Status in grep:
In Progress
Status in gr
This is fixed in the 23.10 dailies. I'm not sure it's really practical
to fix this for the next 22.04 point release, unfortunately.
** Changed in: ubuntu-meta (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: subiquity
Status: Triaged => Fix Released
--
You received this b
Is the point here that dhcpcd -1 exits immediately if it finds no
devices, even if it has a -t argument?
--
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/2037202
Title
https://code.launchpad.net/~mwhudson/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/452586 might be a fix? Not tested at
all.
--
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
** Tags added: foundaitions-todo
** Tags removed: foundaitions-todo
** Tags added: foundations-todo
--
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 i
** Also affects: util-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/2037417
Title:
mantic images after 20230917
So the cause of this, I am fairly sure, is the new "libmount-mountfd"
support in util-linux which seems to have the consequence that "mount -o
remount $mountpoint" fails for an overlay that references paths no
longer available in the current mount namespace.
You can see the discussion of a similar
Ah no it's a bit simpler than that https://github.com/util-linux/util-
linux/issues/2528.
--disable-libmount-mountfd-support looking better tbh.
** Bug watch added: github.com/util-linux/util-linux/issues #2528
https://github.com/util-linux/util-linux/issues/2528
--
You received this bug not
There is also a problem in dhclient where it forks off the daemon and
exits before writing the pidfile which needs a separate fix.
** Changed in: isc-dhcp (Ubuntu Disco)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Also affects: kmod (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Also affects: kmod (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you
Public bug reported:
This looks an awful lot like bug 1645232 but that is claimed to be
fixed:
mwhudson@ringil:~/tmp$ mkfs.ext4 -V
mke2fs 1.44.1 (24-Mar-2018)
Using EXT2FS Library version 1.44.1
mwhudson@ringil:~/tmp$ dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img
0+0 records in
0+0
So this was somehow caused by the ftbfs fix for klibc. On my eoan
system:
mwhudson@anduril:~/images$ sudo /usr/lib/klibc/bin/losetup -f
loop: can't get info on device /dev/loop30: No such device or address
mwhudson@anduril:~/images$ sudo apt install klibc-utils=2.0.6-1ubuntu1
libklibc=2.0.6-1ubun
We found the issue -- I think xnox is going to report it via proper
channels. But basically it's this:
sizeof(dev_t) = 4 sizeof(__kernel_old_dev_t) = 8
This makes the kernel's loop_info 8 bytes bigger than klibc's and so the
kernel is writing past the end of the loopinfo on the stack, which unti
Public bug reported:
Booting the latest focal live server daily gets us this:
Begin: Disabling snap refresh... ... date: unrecognized option
'--iso-8601=seconds'
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu5) multi-call binary.
Usage: date [OPTIONS] [+FMT] [TIME]
Display time (using +FMT), or set
Turns out to be easy to fix in casper.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: casper (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to in
Public bug reported:
In an eoan armhf container on a disco arm64 vm:
root@helped-oyster:~# gdb /bin/true
GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
...
(gdb) r
Starting program: /usr/bin/true
Program received signal SIGSEGV, Segmentation fault.
0xf7fc8ee0 in ?? () from /lib/ld-linux-armhf.so.3
It happe
I don't really know what is happening here but I suspect pretty strongly
it's related to systemtap static probes, because if I do this:
root@helped-oyster:~# cp /lib/ld-linux-armhf.so.3 .
root@helped-oyster:~# objcopy -R .note.stapsdt ld-linux-armhf.so.3
ld-linux-armhf.so.3-nostap
root@helped-oy
No.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1841006
Title:
gdb reports a segfault in ld-linux.so.3 on armhf
Status in binutils package in Ubuntu:
New
Bug descr
I finally got around to reporting this upstream as
https://sourceware.org/bugzilla/show_bug.cgi?id=25215
** Bug watch added: Sourceware.org Bugzilla #25215
https://sourceware.org/bugzilla/show_bug.cgi?id=25215
--
You received this bug notification because you are a member of Ubuntu
Touch seed
I think this got fixed in ubuntu11, but there are more test failures
yet, see bug 1854237
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1853383
Title:
autopkgtest regressi
Ah oops, this one fell through the cracks. Should try to do a quick fix.
** Package changed: subiquity (Ubuntu) => subiquity
** Changed in: subiquity
Status: New => Triaged
** Changed in: subiquity
Importance: Undecided => High
--
You received this bug notification because you are a
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Eoan)
Importance
Public bug reported:
This probably made sense in 2012 but in focal all servers are going to
have cloud-init installed. I *think* apport should consult "< /run
/cloud-init/instance-data.json jq .v1.platform" but someone from server
should probably check that.
** Affects: apport (Ubuntu)
Impor
Chad pointed out in IRC that cloud-init query platform is the supported
way to get that information, but also that cloud-init query in general
can probably be the source for all this information, on clouds other
than EC2 as well.
--
You received this bug notification because you are a member of U
I had a quick look at unbound, it seems quite difficult. People who
install unbound probably want it so they can have DNSSEC supported in
their local resolver which we can't really do by integrating with
resolved. OTOH, if installing unbound replaces (in some sense) resolved
and everything else int
1 - 100 of 202 matches
Mail list logo
