Of that I'm not really certain. I filed this report because as a user the behaviour surprised me that some things would be able to access the network and others wouldn't.
Having dug into the problem a little it's apparent that it's not trivial to solve - that doesn't mean that it's not worth solving, though. Perhaps Ubuntu could integrate the PACRunner project[1], or something similar, and teach the various network dependant tools to talk to that rather than relying on environment variables? Or perhaps the tools can be taught to use libproxy[2]? At the very least maybe we should alert the user that the automatic settings will result in various things, such as software installation, possibly not working. I suppose which resolution is chosen depends on how much of a priority seamless networking on proxied connections is for Ubuntu and the engineers involved. 1. http://git.kernel.org/cgit/network/connman/pacrunner.git 2. https://code.google.com/p/libproxy/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1084851 Title: No system-wide proxy for "automatic" proxy setting method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1084851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
