gdm3 crashed with SIGSEGV in g_str_hash()

Bug #1871344 reported by dan501
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I did a small ubuntu system update and got a black screen. Restart appears to have fixed the problem

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
Date: Tue Apr 7 05:45:04 2020
ExecutablePath: /usr/sbin/gdm3
InstallationDate: Installed on 2020-03-15 (22 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
ProcCmdline: /usr/sbin/gdm3
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7faa8fae1494 <g_str_hash+4>: movsbl (%rdi),%eax
 PC (0x7faa8fae1494) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" 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
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gdm3 crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

mtime.conffile..etc.gdm3.custom.conf: 2020-03-15T15:32:07.723254
separator:

Revision history for this message
dan501 (dan-rudder) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_str_hash () from /tmp/apport_sandbox_qtpjmzb3/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 g_hash_table_lookup () from /tmp/apport_sandbox_qtpjmzb3/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 update_user (user=0x7faa800062c0, manager=0x55d5121c92d0) at ../src/libaccountsservice/act-user-manager.c:1020
 on_user_changed (manager=0x55d5121c92d0, user=0x7faa800062c0) at ../src/libaccountsservice/act-user-manager.c:664
 on_user_changed (user=0x7faa800062c0, manager=0x55d5121c92d0) at ../src/libaccountsservice/act-user-manager.c:650

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gdm3 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gdm3 (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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 1843982, 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.

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.