Bug 70260 - RHN Notification Tool mis-reporting
Summary: RHN Notification Tool mis-reporting
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rhn-applet
Version: 7.3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-31 11:24 UTC by Martin C. Messer
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-04-08 09:47:39 UTC
Embargoed:


Attachments (Terms of Use)
Mouse over (deleted)
2002-07-31 11:26 UTC, Martin C. Messer
no flags Details
Mouse over (deleted)
2002-07-31 11:28 UTC, Martin C. Messer
no flags Details

Description Martin C. Messer 2002-07-31 11:24:50 UTC
Description of Problem:

When I run up2date -l, I see the following updateable packages:

Name                                    Version        Rel     
----------------------------------------------------------
mm                                      1.1.3          8                   
mm-devel                                1.1.3          8           

When I put my mouse over the Notification Tool on my panel, it tells me there
are 4 updates available. When I click on the Notification Tool, I see the same 2
packages listed twice. See the attached screenshots.

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

rhn-applet-1.0.6-11

How Reproducible:

I've noticed it with at least one previous errata release where the number of
packages was duplicated.

Comment 1 Martin C. Messer 2002-07-31 11:29:31 UTC
Well, I won't be attaching anything since Bugzilla is choking when I try. I've
reported the problem to Dave.

Comment 2 Daniel Veillard 2003-04-08 09:47:39 UTC
Hum, I have never been able to reproduce this behaviour, either
the problem was fixed since 7.3 or there was a local corruption
of the rhn-applet cache, or you had mm/mm-devel registered twice
in the RPM database for some reason. Anyway this seems impossible
to fix without being able to reproduce it.

Daniel


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