gdm-session-worker crashed with SIGSEGV in g_str_hash()

[Christian Kirbach]

No idea what happened

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gdm3 3.32.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Sun Aug 25 20:45:19 2019
ExecutablePath: /usr/lib/gdm3/gdm-session-worker
InstallationDate: Installed on 2019-08-24 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
ProcCmdline: gdm-session-worker\ [pam/gdm-autologin]
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f431efa6d44 <g_str_hash+4>: movsbl (%rdi),%edx
 PC (0x7f431efa6d44) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gdm3
StacktraceTop:
 g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
 ?? ()
 ?? ()
Title: gdm-session-worker crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

mtime.conffile..etc.gdm3.custom.conf: 2019-08-24T02:15:33.564225
separator:

[Christian Kirbach (christian-kirbach-e)]

Looks to me like a problem in libaccountsservice

[Apport retracing service (apport)]

StacktraceTop:
 g_str_hash (v=0x0) at ../../../glib/ghash.c:2324
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x55b3927cd360) at ../../../glib/ghash.c:473
 g_hash_table_lookup (hash_table=0x55b3927cd360, key=0x0) at ../../../glib/ghash.c:1509
 console_kit_session_default_init (iface=0x0) at src/libaccountsservice/ck-session-generated.c:1128
 ?? ()

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1841382, so it 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. Feel free to continue to report any other bugs you may find.