Hi Krister,
I have finally seen this occur in real life with my own two eyes!
You are absolutely correct, the 4-retry doesn't seem to be sufficient
sometimes.
The reproducer works on Focal and previous in about 20 minutes, so its
easy to see the issue trigger on Focal. But Focal and previous doe
Hi Krister,
Fascinating. I'm in New Zealand, so I use ap-southeast-2 in Sydney,
Australia for all my instances, and I never gave it any thought that
this could depend on how busy EBS is on the availability zone.
I'll move my instances to us-west-2.
Thanks,
Matthew
--
You received this bug noti
signee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost option i
Attached is a debdiff that solves this issue on Jammy.
** Patch added: "Debdiff for coreutils on Jammy"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+attachment/5745181/+files/lp2033892_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
- Release: 22.04.3 LTS
- coreutils 8.32-4.1ubuntu1
+ [Impact]
- ls triggers unwanted mounts of autofs filesystems
+ Issuing a 'ls -l' or a 'stat' on an autofs share when you have set
+ --ghost in the auto.master file, or browse_mode=yes in autofs.conf will
+ lead to the
I have been running the test packages on AWS with the reproducer running
for 20 days now, and they are still running great. The change to direct
IO really does fix this issue, and my testing has removed any and all
concerns of causing a regression.
Previously focal wouldn't last more than 20 minut
gtkpod has been removed from debian, and thus removed from noble, so no
need to fix there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults w
Attached is a debdiff for mantic which fixes this issue.
** Patch added: "Debdiff for gtkpod on mantic"
https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => Fix Release
Performing verification for Jammy
I set up two Jammy VMs, one a nfs-server and the other an autofs/nfs-
client.
The client is using coreutils 8.32-4.1ubuntu1.1 from -updates.
$ apt-cache policy coreutils | grep Installed
Installed: 8.32-4.1ubuntu1.1
I set up the nfs server and autofs mounts
Thank you for the help sorting autopkgtests Mauricio.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost op
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Low => Medium
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: sts
--
You received this bug not
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided =
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: bionic sts
--
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/b
Attached is a debdiff for systemd on Bionic which fixes this bug.
** Description changed:
- Two servers today that updated systemd to "systemd 237-3ubuntu10.54"
- https://ubuntu.com/security/notices/USN-5583-1
+ [Impact]
- could not resolve dns anymore.
- no dns servers, normally set through
Hello everyone,
I know there are quite a few people watching this bug, so I will provide
a status update.
The test package has been looking good throughout our internal testing,
and we have proceeded to build the next systemd update, version
237-3ubuntu10.55, and it is currently in the bionic-sec
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Released => 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/1988119
Title:
systemd-udevd: Run net_se
The failure mode still exists if "udevadm trigger" has been issued
before the package upgrade to systemd 237-3ubuntu10.55.
That is, if unattended-upgrades or the user had installed open-vm-tools,
and has not rebooted yet, they will lose network connection on upgrade
to 237-3ubuntu10.55.
We need t
Attached is the second patch required to fully fix this bug. It adds a
check on preinstall to see if ID_NET_DRIVER is present on the network
interface, and if it is missing, call udevadm trigger -c add on the
interface to add it.
** Patch added: "Debdiff for systemd on Bionic part two"
https:/
Attached is an improvement on the previous patch revision. Output is now
forwarded to logger, we use shell expansion to enumerate network
devices, we omit loopback, and we added a udevadm settle to wait for any
thunderstorms to resolve before we continue installing the new udev
package.
** Patch a
Hi Krister,
Thanks for the heads up about 1.47.1 upstream, it does indeed look like
a release is coming soon.
It seems Debian unstable already has 1.7.1-rc1:
https://packages.debian.org/sid/e2fsprogs
When the Ubuntu archive opens for OO, we will merge 1.47.1~rc1-1 from
debian unstable, and then
Attached is a V2 patch for Noble for e2fsprogs.
** Patch added: "Debdiff for e2fsprogs on noble V2"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5772258/+files/lp2036467_noble_V2.debdiff
** Patch removed: "Debdiff for e2fsprogs on noble"
https://bugs.launch
Beginning verification for focal
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
I downgraded the HWE kernels down to GA kernels, and each is running
5.4.0-1129-aws.
One is -updates, the other i
Beginning verification for jammy
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
I downgraded the HWE kernels down to GA kernels, and each is running
5.15.0-1066-aws.
One is -updates, the other
Beginning verification for noble
I started two c5.large instances on us-west-2 on AWS, the same parameters that
we used in previous tests. Each has a 60gb GP3 volume attached to it.
Each instance is running the GA kernel, 6.8.0-1012-aws.
One is -updates, the other is e2fsprogs from -proposed:
-
Performing verification for Focal.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.45.5 (07-Jan-2020)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvm
Performing verification for Noble.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.47.0 (5-Feb-2023)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvme
Performing verification for Jammy.
So, I had forgotten all about these instances, so let's check them now.
The instance with -updates:
It failed with:
+ resize2fs /dev/nvme1n1p1
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Superblock checksum does not match superblock while trying to open
/dev/nvm
Hi Krister,
Yes, we are still planning to get this released for focal. To be able to
release, it needs to pass all of its autopkgtests.
If you have a look here:
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/focal/update_excuses.html#e2fsprogs
Its failing on a few of them for some a
Attached is a debdiff which fixes this problem on Focal.
** Patch added: "Debdiff for libunwind on Focal"
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635451/+files/lp1999104_focal.debdiff
--
You received this bug notification because you are a member of Ubun
e: Undecided => Medium
** Changed in: libunwind (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: libunwind (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Patch added: "Debdiff for libunwind on Bionic"
ht
** Summary changed:
- libunwind causes crashes on arm64
+ arm64: broken c++ exception handler support leads to std::terminate() being
called and program abort
** Description changed:
- There is a bug in libunwind in both 18.04 and 20.04 on arm64 where when
- linked with libunwind instead of cat
** Tags added: sts-sponsor
--
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 handler support leads to std::terminate()
being ca
Performing verification for Focal.
I started two instances on AWS, one c6g.medium (arm64) and a t2.micro
(amd64).
I went through the reproducer listed in the testcase with libunwind-dev
1.2.1-9build1 from -release.
$ wget
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachm
Performing verification for Bionic.
I started two instances on AWS, one c6g.medium (arm64) and a t2.micro
(amd64).
I went through the reproducer listed in the testcase with libunwind-dev
1.2.1-8 from -release.
$ wget
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5
Attached is a debdiff for Focal which fixes this bug.
** Patch added: "Debdiff for bind9-libs for Focal"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641515/+files/lp1926139_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
untu Jammy)
Importance: Undecided => High
** Changed in: bind9-libs (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: bind9-libs (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification becaus
** Summary changed:
- dhclient doesn't receive dhcp offer from kernel
+ dhclient: thread concurrency race leads to DHCPOFFER packets not being
received
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
http
packet capture from a reproduction run
** Description changed:
- Platform: Qemu/libvirt on AMD64
- Ubuntu version: 20.04
- isc-dhcp-client version: 4.4.1-2.1ubuntu5
- Problem: When dhclient is used during boot every few reboots the DHCP OFFER
packets aren't pushed from the kernel to dhclient. Th
Screenshot of wireshark.
** Attachment added: "Screenshot of wireshark"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641811/+files/Screenshot_2023-01-17-16-14-21_1920x1200%250A1920x1080%250A1920x1080.png
** Description changed:
[Impact]
Occasionally, du
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1926139
Title:
dhclient: thread concurrency race leads to DHCPOFFER packets not being
received
Status: New
** Also affects: bind9-libs (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: bind9-libs (Ubuntu Focal)
** No longer affects: bind9-libs (Ubuntu Jammy)
** Changed in: isc-dhcp (Ubuntu Focal)
Status: New => In Progress
** Changed in:
Hi William,
I sincerely apologise for the delay.
Currently libunwind is stuck in -proposed due to benign autopkgtest
regressions in the kernel packages.
If you go to the below page:
https://people.canonical.com/~ubuntu-archive/pending-sru.html
And search for "libunwind" you will see entries fo
Hi William.
The libunwind SRU for Bionic and Focal have now been released to
-updates. Their versions are 1.2.1-8ubuntu0.1 for Bionic, and
1.2.1-9ubuntu0.1 for Focal.
I just want to apologise for the significant delay in getting libunwind
released. It really was a exceptional amount of time, and
** Description changed:
[Impact]
This is a long running bug plaguing cloud-images, where on a rare
occasion resize2fs would fail and the image would not resize to fit the
entire disk.
Online resizes would fail due to a superblock checksum mismatch, where
the superblock in memory
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when attemptin
Upstream bug: https://gitlab.gnome.org/GNOME/glib/-/issues/3185
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3185
https://gitlab.gnome.org/GNOME/glib/-/issues/3185
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Attached is a V2 patch for mantic with a different version number, due
to it no longer being the devel release.
** Patch removed: "Debdiff for e2fsprogs on mantic"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707893/+files/lp2036467_mantic.debdiff
** Patch add
Attached is a patch for noble that solves this issue.
** Patch added: "Debdiff for e2fsprogs on noble"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5738302/+files/lp2036467_noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Hi Krister,
I apologise for the delay. The main issue I have been having with
testing is that it reproduces significantly faster on some releases than
others, and I still haven't managed to reproduce once on some releases.
I'll set up some fresh reproducers now, and leave them running.
If you wan
xes.
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: openssl (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: openssl (Ubuntu Groovy)
Importance: Medium
Assi
** Description changed:
[Impact]
In openssl 1.1.1f, the below commit was merged:
commit ba4356ae4002a04e28642da60c551877eea804f7
Author: Bernd Edlinger
Date: Sat Jan 4 15:54:53 2020 +0100
Subject: Fix error handling in x509v3_cache_extensions and related functions
Link:
htt
Attached is a debdiff for openssl on Focal which fixes this bug.
** Patch added: "Debdiff for openssl on focal"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+attachment/5493442/+files/lp1926254_focal.debdiff
--
You received this bug notification because you are a member of
Attached is a debdiff for openssl on Groovy which fixes this bug.
** Patch added: "Debdiff for openssl on Groovy"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+attachment/5493443/+files/lp1926254_groovy.debdiff
--
You received this bug notification because you are a member
** Tags added: sts-sponsor
--
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/1926254
Title:
x509 Certificate verification fails when
basicConstraints=CA:FALSE,pathlen:0 on
Hi Seth,
Thanks for the review.
I read the commit you found:
commit 1e41dadfa7b9f792ed0f4714a3d3d36f070cf30e
Author: Dr. David von Oheimb
Date: Sat Jun 27 16:16:12 2020 +0200
Subject: Extend X509 cert checks and error reporting in v3_{purp,crld}.c and
x509_{set,vfy}.c
Link:
https://github.c
nassigned) => Matthew Ruffell (mruffell)
** Changed in: openssl (Ubuntu Hirsute)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: openssl (Ubuntu Impish)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a memb
I split 'pr12272.patch' into one file per commit, and I did a diff to
ensure that there is no changes to the code:
https://paste.ubuntu.com/p/zDqqXmsM8c/
When using these split up patches "dpkg-buildpackage -d -S" completes
successfully.
--
You received this bug notification because you are a m
Attached is a debdiff for impish which fixes this problem.
** Patch added: "debdiff for openssl on impish"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494810/+files/lp1927161_impish.debdiff
--
You received this bug notification because you are a member of Ubun
Attached is a debdiff for openssl on hirsute which fixes this problem.
** Patch added: "debdiff for openssl on hirsute"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494811/+files/lp1927161_hirsute.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for openssl on groovy, which fixes this issue, and
also bug 1926254
** Patch added: "debdiff for openssl on groovy"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494812/+files/lp1926254_lp1927161_groovy.debdiff
** Patch removed: "debdiff for
Attached is a V2 for impish which correctly has d/p/ in the
debian/changelog.
** Patch added: "debdiff for openssl on impish"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494813/+files/lp1927161_impish_v2.debdiff
** Patch removed: "debdiff for openssl on hirsute
Attached is a V2 for hirsute which correctly has d/p/ in the
debian/changelog.
** Patch added: "debdiff for openssl on hirsute"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494814/+files/lp1927161_hirsute_v2.debdiff
--
You received this bug notification because
** Description changed:
[impact]
openssl doesn't build source properly because of a badly-constructed
patch
[test case]
$ pull-lp-source openssl groovy
...
$ cd openssl-1.1.1f/
$ quilt pop -a
...
$ dpkg-buildpackage -d -S
dpkg-buildpackage: info: source package opens
Performing verification for Focal
Generating the ssl certificates, and reproducing the problem with version
1.1.1f-1ubuntu2.3 from -updates.
ubuntu@select-lobster:~$ sudo apt-cache policy openssl | grep Installed
Installed: 1.1.1f-1ubuntu2.3
ubuntu@select-lobster:~$ mkdir reproducer
ubuntu@sele
Performing verification for Groovy.
I went and generated the ssl certificates and attempted to verify them with
the openssl version 1.1.1f-1ubuntu4.3 from -updates.
ubuntu@deep-mako:~$ sudo apt-cache policy openssl | grep Installed
Installed: 1.1.1f-1ubuntu4.3
ubuntu@deep-mako:~$ mkdir reproduc
Performing verification for Bionic
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.1.8-3.6ubuntu2.18.04.3
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
/etc/pam.d/com
Performing verification for Focal
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu4.2
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
/etc/pam.d/common-auth:
Performing verification for Hirsute
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu6.21.04.1
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
/etc/pam.d/comm
Performing verification for Groovy
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu6.20.10.1
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
/etc/pam.d/commo
I installed software-properties 0.99.20 from -proposed, and opened
software-properties-gtk, and clicked the "Additional Drivers" tab. The
tab loaded correctly and did not crash.
The package in -proposed fixes the issue, happy to mark verified.
--
You received this bug notification because you ar
Public bug reported:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
ubuntu-server-minimal unattended-upgrades
0
** Description changed:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
- ubuntu-server-minimal un
This has been fixed as of ubuntu-meta 1.474
https://launchpad.net/ubuntu/+source/ubuntu-meta/1.474
$ sudo apt rdepends unattended-upgrades
unattended-upgrades
Reverse Depends:
Recommends: python3-software-properties
Recommends: ubuntu-mate-desktop
Recommends: ubuntu-mate-core
Depends: free
.
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: openssl (Ubuntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: focal sts
** Also affects: openssl (Ubuntu Focal)
Importance
Attached is a debdiff for openssl on Focal
** Patch added: "debdiff for openssl on Focal"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+attachment/5560898/+files/lp1960863_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
** Tags added: sts-sponsor
--
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/1960863
Title:
armv8 paca: poly1305 users see segfaults when pointer authentication
in use on A
870.html
ubuntu-devel had strong support for option (3).
Hence, we will revert the below commit to ensure Jammy can be deployed on all
existing MAAS releases.
58b510e580 libsmartcols: sanitize variable names on export output
** Affects: util-linux (Ubuntu)
Importance: High
Assigne
Attached is a debdiff for Jammy util-linux.
** Patch added: "debdiff for util-linux on Jammy"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1961542/+attachment/5562373/+files/lp1961542_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch se
Performing verification for openssl on Focal.
An affected user performed the verification, due to c7g instance types
being in "Preview" state on Amazon AWS, and not generally accessible.
The user started a c7g instance, and checked they had openssl
1.1.1f-1ubuntu2.10 from -updates.
They attempte
Public bug reported:
Opened up "Software & Updates" and clicked the "Additional Drivers Tab",
for the tab to crash.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.19
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_
Yes, when --use-ldaps is specified, adcli will make a TLS connection to
the domain controller, and speak LDAPS. This works, and is the reason
why this bug slipped through our regression testing. I should have
tested without the --use-ldaps flag as well.
Regardless, this bug seems to be caused by t
Attached is a debdiff to revert the changes we made to adcli to restore
functionality to GSS-API.
** Patch added: "Debdiff for adcli on Bionic"
https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627/+attachment/5441133/+files/lp1906627_adcli_bionic.debdiff
--
You received this bug noti
** Changed in: cyrus-sasl2 (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: cyrus-sasl2 (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: cyrus-sasl2 (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1906627
Title:
adcli fails, can't contact L
** Summary changed:
- adcli fails, can't contact LDAP server
+ GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active
Directory, causing recent adcli regression
** Description changed:
- Package: adcli
- Version: 0.8.2-1ubuntu1
- Release: Ubuntu 18.04 LTS
+ [Impact]
- When tryi
Attached is a debdiff for cyrus-sasl2 on Bionic, which resolves the
incompatibilities of the GSS-SPNEGO implementation with the one in
Active Directory.
** Patch added: "cyrus-sasl2 debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627/+attachment/5441530/+files/lp19
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1906627
Title:
GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active
Directo
Attached is option one: a debdiff for adcli, which builds on
0.8.2-1ubuntu1 and simply adds a depends to the fixed libsasl2-modules-
gssapi-mit at greater or equal to relationship. This will require the
0.8.2-1ubuntu2 package in -unapproved queue to be deleted.
** Patch added: "debdiff for adcli o
Attached is option two: a debdiff for adcli, which builds on
0.8.2-1ubuntu2, which re-introduces all of the --use-ldaps patches, and
also adds a depends to the fixed libsasl2-modules-gssapi-mit at greater
or equal to relationship. Use this if option 1 is a no go.
** Patch added: "debdiff for adcli
Performing verification for Bionic
Firstly, I installed adcli and libsasl2-modules-gssapi-mit from
-updates:
adcli 0.8.2-1
libsasl2-modules-gssapi-mit 2.1.27~101-g0780600+dfsg-3ubuntu2.1
>From there, I joined a Active Directory realm:
https://paste.ubuntu.com/p/zJhvpRzktk/
Next, I enabled -pr
To anyone following this bug:
As we get ready to re-release the new adcli package which implements the
--use-ldaps flag, if you are happy to spend a few moments testing the
new package, I would really appreciate it. I really don't want to cause
another regression again.
You can install the new ad
d Apr 8 15:55:32 2020 +0200
Subject: replsess: fix double free of sendbuf in some cases.
Link:
https://github.com/rsyslog/librelp/commit/4a6ad8637c244fd3a1caeb9a93950826f58e956a
** Affects: librelp (Ubuntu)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Pr
Since we only need to change librelp to fix the problem, we won't SRU
the testcase to Focal's rsyslog, since there is no need to risk a
regression for a testcase, which would effectively be a no-change
rebuild.
The testcase is already present in rsyslog on Groovy and Hirsute,
marking as released.
** Description changed:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks file
descriptors due to a bug where it does not correctly close sockets, and
instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the
Attached is the debdiff for librelp for Groovy
** Patch added: "Debdiff for librelp on Groovy"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5449601/+files/librelp_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seede
Attached is the debdiff for librelp for Focal
** Patch added: "Debdiff for librelp on Focal"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5449602/+files/librelp_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to fi
og (Ubuntu)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: rsyslog (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: rsyslog (Ubuntu Hirsute)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
** Changed in: rsyslog (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: rsyslog (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: rsyslog (Ubuntu Hirsute)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
[Impact]
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1912122
Title:
/var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT
restrictions
Status
1 - 100 of 205 matches
Mail list logo
