gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-session (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Apport generated this crash report after I logged in to 22.04.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-session-bin 42.0-1ubuntu1
ProcVersionSign
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Apr 7 15:02:44 2022
ExecutablePath: /usr/libexec/
InstallationDate: Installed on 2022-04-05 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: /usr/libexec/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7f96fea70483 <g_signal_
PC (0x7f96fea70483) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-session
StacktraceTop:
g_signal_
g_signal_
?? ()
?? ()
g_hash_table_find () from /lib/x86_
Title: gnome-session-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
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 #1945430, 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.