gnome-shell crashed with SIGSEGV in gjs_value_from_g_argument()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
New
|
Undecided
|
Unassigned |
Bug Description
don't know what is gong on, or, why today; but this is the third gnome-shell seize-up today! I am not sure that I know the sequence that causes it. It seems to take place when firefox and vlc are both active, but this combination has worked well in tandem for several months now....
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-shell 3.20.4-
ProcVersionSign
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Classic:GNOME
Date: Mon Apr 24 16:26:45 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/
GsettingsChanges:
b'org.gnome.shell' b'app-picker-view' b'uint32 1'
b'org.gnome.shell' b'favorite-apps' b"['ubiquity-
b'org.
b'org.
b'org.
InstallationDate: Installed on 2017-01-18 (95 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fa2a571a740 <gjs_value_
PC (0x7fa2a571a740) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
gjs_value_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in gjs_value_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1575621, 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.