Bug 83798 - up2date doesn't run when http proxy is not valid
up2date doesn't run when http proxy is not valid
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
8.0
i686 Linux
low Severity low
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
:
Depends On:
Blocks: 120092
  Show dependency treegraph
 
Reported: 2003-02-08 17:11 EST by Florin Andrei
Modified: 2005-10-31 17:00 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-26 17:24:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Florin Andrei 2003-02-08 17:11:14 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
If i configure up2date to use a proxy server, then i go to another place where
that proxy hostname is no longer valid, up2date does not run, it dies silently
without a warning or an error message.

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


How reproducible:
Always

Steps to Reproduce:
1.configure up2date to use your proxy server
2.launch up2date from the RHN applet in the panel
3.it works fine
4.go to a different network where the hostname you configured for a proxy is not
valid
5.launch up2date from the RHN applet in the panel
    

Actual Results:  nothing happens. up2date dies silently, but the user does not
get any notification on that

Expected Results:  up2date should prompt an error message saying "proxy not
available" or something like that

Additional info:

this bug is very bad for laptop users. when going to a different network,
up2date dies misteriously.
also, there are way too many places to configure a proxy server. all
applications, including the RHN applet and up2date should use the setting
configured in the Preferences / Network Proxy menu.

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