For most users encountering this problem, the issue was fixed in Beta 135. However, there are still a few who are stuck and we're investigating why. We found one possible thing that will be in the next release, and we're looking for other explanations/fixes as well.
As long as you submitted a bug report (which you stated above), we're aware of your situation and are striving to get things sorted out.
|