gnome-control-center crashed with SIGSEGV in g_signal_emit_valist()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
While analysing bug 2078060 after toggling off fractional scaling and the shell crashing (bug 2078722), following a new login, gnome-control-
ProblemType: Crash
DistroRelease: Ubuntu 24.10
Package: gnome-control-
ProcVersionSign
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.30.0-0ubuntu1
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Sep 2 18:43:40 2024
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2022-11-26 (646 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x5e684488469e: mov (%rax),%rax
PC (0x5e684488469e) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SignalName: SIGSEGV
SourcePackage: gnome-control-
StacktraceTop:
?? ()
?? ()
?? ()
?? () from /lib/x86_
g_signal_
Title: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sudo
separator:
information type: | Private → Public |
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.
Thank you for your understanding, and sorry for the inconvenience!