After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 695105 - Proxy settings are network agnostic. (Possible feature request)
Proxy settings are network agnostic. (Possible feature request)
Status: RESOLVED DUPLICATE of bug 640475
Product: gnome-control-center
Classification: Core
Component: Network
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-04 07:59 UTC by Michael Heyns
Modified: 2013-03-05 03:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Currently located Proxy Settings not showing any relation to network (30.52 KB, image/png)
2013-03-04 07:59 UTC, Michael Heyns 		Details

Description Michael Heyns 2013-03-04 07:59:30 UTC 
Created attachment 237932 [details]
Currently located Proxy Settings not showing any relation to network

As per request by Allan Day:

At the moment global Network Proxy settings are unaware of connected networks.
This poses a problem/inconvenience when moving a device between networks where proxy settings differ or are not used at all. A user has to manually adjust the settings everytime he/she connects.

In my case proxies are used at University and Work but not at Home. And with Gnome paying lots of attention to touch interfaces (and thus predominantly mobile/portable devices) I thought this could offer room for improvement.

WORKAROUND: I came across a small script that can automate the process but it is not an ideal solution. http://nulldereference.wordpress.com/2012/04/08/automatic-proxy-change-under-gnome-3/
Comment 1 Bastien Nocera 2013-03-04 09:59:28 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 640475 ***
Comment 2 Michael Heyns 2013-03-05 03:11:51 UTC 
Oops... Rookie Error. Thanks for the feedback.