screensaver doesn't respond to input after being in another console.

[Max]

Binary package hint: gnome-screensaver

If I go to another console from X (ctrl-alt-F2 for example) and work in there for a while (long enough for the screensaver in the X session to believe I am idle), the screensaver will hang when I switch back to X. What happens is that when I return to the X session, the screensaver starts immediately to fade to black regardless of when the screensaver actually was triggered in X. After fading to black, the screensaver no longer accepts input and must be killed along with the X session.

I am running Hardy Heron upgraded from Gutsy.

[Pedro Villavicencio (pedro)]

Thanks for your report, Is this still an issue for you? May you test the same in Intrepid?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.