gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Bug #1773622 reported by Per-Inge on 2018-05-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)

Bug Description

This is on kernel 4.17.0-041700rc6-generic x86_64.
Got it directly after boot.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.28.1-0ubuntu2
Uname: Linux 4.17.0-041700rc6-generic x86_64
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun May 27 08:17:00 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell

InstallationDate: Installed on 2017-05-15 (376 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
 Segfault happened at: 0x7f8fe339713e <___vsnprintf_chk+126>: movb $0x0,(%r12)
 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
 ___vsnprintf_chk (s=0x0, maxlen=<optimized out>, flags=1, slen=<optimized out>, format=0x7f8fd2eefae5 "%s%s", args=args@entry=0x7f8f93d54d00) at vsnprintf_chk.c:55
 ___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/x86_64-linux-gnu/
 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
UpgradeStatus: Upgraded to cosmic on 2018-04-29 (27 days ago)

Per-Inge (per-inge-hallin) wrote :

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers