** 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
I built the current upstream master branch of adcli, and it too fails on
Bionic:
https://paste.ubuntu.com/p/vsgfxyb9X7/
This must be why the exact same patches work on Focal. The problem
probably isn't adcli itself, but more likely a library it depends on.
# apt depends adcli
adcli
Depends: li
med => Fix Released
** Changed in: adcli (Ubuntu Bionic)
Status: New => In Progress
** Changed in: adcli (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: adcli (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug no
** Tags added: regression-update
--
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 notifications about this bug go to:
https://bugs.launc
** Also affects: adcli (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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 noti
kernels also have full livepatch
support, which is good news for you.
Let me know how the 4.15.0-126-generic kernel goes on the Launchpad git
server, since it should perform just as well as the test kernel you are
currently running.
Thanks,
Matthew
--
You received this bug notification because you
Public bug reported:
Please upgrade haproxy to the latest stable version as of November 2020.
** Affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
** Tags: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
age.
I'll let you know once the kernel has reached -updates, likely Monday or
Tuesday next week.
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/1898786
Title:
bcache: Issues wit
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
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
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-
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 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 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 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
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
0th of November, give or take
a few days if any CVEs turn up.
I believe this kernel should be live-patchable, although this may not be
the case if the kernel is respun before release. Hopefully you will only
have to schedule the maintenance window just the once.
Thanks,
Matthew
--
You received th
Performing verification for Bionic.
I enabled -proposed and installed 4.15.0-125-generic to a i3.8xlarge AWS
instance.
>From there, I followed the testcase steps:
$ uname -rv
4.15.0-125-generic #128-Ubuntu SMP Mon Nov 9 20:51:00 UTC 2020
$ lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda
Performing verification for Focal.
I enabled -proposed and installed 5.4.0-55-generic to a i3.8xlarge AWS
instance.
>From there, I followed the testcase steps:
$ uname -rv
5.4.0-55-generic #61-Ubuntu SMP Mon Nov 9 20:49:56 UTC 2020
$ lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda202:
Performing verification for Groovy.
I enabled -proposed and installed 5.8.0-30-generic to a i3.8xlarge AWS
instance.
>From there, I followed the testcase steps:
$ uname -rv
5.8.0-30-generic #32-Ubuntu SMP Mon Nov 9 21:03:15 UTC 2020
$ lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda202
Performing verification for Focal.
I created a i3.large instance on AWS, since it has 1x NVMe drive that
supports trim and block discard.
I ensured that I could reproduce the problem with 5.4.0-54-generic from
-updates, and I followed the instructions in the Testcase section, and
the final fstrim
** Description changed:
By default, logwatch performs a hostname lookup of every IP address
reported in SSHD logs. This has two negative consequences:
- 1. If there are lots of IP addresses to lookup, this increases the runtime of
logwatch significantly.
- 2. If logwatch is set to email lo
Public bug reported:
By default, logwatch performs a hostname lookup of every IP address
reported in SSHD logs. This has two negative consequences:
1. If there are lots of IP addresses to lookup, this increases the runtime of
logwatch significantly.
2. If logwatch is set to email logs, some spam
** 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
Attached is a revised debdiff for adcli in Bionic.
** Patch added: "adcli debdiff for Bionic v2"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432874/+files/lp1868703_adcli_bionic_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
B
Attached is a revised debdiff for adcli for Focal.
** Patch added: "adcli debdiff for Focal v2"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432871/+files/lp1868703_adcli_focal_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bug
Attached is a debdiff for adcli in Groovy.
** Patch added: "adcli debdiff for groovy"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432870/+files/lp1868703_adcli_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attached is a debdiff for adcli for Hirsute.
** Patch added: "adcli debdiff for hirsute"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432869/+files/lp1868703_adcli_hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Attached is a revised debdiff for sssd for Bionic.
** Patch added: "sssd debdiff for Bionic v2"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703/+attachment/5432867/+files/lp1868703_sssd_bionic_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bug
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,
** 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
** 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
** 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:
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
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 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
** 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
** 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
Tested the mksquashfs command in version 4.4 (2019/08/29) on Ubuntu 20.04.
It now says: Not enough or invalid arguments in pseudo file definition "/ f 444
root root echo"
Appending to the archive now reports "File system corrupted: filename
too long" and fails gracefully.
Listing the archive als
I filed a separate Issue on GitHub:
https://github.com/plougher/squashfs-tools/issues/50
I believe the problems were fixed in these two commits:
https://github.com/plougher/squashfs-tools/commit/c249ba3bbdb41034f6027f93d590a8ea06d32c75
mksquashfs: add filesystem corruption checks when reading fil
** 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
Public bug reported:
Received software update prompt. Followed prompts as always. Received message
asking for GRUB location. Selected the SSD with dual boot to WIN7 and Ubuntu
20.04.01. 64 bit.
GNOME version 3.36.3
Install failed.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: gru
Public bug reported:
My bluetooth mouse loses it's settings at every reconnect. It's a
Logitech MX Master 2S in bluetooth mode (NOT using the usb dongle.) The
control panel always shows my desired settings, but I have to poke both
the speed and scroll direction settings to get them reset to the
** 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
** 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
** 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
I am experiencing this issue also. Looking at the Xorg.0.log I am
seeing the screen disconnect .
[ 71289.913] (--) NVIDIA(GPU-0): DFP-4: disconnected
[ 71289.913] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[ 71289.913] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
[ 71289.913] (
** 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
github.com/SSSD/sssd/commit/24387e19f065e6a585b1120d5568cb4df271d102
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/1868703
Title:
Support new AD requirements (ADV190023)
To manage not
** Changed in: adcli (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: adcli (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: adcli (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: adcli (Ubuntu Focal)
I
Patches have been submitted to the Ubuntu kernel mailing list:
Patchset for Bionic:
https://lists.ubuntu.com/archives/kernel-team/2020-October/114166.html
https://lists.ubuntu.com/archives/kernel-team/2020-October/114167.html
https://lists.ubuntu.com/archives/kernel-team/2020-October/114168.html
h
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1898786
[Impact]
Systems that utilise bcache can experience extremely high IO wait times
when under constant IO pressure. The IO wait times seem to stay at a
consistent 1 second, and never drop as long as the bcache s
ed => Medium
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
- Hello,
+ BugLink: https://bugs.launchpad.net/bugs/1898786
I am having this same issue on my Lenovo X220. Using Ubuntu 20.04.1 LTS.
I am able to boot by disabling the splash screen using:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic
root=UUID=70d5c302-0fe3-4a83-9076-ca834b973ac3 ro nosplash
I am using the stock kernel:
Linux version 5.4.0-51-generic (build
Attached is a debdiff for gnome-shell for Focal with the required
patches to implement VMware Horizon SSO support.
** Patch added: "gnome-shell debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886592/+attachment/5423914/+files/lp1886592_focal.debdiff
--
You rece
Attached is a debdiff for Bionic which implements support for VMware
Horizon SSO in gnome-shell.
** Patch added: "gnome-shell debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886592/+attachment/5423915/+files/lp1886592_bionic.debdiff
--
You received this bug no
** Description changed:
[Impact]
VMware Horizon is a VDI product that runs atop of VMware's normal
virtualisation stack, and it supports SSO authentication for login.
In the past, the VMware Horizon agent has been pretty buggy, and
requires SSO patches to be present to function, ot
Public bug reported:
Appears to be repeatedly conflicting with bat-extras and ripgrep. Had to
uninstall both.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bat 0.12.1-1build1
ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic
5.4.44
Uname: Linux 5.4.0-764
Public bug reported:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-headers-5.4.0-48 linux-headers-5.4.0-48-generic
linux-image-5.4.0-48-generic linux-modules-
s for SRU to the Ubuntu kernels.
Let me know how the test kernel is going next week.
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/1898786
Title:
Issue with bcache bch_mca_scan ca
USC no longer offers any software for sale.
** Changed in: software-center (Ubuntu)
Status: Incomplete => Won't Fix
** No longer affects: ubuntu-translations
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
The release-upgrader can not calculate the upgrade after removal of the
hauppauge kernel drivers. I have some other ppas installed, but those
haven't caused problems on upgrade in the past.
Any assistance you all can provide would be helpful. Thanks!
ProblemType: Bug
Distr
t kernel. Enable
bcache shrinking and try reproduce the problem. Hopefully the test
kernel is an improvement and fixes your issues.
Let me know how the test kernel goes.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Verifying for xenial:
I enabled -proposed, and installed 4.4.0-1116-aws:
$ uname -rv
4.4.0-1116-aws #129-Ubuntu SMP Tue Sep 29 18:17:22 UTC 2020
I rebooted, and was able to ssh in, and dmesg was clean.
I then installed 4.4.0-192-generic:
$ uname -rv
4.4.0-192-generic #222-Ubuntu SMP Tue Sep 29
Andrew, I suggest deciding what you want this bug report to be about.
If it’s about the VLC snap, then in this case Sebastien suggests it’s a
bug in snapd.
If it’s about Ubuntu Software, then you should change the steps to
reproduce to focus on Ubuntu Software.
Either way, it should not be filed
Hello @shaynagar, thank you very much for reporting! We will look into
this asap.
More details: 4.4.0-190-generic is fine, 4.4.0-191-generic contains the
regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Description changed:
- This is a POTENTIAL REGRESSION.
+ [Impact]
- This issue occurs on one of the AWS instance "t2.medium"
+ The new xe
Performing verification:
First, reproducing on older kernel:
$ uname -rv
4.4.0-190-generic #220-Ubuntu SMP Fri Aug 28 23:02:15 UTC 2020
$ grep "clocksource" /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc"
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.0-190-generic
root=UUID=f6
** 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
h support block discard will be affected.
Traditional hard disks, or SSD devices which do not support block
discard would not be affected.
If a regression were to occur, users could work around the issue by
running "mkfs.xfs -K " which would skip block discard entirely.
** Affects: linux
(I see no reason for this to be private, and the person responsible no
longer has an LP account.)
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/47809
d to upstream stable, and are trusted by
the community.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also affects:
Just chiming in to say I am having the same problem with a snap (Tiled),
neither the --classic workaround nor sudo snap connect tiled:removable-
media works. Between this and the other issues people have noted with
snap, it seems like it is just bad software and the team is not doing a
good job cre
Public bug reported:
installing ubuntu on dell poweredge t310 left installer for 10 minutes
then it crashed
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules:
*** This bug is a duplicate of bug 1756315 ***
https://bugs.launchpad.net/bugs/1756315
** This bug has been marked a duplicate of bug 1756315
fstrim and discard operations take too long to complete - Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bug
Hello Alexandre,
I tried to reproduce this bug, and I believe it has been fixed.
I started a i3.4xlarge instance on AWS, with Xenial as the distro:
$ uname -rv
4.4.0-1112-aws #124-Ubuntu SMP Fri Jul 24 11:10:25 UTC 2020
>From there, I checked the NVMe disks:
$ lsblk
NAMEMAJ:MIN RM SIZE RO
As promised, I have an update on the lab machine I left running
ksm_refcnt_overflow.sh for a week straight.
The machine was running 4.15.0-116-generic from -proposed:
$ uname -rv
4.15.0-116-generic #117-Ubuntu SMP Fri Aug 28 16:04:22 UTC 2020
$ uptime
04:36:14 up 7 days, 1 min, 1 user, load av
How about you try a slightly older kernel then:
To install 5.4.0-31-generic:
$ sudo apt install linux-image-5.4.0-31-generic linux-
modules-5.4.0-31-generic linux-modules-extra-5.4.0-31-generic linux-
headers-5.4.0-31-generic linux-headers-5.4.0-31
Then reboot your computer. Do the same as you d
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1894591
[Impact]
The default clocksource for a KVM VM is kvm-clock, and I happen to need
tsc.
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
kvm-clock
If I edit /etc/default/grub and
.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Xenial)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
@braingateway
Can you please try booting into the 5.4.0-42-generic kernel and see if
that works?
When you turn your computer on, press and hold the shift key to access the GRUB
boot menu.
Select "Advanced Options" and then "Ubuntu, with Linux 5.4.0-42-generic"
If 5.4.0-42-generic works and 5.4.
As requested by the kernel team (in https://lists.ubuntu.com/archives
/kernel-team/2020-August/112775.html), I will do some additional testing
for this SRU to really make sure it won't cause any regressions.
I provisioned a lab machine on segmaas, running Bionic. I installed the
4.15.0-116-generic
Verification steps for focal:
Again, I made sure I can reproduce on the existing 5.4.0-42-generic
kernel.
I copied ksm_refcnt_overflow.sh and zero_page_refcount.c to the VM, and
built the kernel module, and inserted it into the kernel:
$ sudo insmod zero_page_refcount.ko
$ cat /proc/zero_page_re
Verification steps for Bionic:
First, I made sure I could reproduce the problem on 4.15.0-115-generic.
I made a fresh Bionic VM, and copied over the ksm_refcnt_overflow.sh and
zero_page_refcound.c files.
I built the kernel module, and inserted it into the kernel.
>From there, I checked the zero
As 5.8.0-16-generic has now been released to the -release pocket,
CONFIG_SECURITY_DMESG_RESTRICT is now enabled in Groovy. Marking the
changes to the kernel as Fix Released.
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification be
As per my most recent email to ubuntu-devel, I am marking the changes to
util-linux as Won't Fix.
Relevant mailing list discussion (for future reference):
Ansgar responded on debian-devel mentioning that adding cap_syslog to
dmesg enables the user to clear the kernel log buffer:
https://lists.de
are still absent on restart
i will now mark this bug closed
thanks for your help
** Changed in: gnome-flashback (Ubuntu)
Assignee: (unassigned) => matthew cooper (mczakk)
** Changed in: gnome-flashback (Ubuntu)
Status: New => Invalid
--
You received this bug notification becau
even though gsettings shows these returns?
org.nemo.desktop show-desktop-icons false
org.nemo.desktop home-icon-visible false
org.nemo.desktop trash-icon-visible false
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Package changed: ubuntu => metacity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893110
Title:
Cant remove desktop icons ubuntu 20.04
To manage notifications about this bug go to:
htt
Public bug reported:
I've just upgraded to 20.04 from 18.04 and am having this issue using Gnome
Flashback(metacity) desktop.
The 'Home' and 'Trash' icons on my desktop continue to be there even after i
have changed the settings using gsettings set
the text below shows the output of gsetting
I asked the customer to test 4.15.0-114-generic on Xenial HWE from
-proposed on their HP DL360 Gen10 machines with the Intel Xeon Gold 5120
CPU. The machine has Sub-NUMA Clustering enabled and it is active.
The machine boots successfully, and there are no call traces or kernel
oops present:
# una
I installed 4.15.0-114-generic from -proposed to my test client machine,
which is a Ubuntu 18.04 Desktop VM.
I mounted two NFS shares, one with sec=sys, and the other with
sec=krb5p. I then opened each share up in separate tabs in Nautilus.
I then CUT a file from the sec=sys share, and PASTED it
701 - 800 of 19691 matches
Mail list logo
