From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
When first logging in, rhn-applet shows up as blue while it is waiting to first
login. Once it finds outdated packages, the red exclamation shows up. It seems
that it would be better to show the green connecting symbol when it says
"Waiting until first checkin...", instead of showing the blue check, and then
seeing a red exclamation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login and look at rhn-applet
Actual Results: rhn-applet shows the blue check
Expected Results: It should have shown the green connecting png
No one is brave enough? Try this patch
Created attachment 94002 [details]
The icon shows up as 'busy' while waiting for first checkin...
In test3, though, it happily changes to the blue check when in reality you
haven't had a chance to register with RHN yet. This means the user will be
thinking they're up to date unless they actually click on the applet icon, which
opens the RHN registration routine. Can we fix this?
With Fedora Core you don't have to register to get updates for example from
Yum repositories. I will check that there are sources defined, and if yes the
applet will be considered configured, if no, then the behaviour will need to
W.r.t. changing the behaviour when loggin in, no there is a random delay
introduced between the time of log-in and the time for the first check, that
need to be maintained. Turning the applet green is not proper, it means that
the applet is actively connecting to the server(s) and it is not the case
during that initial delay.
I realize that there is a delay between first login and first checkin, and that
the green connecting icon is not proper. However, I do not think that the blue
check mark is proper either, because it means that you are up-to-date.
I suggest using a different 'Waiting until first checkin' icon--something
neutral. Maybe a clock/watch or a different colored check mark.
Well increasing the number of icons gets confusing too. The tooltip
allows to get that information already.
Changing the default behaviour is not a clear improvement, it would
lead to more confusion too. At this point, my take is that the status
quo is not that bad, and I prefer to deal with the couple of messages
about a possible improvement, rather than to deal with possibly far more
people confused by new state or new icons. This has to stay *very*
simple because it affects end-users.