Comment 6 for bug 274926

Thanks for the patch. I rebuilt consolekit with the patch applied, but I still seem to have the same problem. Awkwardly, though, the problem doesn't seem to surface regularly as I'm sure I saw the screensaver active at least at one point (just by chance, that is). Now, however, running "gnome-screensaver-command -a" exhibits the same behavior as before. Should I attach a new output of gnome-screensaver --debug --no-daemon?