For added confusion, I see this bug using the Live (install) image, but now it's gone after running an install with normal updates!
For added confusion, I see this bug using the Live (install) image, but now it's gone after running an install with normal updates!