| 2014-02-05 18:42:54 |
Omer Akram |
bug |
|
|
added bug |
| 2014-02-05 18:42:54 |
Omer Akram |
attachment added |
|
unity8_dbus_hang.py https://bugs.launchpad.net/bugs/1276747/+attachment/3970251/+files/unity8_dbus_hang.py |
|
| 2014-02-05 18:55:15 |
Omer Akram |
summary |
after starting dialer-app cannot get proxy object for unity8 |
after starting a new app cannot get proxy object for unity8 |
|
| 2014-02-05 18:56:38 |
Omer Akram |
description |
The title sounds weird, right ?
I am writing integration tests that make sure tapping on the OSD 'accept' button opens the dialer app (more similar tests as well). The problem is that my tests run fine for the first time, but if try to run the test the second time it fails because it seems that after dialer-app is started I cannot get autopilot interface for unity8.
To reproduce this problem
1. Ensure unity8 is running with the testability driver:
stop unity8 ; initctl set-env QT_LOAD_TESTABILITY=1 ; start unity8
2. Download the attached python script
3. push it to the phone's /home/phablet
4. run it and it will print the unity8' Notification object
5. Now start the dialer-app (keep it open or close it)
6. execute the python script again |
I am writing integration tests that make sure tapping on the OSD 'accept' button opens the dialer app (more similar tests as well). The problem is that my tests run fine for the first time, but if try to run the test the second time it fails because it seems that after dialer-app is started I cannot get autopilot interface for unity8.
To reproduce this problem
1. Ensure unity8 is running with the testability driver:
stop unity8 ; initctl set-env QT_LOAD_TESTABILITY=1 ; start unity8
2. Download the attached python script
3. push it to the phone's /home/phablet
4. run it and it will print the unity8' Notification object
5. Now start the any random app (keep it open or close it)
6. execute the python script again
You will see the below error and after a wait of many seconds the Notification object will indeed be printed
ERROR:dbus.proxies:Introspect error on :1.604:/com/canonical/Autopilot/Introspection: 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.
<autopilot.introspection.dbus.Notification object at 0x1c32c90> |
|
| 2014-02-05 18:56:46 |
Omer Akram |
affects |
dialer-app |
unity8 |
|
| 2014-02-05 19:06:16 |
Michał Sawicz |
bug task added |
|
autopilot (Ubuntu) |
|
| 2014-02-05 19:15:28 |
Omer Akram |
description |
I am writing integration tests that make sure tapping on the OSD 'accept' button opens the dialer app (more similar tests as well). The problem is that my tests run fine for the first time, but if try to run the test the second time it fails because it seems that after dialer-app is started I cannot get autopilot interface for unity8.
To reproduce this problem
1. Ensure unity8 is running with the testability driver:
stop unity8 ; initctl set-env QT_LOAD_TESTABILITY=1 ; start unity8
2. Download the attached python script
3. push it to the phone's /home/phablet
4. run it and it will print the unity8' Notification object
5. Now start the any random app (keep it open or close it)
6. execute the python script again
You will see the below error and after a wait of many seconds the Notification object will indeed be printed
ERROR:dbus.proxies:Introspect error on :1.604:/com/canonical/Autopilot/Introspection: 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.
<autopilot.introspection.dbus.Notification object at 0x1c32c90> |
I am writing integration tests that make sure tapping on the OSD 'accept' button opens the dialer app (more similar tests as well). The problem is that my tests run fine for the first time, but if try to run the test the second time it fails because it seems that after dialer-app is started I cannot get autopilot interface for unity8.
To reproduce this problem
1. Ensure unity8 is running with the testability driver:
stop unity8 ; initctl set-env QT_LOAD_TESTABILITY=1 ; start unity8
2. Download the attached python script
3. push it to the phone's /home/phablet
4. run it and it will print the unity8' Notification object
5. Now start any random app (keep it open or close it)
6. execute the python script again
You will see the below error and after a wait of many seconds the Notification object will indeed be printed
ERROR:dbus.proxies:Introspect error on :1.604:/com/canonical/Autopilot/Introspection: 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.
<autopilot.introspection.dbus.Notification object at 0x1c32c90> |
|
| 2014-02-07 02:20:25 |
Thomi Richards |
autopilot (Ubuntu): status |
New |
Triaged |
|
| 2014-02-07 02:20:27 |
Thomi Richards |
autopilot (Ubuntu): importance |
Undecided |
Low |
|
| 2014-02-09 22:18:17 |
Thomi Richards |
autopilot (Ubuntu): status |
Triaged |
Incomplete |
|
| 2014-02-21 16:32:40 |
Thomi Richards |
autopilot (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2014-02-21 16:32:43 |
Thomi Richards |
autopilot (Ubuntu): importance |
Low |
High |
|
| 2014-09-04 21:59:00 |
kevin gunn |
bug task deleted |
unity8 |
|
|
| 2014-09-04 21:59:07 |
kevin gunn |
unity8 (Ubuntu): status |
New |
Opinion |
|
| 2014-09-05 08:03:57 |
Michał Sawicz |
unity8 (Ubuntu): status |
Opinion |
Invalid |
|
