[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
All autopkgtests for the newly accepted linux-meta-ibm (5.15.0.1025.21) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-ibm/5.15.0-1025.28 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-meta-gke-5.15
(5.15.0.1024.29~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.19 (arm64)
linux-gke-5.15/5.15.0-1024.29~20.04.1 (amd64, arm64)
Please
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1992266
Title:
input/keyboard: the keyboard on some Asus
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy
--
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/1996121
** Description changed:
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
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
** Changed in: linux (Ubuntu Kinetic)
Status: Confirmed => Fix Committed
--
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/1999556
Title:
commit
** Changed in: linux (Ubuntu Kinetic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998882
Title:
Mute/mic LEDs no function on a HP
** Changed in: linux (Ubuntu Kinetic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
All autopkgtests for the newly accepted linux-meta-lowlatency (5.19.0.1017.14)
for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-515/515.86.01-0ubuntu0.22.10.1 (arm64)
linux-lowlatency/5.19.0-1017.18 (amd64,
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency
(5.15.0-60.66) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-525/525.78.01-0ubuntu0.22.04.1 (amd64)
Please visit the excuses
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.19
(5.19.0-31.32~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-515/515.86.01-0ubuntu0.22.04.1 (amd64)
Please visit the
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/2003753
Title:
Kinetic update: upstream stable patchset
Wanted to chime in and say that I'm running Pop!_OS (based on Ubuntu)
22.04LTS with kernel 6.0.12-76060006-generic, still getting no sound
from the built in speakers. Like everyone else, Gnome settings sees a
speaker and correctly puts sound through sof-hda-dsp, but there is no
sound. Wired and
** Changed in: linux-kvm (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1998244
Title:
kselftest net/fib_nexthop_nongw.sh fails
Hello Aaron, or anyone else affected,
Accepted ubiquity into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ubiquity/22.04.19 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1057.64
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1011.11
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
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1011.11
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
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1011.11
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
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1011.11
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
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1011.11
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
** Package changed: ubuntu => linux (Ubuntu)
--
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/2003985
Title:
Incorrect number of cores for 12th Gen Intel CPU
Status in linux package in
You have been subscribed to a public bug:
Update:
This is likely due to the WSL2 limit on the number of cores. I used a Ubuntu
22.04 usb boot drive to test and find the correct number of cores.
--
My Laptop has Intel 12th Gen CPU 12800HX, which has 16
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1996071
Title:
[UBUNTU 20.04] boot: Add s390x secure
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
** Tags removed: verification-done-focal
--
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/1996892
Title:
Expose built-in trusted and revoked certificates
Status in linux package in
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1033.40~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' to
'verification-done-focal'. If the problem
All autopkgtests for the newly accepted linux-meta-lowlatency (5.19.0.1016.13)
for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-lowlatency/5.19.0-1016.17 (arm64, amd64)
Please visit the excuses page listed below and
All autopkgtests for the newly accepted linux-meta-ibm (5.15.0.1024.20) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-ibm/5.15.0-1024.27 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.19
(5.19.0-30.31~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-525-server/525.60.13-0ubuntu0.22.04.1 (arm64)
Please visit
Bug still present. Affects 22.04.1 on multiple Lenovo Thinkpads for me.
I have found this report:
https://askubuntu.com/questions/1238485/ubuntu-20-04-cd-drive-keeps-
opening-closing-randomly
Tried the fix; does not help.
That links to this:
Also seeing on Jammy 5.15.0.58.56 with a similar setup (xen, lacp bond,
bridges using openvswitch). Initially tried downgrading vswitch to
2.17.0 from 2.17.3 which didn't make any difference. Both versions of
vswitch are working on the original kernel 5.15.0-25 as well as
5.15.0-33.
--
You
Public bug reported:
[ Impact ]
* On UEFI platforms, sbverify is used by linux-signed packaging to
check correctness of signing (to ensure that kernel was not signed with
a revoked key by accident).
* Some signed packages are missing such build dependency on arm64
platforms.
[ Test Plan ]
60 matches
Mail list logo
