Description of problem:
During the course of automated tests, the gui locks up completely and throws a traceback about dbus to the console.

Version-Release number of selected component (if applicable):
subscription-manager-1.10.3-1.git.1.4b7116f.el7.x86_64
subscription-manager-firstboot-1.10.3-1.git.1.4b7116f.el7.x86_64
python-rhsm-1.10.3-1.git.0.6ac2883.el7.x86_64
subscription-manager-migration-1.10.3-1.git.1.4b7116f.el7.x86_64
subscription-manager-migration-data-2.0.4-1.git.0.6bebf6f.el7.noarch
subscription-manager-gui-1.10.3-1.git.1.4b7116f.el7.x86_64


How reproducible:
??

Steps to Reproduce:
This happens during normal automated tests.  It is hard to see what reproduces it as it seems to happen randomly (or maybe with an async delay) during tests involving subscribing and closing the GUI with the 'X' button - which is to say most of the automated tests.


Actual results:
The GUI locks up and gnome asks me if I want to force quit or close the program.
Then to the console you get this traceback:

GTK Accessibility Module initialized
GTK Accessibility Module initialized
GTK Accessibility Module initialized

** (-c:11873): WARNING **: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.16 was not provided by any .service files

** (-c:11873): WARNING **: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.17 was not provided by any .service files
GTK Accessibility Module initialized

** (-c:11873): WARNING **: AT-SPI: Error in GetItems, sender=(null), error=Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ERROR:dbus.proxies:Introspect error on :1.74:/gui: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
subscription-manager-gui is already running
Traceback (most recent call last):
  File "/sbin/subscription-manager-gui", line 170, in <module>
    remote_object.show_window(dbus_interface=BUS_NAME)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


Expected results:
No taceback, no locking up of GUI.

Additional info:
In an attempt to debug this, I have set the class __init__ function in dbus_interface.py to simply return (thus disabling dbus).  This seems to avoid this lock up issue and automation runs successfully on tests that do not require dbus.