Red Hat Bugzilla – Bug 1336428
rhsm-icon -i fails with libnotify-CRITICAL and GLib-GObject-CRITICAL errors
Last modified: 2016-11-03 16:29:05 EDT
Description of problem: Version-Release number of selected component (if applicable): subscription-manager: 1.17.5-1.el7 python-rhsm: 1.17.2-1.el7 How reproducible: 3/3 Steps to Reproduce: 1.execute rhsm-icon -i 2.wait for the icon 3. Actual results: Observed the error message, and icon never appeared # rhsm-icon -i (rhsm-icon:5420): libnotify-CRITICAL **: notify_notification_close: assertion 'NOTIFY_IS_NOTIFICATION (notification)' failed (rhsm-icon:5420): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (rhsm-icon:5420): libnotify-CRITICAL **: notify_notification_close: assertion 'NOTIFY_IS_NOTIFICATION (notification)' failed (rhsm-icon:5420): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Expected results: rhsm-icon should pop-up Additional info:
Update, the same behaviour is observed with rhsm -c option as well. Basically the icon is not appearing and observed the same error on cli
Another case has been found that seems to match this issue exactly - logs can be provided upon request. The problem seems very simple to reproduce and any information needed should be able to be provided by the case attached.
Still not able to reproduce locally. SOS report attached to support does not show any rhsm specific issues. If it happens again, it would be a good idea to get in touch with the dbus folks to determine if they are seeing a hiccup in versions of RHEL. Those errors are not caused by Sub Man, but are shown when Sub Man tries to use dbus.
Extraordinarily easy to reproduce the error with subscription-manager-gui, even on a VM, with the desktop. Need to have active registrations or it does nothing.
In the RH ticket 01675022 This is trivial to reproduce and can be done on a VM. I would think that this can be worked independently of any customer data. 1. Install 7.2 2. Login to graphical desktop 3. subscription-manager-gui from shell or gnome. 4. Look at journalctl output
Very simple, extraordinarily easy, and trivial PR at https://github.com/candlepin/subscription-manager/pull/1466
That looks good. What I am not sure of is what the interval is that rhsm-icon uses. The man page says every 4 hours, but is that from when it is started, or based on some absolute value based on wall clock? If the latter, could explain part of difficulty in reproducing.
The reproducer is that the system must be registered and fully compliant for the issue to surface.
Reproducer with the version: [root@dhcp35-25 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.9.51.15-1 subscription management rules: 5.15.1 subscription-manager: 1.17.10-1.el7 python-rhsm: 1.17.6-1.el7 [root@dhcp35-25 ~]# rhsm-icon -i (rhsm-icon:6753): libnotify-CRITICAL **: notify_notification_close: assertion 'NOTIFY_IS_NOTIFICATION (notification)' failed (rhsm-icon:6753): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (rhsm-icon:6753): libnotify-CRITICAL **: notify_notification_close: assertion 'NOTIFY_IS_NOTIFICATION (notification)' failed (rhsm-icon:6753):
No error message is seen with following version: [root@dhcp35-25 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.9.51.15-1 subscription management rules: 5.15.1 subscription-manager: 1.17.11-1.el7 python-rhsm: 1.17.7-1.el7 No error message in journalctl Aug 30 14:19:08 dhcp35-25.lab.eng.blr.redhat.com dbus[668]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Aug 30 14:19:08 dhcp35-25.lab.eng.blr.redhat.com dbus-daemon[668]: dbus[668]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Aug 30 14:19:08 dhcp35-25.lab.eng.blr.redhat.com dbus[668]: [system] Successfully activated service 'org.freedesktop.problems' Aug 30 14:19:08 dhcp35-25.lab.eng.blr.redhat.com dbus-daemon[668]: dbus[668]: [system] Successfully activated service 'org.freedesktop.problems' Aug 30 14:19:23 dhcp35-25.lab.eng.blr.redhat.com systemd[1]: Starting Cleanup of Temporary Directories... Aug 30 14:19:23 dhcp35-25.lab.eng.blr.redhat.com systemd[1]: Started Cleanup of Temporary Directories. Aug 30 14:20:01 dhcp35-25.lab.eng.blr.redhat.com systemd[1]: Started Session 4 of user root. Aug 30 14:20:01 dhcp35-25.lab.eng.blr.redhat.com systemd[1]: Starting Session 4 of user root. Aug 30 14:20:01 dhcp35-25.lab.eng.blr.redhat.com CROND[3885]: (root) CMD (/usr/lib64/sa/sa1 1 1)
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