gjs-console crashed with SIGSEGV

[nick]

on login

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gjs 1.39.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CurrentDesktop: GNOME
Date: Thu Mar 6 10:00:00 2014
Disassembly: => 0xb679e627: Cannot access memory at address 0xb679e627
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2014-02-17 (16 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140217)
ProcCmdline: /usr/bin/gjs /usr/share/org.gnome.Weather.Application/org.gnome.Weather.Application
SegvAnalysis:
 Segfault happened at: 0xb679e627: Cannot access memory at address 0xb679e627
 PC (0xb679e627) ok
 SP (0xbfeaf9f0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: gjs
Stacktrace:
 #0 0xb679e627 in ?? ()
 No symbol table info available.
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()
Title: gjs-console crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Stacktrace:
 #0 0xb679e627 in ?? ()
 No symbol table info available.
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0 0xb679e627 in ?? ()
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alberto Salvia Novella (es20490446e)]

It renders essential functionality of the package (or a dependent one) broken.

[Shu Hung (Koala) (koalay)]

The problem also exists in 64bit version. I encountered this issue numerous time on my Ubuntu 14.04 64bit version installation.

[Tim Lunn (darkxst)]

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!