Just checked on the reported bugs page…I was incorrect to say previously that it has been passed to an engineer…it has not yet. No movement on it since first reported on February 11th. So @johnny if you are still experiencing it and have not submitted a bug report, maybe doing so would help to get some movement on it.
