[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-04-01 Thread Albert Astals Cid
Adding qtubuntu-media since backtrace points to libaalmediaplayer.so ** Also affects: qtubuntu-media (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-04-01 Thread Michi Henning
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

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-03-07 Thread Michi Henning
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-03-07 Thread Michi Henning
Ah, sorry. I'm testing on Mako, and the 375 image was from ubuntu-touch /rc-proposed/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550137 Title: Crash loop with rc-proposed build 375 To

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-03-07 Thread Albert Astals Cid
@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. -- You received this bug

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-03-07 Thread Michi Henning
@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. -- You received this bug notification because you are a member of Ubuntu

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-03-04 Thread Michi Henning
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. -- You received this bug notification because

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-03-04 Thread MichaƂ Sawicz
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 -- You received this bug notification because you are a

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-03-04 Thread Albert Astals Cid
Image 375 of which channel exactly? Do you remember which image did you have previously installed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550137 Title: Crash loop with rc-proposed build 375

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-03-03 Thread Marcus Tomlinson
Adding unity8 as affected as this is a unity8-dash crash. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550137 Title:

[Bug 1550137] Re: Crash loop with rc-proposed build 375

2016-02-25 Thread Michi Henning
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