gnome-control-center crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I expect my screen to start to get calibrated etc. as it use to in 17.10, but instead the following are happening:
When I'm trying to calibrate the screen it crashes, it don't start at all I get the different chooses and then after I have placed the calibrator at the correct spot on the screen and I'm pressing the button it just says that a error has accrued.
Ubuntu do notice when I'm pluggin in my calibrator and it auto starts the color application.
I'm using Ubuntu 18.04 LTS I have updated everything to the latest.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 25 21:52:37 2017
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-12-25 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x5631462c0d77: mov 0x8(%rax),%rcx
PC (0x5631462c0d77) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: gnome-control-
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 #1719390, 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.