Okay, I finally got a 10.10 virtual image installed and can confirm that this bug has been fixed in 10.10.
Okay, I finally got a 10.10 virtual image installed and can confirm that this bug has been fixed in 10.10.