Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 237536 - pup doesn't honor the GNOME global proxy settings
pup doesn't honor the GNOME global proxy settings
Status: CLOSED DUPLICATE of bug 213402
Product: Fedora
Classification: Fedora
Component: pirut (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2007-04-23 13:59 EDT by fangorious
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-23 14:13:22 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 fangorious 2007-04-23 13:59:34 EDT
Description of problem:

After setting the HTTP proxy address, port, and authentication credentials in
System->Preferences->Internet and Network->Network Proxy the Software Updater
(Applications->System->Software Updater, pup) still fails.

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


How reproducible:

Every time

Steps to Reproduce:
1. Connect to a network with an HTTP proxy that requires authentication (I don't
know if authentication matters or if pup ignores all GNOME global proxy
settings, my proxy needs auth so that's what I'm reporting)
2. Try to run Applications->System->Software Updater
Actual results:

After a few minutes with no indication that anything is happening, an error
window comes up indicating failure.

Expected results:

The Software Updater GUI should come up, and then try to connect to the
repositories using the proxy information set in in GNOME.

Additional info:
Comment 1 Jeremy Katz 2007-04-23 14:13:22 EDT
pirut-1.3.5 adds the necessary bits for usermode to pass the env vars through.

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

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