I think it went away either with Ubuntu 23.10 or 24.04 - but I don't know if they actually fixed it or just changed something random that masks the bug for now, only to come back with the next kernel version (I've had that issue before).

Given that the issue (or variants thereof, because there were at least 10 different workarounds to try) was somewhat widely reported, the time it took to get this fixed far exceeded anything I would consider tolerable.