Bug 761148 - Subscription assistant has no close button.
Summary: Subscription assistant has no close button.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: subscription-manager
Version: 5.8
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: William Poteat
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 771748 807971
TreeView+ depends on / blocked
 
Reported: 2011-12-07 19:02 UTC by J.C. Molet
Modified: 2012-04-23 14:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-23 14:49:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description J.C. Molet 2011-12-07 19:02:24 UTC 
Description of problem:
The Subscription Assistant in the subscription-manager tool has no close button.  The only way of closing it is using the X button or via keyboard shortcut.  This is not a huge issue, but it is a convenience thing that all other pop-ups and dialogs in the program give you.

This should be added for consistency.


Version-Release number of selected component (if applicable):
subscription-manager-gnome-0.98.5-1.git.2.cd86f84.el5_7
Comment 1 RHEL Program Management 2012-01-09 14:50:14 UTC 
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.8 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.
Comment 3 RHEL Program Management 2012-04-02 10:50:41 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Note You need to log in before you can comment on or make changes to this bug.