I have experienced the same symptom with plain X11 and xlock disabling the screen. And this wasn't a new bug - have seen this behaviour at least a year ago already. Given that I could work-around this by configuring X11 to not disable the screen, I did not bother to create a seperate bug report on this (especially given the much more grave system-crash-inducing instabilities that plague this driver :-( )