Ubuntu
gjs package

gjs-console crashed with signal 5

Bug #1293772 reported by Stevie Card on 2014-03-17

This bug report is a duplicate of: Bug #1283551: gjs-console crashed with signal 5. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gjs (Ubuntu)	New	Undecided	Unassigned

Bug Description

Started up Steam

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gjs 1.39.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Mar 17 15:50:08 2014
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2014-02-17 (28 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ Main\ =\ imports.main;\ Main.start(); --no-default-window
ProcEnviron:
LD_LIBRARY_PATH=<set>
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 5
SourcePackage: gjs
StacktraceTop:
?? () from /usr/lib/libgjs.so.0
?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
Title: gjs-console crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Stevie Card (steveokard) wrote on 2014-03-17:

Dependencies.txt Edit (5.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-18: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1283551, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.