I think the title is self explanatory. This has just happened to me on 5.1 beta 8, but it's previously happened on 5.0 SR-4. When it occurs, it does so in all resources. Restarting Logos always fixes the problem.
