Bug 1302175
Summary: | The "Save this password in your keyring" option is unchecked unexpectedly | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Xiaodai Wang <xiaodwan> |
Component: | virt-manager | Assignee: | Pavel Hrdina <phrdina> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.3 | CC: | juzhou, knoel, mxie, mzhan, phrdina, tzheng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virt-manager-1.4.0-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 02:01:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Xiaodai Wang
2016-01-27 02:32:06 UTC
Upstream commit: commit 7e1bd1d7623c6b5c47eb1e6358a2f2352a1d93c5 Author: Pavel Hrdina <phrdina> Date: Tue Jun 7 14:50:58 2016 +0200 console: fix checkbox to save password if it was loaded from keyring I can reproduce this bug with package: virt-manager-1.3.2-1.el7.noarch Steps are the same as description above. Then try to verify with new build: virt-manager-1.4.0-1.el7.noarch 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. Tick 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 if the password is remembered and "Save this password in your keyring" is ticked. Results: After step5, the password is remembered and "Save this password in your keyring" is ticked. According to the result above in the latest version of virt-manager, 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-2016-2269.html |