gjs-console crashed with signal 5

[vlotho]

gilles@gilles-EP31-DS3L:~/u-boot-sunxi-xen/u-boot-sunxi-sunxi-next$ lsb_release -rd
Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10
gilles@gilles-EP31-DS3L:~/u-boot-sunxi-xen/u-boot-sunxi-sunxi-next$ apt-cache policy gjs
gjs:
  Installé : 1.41.3-0ubuntu1
  Candidat : 1.41.3-0ubuntu1
 Table de version :
 *** 1.41.3-0ubuntu1 0
        500 http://fr.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
        100 /var/lib/dpkg/status

i dont know the exact reasons of this crash ... I was trying to manipulate partitions, from the command line.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gjs 1.41.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
Uname: Linux 3.16.0-5-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jul 27 13:28:37 2014
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2014-04-05 (112 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.1)
ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ Main\ =\ imports.main;\ Main.start();
ProcEnviron:
 LD_LIBRARY_PATH=<set>
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.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 dialout dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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.