| Summary: | vino IPv6 support breaks with tigervnc-server-module | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Sullivan <jsrhbz> |
| Component: | vino | Assignee: | Søren Sandmann Pedersen <sandmann> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | kem, sandmann |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-16 15:45:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
(Found bug 703009 and bug 711212 before submitting: not sure whether they're related, looks like this is something else.) This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
The changelog for vino 2.32.2 says: - Bind both an IPv4 and an IPv6 socket. Old behaviour was for vino to attempt to bind the :0 VNC port (5900) by binding AF_INET/0.0.0.0/5900, if that failed try again :1 (5901), etc. The tigervnc server module runs under Xorg and since it starts first grabs :0, itself binding 0.0.0.0:5900. Therefore vino was (for me) always on :1. With the latest version, vino first attempts to bind :::5900. Since the tigervnc module doesn't support IPv6, this endpoint is unused and the bind works. Then vino goes for the IPv4 endpoint, which fails. Instead of closing the v6 socket and starting again at :1, vino treats binding half the sockets it wanted as success and continues on. (It closes the socket file descriptor, but doesn't report the failure in .xsession-errors.) So we end up with 0.0.0.0:5900 bound to Xorg, and :::5900 bound to vino. Since this particular machine is not remotely accessible over IPv6, vino cannot be accessed. (And since I have yet to figure out how to configure the Xorg module, I can't use that either rendering the desktop completely inaccessible.) Workaround: Use gconf-editor to set /desktop/gnome/remote_access/alternative_port to 5901 and enable use_alternative_port (they can't be configured via the control panel!) Fix: bind the IPv4 address first on failure of either bind roll to next server port or both.