Screensaver breaks mouse and keyboard input
Bug #48108 reported by
david thompson
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-screensaver (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
tsclient (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
I will try to gather more info than this, but here is what happens:
When I remote into Win2K3 Server with RDP the session works fine until the 2k3 server locks itself (goes to ctrl-alt-del). At this point my mouse is moveable, but clicking on anything does nothing. The keyboard still works and everything else seems normal, but I have to restart the X-server to regain the ability to 'click' on anything.
Other users experience the opposite problem - local screensaver causes the same symtoms as described above...
This is apparently related to gnome-screensaver, since killing gnome-screensaver resolves the problem.
Changed in tsclient: | |
status: | Confirmed → Needs Info |
To post a comment you must log in.
I'm experiencing these bug symptoms (clicking does nothing, but cursor is movable, and have to restart X-server).
However, for me it happens when the LOCAL computer goes to sleep (ie, gnome-screensaver kicks in), not when the REMOTE computer goes to sleep. These must be somehow related, since the symptoms are exactly the same.
To recreate my situation, use tsclient to login remotely to some Windows desktop. Set your gnome-screensaver to display in 1 minute. Let it sit to allow the local screensaver to start. After that, you'll notice that the mouse can't click on anything locally or remotely (and things like alt-tab don't work, although in general the keyboard is still responsive, as ctrl-alt-backspace still works to reboot X).
Should I file different bug - "gnome-screensaver with tsclient causes desktop freeze" ?