Bug 725948

Summary:	GNOME does not pick up system proxy
Product:	[openSUSE] openSUSE 12.1	Reporter:	Atri Bhattacharya <badshah400>
Component:	GNOME	Assignee:	E-mail List <gnome-bugs>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P3 - Medium	CC:	federico, ohering
Version:	Final
Target Milestone:	---
Hardware:	All
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Atri Bhattacharya 2011-10-22 11:18:54 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1

If the proxy is set from YaST -> Proxy, GNOME does not pick up this proxy automatically (or even on the next login). It used to do so with openSUSE 11.4 (and GNOME 2.32). At present one has to manually set the proxy once again the "Network" settings in the control-center. SO one has to set/change proxies at two places now: once at the YaST Proxy module for zypper, etc and then again in g-c-c, which is inconvenient.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Vincent Untz 2011-11-24 16:25:44 UTC

*** Bug 732590 has been marked as a duplicate of this bug. ***

Comment 2 Federico Mena Quintero 2012-01-04 16:32:17 UTC

The duplicate bug says this, from Dominique Leuenberger:

- 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

I don't know much about libproxy, or about which apps use it.  I'd *love* to kill our custom proxy plugin for g-s-d and instead have common infrastructure that takes care of this, though.

Can anyone please enlighten me as to the state of things, how libproxy plays into things, etc.?  I can probably work on fixing this at some point, but I'll need to know about the new world order :)

Comment 3 Vincent Untz 2012-01-04 16:50:54 UTC

(In reply to comment #2)
> Can anyone please enlighten me as to the state of things, how libproxy plays
> into things, etc.?  I can probably work on fixing this at some point, but I'll
> need to know about the new world order :)

Here's what I know:

 - libproxy has a GNOME plugin to read the settings from the right place (gsettings now)

 - glib-networking provides a gio module implementing proxy stuff using libproxy, and in general, apps using proxy are using libproxy.

So we already have everything setup to properly work with libproxy. The only missing bit now is what is mentioned in the upstream bug :-)

Comment 4 Olaf Hering 2012-01-18 12:41:58 UTC

12.1 behaviour is really broken, at least the unpatched system.

In second stage install a proxy is configured, and later used when the release-notes download test runs.
After initial login and running yast these proxy settings are still used.

Then I added the proxy settings into the gnome network settings so that firefox may use also a proxy. But when I run yast again, the settings are now ignored and direct internet connection is used. 
zypper on the command line does still use the proxy settings.

Comment 5 Tomáš Chvátal 2017-08-12 20:07:34 UTC

12.1 is out of support scope. Please open a new issue if you still can reproduce the issue on the current release.