Red Hat Bugzilla – Bug 1268043
Back button on first panel of subscription-manager-gui workflow has no effect
Last modified: 2016-11-03 16:27:21 EDT
Description of problem: As a consequence of attempts to address bug 1257179 and bug 1243707, the newly introduced Back button in the subscription-manager-gui has no effect (FIRST PANEL ONLY) and the dialog has no obvious way to be canceled. Arguably one could say that since you are on the first registration panel there is no more going "Back" which explains why the Back button has no effect. It's just not user friendly to be able to click a button that does nothing. Instead, this button should be either disabled or undisplayed when on the first panel of registration. Workarounds for Canceling: 1. right click on the gnome widow decoration and choose "Close" 2. Hit the "Esc" key Version-Release number of selected component (if applicable): [root@jsefler-7 ~]# rpm -q subscription-manager-gui subscription-manager-gui-1.15.9-13.el7.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Either disable or undisplay the back button on first panel of registration workflow Additional info:
deferring to rhel-7.3.0 due to severity and time schedule remaining for rhel-7.2.0
PR https://github.com/candlepin/subscription-manager/pull/1446
Correction Master Commit: ea587429b223b554eefce0001ac722afd442e59a please ignore comment 4
Created attachment 1179595 [details] Back button is disabled for the first panel of registration workflow [root@shwetha-workstation ~]# subscription-manager version server type: This system is currently not registered. subscription management server: 2.0.13-1 subscription management rules: 5.20 subscription-manager: 1.17.9-1.el7 python-rhsm: 1.17.5-1.el7 subscription-manager-gui-1.17.9-1.el7.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2592.html