gnome-shell crashed with SIGSEGV

Bug #1291553 reported by Andy Bach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

No idea what's up - I'm in gdm but I'm on my 4th error.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Wed Mar 12 13:02:51 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

ProcCmdline: gnome-shell --mode=gdm
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x9a1db80: add %eax,(%eax)
 PC (0x09a1db80) in non-executable VMA region: 0x097d4000-0x0a0ba000 rw-p [heap]
 source "%eax" ok
 destination "(%eax)" (0x0a0aa150) ok
 Stack memory exhausted (SP below stack segment)
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0 0x09a1db80 in ?? ()
 No symbol table info available.
 #1 0xb1b03c28 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-02-14 (25 days ago)
UserGroups:

Revision history for this message
Andy Bach (afbach) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x09a1db80 in ?? ()
 No symbol table info available.
 #1 0xb1b03c28 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceSource:
 #0 0x09a1db80 in ?? ()
 #1 0xb1b03c28 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Changed in gnome-shell (Ubuntu):
status: New → Invalid
Revision history for this message
Andy Bach (afbach) wrote : Re: [Bug 1291553] Re: gnome-shell crashed with SIGSEGV

On Wed, May 17, 2017 at 2:54 AM, Daniel van Vugt <
<email address hidden>> wrote:

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1291553
>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
bug/1291553/+subscriptions

Both links, 404, I don't recall submitting this and if I did, it certainly
wasn't recently.

--

a

Andy Bach,
<email address hidden>
608 658-1890 cell
608 261-5738 wk

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Bug 1291553 was private until just now. I removed your core dump and it is now public, so the links should work today without needing to log in.

Otherwise, you can access your own private bugs by logging in to Launchpad.

information type: Private → Public
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.