So, any possibility to have this problem fixed in Hardy? * RANT MODE ON * This is exactly the kind of bugs that drives me mad. This is not some strange problem in a strange function of a remote piece of code in a seldom used app. This is a big problem in the remote access tool of the most used free software desktop. How it is possible that it got into a STABLE release of Gnome AND Ubuntu without nobody noticing it? It is possible that nobody EVER tried a local connection to VNC? As Anybody ever TESTED it? It is not some super strange corner-case: tick local connections, try to connect, IT DOES'T WORK! And nearly a YEAR (form 2007 in Gnome Bugzilla) to have it fixed? Will somebody port the patch to 2.22 or 2.20? Probably not because it is not a new shiny feature and we must work on fast on our next HALF BACKED, STABLE new release! Issue like this are the real problem of the Linux desktop. Sh*&87 bugs not meant to be here in the first time if just a little REAL test was done. Gnome and Kde are and have been full on this untested sh*776 pieces of code from ever in their STABLE releases. Even the explorer.exe of Win95 probably had less bugs than any version of Gnome panel+nautilus+control center ecc.. * RANT MODE OFF *
And please, excuse my bad english -- vino-server doesn't accept IPv4 connections when "local only" is checked https://bugs.launchpad.net/bugs/228370 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
