This bug is awaiting verification that the linux-
lowlatency/6.8.0-35.35.1 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-noble-linux-lowlatency' to
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2004.4 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-noble-linux-raspi-realtime'
to
This bug is awaiting verification that the linux-riscv/6.8.0-35.35.1
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-noble-linux-riscv' to 'verification-done-noble-
linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.8.0-35.35.1
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-noble-linux-riscv' to 'verification-done-noble-
linux-riscv'. If
This bug is awaiting verification that the linux-oem-6.8/6.8.0-1006.6
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-noble-linux-oem-6.8' to 'verification-done-
noble-linux-oem-6.8'.
This bug is awaiting verification that the linux-nvidia/6.8.0-1007.7
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-noble-linux-nvidia' to 'verification-done-
noble-linux-nvidia'. If
This bug is awaiting verification that the linux-intel/6.8.0-1005.12
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-noble-linux-intel' to 'verification-done-noble-
linux-intel'. If
This bug is awaiting verification that the linux-ibm/6.8.0-1006.6 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-noble-linux-ibm' to 'verification-done-noble-linux-
ibm'. If the
This bug is awaiting verification that the linux-gke/6.8.0-1004.7 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-noble-linux-gke' to 'verification-done-noble-linux-
gke'. If the
This bug is awaiting verification that the linux-gcp/6.8.0-1008.9 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-noble-linux-gcp' to 'verification-done-noble-linux-
gcp'. If the
This bug is awaiting verification that the linux-azure/6.8.0-1008.8
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-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If
This bug is awaiting verification that the linux-aws/6.8.0-1009.9 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-noble-linux-aws' to 'verification-done-noble-linux-
aws'. If the
This bug was fixed in the package linux - 6.8.0-35.35
---
linux (6.8.0-35.35) noble; urgency=medium
* noble/linux: 6.8.0-35.35 -proposed tracker (LP: #2065886)
* CVE-2024-21823
- VFIO: Add the SPR_DSA and SPR_IAX devices to the denylist
- dmaengine: idxd: add a new
This bug is awaiting verification that the linux-
bluefield/5.15.0-1043.45 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-linux-bluefield' to
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1056.62~20.04.1 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-focal-linux-
intel-iotg-5.15' to
This bug is awaiting verification that the linux-raspi/5.15.0-1054.57
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-106.116~20.04.1 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-focal-linux-
hwe-5.15' to
This bug is awaiting verification that the linux-aws/5.15.0-1061.67
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-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1056.62 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-linux-intel-iotg' to
This bug is awaiting verification that the linux-ibm/5.15.0-1054.57
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-linux-ibm' to 'verification-done-jammy-
linux-ibm'. If the
This bug is awaiting verification that the linux-gke/5.15.0-1058.63
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-linux-gke' to 'verification-done-jammy-
linux-gke'. If the
This bug is awaiting verification that the linux-gcp/5.15.0-1059.67
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-linux-gcp' to 'verification-done-jammy-
linux-gcp'. If the
This bug was fixed in the package linux - 5.15.0-106.116
---
linux (5.15.0-106.116) jammy; urgency=medium
* jammy/linux: 5.15.0-106.116 -proposed tracker (LP: #2061812)
* CVE-2024-2201
- x86/bugs: Use sysfs_emit()
- KVM: x86: Update KVM-only leaf handling to allow for
This bug is awaiting verification that the linux/6.8.0-32.32 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-noble-linux' to 'verification-done-noble-linux'. If
the problem still
This bug is awaiting verification that the linux-azure/6.5.0-1021.22
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1064.73
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-linux-azure' to 'verification-done-jammy-
linux-azure'. If
Installed the linux/6.5.0-33.33 kernel in -proposed, and the issue is
fixed by the kernel.
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug is awaiting verification that the linux/6.5.0-33.33 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
Installed the linux/5.15.0-104.114 kernel in -proposed, and the issue is
fixed by this kernel.
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug is awaiting verification that the linux/5.15.0-104.114 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-linux' to 'verification-done-jammy-linux'. If
the problem still
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Importance: High => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: High => Medium
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Description changed:
- This is for tracking purpose.
+ [Impact]
+ In an oem project, we found the max playback volume of the headphone
+ is too high on 2 LG machines, it could bring harm to listeners. As
+ requested by OEM customer, we need to decrease the max volume.
+
+
+ [Fix]
+
** Summary changed:
- alsa/realtek: adjust headphone max output valume on 2 LG machines
+ alsa/realtek: adjust max output valume for headphone on 2 LG machines
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
33 matches
Mail list logo
