|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 ignores proxy settings | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Olaf Hering <ohering> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P3 - Medium | CC: | forgotten_KjUTH09OjI |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Outsourced Testing | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
bug742275.tar.xz
.xsession-errors |
||
|
Description
Olaf Hering
2012-01-19 10:14:28 UTC
Created attachment 471845 [details] bug742275.tar.xz some logfiles Created attachment 471846 [details]
.xsession-errors
What does /etc/sysconfig/proxy contain? Where do you configure the proxy after initial login so that firefox works? In YaST, GNOME or Firefox? What module of YaST does not use the proxy setting anymore? (In reply to comment #3) > What does /etc/sysconfig/proxy contain? Its in the logs: PROXY_ENABLED="yes" HTTP_PROXY="http://192.168.2.100:3128" As I said, zypper uses the proxy. > Where do you configure the proxy after initial login so that firefox > works? In YaST, GNOME or Firefox? FireFox uses the GNOME settings, but it can be configured to use private proxy settings. Just checked, thats how I configured firefox while I filed this bug. I used the GNOME network settings as well, which is the place where the per session (or user?) proxy is configured. > What module of YaST does not use the proxy setting anymore? I try online update, repos, and software. Now that I play more with the test installation: reconfiguring firefox to use system settings tells me it uses a proxy it can not reach. After double checking I noticed the GNOME settings dialog has a wrong port number (3180 instead of 3128). Sorry for that. I did also a re-login. Now firefox connects fine using system settings. smolt uses the proxy (not sure which setting it uses) rhythmbox uses the proxy (not sure which setting it uses, likely the GNOME setting). But yast software repos fails. Appearently it tries to connect directly, it gets an IPv6 address and tries to connect to that. To me it looks like yast does not use any proxy setting for some reason. I will paste to full error message. This is what I get with 'refresh all repos': Download (curl) error for 'http://widehat.opensuse.org/update/12.1/repodata/repomd.xml': Error code: Connection failed Error message: Failed to connect to 2a01:138:a004:0:21a:a0ff:fe26:efa9: Network is unreachable olaf@optiplex:~> host widehat.opensuse.org widehat.opensuse.org has address 62.146.92.202 widehat.opensuse.org has IPv6 address 2a01:138:a004:0:21a:a0ff:fe26:efa9 Is perhaps curl the culprit? *** Bug 743361 has been marked as a duplicate of this bug. *** Strange, zypper code doesn't handle proxy settings itself, it is handled by libzypp. So it should work in YaST the same way. Michael, any idea why proxy doesn't work in YaST? Is the proxy initialization related to the target system init? When libzypp reads the proxy settings? In 12.1 this is handled by libproxy, but it's the same for zypper and yast.
It might depend on the way yast is invoked ('su' or 'su -'). libproxy reads the settings from /etc/sysconfig unless the environment tells you are in a kde/gnome session. In this case the kde/gnome settings are used.
So if yast is started from a root login shell /etc/sysconfig is used.
--
The settings libproxy uses can be tested by calling:
_PX_DEBUG=1 proxy <URL>
(proxy is provided by package libproxy-tools)
Olaf, please check the previous comment and try the different ways mentioned there... Thats the output: optiplex:~ # _PX_DEBUG=1 proxy http://dist.suse.de/ Using config: 26sysconfig_config_extension Using ignore: Config is: http://192.168.2.100:3128 http://192.168.2.100:3128 optiplex:~ # Michael, what does that ^^^ mean? I don't understand the proxy stuff at all... Note: There have been various issues with libproxy, so it's recommended to use at least libzypp-11.1.1 and watch out for libproxy updates. The above output shows which proxy conf module libproxy is considering. It is '26sysconfig_config_extension' which is the right for zypp as /etc/sysconfig/proxy rules. So if you start yast from the above shell, the sysconfig settings should be used. libzypp versions prior to 11.1.1 followed libproxy even if gnome/kde config modules were considered. This may easily happen if the GUI launches zypper/yast using a non-login root shell. Since 11.1.1 libzypp forces libproxy into using '26sysconfig_config_extension'. The rest of the output shows the NO_PROXY value (Using ignore:) and PROXY value (Config is:) as derived from the config module used. The last line shows the suggested way of connecting to 'http://dist.suse.de/', i.e. via proxy 'http://192.168.2.100:3128'. (direct:// would instruct to use no proxy). Olaf, could you retry it in the latest openSUSE-12.2 milestone release? There is libzypp 11.1.0 which should have included some proxy fixes as mentioned in the previous comment. (In reply to comment #13) > Olaf, could you retry it in the latest openSUSE-12.2 milestone release? > > There is libzypp 11.1.0 which should have included some proxy fixes as > mentioned in the previous comment. I dont have a 12.2 system at home yet, but I found that yast2 in sles11sp2 has appearently the exact same issue: with zypper or firefox the proxy is used, while yast does not use it. Today I tried a Factory snapshot, a state of roughly Beta2. In yast2 proxy the 'Test Proxy Settings' worked. In yast2 repos the 'refresh all enabled repos' worked as well. Olaf, thanks for retesting it! I'm closing it as FIXED (for 12.2). |