ubuntu-phone team mailing list archive

[Oliver Grawert <ogra@xxxxxxxxxx>]

hi,
Am Mittwoch, den 25.06.2014, 07:00 -0500 schrieb Jamie Strandboge:
> On 06/25/2014 02:21 AM, Oliver Grawert wrote:
> > hi,
> > Am Dienstag, den 24.06.2014, 23:44 -0500 schrieb Victor Thompson:
> >> I've been experiencing frequent reboots, or what I assume are reboots,
> >> while using both my mako and flo devices. While navigating the dash or
> >> waiting for an app to load, frequently the devices will hang a bit and
> >> will then quickly go into the rotating Ubuntu logo "boot
> >> animation" (smaller one without the line/progress bar under it). This
> >> also finishes almost immediately. I don't see the Google splash screen
> >> or anything else. So while I assume the device is rebooting, it does
> >> so far more quickly than usual. Does anyone else see this? Is it
> >> documented anywhere?
> 
> This has been an issue for me for a little while. I'm on 87 now and I think it
> was (at least) two promoted images before that. I can't figure out the exact
> cause so I haven't filed a bug.
this is strange, i run 87 since we have promoted it and it is rock solid
for me ... 

> 
> > if you do not see the google logo it is not rebooting. the symptoms look
> > rather like either lightdm or Mir is crashing, have a look in /var/crash
> > if there are any crash files collected.
> > 
> 
> I sometimes see the google logo and sometimes do not. I have a bunch of crash
> files in /var/crash and I just used /usr/share/apport/whoopsie-upload-all on.
> 
> That said, I've heard all kinds of things from non-authoritative sources about
> these crash reports lately from them not being properly sent to the armhf ones
> not being useful. Can someone set the record straight on this?
> 
the current crash files are useless due to a discrepancy between libstdc
++ and gdb so the generated backtraces will be broken ... this is being
worked on.

ciao
	oli

Attachment: signature.asc
Description: This is a digitally signed message part