This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.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-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~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.5' to
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
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-aws' to 'verification-done-mantic-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
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
Thanks for your help!
** Tags removed: verification-needed-jammy-linux-starfive-6.5
verification-needed-mantic-linux verification-needed-mantic-linux-lowlatency
** Tags added: verification-done-jammy-linux-starfive-6.5
verification-done-mantic-linux verification-done-mantic-linux-lowlatency
--
Good news. I'll mark this verified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049027
Title:
The display becomes frozen after some time when a HDMI device is
connected.
To manage
I'm happy to report that in three working days the problem has not
reoccurred. So the fix in kernel 6.5.0-21-generic #21~22.04.1 looks good
to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049027
Thanks for the clarification! I'm running 6.5.0-21-generic #21~22.04.1
now. I'll report if the problem occurs again (in my usage it happened
every one or two days).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, both contain the fix. We run two cycles in parallel (one for security that
releases earlier nd contains critical fixes (mostly CVEs) and then the sru
cycle that is released 2 weeks after.
This seemed critical and we decided to include in the security cycle so it will
reach end users 2
Hi Roxana,
I'm confused by your comment #11. You write about versions
6.5.0-21.21~22.04.1 and 6.5.0-25.25~22.04.1. Do both contain the fix?
As of today, I can see neither of these versions, but only
6.5.0.21.21~22.04.11 (.11, not .1!). And that version has already been
released as a regular (not
10 matches
Mail list logo
