Hide Forgot
Description of problem: When you kickstart a fresh 5.7 install off of porkchop, the rhsm-compliance-icon isn't running. You have to start it up yourself. Version-Release number of selected component (if applicable): 0.95.5.5 Steps to Reproduce: 1. kick a new 5.7 vm 2. look for rhsm-compliance-icon 3. Actual results: rhsm-compliance-icon is not running Expected results: rhsm-compliance-icon should be running
We were getting a failed assertion in the dbus code. One of our proxies got into a bad state where it was created, but not marked as being associated with a backing dbus connection. When dbus signaled our app that the owner of the com.redhat.SubscriptionManager endpoint changed (probably due to dbus activation), this unassociated proxy was noticed by dbus, and the assertion failed, crashing the app. This happens predictably for the first few times you log in, then stops. Though I'm not sure why. I've got a change to use only one dbus proxy. This seems to fix the issue.
Verified using following setup : subscription-manager-gnome-0.95.5.18-1.git.0.490e92f.el5 subscription-manager-0.95.5.18-1.git.0.490e92f.el5 subscription-manager-firstboot-0.95.5.18-1.git.0.490e92f.el5 Working fine Moving defect status from modified to verified
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-1078.html