GNOME Bugzilla – Bug 553269
gnome proxy settings : socks doesn't work
Last modified: 2015-06-02 17:19:29 UTC
Please describe the problem: I use to configure gnome proxy settings to set the proxy of my company : ]http://uploads.imagup.com/05/1222099796_proxy1.png It works fine, apps access to the internet through the proxy. For some apps, I use a ssh tunnel : proxy socks on localhost:3128, it works very fine. But now, if I want to define this proxy socks globally : http://uploads.imagup.com/05/1222099580_proxy.png It doesn't work, nothing use the tunnel, and no app can access internet :( Steps to reproduce: Actual results: Expected results: Does this happen every time? yes Other information:
When you configure the socks proxy, do the settings in GConf get updated? If so, the problem isn't with the control center, but with the apps using the settings. (If all of them fail to work, it seems more likely there is a problem with your setup, though, tbh; maybe those apps just don't support socks?). You can check the relevant keys with gconftool-2 -R /system/proxy | grep -v old | grep socks
$ gconftool-2 -R /system/proxy | grep -v old | grep socks socks_host = localhost socks_port = 3128 (I know this isn't a problem with the control center, but there wasn't any section which was appropriate, and there was no section "general") If I set the settings (socks proxy localhost:3128) directly in every application (firefox, thunderbird, pidgin, weather-applet...), they use correctly the tunnel. If I set in gnome settings an http proxy proxy.mycompany.com:3128, it works fine too (apt-get, liferea, firefox, thunderbird, pidgin, weather-applet) But if I set the socks proxy settings in gnome global proxy settings, no app manage to get a connection.
Well, nobody would look at a "general" bug. You need to file separate bugs against specific packages which fail to work so the people responsible for those packages can look at it.
Let's start with the weather-applet.
gweather-applet not working is libgweather's fault, which is in turn libsoup's fault
*** Bug 582645 has been marked as a duplicate of this bug. ***
Any chance of having SOCKS support back? I run into the same situation.
Yes, SOCKS proxy support in libsoup would be really useful. In fact, it seems it used to support SOCKS (commit 47d1992e9bda15f604df3dada2ef7ca0e74b4bb2 "SOCKS version 4 and version 5 support. This code is not very simple" by alex <alex> on Sun Jan 14 10:49:59 2001), However socks support was later removed (the removal is mentioned in the NEWS file under "Changes in libsoup from the 2.0 series (1.99.x versions) to 2.2", although it was not explained why) but I could not find the relevant commit for that. Anyway, a bunch of browsers rely on libsoup (through webkitgtk), support for socks proxies would be really helpful. thanks.
GIO's GProxy has socks support. Not sure what's missing for it to be used in libsoup and WebKitGTK+.
Fixed in git, so this will be working as of GNOME 3.6. (It depends on new glib API, so can't be backported to 3.4.)
*** Bug 601895 has been marked as a duplicate of this bug. ***