Description of problem: This is another application that needs a hook in our network code to ask whether a particular port is blocked, and advise the user what to do if that is the case. As it is, vino will mysteriously not work -- the answer is to open a particular port number but how is the user to know?
Yeah, totally. Any ideas on that or are you just saying that this is a general problem which we haven't figured out a solution to? We can do the NTP thing (open the port on boot) for system wide services, but per-user services?
It's a general problem; just noting another need for it. Another that springs to mind is print queue browsing (IPP) -- not sure at this point if that's meant to be per-user or per-system.
*** Bug 134382 has been marked as a duplicate of this bug. ***
*** Bug 159605 has been marked as a duplicate of this bug. ***
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Changing version and component. This is still an issue -- more so with the coming Fedora 9 with stricter firewall settings.
The 'I am providing the requested information for this bug' checkbox didn't work -- changing to ASSIGNED instead.
The VNC port was never open by default, so why is this more an issue with Fedora 9?
The general problem noted in comment #2 is more of an issue with Fedora 9.
This is a RFE for rawhide.
features should get the 'FutureFeature' keyword
*** This bug has been marked as a duplicate of bug 440469 ***