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 551932 - support system wide proxy settings
support system wide proxy settings
Status: RESOLVED DUPLICATE of bug 640475
Product: gnome-control-center
Classification: Core
Component: Network
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-12 10:05 UTC by Michael Vogt
Modified: 2013-02-01 21:57 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
Patch that implements system wide proxy settings (103.25 KB, patch)
2008-09-12 10:09 UTC, Michael Vogt
rejected Details | Review

Description Michael Vogt 2008-09-12 10:05:43 UTC
Please support setting the proxy system wide via the new org.gnome.GConf.Defaults mechanism.

I will attach a patch that adds this feature. There will be two new buttons in the main glade file "Apply System-Wide..." and "Reset". 

When "Apply" is pressed, the setting is written as a system default (via dbus and the gconf defaults feature) for all users that do not override it. Reset resets the personal settings back to the system default.

Thanks,
 Michael
Comment 1 Michael Vogt 2008-09-12 10:09:48 UTC
Created attachment 118573 [details] [review]
Patch that implements system wide proxy settings
Comment 2 Jens Granseuer 2008-09-12 16:17:11 UTC
I am opposed to these changes. I don't see the value of adding these buttons everywhere a possibly suited setting shows up (granted, the proxy settings are probably one of the saner use cases, but still). They are just cluttering up the interface. Maybe we should instead talk about how apps like sabayon can make supporting this easier?

Not to mention that "Apply System-Wide" doesn't actually apply system-wide unless nobody has set anything, yet. And what use is "Reset", anyway?

(Even if I wasn't opposed to the idea as such, I'd certainly be opposed to the patch that touches every single line in the glade file, and thus completely interferes with other ongoing work like bug 477040.)
Comment 3 Michael Vogt 2008-09-12 18:44:57 UTC
Thanks for reviewing the patch. 

I would be happy to cleanup the glade patch to only include a minimal diff and to make the wording more clear (like "Make system default" and "Reset to system default" for example). But if the feature request is rejected on principal grounds, then that does not help I guess.

Are you of the same opinion for other settings that might be useful to apply as system defaults? Like making the keyboard settings global?

Thanks,
 Michael
Comment 4 Jens Granseuer 2008-09-12 22:28:16 UTC
It it was only in the network capplet, I wouldn't mind that much, but if they are going to pop up everywhere (and I expect them to once they are there), those buttons are a problem.

My major problem with the change is: What is the use case? Why do you want those buttons? Who do you expect to use them? What for? I just don't see that.

I didn't immediately close the bug as WONTFIX because I'd like to get a few other opinions first. If I'm the obvious minority, I might give in anyway.
Comment 5 Richard Hughes 2011-09-08 17:01:31 UTC
Now we've ported away from GConf, do people still want to do this with dconf / GSettings?
Comment 6 Pacho Ramos 2011-09-09 14:55:13 UTC
At least from my point of view, I would still like to see this to be supported. Thanks a lot
Comment 7 Rodrigo Moya 2011-09-12 11:08:40 UTC
I think it makes sense, although I've heard we're going to have proxy settings per NM connection. If that's true, maybe we can just remove the proxy settings UI completely, as it will be a property on the connection.
Comment 8 Dan Winship 2013-02-01 21:57:32 UTC
Yeah, with NM-based proxies, if you set proxy information on "System eth0" or whatever, then everyone would get it automatically

*** This bug has been marked as a duplicate of bug 640475 ***