Comment 9 for bug 1714699

I'm seeing this mainly after having shut the vm down and restarted it. I have not confirmed the behavior in the staff client with a fresh-built vm. However, it is consistent if I stop the VM and restart it, being sure to shut services off beforehand and restarting them after starting the vm up again. I used to do this with some frequency and never experienced this behavior until September 2.