Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: If my cursor focus is in a KVM guest (e.g. RHEL 5) and I leave the machine for a while the Fedora screen saver with screen lock does not kick in. This is after there has been no activity (keyboard or mouse) for either the host or the guest. When returning to the machine I press CTRL-ALT to take focus from the RHEL guest back to my Fedora 12 host. The result is that the screen saver kicks in. Apart form being a little annoying, because it is unexpected behavior, it is also probably a security issue. If someone other than me came to my machine abd didn't ctrl-alt out they could see what's running on my host desktop. If I want the screen saver to kick-in after 5 or 10 min of idle time and require a password it is probably NOT a good idea for the KVM focus to somehow override this setting. IT seems that the current setting is that the guest takes over and the host assumes guest activity even if there is none. Version-Release number of selected component (if applicable): Fedora 12 virt manager 0.8.2 How reproducible/Steps to Reproduce: 1. Set up screen save with screen lock in Fedora 2. Run a guest. 3. Move cursor focus into guest. 4. Go for a cup of coffee ;-) i.e. let the machine idle, including guest, for longer than the duration of the screen saver timer. 5. When you return you may continue to work in the guest. 6. (If you have two monitors can can look at another app - perhaps email on the other monitor because screen saver has not kicked in) 7.ctrl-alt to take focus out to the fedora host. 8. The screen saver kicks in and requires you to log in. Actual results: I can view other apps on the screen despite the screen saver/screen lock even after the screen saver time has elapsed. When changing focus back to desktop Fedora finally kicks into screen saver. Expected results: Additional info:
It seems to me that virt-manager is already noticing the keyboard/mouse activity. i.e. if I have focus on the guest and I'm active in the guest for > than the time of the screen saver timer and then ctrl-alt the host doesn't go to screen saver. So it is noticing that there is activity and the fact that ti goes into screen saver in the case I described in the BZ (below) means that it is noticing inactivity in the guest.
*** This bug has been marked as a duplicate of bug 569830 ***