Bug 732590 - GNOME does not honor system proxy settings
Summary: GNOME does not honor system proxy settings
Status: RESOLVED DUPLICATE of bug 725948
Alias: None
Product: openSUSE 12.1
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: x86-64 Linux
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-24 11:23 UTC by Olaf Hering
Modified: 2011-11-24 16:25 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Hering 2011-11-24 11:23:16 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0

After a fresh 12.1 installation with GNOME desktop, firefox connects directly to the internet instead of using the proxy which was configured during the second stage installation.
In the proxy log I see zypper and yast using the proxy, but when I run firefox it ignores the yast proxy settings. 
There is a gnome network configuration window which per default seems to use 'None' as proxy.
If the proxy is configured there once more, firefix finally uses these settings.

Please make sure GNONE follows the system settings per default.

Reproducible: Always
Comment 1 Dominique Leuenberger 2011-11-24 13:04:28 UTC 
This is due to: (gnome-settings-daemon)

- Disable gnome-settings-daemon-system-proxy-configuration.diff for
  now: we really need to fix it the proper way, which likely
  involves libproxy, as mentioned in
  http://code.google.com/p/libproxy/issues/detail?id=165 (tracked
  in bnc#690493).
Comment 2 Vincent Untz 2011-11-24 16:25:44 UTC 
This is bug 725948.

FWIW, the g-s-d patch got dropped because there is no way to disable this in the UI, which is a blocker for the patch.

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