RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
spice-gtk can not parse ipv6 address given in SPICE_PROXY variable or vv-file proxy= key

Version-Release number of selected component (if applicable):
spice-gtk3-0.31-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.
a) run:
  SPICE_PROXY=http://[proxy:v6::address]/ remote-viewer spice://example.org:5900/
b) in vv file, set proxy= key to proxy=http://[proxy:v6::address]/

Actual results:
* spice-gtk attempts direct connection
* spice-gtk prints:
GSpice-WARNING **: Invalid uri port: v6::address]

Expected results:
spice-gtk connects through proxy

Additional info:
when using DNS name with just AAAA record pointing to IP in question, the connection to proxy succeeds over v6 - so the problem is just with v6 address parsing both from environment and .vv file

Patches posted: https://lists.freedesktop.org/archives/spice-devel/2016-May/029055.html

Fixed upstream by commits:
dab190d8d2cb93f85f1858135354dd4e93ff48f8
024eccefba506f57fbff837c6d75864c51ed2add
85051b06c1f04b206c00bb7f674a9a29bfb19594
eacbe261d48979f72585225107d00bba76623e8e
8dcb4129acde2aed353cd66e28678408e7d1257c
b542dfa2d58cd352dc596318a1e50f074865ef5e

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-2229.html