Ubuntu
gnome-settings-daemon package

gsd-power crashed with SIGSEGV in __GI___libc_free()

Bug #2081869 reported by Will Brown
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Seemingly random error.

ProblemType: Crash
DistroRelease: Ubuntu 24.10
Package: gnome-settings-daemon 47.1-1ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 24 13:10:58 2024
ExecutablePath: /usr/libexec/gsd-power
InstallationDate: Installed on 2024-09-24 (0 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Beta amd64 (20240919)
ProcCmdline: /usr/libexec/gsd-power
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7c96390b3395 <__GI___libc_free+37>: mov -0x8(%rdi),%rax
 PC (0x7c96390b3395) ok
 source "-0x8(%rdi)" (0x3c86837e8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SignalName: SIGSEGV
SourcePackage: gnome-settings-daemon
StacktraceTop:
 __GI___libc_free (mem=0x3c86837f0) at ./malloc/malloc.c:3375
 g_hash_table_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_hash_table_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_dbus_interface_info_cache_release () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gsd-power crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

Revision history for this message
Will Brown (wcbrow01) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #2081830, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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