Hi Tobias, thanks for testing and verifying! I really appreciate it, and
it's good to hear that everything works.
I'll just add some of my own test output below, and we should be good to
go for a release to -updates in about a week's time.
--
You received this bug notification because you are a
Performing verification of adcli on Groovy.
Groovy only required one patch, which fixed a missed enablement of
--use-ldaps for the testjoin and update commands.
So, just testing those two.
I installed adcli 0.9.0-1ubuntu1 from -updates, and I set everything up
by issuing a join command. After th
Performing verification of adcli on Focal
The patches for Focal are a bit more involved, as it adds the whole
--use-ldaps ecosystem.
Firstly, I installed adcli 0.9.0-1 from -updates. The manpage did not
have any mention of --use-ldaps, and if I ran a command with --use-
ldaps, it would complain i
Performing verification of adcli on Bionic
The patches for Bionic are a bit more involved, as it adds the whole
--use-ldaps ecosystem.
Firstly, I installed adcli 0.8.2-1 from -updates. The manpage did not
have any mention of --use-ldaps, and if I ran a command with --use-
ldaps, it would complain
Performing verification for Focal.
Since Benjamin hasn't responded, I will try and verify the best I can.
I made a instance on AWS. I used a c5d.large instance type, and added
8gb extra EBS storage.
I installed the latest kernel from -updates to get a performance
baseline. kernel is 5.4.0-54-gen
Performing verification for Bionic.
Since Benjamin hasn't responded, I will try and verify the best I can.
I made a instance on AWS. I used a c5d.large instance type, and added
8gb extra EBS storage.
I installed the latest kernel from -updates to get a performance
baseline. kernel is 4.15.0-124-
Verification for sssd on Focal:
The customer tested sssd from -updates, version 2.2.3-3 and the package
from -proposed, version 2.2.3-3ubuntu0.1.
Begins:
I have successfully tested the [package from -proposed] on Ubuntu
20.04.1.
Before applying the patch [package from -proposed] I confirmed ope
Verification for sssd on Bionic:
The customer tested sssd from -updates, version 1.16.1-1ubuntu1.6 and
the package from -proposed, version 1.16.1-1ubuntu1.7.
Begins:
Before applying the patch [package from -proposed] I confirmed open
ports to our domain controllers using ss and grepping for the
Hi Benjamin,
No worries about being busy.
Now, the kernel is scheduled to be released early next week, around the
30th of November. I think at this stage it is best to wait it out and
install the kernel once it reaches -updates.
That way you will have a fixed kernel that is supported by livepatc
Hi Benjamin,
I have good news. The SRU has completed, and the new kernels have now
been released to -updates. Their versions are:
Bionic:
4.15.0-126-generic
Focal:
5.4.0-56-generic
You can go ahead and schedule that maintenance window now, to install
the latest kernel from -updates. These kerne
Performing verification for Bind9 on Focal.
I first installed 9.16.1-0ubuntu2.6 from -updates to ensure that the
issue is still present.
I checked that I could look up ubuntu.com through the local caching
resolver. From there I started a second VM, and checked I could look up
addresses through th
Hi Jiatong,
Thanks for emailing me, happy to answer questions anytime.
> 1. why linux-hwe-4.15.0 source code is used?
If you look closely at the oops in the description, the customer I was
working with was running:
4.15.0-106-generic #107~16.04.1-Ubuntu
This is the Xenial (16.04) HWE kernel.
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 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 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
Hi Thimo,
Thanks for helping test! I really appreciate it. It is great to hear
that you haven't had any trouble with the test kernel.
Just a quick update on the state of the Raid10 patchset. I submitted
them for SRU for the current cycle, and the kernel team wrote back to me
asking for more testi
Hi Evan,
The patches have been submitted for SRU to the Ubuntu kernel mailing
list, for the 4.15, 5.4, 5.8 and 5.11 kernels:
[0] https://lists.ubuntu.com/archives/kernel-team/2021-May/119935.html
[1] https://lists.ubuntu.com/archives/kernel-team/2021-May/119936.html
[2] https://lists.ubuntu.com/a
Hi Thimo,
As I mentioned in my previous message, I submitted the patches to the
Ubuntu kernel mailing list for SRU.
These patches have now gotten 2 acks [1][2] from senior kernel team
members, and the patches have now been applied [3] to the 4.15, 5.4, 5.8
and 5.11 kernels.
[1] https://lists.ubu
Hi Evan,
As I mentioned in my previous message, I submitted the patches to the
Ubuntu kernel mailing list for SRU.
These patches have now gotten 2 acks [1][2] from senior kernel team
members, and the patches have now been applied [3] to the 4.15, 5.4, 5.8
and 5.11 kernels.
[1] https://lists.ubun
.
Currently looking into what landed in bug 1919143 and bug 1905825.
[Testcase]
[Where problems can occur]
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Affects: mutter (Ubuntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In
Hello,
Just a note that mutter 3.36.9-0ubuntu0.20.04.1 has introduced a
regression in a VMware Horizon VDI environment, where gdm fails to
start, and has taken out several hundred VDIs.
I am tracking the issue in bug 1930359.
The plan is to make a test package with the patches from bug 1905825
r
Hello,
Just a note that mutter 3.36.9-0ubuntu0.20.04.1 has introduced a
regression in a VMware Horizon VDI environment, where gdm fails to
start, and has taken out several hundred VDIs.
I am tracking the issue in bug 1930359.
The plan is to make a test package with the patches from bug 1905825
r
Hi Chris,
Thanks for reporting! Looking at the difference between
4.15.0-142-generic and 4.15.0-143-generic, there is one commit:
ubuntu-bionic$ git log --grep "cifs"
Ubuntu-4.15.0-142.146..Ubuntu-4.15.0-143.147
commit 7dd995facbb57b35b10715a27e252c8af5a39a6c
Author: Shyam Prasad N
Date: Thu
*** This bug is a duplicate of bug 1923670 ***
https://bugs.launchpad.net/bugs/1923670
** This bug has been marked a duplicate of bug 1923670
CIFS DFS entries not accessible with 5.4.0-71.74-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Just adding a note for Bionic users, that the commit "cifs: Set
CIFS_MOUNT_USE_PREFIX_PATH flag on setting cifs_sb->prepath." landed in
4.15.0-143-generic, causing the regression, and it has been reverted in
4.15.0-144-generic.
If you are experiencing any issues with 4.15.0-143-generic, please
upg
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929129
Title:
if cloud-init status is not done, set_installer_password will crash
To manage notifications about this bug go to:
htt
Hi Evan,
The kernel team have built all of the kernels for this SRU cycle, and
have placed them into -proposed for verification.
We now need to do some thorough testing and make sure that Raid10 arrays
function with good performance, ensure data integrity and make sure we
won't be introducing any
Hi Thimo,
The kernel team have built all of the kernels for this SRU cycle, and
have placed them into -proposed for verification.
We now need to do some thorough testing and make sure that Raid10 arrays
function with good performance, ensure data integrity and make sure we
won't be introducing an
Performing verification for Hirsute.
I'm going to do three rounds of verification.
The first is the testcase from this bug, showing block discard
performance.
The second is running through the regression reproducer from bug
1907262.
The third will be results from my testing with my /home direct
Performing verification for Groovy.
I'm going to do three rounds of verification.
The first is the testcase from this bug, showing block discard
performance.
The second is running through the regression reproducer from bug
1907262.
The third will be results from my testing with my /home directo
Performing verification for Focal.
I'm going to do three rounds of verification.
The first is the testcase from this bug, showing block discard
performance.
The second is running through the regression reproducer from bug
1907262.
The third will be results from my testing with my /home director
Performing verification for Bionic.
I'm going to do three rounds of verification.
The first is the testcase from this bug, showing block discard
performance.
The second is running through the regression reproducer from bug
1907262.
The third will be results from my testing with my /home directo
Hi Thimo,
Thanks for letting me know, and great to hear that things are working as
expected. I'll check in with you in one week's time, to double check things are
still going okay.
I spent some time today performing verification on all the kernels in -proposed,
testing block discard performance [
Hi Evan,
Great to hear things are looking good for you and that the block discard
performance is there. If possible, keep running the kernel from
-proposed for a bit longer, just to make sure nothing comes up on longer
runs.
I spent some time today performing verification on all the kernels in
-p
I built a test package based on mutter 3.36.9-0ubuntu0.20.04.1, and
reverted the three commits introduced by LP #1905825, namely:
commit: 92834d8feceeac538299a47a8c742e155de4e6e8
From: Kai-Heng Feng
Date: Mon, 21 Dec 2020 14:34:43 +0800
Subject: renderer/native: Refactor modeset boilerplate into
Hi Thimo,
Just checking in. Are you still running 5.4.0-75-generic on your server?
Is everything nice and stable? Is your data fully intact, and no signs
of corruption at all?
My server has been running for two weeks now, and it does a fstrim every
30 minutes, and everything appears to be stable
Hi Evan,
Just checking in. Are you still running 5.4.0-75-generic on your server?
Is everything nice and stable? Is your data fully intact, and no signs
of corruption at all?
My server has been running for two weeks now, and it does a fstrim every
30 minutes, and everything appears to be stable,
I spent some time attempting to reproduce on AWS today, using a
g4dn.xlarge instance, which has a Nvidia Tesla T4 GPU, which supports
GRID.
I installed ubuntu-desktop-minimal and rebooted, and gdm started fine
with mutter 3.36.9-0ubuntu0.20.04.1. I confirmed this by looking at the
instance screens
** Attachment added: "screenshot of working gdm on AWS"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+attachment/5505412/+files/Screenshot%20from%202021-06-18%2013-40-15.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
lists/linux-btrfs/msg103367.html
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: bionic sts
** Changed in: linux (Ubuntu)
Hi Thimo,
The SRU cycle has completed, and all kernels containing the Raid10 block
discard performance patches have now been released to -updates.
Note that the versions are different than the kernels in -proposed, due
to the kernel team needing to do a last minute respin to fix two sets of
CVEs,
Hi Evan,
The SRU cycle has completed, and all kernels containing the Raid10 block
discard performance patches have now been released to -updates.
Note that the versions are different than the kernels in -proposed, due
to the kernel team needing to do a last minute respin to fix two sets of
CVEs,
The affected user cannot reproduce the issue anymore. The new mutter
packages install fine in their environment, and gdm starts every time.
They have since rolled out the new mutter packages to their fleet
without any issues.
I'm going to mark this bug as invalid, as we can't reproduce the issue
a
Okay, the affected user has now started experiencing the issue again,
and was forced to roll mutter back on their fleet.
We managed to get some logs this time, and we have determined what is
happening.
When the user upgrades the mutter packages, particularly mutter-common,
the libglib2.0-0 hook i
Hi Daniel,
Yes, I am sure this is the same issue that they are experiencing there,
and I now believe the issue lies in glib, and not mutter.
When we install mutter-common, it calls the libglib2.0-0 hook to
recompile the gsettings schemas.
The customer provided me with a tarball of their
/usr/sha
ve a reply.
If you read Richard's mailing list link, it mentions filesystem
corruption with missing extents. This suggests this crash might be
linked to bug 1933172, which I came across while trying to reproduce the
issue in this bug.
** Affects: linux (Ubuntu)
Importance: Undecided
S
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1934709
[Impact]
During an automatic balance, users may encounter an error when writing
the transaction log to disk, when the log tree is being parsed, which
forces the filesystem to be remounted read-only and outputs
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1934709
[Impact]
During an automatic balance, users may encounter an error when writing
the transaction log to disk, when the log tree is being parsed, which
forces the filesystem to be remounted read-only and outputs
** No longer affects: mutter (Ubuntu)
** No longer affects: mutter (Ubuntu Focal)
** Changed in: glib2.0 (Ubuntu)
Status: New => Fix Released
** Changed in: glib2.0 (Ubuntu Focal)
Status: New => In Progress
** Changed in: glib2.0 (Ubuntu Focal)
Importance: Undecided => High
**
Attached is a debdiff for glib2.0 on Focal which fixes this problem.
** Patch added: "Debdiff for glib2.0 for Focal"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1930359/+attachment/5510466/+files/lp1930359_focal.debdiff
** Tags removed: regression-update
** Tags added: sts-sponsor
** 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
** Changed in: linux (Ubuntu Groovy)
Assignee: Sinclair Willis (yousure1222) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: discard leads to corrup
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926254
Title:
x509 Certificate verification fails when
basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs
To m
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
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
signed) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896578
Title:
raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
Hi Thimo,
Thanks for writing back, great timing!
So, the new revision of the patches that we have been testing since
February have just been merged into mainline. The md/raid10 patches got
merged on Friday, and the dm/raid patches got merged on Saturday, and
will be tagged into 5.13-rc1. There's
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 mem
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
Hi Thimo,
As promised yesterday, the new re-spins of the test kernels have
finished building and are now available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1896578-test
The patches used are the ones I will be submitting for SRU, and are more
or less identical to th
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
If anyone is interested in testing, there are new re-spins of the test kernels
available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1896578-test
The patches used are the ones I will be submitting for SRU, and are more
or less identical to the patches in the previous t
I have completed most of my regression testing, and things are still looking
good. The performance of the block discard is there, and I haven't seen any
data corruption.
In particular, I have been testing against the testcase for the regression that
occurred with the previous revision of the patch
Hi Thimo,
I have been doing quite a bit of regression testing, and so far everything is
looking good. The performance of the block discard is there, and I haven't
come across any data corruption.
I have also spent some time running through the testcase you created for this
bug, and I have the res
Public bug reported:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot any further.
The o
** Description changed:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot
Attached is a debdiff for grub2-signed which issues a sed to remove the
GRUB_DISTRIBUTOR=Debian line from /etc/default/grub.d/50-cloudimg-
settings.cfg
** Patch added: "Debdiff for grub2-signed on Xenial"
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1928040/+attachment/5496305/+
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
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921104
Title:
net/mlx5e: Add missing capability check for uplink follow
To manage notifications about this bug go to:
https://bugs.
It seems the revert for "screen: Use clean env when creating new tab" is
already in 3.38.1, and I checked the Ubuntu source package, and the
revert is in place.
https://gitlab.gnome.org/GNOME/gnome-
terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Interesting.
I might try a test build
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that
Attached is a debdiff for Hirsute which re-applies "screen: Use clean
env when creating new tab" and is the same patch in the PPA.
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functi
Hi @Hmpf,
Thanks for filing a bug report.
I had a look at the changes between 5.4.0-70-generic and
5.4.0-71-generic, and I found three patches for CIFS:
$ git log --grep "cifs" Ubuntu-5.4.0-70.78..Ubuntu-5.4.0-71.79
https://paste.ubuntu.com/p/YgrZcN8B6j/
I had a read of the patches, and I think
Thanks Tim for building the test kernel, and Hmpf, thanks for testing it
and confirming it fixes the problem.
Okay, so the problem is:
commit a738c93fb1c17e386a09304b517b1c6b2a6a5a8b
Author: Shyam Prasad N
Date: Thu Feb 11 03:26:54 2021 -0800
Subject: cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag
*** This bug is a duplicate of bug 1923670 ***
https://bugs.launchpad.net/bugs/1923670
Hi Kjell,
Thanks for reporting the issue! We have been tracking it in bug 1923670.
We found the root cause, and we have commit a fix to the source code
tree. This will be fixed in the next kernel update ho
@dannf: Yes, this bug sure is a tricky one.
Most of these reports will be due to failing / faulty / non-spec
complaint USB devices or cables, like the original reason for this bug
being opened. Although, there have been some reports where user's
systems do go back to working when they install my t
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
Performing verification for Focal.
I will first reproduce the problem with glib2.0 2.64.6-1~ubuntu20.04.3
from -security with the libglib2.0-0 libglib2.0-bin libglib2.0-data
packages.
I deleted all existing schemas from /usr/share/glib-2.0/schemas and
replaced them with a set of schemas which rep
Performing verification for Bionic.
I installed 4.15.0-151-generic from -updates, and added the reproducer
btrfs qcow2 image file to my VM.
From there, I mounted the filesystem and attempted to balance:
$ sudo mount /dev/vdb /mnt
$ sudo btrfs filesystem balance start --full-balance /mnt
Segmenta
Performing verification for Bionic.
Firstly, I installed 4.15.0-151-generic from -updates, to get a baseline
for all xfstests results.
I built and ran btrfs/* from xfstests, using the following local config:
export TEST_DEV=/dev/vdc
export TEST_DIR=/mnt/test
export SCRATCH_DEV_POOL="/dev/vdd /de
** Summary changed:
- Support new AD requirements (ADV190023)
+ Support "ad_use_ldaps" flag for new AD requirements (ADV190023)
** Description changed:
- Please backport the following patch to add the option ad_use_ldaps.
+ [Impact]
- With this new boolean option the AD provider should only u
Attached is a debdiff for adcli on Focal.
** Patch added: "adcli debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432450/+files/lp1868703_adcli_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Attached is a adcli debdiff for Bionic
** Patch added: "adcli debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432452/+files/lp1868703_adcli_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Attached is a sssd debdiff for Bionic
** Patch added: "sssd debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432453/+files/lp1868703_sssd_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Attached is a sssd debdiff for Focal
** Patch added: "sssd debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432451/+files/lp1868703_sssd_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868703
Title:
Support "ad_use_ldaps" flag for new AD requirements (ADV190023)
To manage notifications about this bug go to:
** Description changed:
[Impact]
Microsoft has released a new security advisory for Active Directory (AD)
which outlines that man-in-the-middle attacks can be performed on a LDAP
server, such as AD DS, that works by an attacker forwarding an
authentication request to a Windows LDAP se
** Patch removed: "adcli debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432450/+files/lp1868703_adcli_focal.debdiff
** Patch removed: "sssd debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432451/+files
Attached is a revised debdiff for sssd for Focal.
** Patch added: "sssd debdiff for Focal v2"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432866/+files/lp1868703_sssd_focal_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
1 - 100 of 1015 matches
Mail list logo
