Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
3/3
Prerequisites :
Client : Rhel5.7 with following subscription manager client
subscription-manager-firstboot-0.95.5.18-1.git.4.364aa10.el5
subscription-manager-0.95.5.18-1.git.4.364aa10.el5
subscription-manager-gnome-0.95.5.18-1.git.4.364aa10.el5
Steps to Reproduce :
Boot client in run level 3
Execute subscription-manager-gui command on root console.
Expected Result :
No Traceback should display .
Proper message should display for “Xserver” requirement .
Actual Result :
Traceback (most recent call last):
File "/usr/sbin/subscription-manager-gui", line 30, in ?
import gtk
File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 76, in ?
_init()
File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 64, in _init
_gtk.init_check()
RuntimeError: could not open display
I tested this against a few other pygtk apps (caribou, system-config-date, meld) and they exhibit the same behavior. After seeing the other apps, I believe the error message should stay as-is, since it is more informative than a generic "cannot find xserver" message.
marking as NOTABUG, feel free to alter if you disagree though.
Description of problem: Version-Release number of selected component (if applicable): How reproducible: 3/3 Prerequisites : Client : Rhel5.7 with following subscription manager client subscription-manager-firstboot-0.95.5.18-1.git.4.364aa10.el5 subscription-manager-0.95.5.18-1.git.4.364aa10.el5 subscription-manager-gnome-0.95.5.18-1.git.4.364aa10.el5 Steps to Reproduce : Boot client in run level 3 Execute subscription-manager-gui command on root console. Expected Result : No Traceback should display . Proper message should display for “Xserver” requirement . Actual Result : Traceback (most recent call last): File "/usr/sbin/subscription-manager-gui", line 30, in ? import gtk File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 76, in ? _init() File "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 64, in _init _gtk.init_check() RuntimeError: could not open display