gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I think this happens when connecting to a bluetooth device. Everything works, just gnome-control-
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-
ProcVersionSign
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 11 12:16:14 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-08-04 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170804)
ProcCmdline: gnome-control-
SegvAnalysis:
Segfault happened at: 0x7f18f41fd499: cmpq $0x0,0x58(%rax)
PC (0x7f18f41fd499) ok
source "$0x0" ok
destination "0x58(%rax)" (0x00000058) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt 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 #1704618, 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.