xfsettingsd crashed with SIGTRAP in g_log_writer_default()

[Rick S]

This is first boot after install on a KVM current iso dated today.

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: xfce4-settings 4.18.4-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sun Apr 7 12:27:36 2024
ExecutablePath: /usr/bin/xfsettingsd
InstallationDate: Installed on 2024-04-07 (0 days ago)
InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
ProcCmdline: xfsettingsd --display :0.0 --sm-client-id 2837f7668-f84c-4f47-91fe-5527e1d866ed
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Signal: 5
SignalName: SIGTRAP
SourcePackage: xfce4-settings
StacktraceTop:
 g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 __libc_start_call_main (main=main@entry=0x5ae474824800, argc=argc@entry=5, argv=argv@entry=0x7ffd992f56a8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: xfsettingsd crashed with SIGTRAP in g_log_writer_default()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

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

[Apport retracing service (apport)]

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!