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 client with following subscription-manager rpm
subscription-manager-0.95.5.18-1.git.4.364aa10.el5
subscription-manager-gnome-0.95.5.18-1.git.4.364aa10.el5
subscription-manager-firstboot-0.95.5.18-1.git.4.364aa10.el5
Steps to repro :
1) Invoke subscription-manager-gui using “subscription-manager-gui” command executed on console1
2) Execute same command “subscriptio-manager-gui” on console2
Expected Result:
Proper Message should display “ Subscription-manager is already running “
Actual Result :
At step 2
Running subscription-manager gui got terminated
Displayed following trace back on console
(subscription-manager-gui:5318): libglade-WARNING **: unknown attribute `swapped' for <signal>.
(subscription-manager-gui:5318): libglade-WARNING **: unknown attribute `swapped' for <signal>.
subscription-manager-gui is already running
Traceback (most recent call last):
File "/usr/sbin/subscription-manager-gui", line 108, in ?
show = bus.get_object(BUS_NAME, BUS_PATH).get_dbus_method('show_window')
File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 25, in __call__
ret = self._proxy_method (*args, **keywords)
File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 102, in __call__
reply_message = self._connection.send_with_reply_and_block(message, timeout)
File "dbus_bindings.pyx", line 455, in dbus_bindings.Connection.send_with_reply_and_block
dbus_bindings.DBusException: Message did not receive a reply (timeout by message bus)
[root@localhost ~]#
Verified in: subscription-manager-gnome-0.96.4-1.git.47.e65faae.el6.x86_64
it now does not open with the following message:
subscriptoin-manager-gui is already running
moving to VERIFIED.
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.
http://rhn.redhat.com/errata/RHBA-2011-1695.html
Description of problem: Version-Release number of selected component (if applicable): How reproducible: 3/3 Prerequisites: Client : Rhel5.7 client with following subscription-manager rpm subscription-manager-0.95.5.18-1.git.4.364aa10.el5 subscription-manager-gnome-0.95.5.18-1.git.4.364aa10.el5 subscription-manager-firstboot-0.95.5.18-1.git.4.364aa10.el5 Steps to repro : 1) Invoke subscription-manager-gui using “subscription-manager-gui” command executed on console1 2) Execute same command “subscriptio-manager-gui” on console2 Expected Result: Proper Message should display “ Subscription-manager is already running “ Actual Result : At step 2 Running subscription-manager gui got terminated Displayed following trace back on console (subscription-manager-gui:5318): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:5318): libglade-WARNING **: unknown attribute `swapped' for <signal>. subscription-manager-gui is already running Traceback (most recent call last): File "/usr/sbin/subscription-manager-gui", line 108, in ? show = bus.get_object(BUS_NAME, BUS_PATH).get_dbus_method('show_window') File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 25, in __call__ ret = self._proxy_method (*args, **keywords) File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 102, in __call__ reply_message = self._connection.send_with_reply_and_block(message, timeout) File "dbus_bindings.pyx", line 455, in dbus_bindings.Connection.send_with_reply_and_block dbus_bindings.DBusException: Message did not receive a reply (timeout by message bus) [root@localhost ~]#