| 2006-06-02 19:32:19 |
david thompson |
bug |
|
|
added bug |
| 2006-06-13 07:37:21 |
Mikkel Høgh |
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.
Are there any suggestions to help debug this?? It is really annoying. |
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... |
|
| 2006-06-13 07:37:21 |
Mikkel Høgh |
title |
Remote PC sleeps makes desktop freeze. |
PC sleeps makes breaks mouse input and hotkeys |
|
| 2006-06-13 07:39:22 |
Mikkel Høgh |
tsclient: status |
Unconfirmed |
Confirmed |
|
| 2006-06-13 07:39:22 |
Mikkel Høgh |
tsclient: importance |
Medium |
High |
|
| 2006-06-13 07:39:22 |
Mikkel Høgh |
tsclient: statusexplanation |
|
|
|
| 2006-06-16 17:06:25 |
Mikkel Høgh |
bug |
|
|
assigned to gnome-screensaver (Ubuntu) |
| 2006-06-16 17:10:19 |
Mikkel Høgh |
gnome-screensaver: status |
Unconfirmed |
Confirmed |
|
| 2006-06-16 17:10:19 |
Mikkel Høgh |
gnome-screensaver: statusexplanation |
|
|
|
| 2006-06-16 17:11:11 |
Mikkel Høgh |
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... |
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. |
|
| 2006-06-16 17:22:05 |
Mikkel Høgh |
title |
PC sleeps makes breaks mouse input and hotkeys |
Screensaver breaks mouse and keyboard input |
|
| 2006-06-16 17:22:31 |
Mikkel Høgh |
tsclient: status |
Confirmed |
Needs Info |
|
| 2006-06-20 05:28:09 |
Philip Cain |
bug |
|
|
added attachment 'gnome-screensaver-debug.log' (Debug output from gnome-screensaver) |
| 2006-06-20 05:44:01 |
Philip Cain |
bug |
|
|
added attachment 'gnome-screensaver-debug-during-dosbox-game.log' (Debug output from gnome-screensaver (during dosbox/libsdl session)) |
| 2006-06-20 06:51:43 |
Mikkel Høgh |
tsclient: status |
Needs Info |
Rejected |
|
| 2006-06-20 06:51:43 |
Mikkel Høgh |
tsclient: statusexplanation |
|
Seemingly, this isn't related to tsclient, only gnome-screensaver. |
|
| 2006-06-22 08:17:21 |
Philip Cain |
bug |
|
|
added attachment 'gs-grab-x11.c.diff' (Patch from upstream) |
| 2006-10-04 13:57:17 |
Timo Aaltonen |
gnome-screensaver: status |
Confirmed |
Fix Released |
|
| 2006-10-04 13:57:17 |
Timo Aaltonen |
gnome-screensaver: statusexplanation |
|
bah, sorry for the noise, but g-s 2.16 is in edgy, of course. I'll mark this fixed for now, please reopen if the issue still persists after upgrading to Ubuntu 6.10. |
|
