Bug 83158 - rhn-applet-gui requires network to be up before it's started
rhn-applet-gui requires network to be up before it's started
Product: Red Hat Linux
Classification: Retired
Component: rhn-applet (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Veillard
Depends On:
  Show dependency treegraph
Reported: 2003-01-30 15:42 EST by Andre Robatino
Modified: 2007-04-18 12:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-03 16:31:57 EST
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 Andre Robatino 2003-01-30 15:42:53 EST
Description of problem:
  If the network is down when rhn-applet-gui is started, then "Check for
updates" will fail even if the network is subsequently brought up.  For example,
this situation holds if one is on dialup and brings up the network manually
after logging in (when rhn-applet-gui is automatically started).  The only
workaround I'm aware of is to bring up the network, then kill rhn-applet-gui,
then restart it.  My father and I both have the same problem.  I have DSL and
can avoid it by bringing up the network at boot time.  He's on dialup and this
isn't practical, so I advised him to put the appropriate commands in the
modemlights startup.

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

How reproducible:

Steps to Reproduce:
1.  Bring down the network, if it's up.
2.  Login in X windows, causing rhn-applet-gui to start up.  It will gray out,
of course.
3.  Bring up the network.
4.  Get rid of the network error message by left-clicking on the RHN applet and
dismissing it.  Then right-click on the RHN applet and select "Check for updates".
Actual results:
  It turns green, then goes gray.  It can never work unless it's killed and
restarted _after_ the network connection is up. 

Expected results:
  It should turn green, then turn either blue or red depending on whether there
are updates.

Additional info:
Comment 1 Tom Mortell 2003-02-01 21:32:15 EST
I can confirm that this also occurs with rhn-applet-2.0.7-2
Every two minutes it will access the disk while green and
then go gray with a red slash.

If rhn-applet is started while on-line,
green turns to blue with white check mark.
"No updates available..."

Tom Mortell
Comment 2 Daniel Veillard 2003-02-03 16:31:57 EST
I can't reproduce this with the version in RawHide.
As long as the network won't be up, the icon will 
be the grey and red one indicating the absence of 
connection to the server but once the ethernet card
is plugged in the laptop then the connection succeed
and indicate the current status sucessfully within
a couple of minutes.

  Works for me,

Comment 3 Andre Robatino 2003-02-03 16:55:19 EST
  I installed RawHide version 2.0.7-2 in a basically 8.0 installation but it
segfaults when I try to run it.  Presumably the whole fix depends on having the
latest version of other packages as well.  It's important that this work in 8.1,
otherwise anyone on dialup is screwed (though I know that Red Hat isn't
targeting the home user quite yet!).
Comment 4 Daniel Veillard 2003-02-03 17:18:35 EST
Yes it is expected to be fixed in the next release of Red Hat Linux.

Comment 5 Chip Turner 2003-04-09 12:35:14 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

Comment 6 Tom Mortell 2003-04-10 20:36:47 EDT
The problem is still there, for me, after updating to
as noted in errata RHBA-2003-080

Tom Mortell
Comment 7 Tom Mortell 2003-12-16 14:22:26 EST
The problem is gone in Fedora Core 1 with 
rhn-applet 2.1.4-3

Tom Mortell

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