I don't believe this is still occurring for me running the development version of precise. Hard to say what/when it was fixed, but it's working for me now.
I don't believe this is still occurring for me running the development version of precise. Hard to say what/when it was fixed, but it's working for me now.