On 03/05/2022 06:30, Daniel van Vugt wrote:
> Great to hear.
>
> Additional logs certainly won't help if it's working now. But if you
> have the patience then finding out what version number exactly fixed it
> would help. Or what kernel version was the last to have the bug, keeping
> in mind the broken kernel was (roughly) upstream version 5.15.30
>
> ** No longer affects: mutter (Ubuntu)
>
As expected a reboot and the bug is back :(
On 03/05/2022 06:30, Daniel van Vugt wrote:
> Great to hear.
>
> Additional logs certainly won't help if it's working now. But if you
> have the patience then finding out what version number exactly fixed it
> would help. Or what kernel version was the last to have the bug, keeping
> in mind the broken kernel was (roughly) upstream version 5.15.30
>
> ** No longer affects: mutter (Ubuntu)
>