Image #94 on mako / #88 on flo fails to start - mir crash

Bug #1382278 reported by Alan Pope 🍺🐧🐱 🦄
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
android (Ubuntu RTM)
Fix Released
Undecided
Unassigned
qtmir (Ubuntu)
Invalid
Undecided
Unassigned
unity8 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Update from #93 to #94 and I get the constant ubuntu spinning logo.
adb shell to device and find unity8, maliit and unity8-dash dying, this is in their logs.

Reverting to #93 'fixes' it, and going forward to #94 breaks it again.

FATAL: UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is
running, and the correct socket is being used and is accessible. The shell may have
rejected the incoming connection, so check its log file

summary: - Image #94 on mako/flo fails to start - mir crash
+ Image #94 on mako / #88 on flo fails to start - mir crash
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in qtmir (Ubuntu):
status: New → Confirmed
Changed in unity8 (Ubuntu):
status: New → Confirmed
Revision history for this message
David Planella (dpm) wrote :

Same applies to image #95

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Same on #95, and also after --bootstrap. My crashes on #95 after the --bootstrap wipe are as follows. I tried a local backtracing but for some reason it's failing to find ExecutablePath for all of them, so I sent them now to Launchpad:

ubuntu-system-settings: LP: #1382373
media-hub LP: #1382375
mtp-server LP: #1382376

Revision history for this message
Oliver Grawert (ogra) wrote :

qtmir was changed in image #93 (which translates to rtm krillin image 111)

image #94 maps to krillin rtm 112 for which the change set is at http://people.canonical.com/~ogra/touch-image-stats/rtm/112.changes ... note that the libhybris change in there required a change on the android side, i assume this bit was forgotten for mako.

affects: libhybris (Ubuntu) → libhybris (Ubuntu RTM)
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

I've tried reverting libhybris, media-hub and qmenumodel landings, but reverting those to the #93 versions doesn't seem to help.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Reverting to the following media-hub packages seems to help:

libmedia-hub-client2_2.0.0+14.10.20141015-0ubuntu1_armhf.deb
libmedia-hub-common2_2.0.0+14.10.20141015-0ubuntu1_armhf.deb
media-hub_2.0.0+14.10.20141015-0ubuntu1_armhf.deb

Upgrading those back breaks the boot.

libhybris revert was actually not needed, even though I did that first.

Revision history for this message
Benoit C. Barret (benbugohit) wrote :

affected #96 too, with unity8.

Logs showed "media-hub respawn" loop

media-hub downgrade as stated by Timo confirmed to work.
=> regression ?

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Fixed after rebuilding android against latest libhybris.

affects: libhybris (Ubuntu RTM) → android (Ubuntu RTM)
Changed in android (Ubuntu RTM):
status: New → Fix Released
Changed in qtmir (Ubuntu):
status: Confirmed → Invalid
Changed in unity8 (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.