** Changed in: ubuntu-power-systems
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1657646
Title:
[20.04] Missing
flock will not block inotify or udev events being emitted.
See
https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L322
https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L409
it will prevent udevd from running the rules against it. Thus
effectively the event will be
@ Cloud init team, do we want to try changing cloud-utils to use a lock?
And like have a canary "only use locked codepath on this region" such
that we can assert through testing that this no longer happens with new
code, but does with old code.
--
You received this bug notification because you
Some observations:
* growpart uses sfdisk without --no-tell-kernel option, meaning that it does
notify kernel about partition changes
* growpart later calls partx, which may be redundant / cause no changes or
events
* as a side note, partprobe, blockdev --rereadpt can also be used to reread
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1834875
Title:
cloud-init growpart race with udev
Status
On Thu, 31 Oct 2019 at 12:40, ts <1850...@bugs.launchpad.net> wrote:
>
> This was a problem before, I fixed it unlinking /run/systemd/stub-
> resolv.conf and linking /run/systemd/resolv.conf to /etc/
>
Neither of the paths mentioned are correct... did you mean one of:
** No longer affects: gcc-9 (Ubuntu)
** No longer affects: gcc-9 (Ubuntu Eoan)
** No longer affects: gcc-9 (Ubuntu Focal)
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux (Ubuntu Eoan)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because
This is my replacement "minimized" losetup.c that exhibits the problem.
Simply, drop this into klibc sources
and run:
./debian/rules build; sudo ./usr/utils/static/losetup
1 Argc before find_unused_loop_devices()
0 Argc after find_unused_loop_devices()
Argc values before and after did not match.
** Description changed:
[Impact]
- * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as
main(argc) is reset to zero, after ioctl() operations in a function call, quite
unexpectadly.
-
+ * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt,
+ as
given that dropins are not working well enough, we need something
better.
Possibly we need a generator that disables things harder.
Or update alternatives.
But the problem is that timesyncd should only be a fallback
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ [Impact]
+
+ * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as
main(argc) is reset to zero, after ioctl() operations in a function call, quite
unexpectadly.
+
+ [Test Case]
+
+ * sudo /usr/lib/klibc/bin/losetup -vf
+
+should not
** Patch added: "save-argc.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850184/+attachment/5301773/+files/save-argc.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
So, I'm not sure if this is a kernel headers/assembly bug (as ioctl is
used from there), gcc-9 bug, or the combination of the two.
I'm going to save argc, and use a saved copy for now, but this needs
deeper analysis. This sounds like a retpoline mitigation.
** Also affects: klibc (Ubuntu Focal)
so calling an ioctl seems to clear the global argc in klibc built with
gcc-9
163 if(ioctl (fd, LOOP_GET_STATUS,
) == 0)
(gdb) bt
#0 find_unused_loop_device () at usr/utils/losetup.c:163
#1 0x00401135 in main (argc=2, argv=0x7fffe618) at
device = find_unused_loop_device();
if (device == NULL)
return -1;
if (verbose)
printf("Loop device is %s\n", device);
if (argc == optind) {
printf("%s\n", device);
return 0;
}
file = argv[optind];
Somehow... argc == optind condition is false, and instead of
Rebuilding with gcc-8 => losetup works
Rebuilding with gcc-9 => losetup does not work
Rebuilding with gcc-9 & -fcf-protection=none & -fno-stack-clash-protection does
not work (and double checked that there are no gcc invocations in the build log
without those two options set)
--
You received
Public bug reported:
+ python2.7-config --includes
-I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7
+ set +x
+ python3.7-config --includes
-I/usr/include/python3.7m -I/usr/include/python3.7m
+ set +x
+ python3.8-config --includes
-I/usr/include/python3.8 -I/usr/include/python3.8
We will not be upgrading systemd to a new upstream release in 18.04.
W.r.t.
https://github.com/systemd/systemd/pull/9158
https://github.com/systemd/systemd/issues/8398
I thought we tried to backport that before, let me ping a few people if
that was the case or not.
** Bug watch added:
** Also affects: ubuntu-release-upgrader
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/1831736
Title:
[MIR] lz4 by
However 298.1MB is larger than old installs.
--
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/1831736
Title:
[MIR] lz4 by default
Status in Release Upgrader:
New
Sizing:
$ sudo du -sh /boot/* | grep -e grub -e 5.3.0-18
231K/boot/config-5.3.0-18-generic
8.0M/boot/grub
81M /boot/initrd.img-5.3.0-18-generic
4.5M/boot/System.map-5.3.0-18-generic
11M /boot/vmlinuz-5.3.0-18-generic
This is desktop system, amd64, with all microcodes, and
Linux kernel compression was changed to lz4 with bugs
https://bugs.launchpad.net/bugs/1840934
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@Dietmar May (dietmar.may)
All the kernel config options mentioned are enabled, at least in the Ubuntu
19.10 kernel. And i would have expected them to be on in previous releases too,
but didn't check.
I do wonder if ubuntu-drivers-common should detect that hw rng device is
available and offer
@seth this was only added very recently
https://github.com/systemd/systemd/commit/26ded55709947d936634f1de0f43dcf88f594621
Not on by default, and services need to order After=systemd-random-
seed.service to guarantee initialized random pool.
Low entropy is an issue, Excessive entropy usage is
To ellaborate, this is used by initramfs-tools-ubuntu-core as needed by
snapd for the Ubuntu Core product.
If that is all true, imho snappy team should be the bug subscriber and
drive the MIR to completion.
If it doesn't use/need abootimg the dependency should be dropped.
--
You received this
** Changed in: grub2 (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 lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1838525
Title:
LVM setup fails to install grub on
Pushed to
https://git.launchpad.net/~ubuntu-core-
dev/grub/+git/ubuntu/commit/?id=ef72a249cac219fee2ce5dec9648bb9717b16b30
Test-buiding, and uploading.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
@kat-amsterdam
The fixes we are introducing are for upgrades to 18.04, which by default
is not possible from 14.04.
Upgrade from 14.04 to 16.04 (trusty to xenial) has already been fixed a
while back in landscape client, thus if one uses uptodate client,
upgrades should succeed and reboot without
** Changed in: cron (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779767
Title:
Default cron PATH d
Cute, but things in the image build PPA should be MIRed.
This is in use in bionic and up from the sideload PPA.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to abootimg in Ubuntu.
https://bugs.launchpad.net/bugs/1846208
On Thu, 26 Sep 2019 at 20:11, Dan Streetman wrote:
>
> So, am I understanding right that such a system will have two ethernet
> interfaces with identical mac addresses? Isn't that an obvious problem
> that should be fixed instead?
Digging into this, It seems that it is an explicitly supported
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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/1769297
Ti
I believe this will be fixed in v2.41 snapd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779767
Title:
Default cron PATH does not include /snap/bin
Status in cron
I think this should land in Ubuntu as part of a regular snapshot upload
of binutils. I.e. without any special cherrypicking.
This may or might not be fixed in Eoan or f-cycle.
** Changed in: binutils (Ubuntu)
Importance: High => Wishlist
--
You received this bug notification because you are
Public bug reported:
cloud-images should not contain plymouth
** Affects: cloud-images
Importance: Undecided
Status: New
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status:
** Tags added: rls-ee-incoming
--
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/1769297
Title:
resume from hibernation broken when resume image is autodetected
@bryanquigley are you going to SRU that?
And please just that alone?
--
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/1796501
Title:
systemd-resolved tries to mitigate
Neither .25 nor .26 are the most current systemd versions in bionic.
Can you please double check your version numbers?
Could you please try 237-3ubuntu10.28 and check if problem persists?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: lvm2 (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Julian Andres
Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1842436
python-apt is fixed, and actually snapd will stay on xenial for now.
** Changed in: snapd (Ubuntu Eoan)
Status: New => Fix Released
** Changed in: snapd (Ubuntu Eoan)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
For a long time we had v243 rc in proposed, however we have identified
that it has too many regressions. And whilst regressions are getting
fixed upstream, we decided to pull it and start doing slightly more
incremental updates to systemd and jump to v243 final in stages.
Imho this shouldn't
I thought custom ipv6 MTU may not be lower than ipv4 one.
Hence request for 6000 ipv6 is not valid, when link is on 8958.
Can you try 9000?
On Wed, 28 Aug 2019, 15:41 Ryan Harper, <1671...@bugs.launchpad.net> wrote:
> I launched a bionic image on serverstack, updated the netplan.io to
>
Followup on my comments, are any changes required in networkd to support
this in bionic?
--
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/1671951
Title:
networkd should
** Information type changed from Private to Public
** Changed in: gzip (Ubuntu)
Status: New => Fix Committed
** Changed in: ubuntu-z-systems
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Also affects: systemd (Ubuntu Eoan)
Importance: Medium
Assignee: Shih-Yuan Lee (fourdollars)
Status: New
** Changed in: systemd (Ubuntu Eoan)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu Eoan)
Assignee: Shih-Yuan Lee (fourdollars) => Dimitr
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => 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/1668771
Title:
[SRU] systemd-resolved
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => 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/1835809
Title:
AMD Ryzen 3000 series fails
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => 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/1835581
Title:
networkd-dhcp4 does not set
And the VM in question has an arm64 kernel right? Have you tried an
armhf kernel?
--
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
Public bug reported:
hint zlib through due to osp1 regression
zlib is blocked in eoan-proposed due to linux-oem-osp1 regression, which
it cannot have caused as that package is compiled in bionic.
Please hint zlib through.
** Affects: linux-oem-osp1 (Ubuntu)
Importance: Undecided
authentication
- update test certificates
- add support for 'no_tlsv1_3' option
- testsuite fixes
- do not attempt unsupported renegotiation LP: #1832933
-- Dimitri John Ledkov Sun, 16 Jun 2019 01:48:12
+0100
In updates.
** This bug has been marked a duplicate of bug 1832933
*** This bug is a duplicate of bug 1832933 ***
https://bugs.launchpad.net/bugs/1832933
I'm pretty sure this is a duplicate and was fixed before. Let me try to
find the actual relevant package.
Possibly it may need a rebuild / publish in the security pocket, if it
was only published in
** Information type changed from Private to Public
--
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/1736704
Title:
[19.10 FEAT] openssl: SIMD implementation of poly1305
** Information type changed from Private to Public
--
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/1736705
Title:
[19.10 FEAT] openssl: SIMD implementation of chacha20
** Information type changed from Private Security to Public
** Changed in: zlib (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
this is cherrypickable, yes.
** Also affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1840640
https://github.com/systemd/systemd/pull/13352/commits/90ddac6087b5f8f3736364cfdf698e713f7e8869.patch
--
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/1840640
Title:
Using bionic as a base, and upgrading all the way to disco:
(bionic-amd64)root@ottawa:~# echo PURGE | debconf-communicate libpam0g:amd64
0
(bionic-amd64)root@ottawa:~# echo PURGE | debconf-communicate libpam0g
0
(bionic-amd64)root@ottawa:~# echo PURGE | debconf-communicate libc6:amd64
0
Fix committed status is only for SRU team to set on the distro tasks,
when an SRU upload is accepted.
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
** Changed in: gzip (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 gzip in Ubuntu.
** Information type changed from Private to Public
** Changed in: gzip (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1839123
Public bug reported:
snapd snap FTBFS in launchpad snap build due to python-apt regression in
eoan
https://launchpad.net/~xnox/+snap/snapd/+build/626157
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Affects: snapd (Ubuntu)
Importance: Undecided
** Also affects: apache2 (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/1787225
Title:
systemctl disable apache2 does
lz4
6644040 bytes read in 282 ms (22.5 MiB/s)
4466915 bytes read in 191 ms (22.3 MiB/s)
reboot time 39.49s
2019-07-04T16:54:38.012115+ localhost kernel: Unpacking initramfs...
2019-07-04T16:54:38.012178+ localhost kernel: Initramfs unpacking failed:
Decoding failed
uncompressed:
7330304 bytes read in 311 ms (22.5 MiB/s)
reboot time 39.39s
2019-07-04T16:54:38.050180+ localhost kernel: Unpacking initramfs...
2019-07-04T16:54:38.050253+ localhost kernel: Freeing initrd memory: 7200K
--
You received this bug notification because you are a member of
gzip
6644040 bytes read in 283 ms (22.4 MiB/s)
3889013 bytes read in 167 ms (22.2 MiB/s)
reboot time 40.31s
2019-07-04T16:54:37.997158+ localhost kernel: Unpacking initramfs...
2019-07-04T16:54:37.997230+ localhost kernel: Freeing initrd memory: 3840K
--
You received this bug
ls -latr initrd-lzma.img initrd-uncompressed.img initrd-gzip.img
initrd-lz49l.img | sort
-rwxr-xr-x 1 xnox xnox 2852487 Jul 5 00:19 initrd-lzma.img
-rwxr-xr-x 1 xnox xnox 3889013 Jul 5 00:21 initrd-gzip.img
-rwxr-xr-x 1 xnox xnox 4466915 Jul 5 00:22 initrd-lz49l.img
-rwxr-xr-x 1 xnox xnox
$ file initrd.img
initrd.img: LZMA compressed data, streamed
--
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/1832108
Title:
unmkinitramfs fails with lz4
Testing on cm3
switch to partitions #0, OK
mmc0(part 0) is current device
LOADBOOTENV
** Unable to read file uEnv.txt **
Running uenvcmd ...
ENVCMD
6644040 bytes read in 282 ms (22.5 MiB/s) (this is kernel)
2852487 bytes read in 123 ms (22.1 MiB/s) (this is initrd)
FAT: Misaligned buffer address
https://trello.com/c/CVhZRo2o
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1835257
Title:
update tzdata package to 2019b
Status in tzdata package in Ubuntu:
New
Bug
@hws as the status says on launchpad, both xenial and bionic are "in
progress". Awaiting SRU team reviews to be accepted into -proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Description changed:
[Impact]
- * Initramfs exports PATH to init, which is different than the expected
+ * Initramfs exports PATH to init, which is different than the expected
stock / compiled one, which results in slightly different runtime
behaviour of init, if it has environment
** Description changed:
+ [Impact]
+
+ * Initramfs exports PATH to init, which is different than the expected
+ stock / compiled one, which results in slightly different runtime
+ behaviour of init, if it has environment generators as well.
+
+
+ [Test Case]
+
+ * Disable snapd env
** Also affects: initramfs-tools (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug
In effect, I'm saying that we need to (a) fix systemd as per this bug
report (b) fix initramfs-tools (c) only then enable snapd env generator
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: initramfs-tools (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/1791691
Title:
PATH broken in
We have codepaths with and without initrd, which results in different
environment that systemd starts up with.
In bionic, initramfs-tools sets PATH to
PATH=/sbin:/usr/sbin:/bin:/usr/bin
In later releases, initramfs-tools sets PATH to
I think for this ticket we want:
commit b5872f95b64177212b2e129dcae15d91c46abbc8
Author: Yann Ylavic
Date: Fri Jun 15 11:12:19 2018 +
mod_ssl: disable check for client initiated renegotiations with TLS 1.3.
This is already forbidden by the protocol, enforced by OpenSSL, and
@ssp297
I believe this is different. renegotiation & client certs do not depend
on each other, and can be used together or separately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
@benjamin
I believe disabling TLSv1.3 via openssl.cnf tweak would work too,
without downgrading openssl.
Ie. Using something like this https://launchpadlibrarian.net/428208982
/cap-to-tls1.2.patch
(Probably without the CipherString line, which will raise security
requirements higher than the
Reproduce the problem:
# dpkg-query -W initramfs-tools lz4
initramfs-tools 0.131ubuntu19
lz4 1.8.3-1ubuntu1
# sed -i 's/gzip/lz4/' /etc/initramfs-tools/initramfs.conf
# update-initramfs -c -k test
# lsinitramfs /boot/initrd.img-test
cpio: premature end of archive
===
# sed
verification-needed-cosmic is blocking publishing the next initramfs-
tools update in cosmic.
Am I ok to trump the current initramfs-tools in cosmic-proposed with a
new upload?
Do we want to back out this change?
--
You received this bug notification because you are a member of Ubuntu
Touch
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833758
Title:
lvm2: vgcfgbackup in postinst takes several minutes
Status in lvm2 package in
Looking at autopkgtest regressions for python-tornado
http://autopkgtest.ubuntu.com/packages/b/bdfproxy/bionic/ppc64el has
never passed on bionic.
Can sru team please commit badtest hint for bdfproxy and release python-
tarnado?
--
You received this bug notification because you are a member of
downgraded bionic lxd container to bionic release / security packages only.
installing libssl1.1 from -updates fails with:
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned
error exit status 10
Processing
For initramfs-tools... please provide steps to reproduce the issue of
when initrds are expected to be created and are not, with steps how to
get in such situation (e.g. rm /boot/initrd*; update-initramfs...)
*without* requiring to use calamares, or specific images. ie. from any
regular normal
** Description changed:
+ [Impact]
+
+ * Systems that have in error removed debconf database fail to upgrade
+ libssl1.1 (as e.g. is known to be done in some vagrant boxes)
+
+ * libssl1.1 tries to use debconf template from libc6 package, but
+ doesn't ship one by itself as it should for
** Also affects: openssl (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: openssl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu
*** This bug is a duplicate of bug 1832919 ***
https://bugs.launchpad.net/bugs/1832919
@javier
I recommend instead:
dpkg-reconfigure libc6
dpkg --configure -a
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in
*** This bug is a duplicate of bug 1832919 ***
https://bugs.launchpad.net/bugs/1832919
Because your solution, answers the template without showing it to the
user without the appropriate warning as to what the implications of
setting it to true are.
** This bug has been marked a duplicate of
** Also affects: nginx (Ubuntu)
Importance: Undecided
Status: New
--
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/1833476
Title:
libssl1.1 version
** Also affects: systemd (Ubuntu Eoan)
Importance: High
Status: Confirmed
** Also affects: jackd2 (Ubuntu Eoan)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2
On Wed, 19 Jun 2019, 16:30 Sascha Silbe,
wrote:
>
> This update breaks salt-ssh 2016.11.2 (started from a different computer
> that's running Debian Stretch) on Ubuntu 18.04 (running on the machine
> being managed). Having Salt break from one day to the next for managing
> an LTS (!) release is a
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
*** This bug is a duplicate of bug 1833040 ***
https://bugs.launchpad.net/bugs/1833040
Public bug reported:
Jun 18 13:12:01 ottawa audit[7163]: AVC apparmor="DENIED"
operation="file_receive" profile="libvirt-2a671814-742d-4afc-867d-eae2349b336b"
pid=7163 comm="qemu-system-x86"
Public bug reported:
openssl should register libraries/restart-without-asking template or
handle gracefully when it is missing
** Affects: openssl (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Changed in: openssl (Ubuntu)
Assignee
** Description changed:
Hello!
After upgrade to
libssl1.1 1.1.1-1ubuntu2.1~18.04.2
openssl 1.1.1-1ubuntu2.1~18.04.2
on Ubuntu 18.04 server clients can't connect to ejabberd server:
2019-06-15 15:56:26.431 [warning]
<0.858.0>@ejabberd_c2s:process_terminated:290
** Also affects: erlang-p1-tls (Ubuntu)
Importance: Undecided
Status: New
** Changed in: erlang-p1-tls (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
I wonder if
https://github.com/processone/fast_tls/commit/9b25543cf1200e3b216996598771962461ea51c8
is enough to fix connectivity.
Things to test:
- ejabberd server works and accepts various clients
- ejabberd clinet works and connects to various servers
--
You received this bug notification
** Also affects: ejabberd (Ubuntu)
Importance: Undecided
Status: New
--
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/1832933
Title:
upgrade to libssl1.1
701 - 800 of 2744 matches
Mail list logo
