gnome-shell crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Occurred on a fully up-to-date Zesty, Ubuntu Gnome. Several windows were open, and it happened shortly after starting indexing with Recoll. Gnome-shell finally managed to recover or respawn.
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-shell 3.24.0-0ubuntu2
ProcVersionSign
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 9 18:04:06 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-03-31 (8 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170330)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f5b28e430a5: testb $0x1,(%rax)
PC (0x7f5b28e430a5) ok
source "$0x1" ok
destination "(%rax)" (0x7f5a9ebfffe8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/
g_main_
() at /lib/x86_
g_main_loop_run () at /lib/x86_
meta_run () at /usr/lib/
Title: gnome-shell crashed with SIGSEGV
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 #1665883, 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.