Bug 1024199
Summary: | remote-viewer gui tool cannot recognize URI address with space character | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | 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: | 6.5 | CC: | cfergeau, codong, dblechte, dyuan, lcui, marcandre.lureau, mzhan, rbalakri, tzheng, zsong | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | virt-viewer-0.6.0-1.el6 | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Type a URI with additional space characters
Consequence:
The URI is invalid, and the connection fails.
Fix:
Trim the URI string
Result:
Even with additional spaces, the connection will be attempted.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1024204 (view as bug list) | Environment: | ||
Last Closed: | 2014-10-14 06:30:12 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1024204 |
Description
CongDong
2013-10-29 06:27:54 UTC
for future reference, better to put the commit: commit 69ffdb50b9b83c031af4968ff40da084ecfda934 Author: Christophe Fergeau <cfergeau> Date: Tue Oct 29 10:14:29 2013 +0100 Clean-up spaces before/after URI in connection dialog I can reproduce this issue with: virt-viewer-0.5.6-8.el6.x86_64 Verify the bug with virt-viewer-0.6.0-4.el6: 1. # remote-viewer 2. Input address with extra space character "spice://ip_address:5900 " 3. Click "Connect" button. The display window of virt-viewer displayed normally. So change the status 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. http://rhn.redhat.com/errata/RHBA-2014-1379.html |