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
** 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
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
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
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
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,
> 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
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
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
** 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
** 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
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.
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
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
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
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.
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
** 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
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
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
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
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
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
** 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.
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
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
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
** 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
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.
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
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
** 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
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
** 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
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
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.
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
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
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
---
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:
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
** 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
** 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: 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
"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
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
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
** 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
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
** 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)
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
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
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.
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
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
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
(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.
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
** 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
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:
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
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
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
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
** 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
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
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
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
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
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)
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
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
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:
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.
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 **)(_open) = dlsym(RTLD_NEXT, "open");
return (*real_open)(path, flags, mode);
The declaration for real_open here does
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
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
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
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
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
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:
And verified on xenial:
(client-server-5)mwhudson@anduril:~/src/subiquity$ ssh ubuntu@10.187.142.193
"sh -c 'dpkg-query -W libpam-modules; type go '"
libpam-modules:amd641.1.8-3.2ubuntu2.1
go: not found
(client-server-5)mwhudson@anduril:~/src/subiquity$ lxc exec lp1659719-xenial --
apt
Verified the new upload on xenial:
root@xenial-pam-play:~# dpkg -l libpam-modules
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
** Changed in: pam (Ubuntu Xenial)
Status: Won't Fix => In Progress
** Changed in: pam (Ubuntu Xenial)
Assignee: Don van der Haghen (donvdh) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Great thanks for testing. I've uploaded to groovy -- th ext step is to
SRU to focal I guess -- can you provide an impact statement / test case
/ regression potential as described at
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ?
--
You received this bug notification because you
Hi I've updated the patch to the latest version and uploaded the package
to my PPA as version 1.2.11.dfsg-2ubuntu2~ppa2 which should appear here
soon:
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib.
Can you test this on your hardware and let me know how it
** Changed in: zlib (Ubuntu Groovy)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Michael
Hudson-Doyle (mwhudson)
** Changed in: zlib (Ubuntu Focal)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a
Great thanks for confirming. Are you able to test the packages mentioned
above? We don't have z15 hardware to test on (also bug 1884514 while
you're here :-p)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
And bionic:
mwhudson@anduril:~$ ssh ubuntu@10.187.142.63 "sh -c 'dpkg-query -W
libpam-modules; type go '"
libpam-modules:amd641.1.8-3.6ubuntu2.18.04.1
go: not found
mwhudson@anduril:~$ lxc exec test-pam-bionic -- apt install -y
libpam-modules/bionic-proposed
Reading package lists... Done
The focal autopkgtest failures are in cyrus-imapd:
Mail::JMAPTalk version 0.15 required--this is only version 0.13 at
./Cassandane/Cyrus/JMAPCore.pm line 47.
BEGIN failed--compilation aborted at ./Cassandane/Cyrus/JMAPCore.pm line 47.
This seems very unlikely to be due to pam, and it happens
Verified on focal:
mwhudson@anduril:~$ ssh ubuntu@10.187.142.128 "sh -c 'dpkg-query -W
libpam-modules; type go '"
libpam-modules:amd641.3.1-5ubuntu4
go: not found
mwhudson@anduril:~$ lxc exec test-pam-focal -- apt install -y
libpam-modules/focal-proposed
Reading package lists... Done
Hi, is it correct to say that fixing this bug and bug 1882494 just
requires updating the patch we have to the current state of the
https://github.com/madler/zlib/pull/410 pull request? If so, the package
that is currently building at
** Description changed:
- ssh can't call a binary from a snap, it will only work using the full
- path.
+ [impact]
+ ssh can't call a binary from a snap, it will only work using the full path.
+
+ [test case]
+ Create a container. Install the go snap (and make sure golang-go is not
installed).
** No longer affects: snapd (Ubuntu)
** No longer affects: snapd (Ubuntu Groovy)
** Also affects: pam (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Xenial)
So one solution to this would be to run "vgck --updatemetadata" on each
vg in postinst... would there be downside to that?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
I've filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964580
about the pam ordering issue.
** Bug watch added: Debian Bug tracker #964580
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964580
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Here's a better patch that I've tested this time. I dropped the code
around adding /usr/local/games to PATH as that was in trusty.
** Changed in: pam (Ubuntu Groovy)
Status: Confirmed => In Progress
** Patch added: "pam_1.3.1-5ubuntu4_1.3.1-5ubuntu5.patch"
It's easy enough to unconditionally add /snap/bin to path, see attached,
but I can't really see a clean way to only have it present in the $PATH
when snapd is installed (without code changes to pam_env, anyway).
** Patch added: "pam_1.3.1-5ubuntu4_1.3.1-5ubuntu5.patch"
This got fixed quite a while ago I think, apologies for the lack of
updates.
** 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 hostname in Ubuntu.
** Changed in: subiquity
Status: New => Fix Released
--
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/1862846
Title:
Crash and failure installing focal
Status in
1 - 100 of 192 matches
Mail list logo
