This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2013019
and then change the status of the bug to 'Confirmed'.
If, due to the nature
The question is, it's already verified on Jammy generic and Focal HWE
kernel, the tag spamming on derivative kernels are unnecessary.
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy
--
You received this bug notif
Public bug reported:
[Impact]
nbd smoke test is triggering the following hung task timeout trace with
lunar/linux 6.2:
615 10:58:25 DEBUG| [stdout] [ 484.429923] INFO: task
systemd-udevd:16656 blocked for more than 120 seconds.
616 10:58:25 DEBUG| [stdou
*** This bug is a duplicate of bug 2007668 ***
https://bugs.launchpad.net/bugs/2007668
This sounds like one of the symptoms of bug 2007668.
I can confirm that Ubuntu 23.04 works more reliably on 12th gen chips,
but that's not officially released yet.
You might also have more luck by installi
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2013014
and then change the status of the bug to 'Confirmed'.
If, due to the nature
You have been subscribed to a public bug:
I'm not sure if this is an xorg bug because i'm pretty sure I'm using
wayland, however ubuntu-bug says it's an xorg issue.
I installed the GNOME desktop instead of the ubuntu one, however it does
happen on the ubuntu desktop as well. It seems to happen le
Please try a kernel version that is supported on Ubuntu 22.04, like
5.15.0-69.76, 5.19.0-38.39~22.04.1 or 6.1.0-1008.8
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
"Fix Released" in lunar, assuming it is the above issue. If it's not
then please just change the status back.
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504
Importance: Unknown
Status: Unknown
** Changed in: mesa (Ubuntu)
Status: New => Fix Re
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2009024
Title:
Fail to output sound to external m
Public bug reported:
[Impact]
Kernel selftest net:l2tp.sh is failing with the latest lunar/linux 6.2
kernel, the error is the following:
RTNETLINK answers: Protocol not supported
Using `bash -x` we can see that the last command executed is the
following:
ip -netns host-1 l2tp add tunnel tu
Looks most likely to be
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504 which is fixed in
Mesa 22.3.1. But then similar bugs still exist like bug 2012819.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7504
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504
--
You r
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2008897
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Summary changed:
- Desktop freezes or crashes intermittently
+ Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)
** Package changed: kwin (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You
You have been subscribed to a public bug:
My desktop unexpectedly freezes or crashes every now and then (once or
week or less). Typically the machine is not usable but this time I
managed to log back in via the text console and grab the following text
from dmesg:
[11689.245277] gmc_v10_0_process_
** Changed in: ubuntu-kernel-tests
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1923049
Title:
autotest.ubuntu_ltp_stable dio fails on foca
** No longer affects: xorg-server (Ubuntu Jammy)
** Also affects: xorg-server (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-525 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu Jammy)
Status
Test passed on Jammy linux/5.15.0-70.77
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2006453
Ti
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2006692
Title:
net:fcnal-test.sh didn't return a non-zero val
Tested using the same test plan by linux/5.15.0-70.77 and confirmed that
the issue has been resolved.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This fix has already landed in Lunar as well. Mark the linux package as
Fix-released.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a mem
The BT adv feature
1. works with 5.15 + bluez (20/stable) 5.53-7
2. doesn't work with 5.15 + bluez (22/beta) 5.64-3
3. (from Dilyn and Wendell) works with 5.19 + bluez (22/beta)
It's still unclear why bluez requires specific version of kernel.
Do we have a bluez expert to consult what kind of feat
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2012789
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This is caused by duplicate entries in the DBX database shipped by
Lenovo on certain laptops:
https://lore.kernel.org/lkml/c8c65713-5cda-43ad-8018-20f2e32e4...@t-8ch.de/T/#m879b8faa1c2e415aef81e6cf42faa70f304773d9
It can be safely ignored.
** Information type changed from Private Security to Publ
I can confirm this occurred on my machine, it was not an external HDD. I
have an MSI MS-7976 motherboard and a Samsung M.2 SSD.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/2007439
Title
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
This bug was fixed in the package linux - 4.15.0-208.220
---
linux (4.15.0-208.220) bionic; urgency=medium
* bionic/linux: 4.15.0-208.220 -proposed tracker (LP: #2012097)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux-hwe-5.4 - 5.4.0-146.163~18.04.1
---
linux-hwe-5.4 (5.4.0-146.163~18.04.1) bionic; urgency=medium
* bionic/linux-hwe-5.4: 5.4.0-146.163~18.04.1 -proposed tracker (LP:
#2012093)
[ Ubuntu: 5.4.0-146.163 ]
* focal/linux: 5.4.0-146.163 -propo
This bug was fixed in the package linux - 4.15.0-208.220
---
linux (4.15.0-208.220) bionic; urgency=medium
* bionic/linux: 4.15.0-208.220 -proposed tracker (LP: #2012097)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package linux - 4.15.0-208.220
---
linux (4.15.0-208.220) bionic; urgency=medium
* bionic/linux: 4.15.0-208.220 -proposed tracker (LP: #2012097)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.89.02-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-525 (525.89.02-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #2006937):
- Fixed a bug that could cause banding or flickering of color
This bug was fixed in the package linux-aws - 4.15.0-1153.166
---
linux-aws (4.15.0-1153.166) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1153.166 -proposed tracker (LP: #2012003)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Corr
This bug was fixed in the package linux - 4.15.0-208.220
---
linux (4.15.0-208.220) bionic; urgency=medium
* bionic/linux: 4.15.0-208.220 -proposed tracker (LP: #2012097)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
This bug is awaiting verification that the linux/5.15.0-70.77 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-70.77 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-70.77 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-70.77 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-70.77 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-70.77 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-70.77 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-70.77 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
Public bug reported:
Issue opened with OpenSSL.
https://github.com/openssl/openssl/pull/20616
RSA verification failed when all loopargs[] share the same EVP_PKEY
rsa_key.
Tested and reproduced on openssl-3.0 branch
$ apps/openssl speed -engine pka -async_jobs 8 rsa2048
Engine "pka" set.
Doing
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Just wanted to confirm that this also affects me:
* Ubuntu 22.04.2 LTS
* HP Pavilion al001nt (HP HP Pavilion Notebook/820A, BIOS F.56 12/22/2020)
* nvidia-driver-525 (Driver Version: 525.89.02)
* Kernel 5.19.0-38-generic #39~22.04.1-Ubuntu
I've attached the log file to this message.
I'm happy to
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19
(5.19.0-1020.22~22.04.2+1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excu
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19
(5.19.0-1020.22~22.04.2+1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excu
Same Issue with my Sound Blaster Recon3D / Z-Series
I have tried 5.19.0-35 and 5.19.0-38
Works only for kernel 5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2009243
Tit
Public bug reported:
No installed 5.19 because not support Nvidia GT210
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-38-generic (not installed)
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
NonfreeKernelModules: nvi
Public bug reported:
after mentioned updates screens flickers to complete black and back... system
near unusable (sorry for typos but cant see much so i write here mostly blind
whilst i have about half a second a view of my desktop )
I attach here some outputs from the logs (jopurnal -xe) and o
Same Issue with my Sound Blaster Recon3D / Z-Series
I have tried 5.19.0-35 and 5.19.0-38
Works only for kernel 5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2009243
Tit
Confirming the proposed 5.4.0-1099 packages resolve the NFS bug on
Bionic running in AWS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2009325
Title:
NFS deathlock with last Kernel
The following kernel incl. the needed patches for jammy:
5.15.0.70.68 | jammy-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch support for for s3
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2012953
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Hi
I have a XMG Focus 17 laptop.
i7-12700H with Intel Iris Xe Graphics
Nvidia RTX 3060.
Dualboot LinuxMint 21.1 (based on Ubuntu 22.04) / Windows 10
Kernel 5.15.0-67-generic
HDMI output (2nd screen, TV) works fine with :
-Windows
-LinuxMint with Nvidia card activated
BUT
--- Comment From gcwil...@us.ibm.com 2023-03-27 11:56 EDT---
This was fixed and closed on the Canonical side. Moving to closed on ours.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Can confirm that 5.15.0-1033 seems to have resolved the NFS bug on Jammy
running on AWS.
Is there a timeframe for the same patch to be applied to the 5.19 kernel
train?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2007581
Title:
gpio: Restrict usage of
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2008136
Title:
netfilter: flowtable: ad
This bug was fixed in the package lttng-modules -
2.12.5-1ubuntu2~20.04.5
---
lttng-modules (2.12.5-1ubuntu2~20.04.5) focal; urgency=medium
* Backport fixes to jbd2 format in 5.4.229 (LP: #2004644)
- d/p/0013-fix-jbd2-use-the-correct-print-format.patch
- d/p/0014-fix-jbd2-us
5.15.0-69-generic -no change as far I can tell.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
Status in linux package in U
Public bug reported:
[Impact]
Adding these patches address a number of differences between the Ubuntu
kernel and the internal NVIDIA kernel.
[Fix]
These patches do not constitute a single fix or a set of fixes for bugs but
instead enable kernel functionality as well as fix kernel bugs
Re-opening as until linux-kvm is deprecated or the CPC team moves over
to using linux-virtual for KVM images, this is the kernel we're dealing
with and that kernel should be functional.
** Changed in: linux-kvm (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification beca
I just got bit by this, too. Was transferring ~40T via rsync to a new
NAS setup... got about 12T in and it just stopped. Eventually realized
the mountpoint was unresponsive. Rebooting and kicking rsync back off
resulted in the same scenario almost immediately. The machine in
question is runnin
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999882
Title:
[UBUNTU 20.04] KVM: s390: pv: don't allow users
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1013.13
---
linux-oem-6.0 (6.0.0-1013.13) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1013.13 -proposed tracker (LP: #2008351)
* CVE-2023-1281
- net/sched: tcindex: update imperfect hash filters respecting rcu
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1008.8
---
linux-oem-6.1 (6.1.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1008.8 -proposed tracker (LP: #2008352)
* overlayfs mounts as R/O over idmapped mount (LP: #2009065)
- SAUCE: overlayfs: handle i
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux-aws-5.19 -
5.19.0-1022.23~22.04.1
---
linux-aws-5.19 (5.19.0-1022.23~22.04.1) jammy; urgency=medium
* jammy/linux-aws-5.19: 5.19.0-1022.23~22.04.1 -proposed tracker
(LP: #2011999)
[ Ubuntu: 5.19.0-1022.23 ]
* kinetic/linux-aws: 5.19.
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assignin
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package linux - 5.4.0-146.163
---
linux (5.4.0-146.163) focal; urgency=medium
* focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for assig
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.89.02-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-525 (525.89.02-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2006937):
- Fixed a bug that could cause banding or flickering of color
1 - 100 of 141 matches
Mail list logo
