This issue still exists, when trying to figure out why bug #1962308 was happening, this exact same problem still happens on 5.8.0-63 (originally reported on 5.8.0-40).
This issue still exists, when trying to figure out why bug #1962308 was happening, this exact same problem still happens on 5.8.0-63 (originally reported on 5.8.0-40).