unity8 crashes when running ubuntu keyboard test
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Canonical System Image |
High
|
kevin gunn | ||
| | qtmir (Ubuntu) |
Critical
|
Daniel d'Andrada | ||
Bug Description
current build number: 105
device name: arale
channel: ubuntu-
last update: 2015-09-04 11:06:40
version version: 105
version ubuntu: 20150904
version device: 20150818-0b38025
version custom: 20150814-887-8-46
(extact same failure on mako, same rc-proposed image)
Reproduce:
phablet-test-run -v ubuntu_
What happens:
unity8 crashes
What should happen:
unity8 should not crash
Related branches
- Gerry Boland: Approve on 2015-09-07
- PS Jenkins bot: Needs Fixing (continuous-integration) on 2015-09-04
-
Diff: 11 lines (+2/-0)1 file modifiedsrc/modules/Unity/Application/mirsurfaceitem.cpp (+2/-0)
| Jonas G. Drange (jonas-drange) wrote : | #1 |
| Jonas G. Drange (jonas-drange) wrote : | #2 |
| Michael Sheldon (michael-sheldon) wrote : | #4 |
| Michael Sheldon (michael-sheldon) wrote : | #5 |
| Jonas G. Drange (jonas-drange) wrote : | #6 |
| Gerry Boland (gerboland) wrote : | #7 |
Shell rejecting OSK's re-connection attempts, which is wrong. It shouldn't also crash...
| Changed in unity8 (Ubuntu): | |
| importance: | Undecided → Critical |
| assignee: | nobody → Daniel d'Andrada (dandrader) |
| status: | New → Triaged |
| Changed in qtmir: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| assignee: | nobody → Daniel d'Andrada (dandrader) |
| Albert Astals Cid (aacid) wrote : | #8 |
Seems to be crashing in the scene graph renderer?
#0 0xb68c53ec in QSGOpaqueTextur
#1 0xb68b3566 in QSGBatchRendere
#2 0xb68baac4 in QSGBatchRendere
#3 0xb68c1560 in QSGRenderer:
#4 0xb68c18e8 in QSGRenderer:
#5 0xb68cc2b4 in QSGRenderContex
#6 0xb68feab8 in QQuickWindowPri
#7 0xb68df738 in QSGRenderThread
#8 0xb68e0908 in QSGRenderThread
#9 0xb63cf496 in ?? () from /usr/lib/
#10 0xb6055490 in start_thread () from /lib/arm-
#11 0xb6216c4c in ?? () from /lib/arm-
| Gerry Boland (gerboland) wrote : | #9 |
I assigned you Daniel as I recall we had this same issue last week with the welcome wizard
| Changed in canonical-devices-system-image: | |
| milestone: | none → ww40-2015 |
| assignee: | nobody → kevin gunn (kgunn72) |
| importance: | Undecided → High |
| Changed in qtmir: | |
| status: | Triaged → In Progress |
| Changed in unity8 (Ubuntu): | |
| status: | Triaged → In Progress |
| Daniel d'Andrada (dandrader) wrote : | #10 |
@michael-sheldon
Thanks a lot for comment #4. Saved me a lot of time.
| Changed in unity8 (Ubuntu): | |
| status: | In Progress → Invalid |
| Changed in canonical-devices-system-image: | |
| status: | New → Confirmed |
| Changed in qtmir: | |
| status: | In Progress → Fix Released |
| no longer affects: | unity8 (Ubuntu) |
| dobey (dobey) wrote : | #11 |
I am still seeing a crash in unity8 with the stack trace similar to what's in comment #8 here. Do we need to open a separate bug for that crash?
| Changed in qtmir: | |
| status: | Fix Released → New |
| Changed in qtmir: | |
| status: | New → In Progress |
| Daniel d'Andrada (dandrader) wrote : | #12 |
- Flashed my mako with r248 (using "ubuntu-
- Unlocked the phone and had in a ssh terminal "powerd-cli display on"
- did "sudo gdb -p $(pidof unity8)" in another ssh terminal and resumed unity8 with "cont"
- Run "phablet-test-run -v ubuntu_
Didn't get any crash.
Therefore I consider this bug as indeed fixed.
dobey, if you're still getting similar crashes please file a new bug with the exact steps and preconditions to reproduce the issue. It's likely a different, but similar, bug.
| Changed in qtmir: | |
| status: | In Progress → Fix Released |
| dobey (dobey) wrote : | #13 |
I've filed bug #1499388
| Changed in canonical-devices-system-image: | |
| status: | Confirmed → Fix Released |
| status: | Fix Released → Fix Committed |
| Changed in canonical-devices-system-image: | |
| status: | Fix Committed → Fix Released |
| affects: | qtmir → qtmir (Ubuntu) |


The actual trigger appears to be when maliit restarts (which the tests do to enable extra introspection), so this can be reproduced by simply running "restart maliit-server"