Ubuntu
gconf package

setting http proxy directly via gconf no longer works

Bug #290995 reported by Anton Keks
2
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Starting from intrepid, http proxy settings cannot be enabled using either gconf-editor or gconftool-2.

You can modify any of the /system/http_proxy/* values and they got reflected immediately in the gnome-network-preferences, except for the /system/http_proxy/use_http_proxy - setting this from outside of the gnome-network-preferences has no effect, so no applications pick the newly set values.

However, when using the radio buttons in the gnome-network-preferences to enable/disable the proxy, the /system/http_proxy/use_http_proxy gets properly enabled/disabled in the gconf-editor. It appears that gnome-network-preferences has started doing something else itself to enable the proxy that is not done when the setting is changed by other programs.

Intrepid regression: it is not possible to enable/disable proxy from the command-line anymore, e.g. with a NetworkManager dispatch script.

Revision history for this message
Anton Keks (anton-azib) wrote :

OK, actually I have figured that out:

Since Gnome 2.24(?) the main setting moved to /system/proxy/mode, which can take values of 'auto', 'manual' and 'none'. This probably replaces the old /system/http_proxy/use_http_proxy, so setting of the latter directly has no effect, while setting the mode to 'manual' in the new location enables the use_http_proxy as well.

Revision history for this message
Anton Keks (anton-azib) wrote :

Here is what I was talking about:
http://blog.azib.net/2008/11/enable-http-proxy-in-gnome.html

The bug may be closed now, but probably it would be nice to reflect setting of /system/http_proxy/use_http_proxy by setting /system/proxy/mode to manual as well, ignoring direct changes of use_http_proxy is not nice, especially when it used to work before.

Revision history for this message
Sebastien Bacher (seb128) wrote :

that's not a gconf bugs, the key change could be discussed on bugzilla.gnome.org though

Changed in gconf:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.