This just hit me again, but this time I was able to recover.
Logging in remotely I found nothing obviously wrong. System was almost entirely idle.
So I went back to the system keyboard and tried again. Initially I could not get Ctrl-Alt-F# to give me a tty, but eventually I got one after trying several times. Looking around there I still saw nothing abnormal.
Finally I hit Ctrl-Alt-F2 and was back at the screen saver password entry dialog. I entered the password and everything worked fine.
I'm not convinced this is the same bug that is being discussed above because I don't see X (or any other processes) chewing up CPU. However, the overall failure mode - sporadic inability to exit the screen saver properly - sure seems related.
If there are things I can provide to help debug this please let me know.
This just hit me again, but this time I was able to recover.
Logging in remotely I found nothing obviously wrong. System was almost entirely idle.
So I went back to the system keyboard and tried again. Initially I could not get Ctrl-Alt-F# to give me a tty, but eventually I got one after trying several times. Looking around there I still saw nothing abnormal.
Finally I hit Ctrl-Alt-F2 and was back at the screen saver password entry dialog. I entered the password and everything worked fine.
I'm not convinced this is the same bug that is being discussed above because I don't see X (or any other processes) chewing up CPU. However, the overall failure mode - sporadic inability to exit the screen saver properly - sure seems related.
If there are things I can provide to help debug this please let me know.