According to the link that Garry posted to 2031537, this may be fixed in kernel 6.2.0-36.37 which was released a week ago.
However it's not clear to me if this bug and that one share a root cause (ie: are duplicates).
Is anyone here brave enough to try the latest and can report back?
According to the link that Garry posted to 2031537, this may be fixed in kernel 6.2.0-36.37 which was released a week ago.
However it's not clear to me if this bug and that one share a root cause (ie: are duplicates).
Is anyone here brave enough to try the latest and can report back?