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've tried to make second monitor work after nvidia-530 drivers were installed
(nvidia-driver-525 doesn't work the same way: built-in monitor completely white all the time)
xserver-
Tried to re-position primary monitor at Settings->Displays dialog
ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 6.2.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 29 23:23:09 2023
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2023-01-10 (78 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x55a5257a5224: mov (%rdi),%rax
PC (0x55a5257a5224) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
?? ()
g_closure_invoke () from /lib/x86_
?? () from /lib/x86_
g_signal_
g_signal_emit () from /lib/x86_
Title: gnome-control-
UpgradeStatus: Upgraded to lunar on 2023-02-23 (34 days ago)
UserGroups: adm cdrom dip docker 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 #2006500, 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.