Description of problem: Screen locks when mouse/keyboard captured inside guest OS with Virt Manager console using Spice graphics. Unable to free keyboard lock to unlock lightdm session. Version-Release number of selected component (if applicable): lightdm 1-18.2-1.fc25 virt-manager 1.4.0-3.fc25 mate desktop environment with i3 window manager replacing marco How reproducible: sudo virt-manager create new virtual machine click into install screen so that virt-manager grabs mouse/keyboard screen will lock Steps to Reproduce: 1. install mate desktop, i3wm, virtualization group 2. follow steps above 3. wait for screen to lock Actual results: Screen locks with keyboard captured, cannot log in to lightdm session Expected results: screen should not lock while use virt-manager with spice graphics. If screen is locked, should be able to release keyboard and log in to lightdm session. Additional info:
Can you describe specifically what you mean by "screen locks"? I'm guessing that it means it freezes and no longer accepts input?
Sorry for the confusion, no the screen does not freeze. The login manager for the host, lightdm, returns to the session login screen. I try to enter my password to log in, and cant, it seems like the guest still has the keyboard locked.
The issue is more likely to be in the greeter
Do you use the keypad for typing numbers for the password? Here pressing 2 times the enable-keypad-button helps to enable the keypad.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.