gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This is on kernel 4.17.0-
Got it directly after boot.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.28.1-0ubuntu2
Uname: Linux 4.17.0-
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun May 27 08:17:00 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2017-05-15 (376 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f8fe339713e <___vsnprintf_
PC (0x7f8fe339713e) ok
source "$0x0" ok
destination "(%r12)" (0x00000000) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
___vsnprintf_chk (s=0x0, maxlen=<optimized out>, flags=1, slen=<optimized out>, format=
___snprintf_chk (s=<optimized out>, maxlen=<optimized out>, flags=<optimized out>, slen=<optimized out>, format=<optimized out>) at snprintf_chk.c:34
XauFileName () from /usr/lib/
XauGetBestAuth
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
UpgradeStatus: Upgraded to cosmic on 2018-04-29 (27 days ago)
UserGroups:
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 #1559650, 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.