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
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
** 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
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:
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
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
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
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
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
** 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
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 - 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
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
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
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
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
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
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
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
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
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
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
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
** 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
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
"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
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
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
** 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
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]
** 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
--
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
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
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
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
** 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)
** 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
101 - 141 of 141 matches
Mail list logo
