Bug 181307
| Summary: | pirut doesn't work with a proxy (even if yum does) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | oll <olivier.lelain> |
| Component: | pirut | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | sundaram |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | test3 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-20 20:15:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
These bugs are being closed since a large number of updates have been released after the FC5 test1 and test2 releases. Kindly update your system by running yum update as root user or try out the third and final test version of FC5 being released in a short while and verify if the bugs are still present on the system .Reopen or file new bug reports as appropriate after confirming the presence of this issue. Thanks Thank you very much : this is indeed now fixed. But I have exactly the same problem with system-config-kickstart ? Will it be also solved soon or should I open a bug ? Better to file another report on it. Thanks |
Description of problem: Pirut simply doesn't work behind a proxy Version-Release number of selected component (if applicable): pirut-0.9.10-1 How reproducible: Always Steps to Reproduce: 1.run pirut 2. 3. Actual results: "Retrieving Software information window appears" but freezes untill I kill it. Expected results: I don't know : I never saw the next point :-) Additional info: Setting the http_proxy variable makes yum work very well. I also set gnome proxy preferences. I think it's a proxy problem since strace gives me : connect(.....sin addr=inet addr("209.132.177.50"}} and direct connection are indeed firewalled