Comment 0 for bug 1103751

Using the autopilot launch tool in conjunction with autopilot vis fails for some common desktop applications.

1) Running autopilot launch XXXX, gives 'No handlers could be found for logger "autopilot.introspection"'. This always occurs.

2) Running autopilot launch and one of the below applications causes a 'RuntimeError: Unable to find Autopilot interface.' error.
 gnome-terminal
 geany
 skype
 xchat
       nautilus
      gnumeric

3) Running autopilot launch for firefox (using '/usr/lib/firefox/firefox') fails with the following error: Error: Could not determine introspection type to use for application .

4) Running autopilot launch for vlc (using 'autopilot launch '/usr/bin/vlc') fails with the following error: Error: Could not determine introspection type to use for application .Is passing command line options to the binary to run support? (eg, vlc -I qt4)

5) Running autopilot launch gcalctool, autopilot vis results in this crash after selecting the connection in the vs tool.

Tons of things like:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.818 was not provided by any .service files
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 96, in apport_excepthook
    dbus_service_unknown_analysis(exc_obj, pr)
  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 172, in dbus_service_unknown_analysis
    cp = ConfigParser(interpolation=None)
TypeError: __init__() got an unexpected keyword argument 'interpolation'
 gcalctool