Spotted in several autopilot logs, such as http://10.97.0.1:8080/job/saucy-touch-mako-smoke-phone-app-autopilot/10/console:
Jul 18 09:24:11 ubuntu-phablet utah: Running command: utah-autopilot run -v phone_app.tests.test_call_panel.TestCallPanel.test_keypad
Jul 18 09:24:12 ubuntu-phablet utah: Loading tests from: /usr/lib/python2.7/dist-packages#012
Jul 18 09:24:12 ubuntu-phablet utah: 09:24:12.227 ERROR importer:51 - Could not find any typelib for Gdk
Jul 18 09:24:12 ubuntu-phablet kernel: [ 98.286006] input: autopilot-finger as /devices/virtual/input/input6
Jul 18 09:24:12 ubuntu-phablet utah: 09:24:12.391 INFO globals:49 - ************************************************************
Jul 18 09:24:12 ubuntu-phablet utah: 09:24:12.392 INFO globals:50 - Starting test phone_app.tests.test_call_panel.TestCallPanel.test_keypad (with touch)
I. e. the "ERROR importer:51 - Could not find any typelib for Gdk". It seems it is mostly harmless, but it looks odd in logs. This seems to come from http://bazaar.launchpad.net/~autopilot/autopilot/trunk/view/head:/autopilot/display/_X11.py
If this is ok to ignore, I suggest catching the ImportError there and outputting a warning (if there is reduced functionality).
If this is important functionality, I suggest that autopilot should grow a dependency to python-gi and gir1.2-gtk-3.0. Alternatively this could also drop the usage of Gdk and instead just query xrandr.
"ERROR importer:51 - Could not find any typelib for Gdk" is expected on the phone, it's first looking for the _x11 backend, when that doesn't work it looks for the ubuntu platform api backend and uses that.