Description of problem: When I start subscription-manager-gui I got lots of warnings on stdout. Version-Release number of selected component (if applicable): subscription-manager-0.93.2-1.git.1.c76a8b0.el6.x86_64 How reproducible: always Steps to Reproduce: 1. run subscription-manager on rhel6 Actual results: [root@dri/~]# subscription-manager-gui (subscription-manager-gui:9196): libglade-WARNING **: Unexpected element <property> inside <widget>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. (subscription-manager-gui:9196): libglade-WARNING **: unknown attribute `swapped' for <signal>. Expected results: no errors
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
*** Bug 703643 has been marked as a duplicate of this bug. ***
Negative. We should care about warning. This is trivial issue. I will try to spend 10 minutes on this issue. However feel free to flip this bz to fedora or comunity version of subscription-manager. swapped attribute is not needed: http://stackoverflow.com/questions/7827310/how-do-i-fix-the-unknown-attribute-swapped-warnings-from-libglade
Created attachment 561505 [details] swapped patch patch fixing issue with (subscription-manager-gui:23411): libglade-WARNING **: unknown attribute `swapped' for <signal>.
problem with: (subscription-manager-gui:9196): libglade-WARNING **: Unexpected element <property> inside <widget>. is not present in current HEAD of git://git.fedorahosted.org/subscription-manager.git it is caused by tag <signal> which is in some .glade file present *before* <property> tag. And in glade order matters. First must be all instances of <property> and then <signal>. I tried to find such case, but did not find it within my timeframe I dedicated it for this BZ.
Applied in master at ff25f5c3354a83d407734b94dc63e54c12436630. Thank you for the patch!
Testing against version: subscription-manager-gnome-0.99.8-1.git.18.e98707c.el6.x86_64 ================================ [root@jmolet-vm0 ~]# subscription-manager-gui /usr/sbin/subscription-manager-gui:31: DeprecationWarning: The dbus_bindings module is not public API and will go away soon. Most uses of dbus_bindings are applications catching the exception dbus.dbus_bindings.DBusException. You should use dbus.DBusException instead (this is compatible with all dbus-python versions since 0.40.2). If you need additional public API, please contact the maintainers via <dbus.org>. import dbus.dbus_bindings /usr/share/rhsm/subscription_manager/gui/widgets.py:245: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed self.glade.get_widget(widget_prefix + "_text").destroy() ============ No 'libglade-WARNING's were displayed in the above invocation. Marking 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-2012-0804.html