Crash loop with rc-proposed build 375

Bug #1550137 reported by Michi Henning
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qtubuntu-media (Ubuntu)
New
Undecided
Unassigned
unity-scopes-shell (Ubuntu)
New
Undecided
Unassigned
unity8 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

I just flashed 375 from rc-proposed. After the reboot, the shell is stuck in a crash loop. After unlocking, the shell briefly appears with the main click scope page showing and the activity bar at the bottom bouncing left/right. Then the crash, back to the spinner in the center of the screen ("Scope"), back to the main page, bottom bar bouncing, crash, ad infinitum.

Crash dump attached.

After rebooting, the crash loop stopped.

Revision history for this message
Michi Henning (michihenning) wrote :
Revision history for this message
Michi Henning (michihenning) wrote :

After I restarted, and the crash loop went away, I installed some updates from silo 75 (not related to the crash). I used citrain device-upgrade. After the reboot, the crash loop was back. Then I re-started, and the crash loop disappeared again.

It's starting to look like that the crash appears on the first boot after an update and, thereafter, goes away?

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

Adding unity8 as affected as this is a unity8-dash crash.

Revision history for this message
Albert Astals Cid (aacid) wrote :

Image 375 of which channel exactly? Do you remember which image did you have previously installed?

Revision history for this message
Michał Sawicz (saviq) wrote :

The dash crash (unity8 died so it lost connection) will likely be a red herring, can you please clear /var/crash and reproduce it again to see that you get a unity8 crash?

Changed in unity8 (Ubuntu):
status: New → Incomplete
Revision history for this message
Michi Henning (michihenning) wrote :

Will try that on Monday. (I left the phone at the office.)

I've seen it more than once now, with images other than 375. In all cases, the crash loop happens after the first restart after flashing and goes away for the second and subsequent restarts.

Revision history for this message
Michi Henning (michihenning) wrote :

@albert: It was from rc-proposed. I'm not sure about the previous image, but it likely would have been either 370 or 372. (That's from memory, I'm afraid.)

I'm sorry, I forget to re-test this today. Will do so tomorrow.

Revision history for this message
Albert Astals Cid (aacid) wrote :

@michi: when saying rc-proposed it's better if you say it is ubuntu-touch/rc-proposed/ubuntu or ubuntu-touch/rc-proposed/bq-aquaris.en or a different channel, also since the image number is phone dependant in some cases also helps if you say which phone you're using.

Revision history for this message
Michi Henning (michihenning) wrote :

Ah, sorry. I'm testing on Mako, and the 375 image was from ubuntu-touch/rc-proposed/ubuntu

Revision history for this message
Michi Henning (michihenning) wrote :

After downgrading to r375 (mako, rc-proposed), I'm getting the crash loop again. Rebooting fixes the problem.

I then upgraded to r382, and the problem is gone. Whatever this was, it looks like it's gone away.

Revision history for this message
Michi Henning (michihenning) wrote :

Crash loop is back. I just flashed from r382 to r408:

$ system-image-cli -i
current build number: 408
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2016-04-01 16:39:11
version version: 408
version ubuntu: 20160401
version device: 20160329
version custom: 20160401

Now the crash loop is happening again. I'm attaching the crash dump and the unity8 and unity8-dash logs. I checked the registry log, and it shows nothing unusual.

As before, after a reboot, things work as expected again.

Revision history for this message
Albert Astals Cid (aacid) wrote :

Adding qtubuntu-media since backtrace points to libaalmediaplayer.so

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.