untu Eoan)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
** Changed in: openssl (Ubuntu Eoan)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.lau
** Patch added: "cap-to-tls1.2.patch"
https://bugs.launchpad.net/ubuntu/bionic/+source/openssl/+bug/1832370/+attachment/5270755/+files/cap-to-tls1.2.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
So bionic-release, disco, eoan are all good.
Regressions are in bionic-updates|-proposed and cosmic.
I.e. regression introduced in 1.1.1, present in 1.1.1a, fixed in 1.1.1b
and later.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1832370
Title:
Una
** Changed in: openssl (Ubuntu Eoan)
Status: New => Fix Committed
--
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/1832421
Title:
openssl reboot needed message using
** Changed in: openssl (Ubuntu)
Status: Confirmed => Fix Committed
--
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/1832522
Title:
openssl maintainer scripts do not
** Tags added: regression-update
** Tags added: regression-release
--
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/1832659
Title:
openssl 1.1.1-1ubuntu2.1~18.04.1
Disco:
# dpkg-query -W openssl libssl1.1
libssl1.1:amd64 1.1.1b-1ubuntu2.2
openssl 1.1.1b-1ubuntu2.2
Run the procedure, got text output:
...
N8j0iLb0NtNIssnxRKKlw7NG4fGCOs7uHUbIcDg2u8nFM9bUoAQoUauRaNQjmWkZ
tx4U93+m6UnLSCxc9fyZWrax5mVL05C/AyB9H6NcfTYEyYyBPob5C4fG
-END CERTIFICATE-
Data
Cosmic
# dpkg-query -W openssl libssl1.1
libssl1.1:amd64 1.1.1-1ubuntu2.3
openssl 1.1.1-1ubuntu2.3
Run the procedure, got text output:
...
tEInj8E8hiIwr3qgnHEeaoHrk2v3H82zDSI6NFalcwqCVeLtP3SeLFNvBYovISBX
JQrpUFhq1/+PwOMogxfRZQBmS1Za0Yxd8VK12M5smfI4WRDbqUbmZfqA
-END CERTIFICATE-
Data Base
Removed /dev/null redirects and everything seems to be passing for
me
https://paste.ubuntu.com/p/4w5X6Rx3j9/
--
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/1832689
** Also affects: openssl (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Cosmic)
Is it possible to get output from that script without &>/dev/null
redirection? to get all the stdout and stderr messages?
** Also affects: plainbox-provider-tpm2
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu)
Status: New => Incomplete
** Changed in:
@Steve
Ubuntu 18.04 ships salt 2017.7.4 which has been patched for openssl
1.1.1 compatibility.
Please see:
https://launchpad.net/ubuntu/+source/salt/2017.7.4+dfsg1-1ubuntu18.04.1
salt (2017.7.4+dfsg1-1ubuntu18.04.1) bionic; urgency=medium
* Cherrypick two upstream patches to fix compat
The issue mentioned should be included in openssl 1.1.1b and hence fix
released in disco and eoan.
--
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/1832659
Title:
openssl
Can you please provide sources of your app / example of behaviour that
needs fixing?
For us to prepare an SRU, we'd need to provide the following details:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
Would you be able to provide details requested there? as in fill out the
below
Launched lxd container, with sshd & apache2 running and old ssl still
installed
# dpkg-query -W libssl1.1
libssl1.1:amd64 1.1.0g-2ubuntu4.3
Started journal monitoring to notice services restarts:
# journalctl -f &
Enabled -proposed, and checked that new libssl1.1 from proposed is
available
#
Run through CA setup, and ended up corrupting my terminal due to binary
output using the current bionic-updates 1.1.1-1ubuntu2.1~18.04.1
Upgraded to:
# dpkg-query -W openssl libssl1.1
libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.2
openssl 1.1.1-1ubuntu2.1~18.04.2
Rerun the procedure and ended up with
** Description changed:
[Impact]
- * openssl command line utility option parsing has regressed in 1.1.0i+
+ * openssl command line utility option parsing has regressed in 1.1.0i+
and produces binary output, where text output is expected, breaking
applications that parse that.
Public bug reported:
[Impact]
* Major libssl ugprades require services to be restarted, for them to continue
to function correctly at runtime.
* The maintainer scripts were not adjusted to trigger.
[Test Case]
* Install bionic from release pocket and install ssl using daemon e.g.
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1777512
Can you please provide the Ubuntu version
In a terminal
lsb_release -a
perhaps even better
uname -a
attach the appropriate logs?
/var/log/syslog
or possibly
/var/log/messages
your dbus conf, everything in
/etc/dbus-1/
--
You received this bug notification because you are a
** Patch added: "disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1828215/+attachment/5270241/+files/disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
** Patch added: "cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1828215/+attachment/5270242/+files/cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
** Patch added: "bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1828215/+attachment/5270243/+files/bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
** Tags added: rls-ee-incoming
--
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/1832370
Title:
Unable to configure or disable TLS 1.3 via openssl.cnf
Status in openssl
** Bug watch added: Debian Bug tracker #930366
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930366
** Also affects: initramfs-tools (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930366
Importance: Unknown
Status: Unknown
** Description changed:
+ [Impact]
+
Public bug reported:
[Impact]
* 18.04 LTS release with a long support time frame
* There are two versions of OpenSSL shipped in 18.04:
- obsolete 1.0.2
- current long term supported 1.1.1 series
* OpenSSH in 18.04 is the only package in main using libcrypto from 1.0.2
* The fact that
Note one can create .deb packages with arbitrary version numbers not
matching what is listed in debian/changelog.
And this package does that, for Spaß and clarity.
And both builds appear to produce binaries with version numbers
matching the underlying source gcc versions e.g. both builds produce:
No, we do not wish to support weak-ssl-ciphers, they are long obsolete
and dead.
If you need to access acient servers or use acient clients you can e.g.
launch precise in a lxd container with $ lxc launch ubuntu:precise
Which ones are you specifically after?
** Changed in: openssl (Ubuntu)
(specifically published RFCs defining the relevant digest-algo /
signature types format to be used in x.509 certificates / or any pki
generically. Just the definition of the math to calculate the digest is
not enough)
** Changed in: openssl (Ubuntu)
Status: Incomplete => Opinion
--
You
I don't think it follows.
For example, with an RSA key I can use SHA3-512.
Signature Algorithm: RSA-SHA3-512
The point is, that digests are not independant, and one cannot just use
any as they need to have well known identifiers as specified in the
relevant RFCs.
Ie.
built and passed all autopkgtests on all architectures.
** 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
reset index.txt, and resigned pkac with upgraded openssl in eoan, the
output is pure text and can be read/parsed by humans and machines.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
** Changed in: openssl (Ubuntu Eoan)
Status: Confirmed => Fix Committed
--
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/1828215
Title:
openssl ca -spkac output
Follow roughly https://blog.felipe-alfaro.com/2005/11/18/setting-up-
certificate-authority-ca-using-openssl/ to setup CA
Generate req & spkac => however somehow my spkac only had the SPKAC=
line so I had to edit in:
countryName=AU
stateOrProvinceName=Some-State
organizationName=Internet Widgits
Ship it!
** 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.
we really should not have published this SRU, as it has dependencies on
openssl 1.1.1 which is not published, and is thus now uninstallable.
=/
however it has been a while, so might as well wait for openssl 1.1.1 to
be published.
--
You received this bug notification because you are a member
Public bug reported:
unmkinitramfs fails with lz4 compressed initrds
Note:
$ lz4cat -t unmkinitramfs_Cz6Yl9
File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process
file: unmkinitramfs_Cz6Yl9
And
$ lsinitramfs /boot/initrd.img
kernel
kernel/x86
kernel/x86/microcode
I.e. instead of the current
$ cat debian/linux-firmware.postinst
#!/bin/sh
set -e
if [ -x /usr/sbin/update-initramfs ]; then
/usr/sbin/update-initramfs -u -k all
fi
#DEBHELPER#
It should do instead
$ cat cat debian/linux-firmware.triggers
activate-noawait update-initramfs
**
Normally, postinst should only hint a trigger to run initramfs update.
And not force creation of an initrd.
--
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/1792189
Public bug reported:
static ip= address configuration does not end up in netplan file
klibc ipconfig process ip=...:$proto and dumps the state into a file,
which is then parsed to generate runtime netplan configs.
For static ip configuration ipconfig parses $proto values "off" "none"
"static"
@Martin
Encrypted root is available in Ubuntu.
--
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/1382054
Title:
Add support for configuring VLAN interfaces in the
I will go with dracut syntax here:
vlan=:
And will only support the .id naming, e.g.:
vlan=eth0.1:eth0
As i'd think dracut syntax is more popular, despite being a bit
backwards parsing the pairs.
With added support, that phydevice is activated as well on s390x.
--
You received this bug
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Milestone: None => ubuntu-19.06
--
You received this bug notificatio
** Description changed:
Use `lz4 -9 -l` compression for initramfs by default as discussed on
ubuntu-devel.
This would also pull the lz4 package into main
https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html
[Regression Potential]
We are trying to optimize
** Description changed:
Use `lz4 -9 -l` compression for initramfs by default as discussed on
ubuntu-devel.
This would also pull the lz4 package into main
https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html
+
+ [Regression Potential]
+
+ We are trying to optimize
** Changed in: lz4 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
/usr/lib/apt/apt.systemd.daily should force set a Useragent
apt.systemd.daily, for all operations.
irrespective how/who/what invoked /usr/lib/apt/apt.systemd.daily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
Can you boot with old initrd from the boot menu options?
Can you unlock things by-hand from the initramfs shell, and continue the
boot by exiting the shell?
What is the expected layout of things that should be done? And what are
the contents of /etc/crypttab /etc/fstab ?
** Changed in: lvm2
** Changed in: livecd-rootfs (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/1831736
Title:
[MIR] lz4 by default
** Changed in: lz4 (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
** Changed in: live-build (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
Use `lz4 -9 -l` compression for initramfs by default as discussed on
ubuntu-devel.
This would also pull the lz4 package into main
https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
lz4 is now called with the legacy option on.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This is still not fixed.
** Changed in: systemd (Ubuntu)
Status: Fix Released => Confirmed
--
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/1803993
Title:
Password
Well, it's "better" but still failing.
http://autopkgtest.ubuntu.com/packages/systemd/eoan/ppc64el
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hahahhahaha
So
yeah
because the _host_ bootid is in use =) and you didn't reboot the host.
Specifically, everything in systemd reads
/proc/sys/kernel/random/boot_id and that appears to be the same as on
the host.
Maybe lxc/lxd should fake that file and generate new "boot_id" each time
Is that the full networkd config?
Slightly confused why enp3s0 is degraded. Does it have a cable plugged
in?
Could you tar up and share /run/systemd/netif ?
Does adding below
[DHCP]
ClientIdentifier=mac
to the enp3s0.2.network help?
--
You received this bug notification because you are a
Please attach output from networkd on boot prior to / without the extra
dhclient unit if you can.
$ networkctl | pastebinit
$ journalctl -b -u systemd-networkd | pastebinit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
How does your vlan .netdev unit looks like?
You need something that creates the vlan device on top of the selected
underlying device, ie.:
$ cat enp3s0.2.netdev
[NetDev]
Name=enp3s0.2
Kind=vlan
[VLAN]
Id=2
Without that, there won't be vlan device created (nor visiable in $ ip a), and
thus no
autopkgtest regressions:
some kernel flavours are failing to build from source due to running out
of memory whilst compiling mellanox drivers. Requesting to add all
kernel flavours to big_packages configuration in
https://bugs.launchpad.net/auto-package-testing/+bug/1831446
--
You received
autopkgtest regressions:
libgeo-coder-googlev3-perl request to badtest + sru to unbreak autopkgtests
https://bugs.launchpad.net/ubuntu/+source/libgeo-coder-googlev3-perl/+bug/1831443
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
RE: perl openssl read/write|_all changes
OpenSSL 1.1.1 has enabled AUTO_RETRY by default and all non-application
data records are retried by default. Thus this is effectively a no-
change for higher level users as retries have moved further down the
stack to libssl itself.
Upstream executes
** 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/1831252
Title:
panic=-1 is completely ignored by the initrd causing unexpected
Lol
On Thu, 30 May 2019, 20:20 Rafael David Tinoco, <
rafaeldtin...@kernelpath.com> wrote:
> xnox, it looks like you're missing a "$" in md5sum command from:
>
>
> https://launchpadlibrarian.net/426017250/systemd_240-6ubuntu7_240-6ubuntu8.diff.gz
>
> for the -proposed systemd version:
>
>
@Sergio: your issue is different. It is being killed during a kernel
operation (sys_write) due to a vmalloc failure, where this bug is
occurring during a userspace compile. Please open a new bug
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
rapidly adopted due to increased set of
@Ian - renaming this bug wfm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1830502
Title:
apparmor fails to start with no parser errors
Status in apparmor package in
The route looks invalid to me, please clarify
** 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/1826459
Once you can get a profile to compile apparmor can cache the compile for
you, so ideally the compile only needs to happen once per kernel.
But I completely get even then, with this profile that is a problem.
Can I keep the profile, and add it to a test suite, to look into
reducing the compilers
So yes that does appear to be part of it. I pulled your profile and
tested just a compile
time apparmor_parser -QT -D dfa-stats /tmp/layouts-test-1.txt
Created dfa: states 16780 proto { cache: size=16780 dups=36386 longest=1244
avg=6 }, nnodes { cache: size=16761 dups=36405 longest=1243 avg=5
enp0s31f6: Could not set route: Invalid argument
enp0s31f6: Routes set
addresses:
- 95.216.96.148/26
gateway4: 95.216.96.129
routes:
- on-link: true
to: 95.216.96.148/26
via: 95.216.96.129
I do not quite understand what above is supposed to mean.
** Package changed: systemd (Ubuntu) => ceph (Ubuntu)
--
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/1828617
Title:
Hosts randomly 'losing' disks, breaking ceph-osd
Only affects xenial at the moment.
** Changed in: systemd (Ubuntu Xenial)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Oh joy! This is like the ultimate "have you tried turning it on and off
again".
I wonder, if shutdown should inhibit sleep as its first action. And/or
sleep api should be checking for in flight shutdown transaction.
I agree this is a bad behaviour.
--
You received this bug notification because
** 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/1814373
Title:
storage / luks / dmsetup
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => Won't Fix
--
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/1829347
Title:
systemd autopkgtest 'storage'
** 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/1829450
Title:
Does installing finalrd package help?
It should pivot off root on shutdown, and unmount separate /var and
/var/log cleanly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** 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/1825378
Title:
systemd-networkd doesn't
** 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/1825997
Title:
boot-smoke fails due to
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
Failing to remove the module, means the testcase / systemd has failed.
Which has been diagnosed and narrowed down to a bug in systemd.
Whilst the proposed improvements to the test case are ok, they make it
skip a lot more without making it more fool proof.
Ideally, I'd like to make the testcase
"and so causes autopkgtest failures." is not true.
>From http://autopkgtest.ubuntu.com/packages/systemd/bionic/amd64
E.g.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20190529_090547_1f40a@/log.gz
Ensure that
It's a critical but in the Ubuntu platform if the very first kernel log
line is not available in the system logs.
And it is present on all arches, apart from the identified buggy arm64
which is in-flight being fixed (in eoan-proposed & disco-proposed with
other releases to follow).
** Changed in: python-tornado (Ubuntu)
Status: Confirmed => In Progress
--
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/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04
We can get a diff of loaded vs. expected profiles
for a straight list of loaded profiles names, you can do
$ sudo cat /sys/kernel/security/apparmor/profiles
/snap/core/6964/usr/lib/snapd/snap-confine (enforce)
/snap/core/6964/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
** Also affects: libwww-perl (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/1797386
Title:
[SRU] OpenSSL 1.1.1 to
Test suite got fixed in master too, all is good:
https://git.busybox.net/busybox/commit/?id=b2c123d484dbe261758f27ced213f4649173803b
Thanks a lot for the quick fixes! Included in Ubuntu devel series.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I'm not aware of any way to get the apparmor.service to print out what
profile it is working on without actually modifying the service
however your dmesg does show the reason for the failure, it looks like
the apparmor_parser is being killed by the oom killer
[ 5986.338089] [13520] 0 13520
No the warnings won't cause apparmor to fail, however the kernel killing
the apparmor_parser will, and that won't report a parse error.
The Ubuntu apparmor.service calls the apparmor_parser once for each
profile. Which means you are getting a some profiles loaded but not all
of them.
Can you
Nice!
It is valgrind clean now, but the testsuite fails:
$ ./bunzip2.tests
PASS: bunzip2: doesnt exist
PASS: bunzip2: unknown suffix
PASS: bunzip2: already exists
PASS: bunzip2: stream unpack
PASS: bunzip2: delete src
PASS: bunzip2: test_bz2 file
PASS: bunzip2: pbzip_4m_zeros file
PASS:
** Also affects: packagekit (Ubuntu Eoan)
Importance: Medium
Status: Triaged
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
** Changed in: busybox (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1828282
Title:
busybox 1.30.1 crashes bzip2 test
** Bug watch added: Busybox Bugzilla #11896
https://bugs.busybox.net/show_bug.cgi?id=11896
** Also affects: busybox via
https://bugs.busybox.net/show_bug.cgi?id=11896
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
On fresh disco and up installations this "just works" due to /usr-merge
by default.
On prior releases bin dir is configurable at lvm build time, which we
set to /bin (as that's where we want lvm2 utils to end up), but that's
not the location of systemd-run.
Needs a manual patch to lvm2, to
** Changed in: console-setup (Ubuntu Xenial)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1604737
Title:
headless
** Description changed:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
rapidly adopted due to increased set of
$ cat /boot/config-5.0.0-16-generic | grep LOG_BUF
CONFIG_LOG_BUF_SHIFT=18
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
$ uname -a
Linux doerfel 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:54:19 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
And journal shows complete kernel boot messages, thus this all
1201 - 1300 of 4696 matches
Mail list logo
