1.) Install image #95
2.) Update qtubuntu-sensors to 0.1+14.10.20140624-0ubuntu1
3.) Run the autopilot test. You will see the following errors happen quickly:
10:48:20.537 ERROR proxies:410 - Introspect error on :1.140:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
10:48:20.539 DEBUG proxies:413 - Executing introspect queue due to error
10:48:20.551 INFO __init__:387 - dbus.DBusException while attempting to get PID for :1.139: DBusException("Could not get PID of name ':1.139': no such name",)
10:48:20.560 INFO __init__:387 - dbus.DBusException while attempting to get PID for :1.138: DBusException("Could not get PID of name ':1.138': no such name",)
10:48:21.565 INFO _launcher:368 - waiting for process to exit.
4.) Update ubuntu-application-api2-touch to 2.1.0+14.10.20140624.4-0ubuntu1
5.) Run the test again. The errors no longer appear, but the hang is now present.
So the bisect concludes:
1.) Install image #9510.20140624-0ubuntu1
2.) Update qtubuntu-sensors to 0.1+14.
3.) Run the autopilot test. You will see the following errors happen quickly:
10:48:20.537 ERROR proxies:410 - Introspect error on :1.140:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)"Could not get PID of name ':1.139': no such name",)"Could not get PID of name ':1.138': no such name",)
10:48:20.539 DEBUG proxies:413 - Executing introspect queue due to error
10:48:20.551 INFO __init__:387 - dbus.DBusException while attempting to get PID for :1.139: DBusException(
10:48:20.560 INFO __init__:387 - dbus.DBusException while attempting to get PID for :1.138: DBusException(
10:48:21.565 INFO _launcher:368 - waiting for process to exit.
4.) Update ubuntu-application-api2-touch to 2.1.0+14.10.20140624.4-0ubuntu1
5.) Run the test again. The errors no longer appear, but the hang is now present.