gnome-control-center crashed with SIGSEGV on "Colors"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After a distro upgrade from Jammy to Kinetic (I know, I know, what am I doing?), gnome-control-
Description: Ubuntu Kinetic Kudu (development branch)
Release: 22.10
gnome-control-
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
*** 1:43.0-1ubuntu1 500
500 http://
100 /var/lib/
What You Expected To Happen:
Color profiles pane to open and display current display device color profile.
What Actually Happened:
Color profile pane opened stating there was no display device to configure, then Settings crashed outright.
ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-control-
ProcVersionSign
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 16 19:01:48 2022
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2022-09-06 (10 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
JournalErrors: -- No entries --
ProcCmdline: gnome-control-
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x5652c3340e58: cmpl $0x1,0x28(%rax)
PC (0x5652c3340e58) ok
source "$0x1" ok
destination "0x28(%rax)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
?? ()
?? ()
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
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 #1988881, 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.