I just did a fresh install using the 12-Apr alternate iso image and still experienced this bug. If the fix has been released, it has not made it to the distribution, yet.
I just did a fresh install using the 12-Apr alternate iso image and still experienced this bug. If the fix has been released, it has not made it to the distribution, yet.