gnome-session-binary crashed with SIGSEGV in GSM_IS_DBUS_CLIENT() from _disconnect_dbus_client() from foreach_remove_wrapper()

Bug #1989360 reported by Daniil
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

https://errors.ubuntu.com/problem/aa1e7373ce23aa7acbef3e8072bef2d8633118e7

---

After upgrading open-vm-tools, system not upgrading, deleted open-vm-tools and set nomodeset in grub.

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-session-bin 42.0-1ubuntu4
Uname: Linux 5.19.3-051903-generic x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Sep 12 17:25:17 2022
ExecutablePath: /usr/libexec/gnome-session-binary
InstallationDate: Installed on 2022-05-13 (121 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220513)
ProcCmdline: /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart
SegvAnalysis:
 Segfault happened at: 0x56242209360d: mov (%rbx),%rax
 PC (0x56242209360d) ok
 source "(%rbx)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-session
StacktraceTop:
 ()
 ()
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 ()
Title: gnome-session-binary crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

Revision history for this message
Daniil (danik2343) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 GSM_IS_DBUS_CLIENT (ptr=0x30) at ../gnome-session/gsm-dbus-client.h:27
 _disconnect_dbus_client (id=<optimized out>, client=0x30, data=0x7f7f43ffe5d0) at ../gnome-session/gsm-manager.c:1826
 foreach_remove_wrapper (id=0x7f7f4e3dd360 <g_object_unref> "\363\017\036\372AW\276P", object=<optimized out>, data=0x7f7f43ffe580) at ../gnome-session/gsm-store.c:167
 g_hash_table_foreach_remove_or_steal (hash_table=0x562422c960c0, func=0x56242208d810 <foreach_remove_wrapper>, user_data=user_data@entry=0x7f7f43ffe580, notify=notify@entry=1) at ../../../glib/ghash.c:1975
 g_hash_table_foreach_remove (hash_table=<optimized out>, func=<optimized out>, user_data=user_data@entry=0x7f7f43ffe580) at ../../../glib/ghash.c:2021

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

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!

Changed in gnome-session (Ubuntu):
status: New → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
summary: - gnome-session-binary crashed with SIGSEGV
+ gnome-session-binary crashed with SIGSEGV in GSM_IS_DBUS_CLIENT() from
+ _disconnect_dbus_client() from foreach_remove_wrapper()
Changed in gnome-session (Ubuntu):
status: Invalid → New
information type: Private → Public
tags: added: jammy
Changed in gnome-session (Ubuntu):
status: New → Confirmed
description: updated
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.