Reviewing other bug reports (specially #457777 which seems related) I've found a pointer to http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#head-d50bc17e7d6f3a51c4715f02c657195e80e26c2c on how to generate debug information.
I'm attaching to this bug report to samples of debug output: - gscreen-debug.ERR.txt.gz: in this one the value of lock_dialog_theme is 'default', I started up gnome-screensaver in debug mode, locked it up inmediately using 'gnome-screensaver-command -l' and then pressed shift three times. No dialog appears (but you can see that it goes through the unlock process) at all and I can not login. I end up the process killing it from a vty. - gscreen-debug.OK.txt.gz: in this case the value of lock_dialog_theme is set to 'system'. I follow the same procedure as above but when I press a key I inmediately get the login prompt and I'm able to unlock the screen. I killed the process from the terminal it was started from. Just in case this debug information is of use. Regards Javier
gscreen-debug.ERR.txt.gz
Description: Binary data
gscreen-debug.OK.txt.gz
Description: Binary data
signature.asc
Description: Digital signature
