Hide Forgot
Description of problem: The password is not cleared after unchecking "Save this password in your keyring". Version-Release number of selected component (if applicable): virt-manager-0.9.0-31.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. launch "virt-manager" 2. Open hardware details and click "display spice" device and Set a password for it. 3. Start the guest. 4. Check the "Save this password in your keyring" option and type the password. 5. Close the vm window and double click the vm to open the vm window again, check the password is remembered. 6. Uncheck the "Save this password in your keyring" option and click login. 7. Close the vm window and double click the vm to open the vm window again. Actual results: The password is remembered and the "Save this password in your keyring" option is still checked. Expected results: The password should be cleared and the "Save this password in your keyring" option should be unchecked. Additional info: 1. It's better to only save the password when login success, now it saves every password no matter what the password is.
I can reproduce this issue with package: virt-manager-0.9.0-31.el6.x86_64 Then try to verify with new build: virt-manager-0.9.0-33.el6.x86_64 Steps: 1. launch "virt-manager" 2. Open hardware details and click "display spice" device and Set a password for it. 3. Start the guest. 4. Check the "Save this password in your keyring" option and type the password. 5. Close the vm window and double click the vm to open the vm window again, check the password is remembered. 6. Uncheck the "Save this password in your keyring" option and click login. 7. Close the vm window and double click the vm to open the vm window again. Result: The password is cleared and the "Save this password in your keyring" option is unchecked. And also repeat step4-7, no error find, so move this bug from ON_QA to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0686.html