Bug 98369 - clicked on the "view advisory" button in up2date confused app
Summary: clicked on the "view advisory" button in up2date confused app
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
(Show other bugs)
Version: 9
Hardware: i686 Linux
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Fanny Augustin
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-01 19:21 UTC by Shawn Houston
Modified: 2007-04-18 16:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-20 21:03:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Shawn Houston 2003-07-01 19:21:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
I clicked on the "view advisory" button in up2date after selecting all components:

$ up2date
Traceback (most recent call last):
  File "/usr/share/rhn/up2date_client/gui.py", line 1063, in showAdvisory
    advisories = rhnErrata.getAdvisoryInfo(rowData[1])
TypeError: unsubscriptable object

After selecting just one the app proceeded. This is a very non-critical bug, but
shows sloppy programming.

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

How reproducible:

Steps to Reproduce:
1.run up2date
2.either fail to select a component or select all
3.click "view advisory"

Actual Results:  The app generates strange error, the hour glass appears, no
feedback is given that the user can proceed even though in testing they can.

Expected Results:  Either nothing happens (kind of acceptable), or a nice
warning along the lines of "please select one item before clicking view advisory"

Additional info:

Comment 1 Ronan Waide 2003-07-07 12:36:54 UTC
Also happens if you don't select /any/ items on the list.

Comment 2 Adrian Likins 2003-07-09 21:25:01 UTC
I belive both of these should be fixed in 3.1.41 or later.

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