Description of problem: I did a dnf update on several machines recently, and lost the ability to do a remote-viewer or any other remote VNC access to my Gnome sessions. Unfortunately, the dnf update can't be reverted with dnf history undo on either machine, for different reasons. Version-Release number of selected component (if applicable): vino.x86_64 3.22.0-1.fc25 @anaconda How reproducible: Always (seen on three machines) Steps to Reproduce: 1. Update with 'dnf update' 2. Do a remote-viewer vnc://localhost:5900 3. Verify that you can see the desktop (in self-mirror effect) 4. Do a remote-viewer vnc://your-host:5900 from another machine, or use another VNC client (I was using Screen Sharing successfully so far) Actual results: Error message, access to port 5900 is apparently denied. Expected results: Remote connection to desktop over VNC Additional info:
Shutting down firewalld does not help. lsof -i: vino-serv 2195 ddd 12u IPv6 30216 0t0 TCP *:rfb (LISTEN) Why only IPv6? Same with netstat -lptu / -lptun : tcp6 0 0 [::]:rfb [::]:* LISTEN 2195/vino-server tcp6 0 0 :::5900 :::* LISTEN 2195/vino-server
I'm starting to wonder if the dnf update is not a red herring. Another possibility is that something changed in my network configuration, and that I was relying on IPv6 before.
May be related to https://bugs.launchpad.net/ubuntu/+source/vino/+bug/228370. Tried to connect manually with IPv6, i.e. remote-viewer vnc://[v6-addr]/?port=5900. Same error. Tried to force DNS resolution to return IPv6 address, and to connect with IPv6 address on Apple Screen Sharing, still not working.
It took me several hours to find a workaround, but here it is: - Run dconf editor - Go to /org/gnome/desktop/remote-access/network-interface - Change "default value" to "off" - Set custom value to the name of your network interface After that, connections through IPv4 are accepted again, and I can connect both from Linux and macOS.
Digging further with information from https://bugzilla.redhat.com/show_bug.cgi?id=703009 that seemed to suggest the problem might be related to localhost, I noticed that my new DNS setup had the following in /etc/bind/db.local: @ IN SOA localhost. root.localhost. ( 2 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS localhost. @ IN A 127.0.0.1 @ IN AAAA ::1}}} The AAAA line is sufficient to throw all vino-server instances on the network off. With it, lsof -i -P does not show an IPv4 port. With it, I get: [root@shuttle ddd]# lsof -i -P | grep -i vino vino-serv 1845 ddd 12u IPv6 33997 0t0 TCP *:5900 (LISTEN) vino-serv 1845 ddd 13u IPv4 33998 0t0 TCP *:5900 (LISTEN) vino-serv 1845 ddd 15u IPv4 35300 0t0 TCP shuttle.dinechin.org:5900->192.168.77.22:53614 (ESTABLISHED) I am not sure if this is expected or not. I find it a bit surprising, since the mapping of localhost to ::1 is rather common (although putting it in a DNS might not be).
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.