Red Hat Bugzilla – Bug 230746
Lock Screen hangs desktop if rdesktop has focus
Last modified: 2008-03-18 14:41:07 EDT
Description of problem:
If you lock the screen when rdesktop has the focus and the mouse cursor is
within this window then either the lock doesn't occur or the lock doesn't appear
but nothing works on the desktop, except the rdesktop session which can be
operated by the keyboard only.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start an rdesktop session, connecting it to a Windows terminal server.
2. With the rdesktop window active, open the System menu at the top.
3. Select Lock Screen while the mouse is in the rdesktop client area. This can
be achieved in two ways:
a. If the rdesktop window fills your desktop (such that the Lock Screen menu
item obscures the rdesktop window).
b. Move the mouse cursor to the rdesktop window and activate the Lock Screen
menu item by pressing return.
Either the Lock Screen isn't activated or, nothing appears to happen, then when
you try to click on items on the desktop (other applications, GNOME system menu,
etc.) nothing happens (menu bar items highlight but do not drop down). With the
rdesktop window active, you can close this with the keyboard (Ctrl+Alt+Del). The
only option with the GNOME desktop is Ctrl+Alt+BkSp and start again.
Lock Screen starts normally.
rdesktop grabs the keyboard while it has focus . But g-s tries to nuke the
focus before it grabs the keyboard. Last I checked this was working ok with
2.16.1. Can you file a bug upstream (bugzilla.gnome.org) and include a debug
log when this occurs ?
I don't think I can. There only seems to be an RPM for
gnome-screensaver-debuginfo-2.16.0-7, but the main package is
gnome-screensaver-2.16.1-4 so there's no match. If I "run gnome-screensaver
--no-daemon --debug" the problem doesn't occur in quite the same way (the screen
doesn't go blank until you move the mouse, but when it does you can unlock it in
the normal way).
We no longer support Fedora Core 6 and I am currently trying to get my open bug
count down to a more manageable state. I'm going to close this bug as WONTFIX.
If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?
(this is a mass message)