Public bug reported: If I set a socks proxy without setting an http proxy, gnome terminal sessions still have the http_proxy environment variable set, but as "http://:8080". Needless to say, this does not work.
Not only do programs not use the socks proxy as I request (not surprising as adding socks support is not completely trivial), but they also try to use an invalid http proxy when I didn't indicate that I wanted one at all. Presumably if the HTTP proxy section is left blank, then http_proxy should be left unset. ** Affects: control-center (Ubuntu) Importance: Undecided Status: Unconfirmed -- http_proxy defined incorrectly https://launchpad.net/bugs/78098 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs