| Summary: | remote-viewer gui tool cannot recognize URI address with space character | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | CongDong <codong> |
| Component: | virt-viewer | Assignee: | Christophe Fergeau <cfergeau> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | cfergeau, codong, dblechte, dyuan, jjongsma, marcandre.lureau, mzhan, rbalakri, tzheng |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-viewer-0.6.0-1.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Extra spaces in commandline arguments are not ignored
Consequence: Extra spaces cause problems connecting to remote host
Fix: trim spaces from URL before using it
Result: extra spaces are ignored and application can connect properly
|
Story Points: | --- |
| Clone Of: | 1024199 | Environment: | |
| Last Closed: | 2015-03-05 13:38:26 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: | |
| Bug Depends On: | 1024199 | ||
| Bug Blocks: | |||
|
Description
CongDong
2013-10-29 06:40:02 UTC
commit 69ffdb50b9b83c031af4968ff40da084ecfda934
Author: Christophe Fergeau <cfergeau>
Date: Tue Oct 29 10:14:29 2013 +0100
Clean-up spaces before/after URI in connection dialog
Fixed by rebase to 0.6.0 I can reproduce with : virt-viewer-0.5.7-7.el7.x86_64 VERIFY: virt-viewer-0.6.0-1.el7.x86_64 Steps: 1. # remote-viewer 2. Input address with extra space character "spice://10.66.7.84:5900 " and " spice://127.0.0.1:5900" 3. Click "Connect" button. Result: Can connect the guest, and the content in title bar is right. As the result set 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-2015-0295.html |