On Wed, Jun 25, 2014 at 02:30:28PM +0200, Oliver Grawert wrote:
> > > 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.

By whom?

The Foundations team is aware of issues regarding backtracing on armhf. 
None of them involve any discrepancies in libstdc++.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slanga...@ubuntu.com                                     vor...@debian.org

Attachment: signature.asc
Description: Digital signature

-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to     : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Reply via email to