unity8 crashes when running ubuntu keyboard test

Bug #1492185 reported by Jonas G. Drange on 2015-09-04
18
This bug affects 2 people
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-touch/rc-proposed/meizu.en
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_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess

What happens:
unity8 crashes

What should happen:
unity8 should not crash

Related branches

Jonas G. Drange (jonas-drange) wrote :
Jonas G. Drange (jonas-drange) wrote :
Jonas G. Drange (jonas-drange) wrote :
description: updated

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"

Jonas G. Drange (jonas-drange) wrote :
Gerry Boland (gerboland) wrote :

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 :

Seems to be crashing in the scene graph renderer?

#0 0xb68c53ec in QSGOpaqueTextureMaterial::compare (this=0x23b9b00, o=0x23bf1d8) at scenegraph/util/qsgtexturematerial.cpp:295
#1 0xb68b3566 in QSGBatchRenderer::Renderer::prepareAlphaBatches (this=this@entry=0x15b8fd8) at scenegraph/coreapi/qsgbatchrenderer.cpp:1594
#2 0xb68baac4 in QSGBatchRenderer::Renderer::render (this=0x15b8fd8) at scenegraph/coreapi/qsgbatchrenderer.cpp:2544
#3 0xb68c1560 in QSGRenderer::renderScene (this=0x15b8fd8, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:206
#4 0xb68c18e8 in QSGRenderer::renderScene (this=<optimized out>, fboId=0) at scenegraph/coreapi/qsgrenderer.cpp:168
#5 0xb68cc2b4 in QSGRenderContext::renderNextFrame (this=0x1234498, renderer=0x15b8fd8, fboId=<optimized out>) at scenegraph/qsgcontext.cpp:554
#6 0xb68feab8 in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x12351b8, size=...) at items/qquickwindow.cpp:379
#7 0xb68df738 in QSGRenderThread::syncAndRender (this=this@entry=0x14f68a0) at scenegraph/qsgthreadedrenderloop.cpp:582
#8 0xb68e0908 in QSGRenderThread::run (this=0x14f68a0) at scenegraph/qsgthreadedrenderloop.cpp:663
#9 0xb63cf496 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#10 0xb6055490 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#11 0xb6216c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6

Gerry Boland (gerboland) wrote :

I assigned you Daniel as I recall we had this same issue last week with the welcome wizard

Bill Filler (bfiller) on 2015-09-04
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 :

@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 :

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?

kevin gunn (kgunn72) on 2015-09-23
Changed in qtmir:
status: Fix Released → New
Changed in qtmir:
status: New → In Progress
Daniel d'Andrada (dandrader) wrote :

- Flashed my mako with r248 (using "ubuntu-device-flash touch ubuntu-system --channel ubuntu-touch/rc-proposed/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_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess" in another terminal, 4 times in a row.

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 :

I've filed bug #1499388

kevin gunn (kgunn72) on 2015-09-29
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
Michał Sawicz (saviq) on 2017-03-13
affects: qtmir → qtmir (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers