autopilot vis logs connection problem, but does not tell which application is causing it

[Daniel Kessel]

I ran autopilot vis to check which applications can be inspected by it. It found "Unity" and I can inspect it. I am running the current daily PPA version.

However, it also logs DBusExceptions which look like there is another application (which is not responding as expected).

It should log the name of the non-responding application, or maybe list it as "non-inspectable application", if possible.
Console output:

ERROR:dbus.proxies:Introspect error on :1.94:/: 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.

[Thomi Richards (thomir-deactivatedaccount)]

Hi Daniel,

Thanks for reporting this bug, and thanks for using autopilot. We're aware that AP is a bit rough around the edges in a few places.

This error message is actually generated by the dbus library, rather than autopilot. However, I'm not able to reproduce. In any case, it's unlikely that this is an actual problem. Autopilot scans dbus when you launch the vis tool, and some processes don't like being poked at.

I'll look into this if I manage to reproduce it. In the mean time, feel free to contact me on IRC.