This bug is awaiting verification that the linux-azure/5.15.0-1072.81
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 t
This bug is awaiting verification that the linux-
hwe-6.8/6.8.0-41.41~22.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-jammy-linux-
hwe-6.8' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux/5.15.0-121.131 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 ex
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.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-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1010.10~22.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-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux/5.15.0-120.130 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 ex
This bug is awaiting verification that the linux/5.15.0-120.130 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 ex
This bug is awaiting verification that the linux/5.15.0-120.130 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 ex
This bug is awaiting verification that the linux/5.4.0-195.215 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' to 'verification-done-focal-linux'. If
the problem still exi
This bug is awaiting verification that the linux-
azure-5.4/5.4.0-1135.142~18.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-bionic-linux-
azure-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
ibm-5.15/5.15.0-1060.63~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-
ibm-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
azure-5.4/5.4.0-1135.142~18.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-bionic-linux-
azure-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux/6.8.0-43.43 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 exist
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~22.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-jammy-linux-
riscv-6.8' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~22.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-jammy-linux-
riscv-6.8' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10
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' to 'verification-done-noble-
linux-raspi'. If th
This bug is awaiting verification that the linux-azure/6.8.0-1012.14
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 th
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~22.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-jammy-linux-
riscv-6.8' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10
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' to 'verification-done-noble-
linux-raspi'. If th
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~22.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-jammy-linux-
riscv-6.8' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10
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' to 'verification-done-noble-
linux-raspi'. If th
301 - 400 of 28222 matches
Mail list logo