Re-enable non-visual component exporting in autopilot-qt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Autopilot |
Critical
|
Christopher Lee | ||
| | Autopilot Qt Support |
Critical
|
Christopher Lee | ||
Bug Description
It seems all autopilot tests so far seem to fail when run with Qt 5.2. The test app seems to be starting but eventually the failure happens as shown in the attached simple test log (Friends app).
You can upgrade the device to Qt 5.2 currently with the following instructions: http://
I filed bug #1273720 against unity8 already yesterday, but it seems all AP tests tend to fail, so it's not unity8 specific.
The PPA (https:/
All fixes should be made so that both Qt 5.0.2 and Qt 5.2 continue to work, ie usage of #ifdef:s or similar constructions.
| Timo Jyrinki (timo-jyrinki) wrote : | #1 |
| Timo Jyrinki (timo-jyrinki) wrote : | #3 |
| Timo Jyrinki (timo-jyrinki) wrote : | #4 |
Chris Lee had two quick thoughts on IRC:
"Is it perhaps an AppArmor issue? Looks like there is a dbus exception happening"
and
"Is it possible that in this new version Qt have removed the ability to load the testability driver? I know we had to patch something in at some stage, but I'm not sure of the specifics off the top of my head"
To the latter I'm able to answer that the load_testabilit
| description: | updated |
| Timo Jyrinki (timo-jyrinki) wrote : | #5 |
Christopher at it again. It seems https:/
| Changed in autopilot: | |
| assignee: | nobody → Christopher Lee (veebers) |
| Changed in autopilot: | |
| status: | New → Fix Released |
| Changed in autopilot-qt: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| assignee: | nobody → Christopher Lee (veebers) |
| summary: |
- autopilot/phablet-test-run does not seem to work with Qt 5.2 + Re-enable non-visual component exporting in autopilot-qt |
| Changed in autopilot-qt: | |
| status: | Confirmed → Fix Released |
| Thomi Richards (thomir) wrote : | #6 |
Hi,
This is not fixed, or released yet - The 5.2 issue works, but this bug is to track the status of exporting non-visual components from Qt.
| Changed in autopilot-qt: | |
| status: | Fix Released → Triaged |
| Pat McGowan (pat-mcgowan) wrote : | #7 |
Can we remove the qt5.2 tag then? Is it still critical?
| Changed in autopilot: | |
| status: | Fix Released → Confirmed |
| Florian Boucault (fboucault) wrote : | #9 |
Is this related to https:/

The binding loop problem seen in messaging app is on the UI Toolkit side, bug #1204453 bumped now to Critical because it affects Qt 5.2 more.