Description of problem:
After choosing one of the "rss-glx" modules in the "gnome-screensaver"
preferences and locking the screen, it is impossible to quit the
screensaver gracefully. The unlock dialog pops up, but after entering
the password, the screen turns black and the system just sits there
without responding to user interaction. It is necessary to kill the
corresponding process from a virtual console to unlock the screen.

Version-Release number of selected component (if applicable):
rss-glx-gnome-screensaver-0.8.1.p-3.fc6

How reproducible:
Always.

Steps to Reproduce:
1. Open "gnome-screensaver" preferences.
2. Choose an "rss-glx" module.
3. Lock the screen.
  
Actual results:
The screensaver sets in correctly with enabled direct rendering. After
entering the password to unlock the screen, nothing happens, and the
screensaver does not respond anymore.

Expected results:
The screensaver should unlock the screen.

Additional info:
The same happens, if the screensaver sets in after the given time
interval, and it was set to lock the screen when active.
However, when the screensaver sets in without locking the screen,
moving the mouse or hitting a key lets it exit gracefully.