I created a new c5d.large instance on AWS, and installed
4.4.0-177-generic from -updates. I ran through the reproduction steps,
and the issue reproduces.
I then created a new c5d.large instance, enabled -proposed and installed
4.4.0-178-generic. I again ran through the reproduction steps, and
Oops, sorry. I rebooted my machine and the problem does not reproduce,
since I installed 3.36.0-2ubuntu2 and hadn't rebooted.
** Changed in: gnome-shell (Ubuntu Focal)
Status: Incomplete => Fix Released
** Tags removed: champagne
--
You received this bug notification because you are a
Oops, sorry. I rebooted my machine and the problem does not reproduce,
since I installed 3.36.0-2ubuntu2 and hadn't rebooted.
** Changed in: gnome-shell (Ubuntu Focal)
Status: Incomplete => Fix Released
** Tags removed: champagne
--
You received this bug notification because you are a
Oops, sorry. I rebooted my machine and the problem does not reproduce,
since I installed 3.36.0-2ubuntu2 and hadn't rebooted.
** Changed in: gnome-shell (Ubuntu Focal)
Status: Incomplete => Fix Released
** Tags removed: champagne
--
You received this bug notification because you are a
Attached is a screencast demonstrating the problem.
** Attachment added: "Screencast of virtual desktops breaking"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+attachment/5343942/+files/Screencast%20from%2001-04-20%2011%3A08%3A18.webm
--
You received this bug
Attached is a screencast demonstrating the problem.
** Attachment added: "Screencast of virtual desktops breaking"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+attachment/5343942/+files/Screencast%20from%2001-04-20%2011%3A08%3A18.webm
--
You received this bug
Attached is a screencast demonstrating the problem.
** Attachment added: "Screencast of virtual desktops breaking"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+attachment/5343942/+files/Screencast%20from%2001-04-20%2011%3A08%3A18.webm
--
You received this bug
Public bug reported:
gnome-shell: virtual desktops broken as windows appear on every desktop,
regardless of where they are placed
On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you
open a few applications, such as gnome-disks, nautilus and firefox, then
move a window to a
Public bug reported:
gnome-shell: virtual desktops broken as windows appear on every desktop,
regardless of where they are placed
On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you
open a few applications, such as gnome-disks, nautilus and firefox, then
move a window to a
Public bug reported:
gnome-shell: virtual desktops broken as windows appear on every desktop,
regardless of where they are placed
On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you
open a few applications, such as gnome-disks, nautilus and firefox, then
move a window to a
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869970
Title:
yaru: Long passwords cause lock screen and gdm password boxes to
expand
To manage notifications about this bug
Public bug reported:
yaru: Long passwords cause lock screen and gdm password boxes to expand
On focal, with yaru-theme 20.04.4, if the user has a very long password,
the small password box will expand for a split second once the user
presses the enter key to accept the password.
I believe this
Attached is a screencast of the bug being reproduced.
** Attachment added: "Screencast of password box expanding"
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1869970/+attachment/5343940/+files/Screencast%20from%2001-04-20%2010%3A49%3A43.webm
** Tags added: champagne
--
You
Public bug reported:
yaru: Long passwords cause lock screen and gdm password boxes to expand
On focal, with yaru-theme 20.04.4, if the user has a very long password,
the small password box will expand for a split second once the user
presses the enter key to accept the password.
I believe this
untu 16.10 and later, meaning xenial is the
only impacted supported release.
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: lvm2 (Ubuntu Xenial)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: Won't Fix
** Affects: lv
untu 16.10 and later, meaning xenial is the
only impacted supported release.
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: lvm2 (Ubuntu Xenial)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: Won't Fix
** Affects: lv
untu 16.10 and later, meaning xenial is the
only impacted supported release.
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: lvm2 (Ubuntu Xenial)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: Won't Fix
** Affects: lv
Public bug reported:
On Focal, I created a new KVM machine using virt-manager. Nothing
special, just a bionic guest.
Upon examining the qemu-system-x86_64 process that got spawned, /usr/bin
/qemu-system-x86_64 was executed directly, and my override in
/usr/local/bin/qemu-system-x86_64 was not
On Mon, Mar 16, 2020 at 12:58:37PM -0400, Jerry Geis wrote:
> > Just a guess,
> > Recompile Dadhi.
>
>
> I'd rather not have to do that step. I "desire" to make the image and
> copy to the physical disk with dd and have everything set to go. Not
> take further time and "recompile" things.
>
>
** Description changed:
[Impact]
- nvme-cli in bionic lacks the toshiba-nvme plugin. This plugin provides
functionality unique to Toshiba NVME devices:
- $ sudo ./nvme toshiba
+ The version of nvme-cli in Bionic (1.5-ubuntu1) lacks support for
+ functionality unique to Toshiba NVMe
** 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/1866897
Title:
Add toshiba plugin support
To manage notifications about this bug go to:
to pull in "5e9239e Fixes for log page access".
** Changed in: nvme-cli (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: nvme-cli (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: nvme-cli (Ubuntu Bionic)
Stat
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Low
Status: Fix Released
** Also affects: yaru-theme (Ubuntu Focal)
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Low
Status: Fix Released
** Also affects: yaru-theme (Ubuntu Focal)
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Low
Status: Fix Released
** Also affects: yaru-theme (Ubuntu Focal)
I did some extensive digging and found why it is fixed in Adwaita and
not Yaru.
Two weeks ago, the below commit was merged to gnome-shell. It checks to
see if the string width is longer than the box width, and if it is, it
switches to a hardcoded "leightweight" width of 13pt.
commit
I did some extensive digging and found why it is fixed in Adwaita and
not Yaru.
Two weeks ago, the below commit was merged to gnome-shell. It checks to
see if the string width is longer than the box width, and if it is, it
switches to a hardcoded "leightweight" width of 13pt.
commit
I did some extensive digging and found why it is fixed in Adwaita and
not Yaru.
Two weeks ago, the below commit was merged to gnome-shell. It checks to
see if the string width is longer than the box width, and if it is, it
switches to a hardcoded "leightweight" width of 13pt.
commit
I found the bug. The font-size is too large in .message-dialog-content
.message-dialog-title.
It is set to 18pt, but the largest it should be is 13pt.
Attached is a picture demonstrating each font size, no other changes made.
** Attachment added: "Comparison of font sizes"
I found the bug. The font-size is too large in .message-dialog-content
.message-dialog-title.
It is set to 18pt, but the largest it should be is 13pt.
Attached is a picture demonstrating each font size, no other changes made.
** Attachment added: "Comparison of font sizes"
I found the bug. The font-size is too large in .message-dialog-content
.message-dialog-title.
It is set to 18pt, but the largest it should be is 13pt.
Attached is a picture demonstrating each font size, no other changes made.
** Attachment added: "Comparison of font sizes"
I went and checked Yaru theme from Eoan, and the dialogue is displayed
correctly. Maybe something broke on the move to the new dialogue box? Attached
is the same gnome-disks dialogue on Eoan.
I still think the issue is the font is too big on the title of the new Yaru
theme dialogue box.
**
I went and checked Yaru theme from Eoan, and the dialogue is displayed
correctly. Maybe something broke on the move to the new dialogue box? Attached
is the same gnome-disks dialogue on Eoan.
I still think the issue is the font is too big on the title of the new Yaru
theme dialogue box.
**
I went and checked Yaru theme from Eoan, and the dialogue is displayed
correctly. Maybe something broke on the move to the new dialogue box? Attached
is the same gnome-disks dialogue on Eoan.
I still think the issue is the font is too big on the title of the new Yaru
theme dialogue box.
**
Hello MadsRH and Daniel,
I checked the Adwaita theme, and no text clipping is seen, and things are as
expected. Attached is a screenshot of the same gnome-disks password dialogue in
Adwaita.
** Attachment added: "Screenshot of Adwaita password overlay box"
Hello MadsRH and Daniel,
I checked the Adwaita theme, and no text clipping is seen, and things are as
expected. Attached is a screenshot of the same gnome-disks password dialogue in
Adwaita.
** Attachment added: "Screenshot of Adwaita password overlay box"
Hello MadsRH and Daniel,
I checked the Adwaita theme, and no text clipping is seen, and things are as
expected. Attached is a screenshot of the same gnome-disks password dialogue in
Adwaita.
** Attachment added: "Screenshot of Adwaita password overlay box"
Public bug reported:
If you have a password overlay dialogue box present on your screen, for
example, trying to mount an encrypted disk image from gnome-disks, or
trying to unlock an ssh key, if the lock screen appears while the
dialogue is in place, after unlocking the screen, you can still
Public bug reported:
If you have a password overlay dialogue box present on your screen, for
example, trying to mount an encrypted disk image from gnome-disks, or
trying to unlock an ssh key, if the lock screen appears while the
dialogue is in place, after unlocking the screen, you can still
Public bug reported:
If you have a password overlay dialogue box present on your screen, for
example, trying to mount an encrypted disk image from gnome-disks, or
trying to unlock an ssh key, if the lock screen appears while the
dialogue is in place, after unlocking the screen, you can still
I opened an issue upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/2321
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1866275
Title:
Password overlay dialogue
I opened an issue upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/2321
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866275
Title:
Password overlay dialogue breaks during screen lock
I opened an issue upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/2321
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1866275
Title:
Password overlay dialogue breaks
Public bug reported:
On focal with yaru-gtk-theme 20.04.2, the text in the password overlay
dialogue boxes is clipped. Possibly the font is too big, or the dialogue
box not wide enough?
Attached is a screenshot of attempting to mount an encrypted disk image in
gnome-disks, and I can also
Public bug reported:
On focal with yaru-gtk-theme 20.04.2, the text in the password overlay
dialogue boxes is clipped. Possibly the font is too big, or the dialogue
box not wide enough?
Attached is a screenshot of attempting to mount an encrypted disk image in
gnome-disks, and I can also
*** This bug is a duplicate of bug 1864586 ***
https://bugs.launchpad.net/bugs/1864586
Hi Jonathan,
Thanks for reporting! This is an issue where the necessary files for the
new plymouth theme, plymouth-theme-spinner / bgrt, are not placed in
initrd properly. We are tracking this in Bug
*** This bug is a duplicate of bug 1864586 ***
https://bugs.launchpad.net/bugs/1864586
Hi Jonathan,
Thanks for reporting! This is an issue where the necessary files for the
new plymouth theme, plymouth-theme-spinner / bgrt, are not placed in
initrd properly. We are tracking this in Bug
Attached is a standard journalctl with no additional debugging enabled.
** Attachment added: "Journalctl Standard"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1864586/+attachment/5331398/+files/journalctl_standard.log
--
You received this bug notification because you are a
Attached is journcalctl with plymouth:debug appended to the kernel
command line.
** Attachment added: "Journalctl with debugging"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1864586/+attachment/5331399/+files/journalctl_plymouth_debug.log
--
You received this bug notification
Attached is plymouth debug logs.
** Attachment added: "plymouth debugging logs"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1864586/+attachment/5331400/+files/plymouth_debug.log
** Also affects: plymouth (Ubuntu Focal)
Importance: High
Status: Incomplete
** Changed in:
Public bug reported:
I Installed focal from the daily-pending ISO image, timestamp 2020-02-21
07:52
In the installer I selected LVM + LUKS.
Upon reboot I am shown a text plymouth theme, which is an incorrect
screen size and the LUKS password prompt is missing. See attached
screenshot.
If you
$ sudo apt-cache policy plymouth
[sudo] password for ubuntu:
plymouth:
Installed: 0.9.4git20200109-0ubuntu3
Candidate: 0.9.4git20200109-0ubuntu3
Version table:
*** 0.9.4git20200109-0ubuntu3 500
500 http://nz.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100
Public bug reported:
On Focal, if you go to the 'About' pane in gnome-control-center, a large
GNOME icon is displayed. On previous releases, usually an Ubuntu logo is
displayed instead.
Is this change intentional? Or did upstream GNOME change a file name or
something?
Attached is a screenshot.
Public bug reported:
On Focal, if you go to the 'About' pane in gnome-control-center, a large
GNOME icon is displayed. On previous releases, usually an Ubuntu logo is
displayed instead.
Is this change intentional? Or did upstream GNOME change a file name or
something?
Attached is a screenshot.
Public bug reported:
On Focal, if you go to the 'About' pane in gnome-control-center, a large
GNOME icon is displayed. On previous releases, usually an Ubuntu logo is
displayed instead.
Is this change intentional? Or did upstream GNOME change a file name or
something?
Attached is a screenshot.
I managed to figure out what was going on, and made a patch to fix the
problem. I sent it upstream for feedback:
Cover Letter:
https://lore.kernel.org/linux-fsdevel/20200220051015.14971-1-matthew.ruff...@canonical.com/
Patch:
I managed to figure out what was going on, and made a patch to fix the
problem. I sent it upstream for feedback:
Cover Letter:
https://lore.kernel.org/linux-fsdevel/20200220051015.14971-1-matthew.ruff...@canonical.com/
Patch:
** Summary changed:
- Logitech USB Headset Causes Softlockups During Meetings
+ snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Logitech USB Headset Causes Softlockups During Meetings
+ snd_usb_audio: Logitech USB Headset Causes Softlockups During Meetings
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Attached is syslog from jorunalctl --since today
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329622/+files/syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Attached is dmesg for 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31
20:24:34 UTC 2020
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329621/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Attached is lsusb -vvv
** Attachment added: "lsusb -vvv"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329623/+files/lsusb.txt
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided =>
Attached is syslog from jorunalctl --since today
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329622/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
I have a Logitech H340 USB Headset and a Logitech C270 Webcam I use for
meetings.
I access Google Meet with Firefox.
During a meeting, or immediately after one, and especially so if I join
a second meeting after one finishes, my input devices start acting up
and
Public bug reported:
[Impact]
I have a Logitech H340 USB Headset and a Logitech C270 Webcam I use for
meetings.
I access Google Meet with Firefox.
During a meeting, or immediately after one, and especially so if I join
a second meeting after one finishes, my input devices start acting up
and
Attached is lsusb -vvv
** Attachment added: "lsusb -vvv"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329623/+files/lsusb.txt
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided =>
Attached is dmesg for 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31
20:24:34 UTC 2020
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863973/+attachment/5329621/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** 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/1858857
Title:
gnome-calendar: Hits assert when timezone set to Etc/UTC
To manage notifications
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1858857
Title:
gnome-calendar: Hits assert when timezone set to Etc/UTC
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1858857
Title:
gnome-calendar: Hits assert when timezone set to Etc/UTC
Hi Mohammad,
Thanks for verifying the kernel again, and good to see that things have
been fixed when you run padded traffic over your NICs.
The SRU cycle has completed, and the 4.15.0-88-generic kernel has been
released to -updates. You can go ahead and tell your affected customers
to upgrade to
Hi Mohammad,
Thanks for verifying the kernel again, and good to see that things have
been fixed when you run padded traffic over your NICs.
The SRU cycle has completed, and the 4.15.0-88-generic kernel has been
released to -updates. You can go ahead and tell your affected customers
to upgrade to
The regression was introduced by the following commit:
commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03
Author: Paul Wise
Date: Fri Aug 2 21:49:05 2019 -0700
Subject: coredump: split pipe command whitespace before expanding template
You can read it here:
The regression was introduced by the following commit:
commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03
Author: Paul Wise
Date: Fri Aug 2 21:49:05 2019 -0700
Subject: coredump: split pipe command whitespace before expanding template
You can read it here:
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (U
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (U
I cannot reproduce this. I compiled the reproducer program and tested on
a Eoan VM running in KVM, with the same 5.3.0-29-generic kernel:
ubuntu@ubuntu:~$ ./socktest
Segmentation fault (core dumped)
ubuntu@ubuntu:~$ tail /var/log/kern.log
Feb 14 04:00:41 ubuntu kernel: [ 134.951620]
I cannot reproduce this. I compiled the reproducer program and tested on
a Eoan VM running in KVM, with the same 5.3.0-29-generic kernel:
ubuntu@ubuntu:~$ ./socktest
Segmentation fault (core dumped)
ubuntu@ubuntu:~$ tail /var/log/kern.log
Feb 14 04:00:41 ubuntu kernel: [ 134.951620]
Hi Mohammad,
Can you please test the 4.15.0-88-generic kernel in -proposed again? The
SRU cycle will end in the next few days, and this bug needs to be
verified if at all possible.
To the kernel team:
The two commits:
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding
net/mlx5e:
Hi Mohammad,
Can you please test the 4.15.0-88-generic kernel in -proposed again? The
SRU cycle will end in the next few days, and this bug needs to be
verified if at all possible.
To the kernel team:
The two commits:
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding
net/mlx5e:
Hi Mohammad,
Can you double check that you tested with the 4.15.0-87-generic kernel
from -proposed with the following uname string?
4.15.0-87-generic #87-Ubuntu SMP Fri Jan 31 19:32:37 UTC 2020
You can verify that the patches have landed in the kernel by looking at
the git tree:
Checkout the
Hi Mohammad,
Can you double check that you tested with the 4.15.0-87-generic kernel
from -proposed with the following uname string?
4.15.0-87-generic #87-Ubuntu SMP Fri Jan 31 19:32:37 UTC 2020
You can verify that the patches have landed in the kernel by looking at
the git tree:
Checkout the
Verification for eoan, via the Bionic 5.3 HWE kernel. The customer
installed 5.3.0-40-generic #32~18.04.1-Ubuntu to their bionic machine,
and mounted their multi-tier cifs share:
@:~$ uname -rv
5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020
@:~$ cd /mnt/share/
@:/mnt/share$
Verification for eoan, via the Bionic 5.3 HWE kernel. The customer
installed 5.3.0-40-generic #32~18.04.1-Ubuntu to their bionic machine,
and mounted their multi-tier cifs share:
@:~$ uname -rv
5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020
@:~$ cd /mnt/share/
@:/mnt/share$
Hi Mohammad,
It seems things have returned back to normal for this current SRU cycle,
and the two commits you requested:
net/mlx5e: Rx, Fix checksum calculation for new hardware
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding
Have been tagged and built into the 4.15.0-87-generic
Hi Mohammad,
It seems things have returned back to normal for this current SRU cycle,
and the two commits you requested:
net/mlx5e: Rx, Fix checksum calculation for new hardware
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding
Have been tagged and built into the 4.15.0-87-generic
Hi Mohammad,
I have some bad news. The patches are not present in the current SRU
cycle and have been delayed until the next SRU cycle.
This is not unique to us and this LP bug, everyone has had the same
thing happen to them.
The reason is that the kernel team are currently spinning kernels for
Hi Mohammad,
I have some bad news. The patches are not present in the current SRU
cycle and have been delayed until the next SRU cycle.
This is not unique to us and this LP bug, everyone has had the same
thing happen to them.
The reason is that the kernel team are currently spinning kernels for
Verification for disco. I went and installed 5.0.0-40-generic from -proposed
to a disco box:
$ uname -rv
5.0.0-40-generic #44-Ubuntu SMP Wed Jan 15 02:03:45 UTC 2020
I do not have access to a multi tier cifs mount, so I will try and
connect to a known one with a bad username / password to ensure
Verification for disco. I went and installed 5.0.0-40-generic from -proposed
to a disco box:
$ uname -rv
5.0.0-40-generic #44-Ubuntu SMP Wed Jan 15 02:03:45 UTC 2020
I do not have access to a multi tier cifs mount, so I will try and
connect to a known one with a bad username / password to ensure
Verification for the revert:
lab@hostname:~$ uname -a
Linux hostname 4.15.0-75-generic #85-Ubuntu SMP Wed Jan 15 00:31:23 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
lab@hostname:~$ dmesg | grep "Cannot enable"
lab@hostname:~$ dmesg | grep "Maybe"
lab@hostname:~$
Booting the bionic kernel
Verification for the revert:
lab@hostname:~$ uname -a
Linux hostname 4.15.0-75-generic #85-Ubuntu SMP Wed Jan 15 00:31:23 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
lab@hostname:~$ dmesg | grep "Cannot enable"
lab@hostname:~$ dmesg | grep "Maybe"
lab@hostname:~$
Booting the bionic kernel
Hi Corey,
libvirt-bin has been released properly to xenial -updates now.
Sorry for all the fuss related to releasing a package still in -proposed
to trusty-mitaka. You can go ahead pick up 1.3.1-1ubuntu10.29 from
xenial -updates and release that to trusty-mitaka if you like.
Thanks for your
The customer has been unresponsive in testing the package in -proposed
in their environment, so we will move on with verification.
In my previous comment on 2019-11-27, we showed that libvirt
1.3.1-1ubuntu10.29 can successfully execute a blockcommit on a lvm
backed volume with virsh.
This still
The following is from the customer testing the package in -proposed,
after swapping out a failed Micron NVMe drive for a new replacement
Micron NVMe drive:
Begins:
I've tested the version of the package in `bionic-proposed` and it seems
to be fine. Here are the relevant terminal outputs in ASCII
Hello Mohammad,
The kernel team has reviewed the patches and they have received two acks
from senior kernel developers:
https://lists.ubuntu.com/archives/kernel-team/2019-December/106516.html
https://lists.ubuntu.com/archives/kernel-team/2020-January/106624.html
>From there, the patch was
Hello Mohammad,
The kernel team has reviewed the patches and they have received two acks
from senior kernel developers:
https://lists.ubuntu.com/archives/kernel-team/2019-December/106516.html
https://lists.ubuntu.com/archives/kernel-team/2020-January/106624.html
>From there, the patch was
Hi Mohammad,
Thanks for testing those kernels.
The second one did not include 0aa1d18615c163f92935b806dcaff9157645233a,
which is why you still see the splat. Re-reading it,
db849faa9bef993a1379dc510623f750a72fa7ce depends on
0aa1d18615c163f92935b806dcaff9157645233a to function, and I probably
Hi Mohammad,
Thanks for testing those kernels.
The second one did not include 0aa1d18615c163f92935b806dcaff9157645233a,
which is why you still see the splat. Re-reading it,
db849faa9bef993a1379dc510623f750a72fa7ce depends on
0aa1d18615c163f92935b806dcaff9157645233a to function, and I probably
** Description changed:
- Hi,
- we have the following issue which affects a lot of our customers this issue
fixes upstream and need to add the fixes to ubuntu 18.04.
+ BugLink: https://bugs.launchpad.net/bugs/1854842
- Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel
-
1301 - 1400 of 2042 matches
Mail list logo
