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
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
** 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
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
** 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.
Performing verification for Bionic.
I want to say straight up, I haven't been able to reproduce the problem,
I have tried many mechanisms, but I can not reproduce the 20 second
shell hang and crash, as documented in https://github.com/GSConnect
/gnome-shell-extension-gsconnect/issues/549#issuecomm
Performing verification for Focal.
I installed qemu 4.2-3ubuntu6.14 from -updates with the usual KVM stack
command:
$ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients
bridge-utils
$ sudo reboot
>From there I installed and configured a NFS server:
$ sudo -s
$ sudo apt install
Performing verification for Groovy.
I installed qemu 5.0-5ubuntu9.6 from -updates with the usual KVM stack
command:
$ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients
bridge-utils
$ sudo reboot
>From there I installed and configured a NFS server:
$ sudo -s
$ sudo apt install
Might also be related:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/303
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922839
Title:
Opening new tab in gnome-terminal launched from nautilu
Seems this is a long running issue.
Upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #253
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added: gitlab.gnome.org/GNOME/gnome-term
Version tested in hirsute is 3.38.1-1ubuntu1.
I checked Groovy, with 3.38.0-1ubuntu1.1, and the problem does not happen.
Both systems using Wayland session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
[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 most environment va
Thanks for the quick work Christian!
I'll keep an eye out and be ready to test once builds enter -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921665
Title:
QEMU hits assertion when vir
Attached is a debdiff for Groovy which fixes this bug.
** Patch added: "QEMU debdiff for Groovy"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921665/+attachment/5481777/+files/lp1921665_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Attached is a debdiff for Focal which fixes this bug.
** Patch added: "QEMU debdiff for focal"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921665/+attachment/5481776/+files/lp1921665_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
osix: Allow byte-aligned O_DIRECT with NFS
Link:
https://git.qemu.org/?p=qemu.git;a=commit;h=5edc85571e7b7269dce408735eba7507f18ac666
Mailing list discussion:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg721982.html
** Affects: qemu (Ubuntu)
Importance: Undecided
Stat
Performing verification for gnome-shell in Bionic.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based
Performing verification for gnome-shell in Focal.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based a
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 Thimo,
Recently, Xiao Ni, the original author of the Raid10 block discard
patchset, has posted a new revision of the patchset to the linux-raid
mailing list for feedback.
Xiao has fixed the two bugs that caused the regression. The first was
incorrectly calculating the start offset for block di
Hi everyone,
The original patch author, Xiao Ni, has sent a V2 patchset to the linux-
raid mailing list for feedback. This new patchset fixes the problems the
previous version had, namely, properly calculating the discard offset
for second and onward disks, and correctly calculates the stripe size
** 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
Performing verification for Focal.
The affected user enabled -proposed and installed 5.4.0-66-generic to
the system with a QLogic FastLinQ QL41000 Series 10/25/40/50GbE
Controller.
They then set all interfaces down, and brought up the QLogic NIC only.
# uname -rv
5.4.0-66-generic #74~18.04.2-U
Performing verification for Focal.
I installed 5.4.0-65-generic to a c5.metal AWS machine, and installed
ubuntu-desktop and a KVM stack. I install xrdp and verified I could
reach the VMs desktop.
I installed virt-manager, and configured the Windows 2k19 VM in
accordance with the testcase section,
Attached is reproducing the problem with 5.4.0-66-generic. Note that CPU
is low, and system boots to desktop correctly.
** Attachment added: "5.4.0-66-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911848/+attachment/5462097/+files/5.4.0-66-generic.png
--
You received this bu
Attached is reproducing the problem with 5.4.0-65-generic, note, see how
CPU reaches 100% and is stuck.
** Attachment added: "5.4.0-65-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911848/+attachment/5462096/+files/5.4.0-65-generic.png
--
You received this bug notification b
Attached is a V2 of the patch that fixes this bug, Bind9 for Focal.
** Patch removed: "Debdiff for bind9 on Focal"
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+attachment/5461528/+files/lp1909950_focal.debdiff
** Patch added: "Debdiff for bind9 on Focal V2"
https://bugs.l
Attached is a debdiff for Bind9 on Focal to fix this bug.
** Patch added: "Debdiff for bind9 on Focal"
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+attachment/5461528/+files/lp1909950_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Summary changed:
- TCP connections never close
+ named: TCP connections sometimes never close due to race in socket teardown
** Description changed:
- The default timeout for TCP connections on port 53 to named/bind9 is 300
- seconds. The upstream ISC build of bind9 uses this and honors an
-
ckets stuck in ESTABLISHED and not torn down.
I will let you know once there is a new build in -proposed for
verification.
Thanks,
Matthew
** Changed in: bind9 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: bind9 (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffel
Hi Manish,
Thanks for testing the Groovy 5.8 kernel in -proposed!
The Focal 5.4 / Bionic 5.4 HWE kernel will be in -proposed next week
sometime, if you are looking to verify that as well.
I will also ask our customer in common to verify the Bionic HWE kernel
when it becomes available.
Thanks fo
Hi Adam,
I think I have found the issue that you are experiencing. I don't have a
way to reproduce just yet, but I have built a test package for you to
try.
I came across the following upstream bug:
https://gitlab.isc.org/isc-projects/bind9/-/issues/1700
The users mention that tcp connections s
** Also affects: bind9 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
Performing verification for Focal.
I installed rsyslog-relp 8.2001.0-1ubuntu1.1 and librelp0 1.5.0-1ubuntu2
from -updates.
>From there I set up the configuration file, launched a new rsyslog
instance, and used netcat to set 100 packets to the relp port.
https://paste.ubuntu.com/p/HfSDvNJzpX/
As
Performing verification for Focal.
The previous version in -proposed, 1.5.0-1ubuntu2.20.04.1, failed to
build on riscv64, as can be seen in the below links:
https://launchpad.net/ubuntu/+source/librelp/1.5.0-1ubuntu2.20.04.1
https://launchpad.net/ubuntu/+source/librelp/1.5.0-1ubuntu2.20.04.1/+bui
Attached is a debdiff for librelp on Hirsute.
** Patch added: "librelp debdiff for hirsute"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1912969/+attachment/5456836/+files/lp1912969_librelp_hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: librelp (Ubuntu Hirsute)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912969
Title:
librelp is FTBFS on riscv64 on Focal
To manage notifications
Hi Mauricio,
I filed bug 1912969 to fix the FTBFS for librelp on focal. Adjusting the
packets down from 50,000 to 10,000 makes the build succeed on riscv64.
I attached two debdiffs, one an incremental patch from
1.5.0-1ubuntu2.20.04.1, and the other a full patch from 1.5.0-1ubuntu2.
Please revie
Attached is a debdiff from librelp_1.5.0-1ubuntu2 to
librelp_1.5.0-1ubuntu2.20.04.2
** Patch added: "librelp debdiff from -1ubuntu2"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1912969/+attachment/5456452/+files/lp1912969_librelp_focal_alternate.debdiff
--
You received this bug no
Attached is a debdiff for librelp from librelp_1.5.0-1ubuntu2.20.04.1 to
librelp_1.5.0-1ubuntu2.20.04.2
** Patch added: "librelp debdiff from -1ubuntu2.20.04.1"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1912969/+attachment/5456439/+files/lp1912969_librelp_focal.debdiff
--
You re
** Description changed:
[Impact]
During the recent SRU for bug 1908473, we found that librelp is FTBFS on
riscv64 on Focal, due to the test cases basic-realistic.sh and tls-
basic-realistic.sh failing during dh_auto_test during package build.
dh_auto_test --no-parallel
make -j1
** Description changed:
[Impact]
During the recent SRU for bug 1908473, we found that librelp is FTBFS on
riscv64 on Focal, due to the test cases basic-realistic.sh and tls-
basic-realistic.sh failing during dh_auto_test during package build.
dh_auto_test --no-parallel
- make
mportance: Undecided
Status: Fix Released
** Affects: librelp (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Changed in: librelp (Ubuntu)
Status: New => Fix Released
** Also affects: librelp
Hi Mauricio,
It seems riscv64 passes on Groovy due to tests being skipped on the
riscv64 architecture.
>From Groovy's build log:
https://paste.ubuntu.com/p/NCJPDVSbSW/
If you look at the man page for dh_auto_test it mentions:
If the DEB_BUILD_OPTIONS environment variable contains nocheck, no t
Performing verification for Focal
I installed rsyslog-relp 8.2001.0-1ubuntu1.1 and librelp0 1.5.0-1ubuntu2
from -updates.
>From there I set up the configuration file, launched a new rsyslog instance,
>and
used netcat to set 100 packets to the relp port.
https://paste.ubuntu.com/p/jCs9Dy6FYF/
A
Performing verification for librelp in Groovy.
I installed rsyslog-relp 8.2006.0-2ubuntu1 and librelp 1.5.0-1ubuntu2
from -updates to reproduce:
https://paste.ubuntu.com/p/gtn4rcXc72/
>From there I set up the configuration script, ran a new instance of
rsyslog, and used netcat to open 100 connec
Same one failure on today's rebuild. Strange, since this is the exact
same code as Groovy.
** Attachment added:
"buildlog_ubuntu-focal-riscv64.librelp_1.5.0-1ubuntu2.20.04.1_BUILDING.txt.gz.5"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5454976/+files/buildlog_
Hi Robie, I agree this probably isn't worth a SRU to Groovy, I just made
the packages available in the odd chance that they might be considered.
I will mark Groovy as won't fix.
Hirsute is what really matters in the end.
** Changed in: rsyslog (Ubuntu Groovy)
Status: In Progress => Won't F
Hello,
A another user has reported a very similar issue. They operate bind9
resolvers in both recursive and authoritative configurations, and
occasionally, their servers will stop responding to TCP requests.
UDP still operates as normal, but TCP connections will time out.
named is still listenin
Attached is a patch which changes /var/log/dmesg to 0640 on groovy. It
also contains Steve's recommendation to set the logrotate files to 0640.
** Patch added: "Debdiff for syslog on groovy"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122/+attachment/5454311/+files/lp1912122_gro
Attached is a patch which changes /var/log/dmesg to 0640 on hirsute. It
also contains Steve's recommendation to set the logrotate files to 0640.
** Patch removed: "Debdiff for rsyslog on hirsute"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122/+attachment/5454004/+files/lp191212
** 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/1912122
Title:
/var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT
restrictions
To manage notifications abo
Attached is a debdiff for Groovy to change /var/log/dmesg to 0640.
** Patch added: "Debdiff for syslog on groovy"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122/+attachment/5454005/+files/lp1912122_groovy.debdiff
--
You received this bug notification because you are a member
Attached is a debdiff for hirsute to set /var/log/dmesg to 0640.
** Patch added: "Debdiff for rsyslog on hirsute"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1912122/+attachment/5454004/+files/lp1912122_hirsute.debdiff
--
You received this bug notification because you are a member
** 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/1912122
Title:
/var/log/dmesg is 0644, should be 0640 to match new DMESG_RESTRICT
restrictions
To manage notifications about this
** 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]
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)
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1911848
[Impact]
On CascadeLake based KVM hosts, Windows Server 2k16 and 2k19 guests will
fail to start once they have enabled the hyper-v role for nested
virtualisation.
The Windows Server guests will get stuck
are no workarounds. Users would
need to downgrade their kernel while a fix is developed.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Pr
(unassigned) => Matthew Ruffell (mruffell)
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1909062
[Impact]
For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000
Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel
to the 5.4 kern
I built 1.9.0-1ubuntu0+lp1910307v20210113b2 in
https://launchpad.net/~mruffell/+archive/ubuntu/lp1910307-test, and
contains the identical code to the debdiff above. It builds successfully
on all supported architectures, which also includes riscv64, which means
the patch we merged in still works as
Attached is the revised debdiff between librelp_1.9.0-1.dsc and
librelp_1.9.0-1ubuntu1.dsc
** Patch removed: "Debdiff with the merge from Debian"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1910307/+attachment/5449599/+files/librelp_diff_debian.debdiff
** Patch added: "Debdiff with
** Description changed:
[Impact]
librelp 1.9.0-1 is available in Debian, and is much newer than what we
carry in Ubuntu 1.5.0-1ubuntu2. This bug tracks the merge to the newer
version.
This bug is needed for the SRU of bug 1908473, which fixes a file
descriptor leak in librelp. Th
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Groovy)
Status: Fix Released
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1909062
[Impact]
For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000
Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel
to the 5.4 kernel, Kubernetes Internal DNS requests wil
** 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/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
To manag
Note - we no longer need to carry the "python2.diff" patch present in
librelp_1.5.0-1ubuntu2.dsc due to the test system being ported to
python3.
The tests have been changed so that the scripts are executed by a python
interpreter, and not bash, so the shbangs for "/usr/bin/env python" are
now dead
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
Bugs, which is
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
Bugs, which
Attached is the debdiff from librelp_1.5.0-1ubuntu2.dsc to
librelp_1.9.0-1ubuntu1.dsc
** Patch added: "Debdiff with changes from old ubuntu to new ubuntu"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1910307/+attachment/5449600/+files/librelp_diff_ubuntu.debdiff
** Description chang
Attached is the debdiff from librelp_1.9.0-1.dsc to the new
librelp_1.9.0-1ubuntu1.dsc
** Patch added: "Debdiff with the merge from Debian"
https://bugs.launchpad.net/ubuntu/+source/librelp/+bug/1910307/+attachment/5449599/+files/librelp_diff_debian.debdiff
--
You received this bug notificat
(Ubuntu)
Importance: Wishlist
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: librelp (Ubuntu Hirsute)
Importance: Wishlist
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Tags added: sts
** Also affects
** 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
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.
Thanks Manish! I am building a test kernel now, and I will let you know
once it is ready to test.
If we get good test results, I will submit the patch for SRU to the
Ubuntu kernels once the patch has hit mainline.
** Description changed:
- With QL41xxx and Ubuntu DNS server DNS failures are seen
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Summary changed:
- Ubuntu kernel 5.x QL41xxx NIC (qede driver) Kubernetes internal DNS failure
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Thanks Tobias for the testing. Good to hear it functions as intended.
Performing verification for Bionic
I installed adcli 0.8.2-1ubuntu1.2 from -proposed, and joined a domain
without using the --use-ldaps flag.
https://paste.ubuntu.com/p/RByVZRPhCK/
Next, I added the firewall rules from the te
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
Hi Tobias,
If you have a moment, could you please help test the new adcli package
in -proposed? Mainly focusing on testing Bionic, to ensure the
regression has been fixed.
Can you run through some tests with and without the --use-ldaps flag?
You can install the new adcli package in -proposed lik
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
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
Hi @hloeung, these patches are available in 4.15.0-128-generic, and
5.4.0-58-generic.
They are both re-spins of 4.15.0-126-generic and 5.4.0-56-generic,
respectively.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Hi Benjamin,
The respun kernel has now landed in -updates, and is version
4.15.0-128-generic.
Please re-schedule the maintenance window for the Launchpad git server,
and re-attempt moving to the fixed kernel.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubu
Performing verification for Focal.
I spun up a m5d.4xlarge instance on AWS, to utilise the 2x 300GB NVMe
drives that support block discard.
I enabled -proposed, and installed the 5.4.0-58-generic kernel.
The following is the repro session running through the full testcase:
https://paste.ubuntu.
Performing verification for Bionic.
I spun up a m5d.4xlarge instance on AWS, to utilise the 2x 300GB NVMe
drives that support block discard.
I enabled -proposed, and installed the 4.15.0-128-generic kernel.
The following is the repro session running through the full testcase:
https://paste.ubun
Hi Markus,
I am deeply sorry for causing the regression. We are aware, and tracking
the issue in bug 1907262.
The kernel team have started an emergency revert and you can expect
fixed kernels to be released in the next day or so.
--
You received this bug notification because you are a member of
Hi Thimo,
Firstly, thank you for your bug report, we really, really appreciate it.
You are correct, the recent raid10 patches appear to cause filesystem
corruption on raid10 arrays.
I have spent the day reproducing, and I can confirm that the
4.15.0-126-generic, 5.4.0-56-generic and 5.8.0-31-gen
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Stat
Hi Thimo,
Thank you for the very detailed bug report. I will start investigating this
immediately.
Thanks,
Matthew
--
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 lead
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
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
** 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/1906627
Title:
GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active
Directory, causing recent adcli regress
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
** 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
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627
Title:
adcli fails, can't contact LDAP server
To manage notificati
** 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
*** This bug is a duplicate of bug 1906627 ***
https://bugs.launchpad.net/bugs/1906627
** This bug has been marked a duplicate of bug 1906627
adcli fails, can't contact LDAP server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
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
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
401 - 500 of 829 matches
Mail list logo