Bug 90094 - gnome-network-preferences does not set gconf-http_proxy-key
gnome-network-preferences does not set gconf-http_proxy-key
Product: Red Hat Linux
Classification: Retired
Component: control-center (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jonathan Blandford
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-05-02 09:13 EDT by Fabian Deutsch
Modified: 2013-04-02 00:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-21 08:53:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fabian Deutsch 2003-05-02 09:13:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.2.1) Gecko/20030225

Description of problem:
When I changed the GNOME Proxy-settings it was simply ignored.
The gnome-network-preferences dialog doesn't change the value of the

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Open GNOME Netork Proxy (gnome-network-preferences)
2. Choose "Manual Proxy Configuration"
3. Enter your Proxyserver IP and port and close the dialog.
4. Look at the gconf-key /system/http_proxy/use_http_proxy or test it: Open
nautilus and enter http://www.gnome.org, nothing happens.

Actual Results:  Nothing happens.

Expected Results:  Nautilus would show me the html-code of www.gnome.org/index.htm

Additional info:

To activate the proxy just type "gconftool-2 --set
/system/http_proxy/use_http_proxy --type=bool [true|false]" on the console.
Comment 1 Marco Pesenti Gritti 2004-10-21 08:02:44 EDT
Works fine for me on rawhide. If I keep gconf-editor open I can see
the box to be checked/unchecked when I switch None/Manual in

Could you try with a more recent version please ?
Comment 2 Fabian Deutsch 2004-10-21 08:53:57 EDT
True, is working now.

Note You need to log in before you can comment on or make changes to this bug.