*** This bug is a duplicate of bug 1958191 ***
https://bugs.launchpad.net/bugs/1958191
This bug happens to me on fresh install of Kubuntu 22.10. I am running
AMD not Intel and have the same issue. I have yet to find a solution
that works, but I am testing different configs as I type.
Here
Hi everyone,
I have built a test kernel based on the current 5.19.0-38-generic kernel for
both Kinetic and Jammy HWE. It has the below patch reverted:
commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
Author: Thomas Zimmermann
Date: Mon Jul 18 09:23:18 2022 +0200
Subject: video/aperture:
Public bug reported:
Issue found with K-kvm 5.19.0-1021.22 after enabling tests on openstack.
Test build failed with:
GEN-SKEL [test_progs] test_ksyms_module.lskel.h
GEN-SKEL [test_progs] test_ksyms_weak.lskel.h
make[1]: Leaving directory
This is also affecting J-kvm
** Tags added: sru-20230320
** Summary changed:
- ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9
+ ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm
--
You
> Package: nvidia-driver-530 (not installed)
suggests the driver is not installed properly. Please try reinstalling
it:
sudo apt install --reinstall nvidia-driver-530 nvidia-dkms-530
and reboot.
If the problem continues after that then please run:
lspci -k > lspci.txt
journalctl -b0 >
With config_dummy enabled for KVM kernels (bug 1998244) this test is now
failing with:
Running 'make run_tests -C net TEST_PROGS=rtnetlink.sh TEST_GEN_PROGS=''
TEST_CUSTOM_PROGS='''
make: Entering directory
Public bug reported:
On Wayland only, offloading works for `glxinfo` but cannot run 3D app
like X-Plane 11:
$ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep
"OpenGL vendor string"
OpenGL vendor string: NVIDIA Corporation
$ __NV_PRIME_RENDER_OFFLOAD=1
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.15
---
zfs-linux (0.8.3-1ubuntu12.15) focal; urgency=medium
* Fix zfs_arc_max getting ignored when value below allmem/32 (LP: #1964992)
- d/p/4930-Dont-ignore-zfs_arc_max-below-allmem-32.patch
-
*** This bug is a duplicate of bug 1998950 ***
https://bugs.launchpad.net/bugs/1998950
You might also want to try the workaround in bug 2007668
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1998950 ***
https://bugs.launchpad.net/bugs/1998950
Zac, please open a new bug because this is just a duplicate of a closed
bug (other people don't experience the issue anymore).
--
You received this bug notification because you are a member of Kernel
Public bug reported:
#41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
5.19.0-40-generic
[0.142828] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[0.823547] nvidia-gpu :01:00.3: enabling device ( -> 0002)
[1.225432] ata1.00: supports DRM functions and may not be fully accessible
[
This issue has returned: In linux-modules-extra-5.19.0-1022-aws there
are no snd-* kernel modules (I personally need snd-aloop.ko).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
Rebased the changes on top of the latest iotg kernel and these are the
changes now required:
0005-tcc-driver-should-exit-if-no-psram-entry-found-in-PTCT.tcc
0006-tcc-tcc-drvier-should-not-exit-even-if-no-psram-entry.tcc
0013-Add-new-IOCTL-to-read-error-log-buffer.tcc
** Changed in: linux-hwe-5.15 (Ubuntu Focal)
Status: In Progress => Fix Released
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Changed in: linux-hwe-5.15 (Ubuntu Focal)
Status: Fix Released => Fix Committed
--
You received this bug
** Changed in: linux-hwe-5.15 (Ubuntu Focal)
Status: In Progress => Fix Released
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Changed in: linux-hwe-5.15 (Ubuntu Focal)
Status: Fix Released => Fix Committed
--
You received this bug
--- Comment From boris.m...@de.ibm.com 2023-04-18 15:36 EDT---
A fix is already available. Commit ID or backport to jammy (22.04) will be
provided.
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux
Yes.
--
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/1998643
Title:
smartpqi: Update 22.04 driver to include recent bug fixes and support
current generation devices
Status in linux
** Changed in: linux (Ubuntu Kinetic)
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/2009136
Title:
No HDMI audio under 5.19.0-35 & -37
Note that the riscv64 patch is also missing from Focal (20.04), and the
package also fails to build there. Upstream included initial support in
zfs-2.0.0, so newer Ubuntu releases should have it by default:
$ git describe --contains 4254e407294b211f3399da2ee131b45fe9f4ac80
zfs-2.0.0-rc1~665
**
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned)
I just checked the following repo:
https://github.com/SUSE/kernel.git
branches SLES15-SP5 and SLES15-SP5-GA
And they are current with Linus's tree...
Looks like Martin Wilck applied them
March 22...
--
You received this bug notification because you are a member of Kernel
BTW: I'm sending up 12 new patches today. Will take time for
review/inclusion into Linux.
--
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/1998643
Title:
smartpqi: Update 22.04 driver to
Hi Don,
When you say you redacted those two patches, just to be clear you're
saying to remove them from the list of patches to apply, correct?
0ca190805784 scsi: smartpqi: Call scsi_done() directly
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
I have a member of my team working
** Description changed:
- System Configuration
- OS: Ubuntu 22.04 LTS
- Kernel: 5.15.0-25-generic
- CPUs: 256
- NIC: Intel E810 NIC with 512 MSIx vectors each function
+ SRU Justification:
+
+ [Impact]
+
+ There is a user reporting errors in setup with their Intel E810 NIC with
Hi Philippe and everyone else affected,
This bug was reported against Ubuntu kernel 5.11 which is EOL, therefore
I'm closing this bug as Won't Fix. Please feel free to re-open it if you
are experience this issue with newer supported kernels.
Thanks.
** Changed in: linux (Ubuntu)
Status:
Hi Steve,
This bug was reported against Hirsute 5.11 kernel which is EOL so I'm
closing this bug as Won't Fix. Please feel free to re-open it if you are
still having the issue with more recent kernels.
Thanks.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received
Resolved - I uninstalled kernel 5.4.0-147 then reinstalled the same.
Works now.
--
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/2016897
Title:
kernel 5.4.0-147 boots to black screen
The attachment "zfs-
linux-0.8.3-1ubuntu12.15..0.8.3-1ubuntu12.16.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
*** This bug is a duplicate of bug 1998950 ***
https://bugs.launchpad.net/bugs/1998950
Bug seems to remain in 5.19.0-40-generic and is specific to happening
when settings panel is up. For me, I've only noticed this happen when
manipulating the printers in the settings panel. This is on
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.19
(5.19.0-1021.23~22.04.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
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New =>
I just got a Lenovo T16 with bios 1.11 (N3MET12W)
For me the sleep issue is still present in a severe way. It shipped with
20.04 and I used the GUI software updater to move to 22.04 and since
that it won't wake from sleep.
A colleague claims that Fedora 37 works well on this model, so I don't
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
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/2007823
Title:
Mute/mic LEDs no function
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
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/2007824
Title:
Mute/mic LEDs and speaker
Sorry to bother, but unfortunately, I have difficulties to understand
the state of this bug.
As I understand from comment 55
https://bugs.launchpad.net/ubuntu/bionic/+source/linux/+bug/2009325/comments/55
The NFS bug is fixed with package
jammy/linux: 5.15.0-69.76
And the latest Ubuntu 22.04
solved by removing evdi:
sudo dkms remove evdi/1.9.1 --all
and
sudo apt install -f
--
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/2016895
Title:
package
Public bug reported:
SRU Justification
[Impact]
The MANA driver does not support jumbo frames
[Fix]
net: mana: Add support for jumbo frame
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=80f6215b450eb8e92d8b1f117abf5ecf867f963e
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 2016897
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: linux-azure (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2014015
Title:
Azure: Add new MANA VF
Public bug reported:
After updating to Kernel 5.4.0-147 the machine boots to a black screen. I can
boot in recovery mode but don't have the video driver functions, think the
driver may be the issue. Tried to find a update for the video driver but could
not. Had to go back to 5.4.0-146. Here
Public bug reported:
Updated system with update-manager -d
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2016895
Title:
package
Public bug reported:
Split firmware into separate package
* Currently gsp.bin is shipped by nvidia-kernel-common that pulls in
userspace dependencies and is required to match a particular driver
* This prevents co-installing LRM of different nvidia upstream releases
from different kernels,
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9
---
linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921)
* Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846)
- ACPICA: MADT:
Public bug reported:
I think that problem with nvidia driver
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-525-5.19.0-40-generic 5.19.0-40.41~22.04.1+1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
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
** Patch added: "zfs-linux-0.8.3-1ubuntu12.15..0.8.3-1ubuntu12.16.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+attachment/5664989/+files/zfs-linux-0.8.3-1ubuntu12.15..0.8.3-1ubuntu12.16.debdiff
--
You received this bug notification because you are a member of
Public bug reported:
Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single
patch missing:
https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Note livepatches can only start with the next abi specifically
https://bugs.launchpad.net/kernel-sru-workflow/+bug/2016820 jammy/linux:
5.15.0-71.78 it started building already, and will undergo testing soon.
--
You received this bug notification because you are a member of Kernel
Packages,
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:
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:
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:
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
I got a kernel upgrade today. the issue seems to remain.
5.15.0-70-generic #77-Ubuntu (Linux Mint). Please try to upstream the
patch(es).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I'm using a Raspberry Pi 4 and updated from kinetic to lunar with "do-
release-upgrade -d".
[Expected behavior]
After switching off and on the wifi carrier I can still connect to my Raspi via
ssh.
[Observed behavior]
After switching off and on the wifi carrier I can
Just merry with the same error running a Lenovo Thinkpad T470s with a
Toshiba Nvme 256GB ssd
** Attachment added: "IMG_5075.jpeg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+attachment/5664964/+files/IMG_5075.jpeg
--
You received this bug notification because you are a
My output to cat /sys/power/mem_sleep is s2idle [deep]
--
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/1805816
Title:
APST quirk needed for PM951 Samsung 1TB NVMe Drive
Status in linux
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 2016410
and then change the status of the bug to 'Confirmed'.
If, due to the
** 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/1639924
Title:
Kernel livepatch support for for s390x
Status
https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate
suggests filing against the kernel if unsure which package to use.
** Tags added: jammy
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is
I have hit this on Focal too (kopter):
SRU Cycle: 2023.03.20
Series: focal
Package:linux-hwe-5.15
Version:5.15.0-70.77~20.04.1
Instance: kopter-kernel
** Tags added: sru-20230320
--
You received this bug notification because you are a member of Kernel
Packages,
I saw the upstream discussion about CONFIG_SND_INTEL_BYT_PREFER_SOF here:
https://github.com/thesofproject/sof/issues/3868#issuecomment-1509831655
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
Status for sound on Dell Chromebook 3120. On Ubuntu 22.04.2 (kernel
5.15.0-69-generic):
1. alsa-ucm-conf now seems to include the required UCM2 files. Hurrah!
2. you also need the firmware-sof-signed package, which you have to enable the
"restricted" apt repository to get. Some people enable
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
Hello everyone,
I was able to confirm the fix for focal using the test case from the
description:
root@zfs-test:~$ free -h
totalusedfree shared buff/cache available
Mem: 31Gi 247Mi30Gi 1.0Mi 352Mi30Gi
Swap:
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux - 5.19.0-40.41
---
linux (5.19.0-40.41) kinetic; urgency=medium
* kinetic/linux: 5.19.0-40.41 -proposed tracker (LP: #2012668)
* CVE-2023-0468
- io_uring: fix tw losing poll events
- io_uring: make poll refs more robust
*
This bug was fixed in the package linux-gcp - 5.19.0-1020.22
---
linux-gcp (5.19.0-1020.22) kinetic; urgency=medium
* kinetic/linux-gcp: 5.19.0-1020.22 -proposed tracker (LP: #2011863)
* Miscellaneous Ubuntu changes
- [config] Enable CONFIG_TDX_GUEST_DRIVER=m
-
This bug was fixed in the package linux - 5.19.0-40.41
---
linux (5.19.0-40.41) kinetic; urgency=medium
* kinetic/linux: 5.19.0-40.41 -proposed tracker (LP: #2012668)
* CVE-2023-0468
- io_uring: fix tw losing poll events
- io_uring: make poll refs more robust
*
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux - 5.19.0-40.41
---
linux (5.19.0-40.41) kinetic; urgency=medium
* kinetic/linux: 5.19.0-40.41 -proposed tracker (LP: #2012668)
* CVE-2023-0468
- io_uring: fix tw losing poll events
- io_uring: make poll refs more robust
*
This bug was fixed in the package linux - 5.19.0-40.41
---
linux (5.19.0-40.41) kinetic; urgency=medium
* kinetic/linux: 5.19.0-40.41 -proposed tracker (LP: #2012668)
* CVE-2023-0468
- io_uring: fix tw losing poll events
- io_uring: make poll refs more robust
*
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux - 5.19.0-40.41
---
linux (5.19.0-40.41) kinetic; urgency=medium
* kinetic/linux: 5.19.0-40.41 -proposed tracker (LP: #2012668)
* CVE-2023-0468
- io_uring: fix tw losing poll events
- io_uring: make poll refs more robust
*
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux - 5.19.0-40.41
---
linux (5.19.0-40.41) kinetic; urgency=medium
* kinetic/linux: 5.19.0-40.41 -proposed tracker (LP: #2012668)
* CVE-2023-0468
- io_uring: fix tw losing poll events
- io_uring: make poll refs more robust
*
This bug was fixed in the package linux - 5.19.0-40.41
---
linux (5.19.0-40.41) kinetic; urgency=medium
* kinetic/linux: 5.19.0-40.41 -proposed tracker (LP: #2012668)
* CVE-2023-0468
- io_uring: fix tw losing poll events
- io_uring: make poll refs more robust
*
This bug was fixed in the package linux - 5.15.0-70.77
---
linux (5.15.0-70.77) jammy; urgency=medium
* jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)
* CVE-2023-26545
- net: mpls: fix stale pointer if allocation fails during device rename
* CVE-2023-1281
This bug was fixed in the package linux-hwe-5.19 - 5.19.0-40.41~22.04.1
---
linux-hwe-5.19 (5.19.0-40.41~22.04.1) jammy; urgency=medium
* jammy/linux-hwe-5.19: 5.19.0-40.41~22.04.1 -proposed tracker (LP:
#2011875)
[ Ubuntu: 5.19.0-40.41 ]
* kinetic/linux: 5.19.0-40.41
1 - 100 of 124 matches
Mail list logo
