Comment 5 for bug 314545

Here's is a snippet of the debug log. The full log was 18,000+ lines before I encountered this problem. I grabbed the data about 4 to 5 minutes before attempting to unlock and all of the data afterwards. It appears as if the screen lock happened at line 143. The (failed) unlock request appears to start on line 196. Somewhere after that there is also a successful unlock.