gnome-control-center crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I cannot provide more information it just crashed.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Apr 7 18:13:18 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-12-27 (101 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: gnome-control-
ProcEnviron:
LANGUAGE=de_DE
PATH=(custom, user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x55bf1870d311: mov 0x90(%rbp),%rsi
PC (0x55bf1870d311) ok
source "0x90(%rbp)" (0x00000090) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
()
()
() at /usr/lib/
() at /usr/lib/
g_main_
Title: gnome-control-
UpgradeStatus: Upgraded to bionic on 2018-04-07 (0 days ago)
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 #1754924, 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.