DBus Exception NoReply when running Telegram autopilot Logout test case on BQ Aquaris M10

Bug #1634097 reported by Paz Chauhan on 2016-10-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description


I am executing the following autopilot test case:


On a BQ Aquaris M10 tablet and it fails with the Traceback below.

** NOTE: The testcase passes fine on a BQ Aquaris E4.5 device and the desktop.

Desktop OS: Ubuntu 16.04
Branch: bzr branch lp:~cellsoftware/telegram-app/autopilotTest-3
M10 Tablet OS: Ubuntu 15.04 (OTA-13)
E4.5 phone OS: Ubuntu 15.04 (OTA-12)

Traceback (most recent call last):
  File "/opt/click.ubuntu.com/com.ubuntu.telegram/", line 48, in test_UserLogout
    logout_confirm_dialog = self.app.wait_select_single(objectName='logoutDialog')
  File "/usr/lib/python3/dist-packages/autopilot/introspection/dbus.py", line 366, in wait_select_single
    return self._select_single(type_name, **kwargs)
  File "/usr/lib/python3/dist-packages/autopilot/introspection/dbus.py", line 266, in _select_single
    instances = self._select(type_name_str, **kwargs)
  File "/usr/lib/python3/dist-packages/autopilot/introspection/dbus.py", line 258, in _select
    return self._execute_query(new_query)
  File "/usr/lib/python3/dist-packages/autopilot/introspection/dbus.py", line 91, in _execute_query
    getattr(self, '_id', None),
  File "/usr/lib/python3/dist-packages/autopilot/introspection/backends.py", line 250, in execute_query_get_proxy_instances
    data = self.execute_query_get_data(query)
  File "/usr/lib/python3/dist-packages/autopilot/introspection/backends.py", line 226, in execute_query_get_data
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

The problem lies when trying to interact with a Popup.Dialog with an object name set to 'logoutDialog'

Omer Akram (om26er) wrote :

My initial conviction was that you need to select the root object but it seems that you already are selecting on the root `app` instance. Can you please tell if the same bug is reproducible on desktop as well ? So that I can actually try to reproduce the issue ?

Paz Chauhan (paz-chauhan) wrote :

Hi Omer,
Thanks for looking into this. Unfortunately, this bug was not reproducible on desktop. Only on the BQ M10 tablet.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers