This bug no longer appears to be reproducible on noble with the 6.8 generic kernels, so I have marked it as resolved.
This bug no longer appears to be reproducible on noble with the 6.8 generic kernels, so I have marked it as resolved.