gsd-xsettings crashed with SIGSEGV in g_closure_invoke()

Bug #2032900 reported by Khairul Aizat Kamarudzzaman
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

crashed when change to dark mode

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-settings-daemon 44.1-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 24 15:59:41 2023
Disassembly: => 0x7f5cc9f924b0: Cannot access memory at address 0x7f5cc9f924b0
ExecutablePath: /usr/libexec/gsd-xsettings
InstallationDate: Installed on 2023-07-08 (47 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705)
ProcCmdline: /usr/libexec/gsd-xsettings
SegvAnalysis:
 Segfault happened at: 0x7f5cc9f924b0: Cannot access memory at address 0x7f5cc9f924b0
 PC (0x7f5cc9f924b0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? ()
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gsd-xsettings crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin nordvpn plugdev sudo users
separator:

Revision history for this message
Khairul Aizat Kamarudzzaman (fenris) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_closure_invoke (closure=0x5615061a4900, return_value=0x0, n_param_values=2, param_values=0x7ffd2f17e300, invocation_hint=0x7ffd2f17e250) at ../../../gobject/gclosure.c:832
 signal_emit_unlocked_R.isra.0 (node=node@entry=0x7ffd2f17e3f0, detail=detail@entry=349, instance=instance@entry=0x561505fc6cb0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffd2f17e300) at ../../../gobject/gsignal.c:3980
 signal_emit_valist_unlocked (instance=instance@entry=0x561505fc6cb0, signal_id=signal_id@entry=1, detail=detail@entry=349, var_args=var_args@entry=0x7ffd2f17e550) at ../../../gobject/gsignal.c:3612
 g_signal_emit_valist (instance=0x561505fc6cb0, signal_id=1, detail=349, var_args=var_args@entry=0x7ffd2f17e550) at ../../../gobject/gsignal.c:3355

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.