after starting a new app cannot get proxy object for unity8
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopilot (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
unity8 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug 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_
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.
<autopilot.
summary: |
- after starting dialer-app cannot get proxy object for unity8 + after starting a new app cannot get proxy object for unity8 |
description: | updated |
affects: | dialer-app → unity8 |
description: | updated |
Changed in autopilot (Ubuntu): | |
status: | Triaged → Incomplete |
Changed in autopilot (Ubuntu): | |
status: | Incomplete → Confirmed |
importance: | Low → High |
no longer affects: | unity8 |
Changed in unity8 (Ubuntu): | |
status: | New → Opinion |
Changed in unity8 (Ubuntu): | |
status: | Opinion → Invalid |
Hi,
I'm able to reproduce the delay, but you get a proxy object in the end, so I'm not sure what the problem is here. Is it just that things take a bit longer?
We can take a look at why it's taking longer, but unless this is critical, I doubt we'll get to it in the next few days.