gdm3 crashed with SIGSEGV in ensure_display_for_seat()

Bug #1945061 reported by L3P3
82
This bug affects 9 people
Affects Status Importance Assigned to Milestone
gdm
Fix Released
Unknown
gdm3 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

https://errors.ubuntu.com/problem/131b21d4843931d315a4548121d7d352cfd1e3a8
https://errors.ubuntu.com/problem/175aaeced63f2d1fd3c1361b9802cfff7821bd42

---

no time for handling, hope everything required in automatically attached files

ubuntu impish proposed

i5 + amd 6000 (radeon) in hp g6 notebook

switched from wayland to xorg by adjusting gdm config file

reason for editing config file: want to try out to switch gpu for ui/games

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gdm3 41~rc-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat Sep 25 17:42:29 2021
ExecutablePath: /usr/sbin/gdm3
ProcCmdline: /usr/sbin/gdm3
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x5638df1e412a: mov (%r15),%rcx
 PC (0x5638df1e412a) ok
 source "(%r15)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gdm3
StacktraceTop:
 ?? ()
 ?? ()
 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
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gdm3 crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
mtime.conffile..etc.gdm3.custom.conf: 2021-09-25T17:42:14.958231
separator:

Revision history for this message
L3P3 (l3p3) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ensure_display_for_seat (factory=factory@entry=0x5638e0106ab0, seat_id=0x5638e0148750 "seat0") at ../daemon/gdm-local-display-factory.c:681
 on_display_status_changed (display=0x5638e00ff360, arg1=<optimized out>, factory=0x5638e0106ab0) at ../daemon/gdm-local-display-factory.c:557
 g_closure_invoke (closure=0x5638e014de30, return_value=0x0, n_param_values=2, param_values=0x7ffdc5ba3720, invocation_hint=0x7ffdc5ba36a0) at ../../../gobject/gclosure.c:810
 signal_emit_unlocked_R (node=node@entry=0x5638e00e7a40, detail=detail@entry=239, instance=instance@entry=0x5638e00ff360, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffdc5ba3720) at ../../../gobject/gsignal.c:3741
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffdc5ba38f0) at ../../../gobject/gsignal.c:3497

tags: removed: need-amd64-retrace
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
summary: - gdm3 crashed with SIGSEGV in g_closure_invoke()
+ gdm3 crashed with SIGSEGV in ensure_display_for_seat()
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
information type: Private → Public
description: updated
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 :

Seems to be a regression in 41~rc-0ubuntu1

tags: added: regression-release
Changed in gdm3 (Ubuntu):
milestone: none → ubuntu-21.10
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gdm3 (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Changed in gdm3 (Ubuntu):
milestone: ubuntu-21.10 → impish-updates
Revision history for this message
Sebastien Bacher (seb128) wrote :

Upstream proposed a fix in https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/160 and describe the crash as being an issue when neither wayland nor xorg is working. Could someone describe in which kind of setup they encounter the error?

Revision history for this message
L3P3 (l3p3) wrote :

Well, I used the "proposed" repository. After update&upgrade a few days later, the issue was resolved.

Revision history for this message
Xosé (ubuntu-galizaweb) wrote :

I log in as the primary user. Then, I try to switch users: I get to the login screen, type in the password, the screen goes black and then comes back to the login screen. I see the input field and the pointer, but the computer is frozen - I can't access a console.

If I reboot, I can log in to a different user, but if then I try to log in to the primary user, the same thing happens.

This only happens when switching between users. If I log out of the current user (end session) I can sign into the second account without any problem.

Revision history for this message
Hassan El Jacifi (waver) wrote :

Hi Guys,

Is there any update in regards of this annoying bug?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The GNOME developers are working on a fix in https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/160

tags: added: fixed-in-41.3 fixed-upstream
Changed in gdm3 (Ubuntu):
status: Triaged → Fix Committed
description: updated
tags: added: jammy
Revision history for this message
Hassan El Jacifi (waver) wrote :

Hi Guys,

I tested the latest gdm from jammy and the issue is still present

Package: gdm3
Version: 41.3-1ubuntu2
Status: install ok installed
Priority: optional
Section: gnome

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

It looks like the fix in 41.3 is working because we have received zero crash reports since.

Hassan: If you still have problems then please open a new bug.

Changed in gdm3 (Ubuntu):
status: Fix Committed → Fix Released
tags: added: rls-ii-incoming
Revision history for this message
Hassan El Jacifi (waver) wrote :

Hello Daniel,

Issue is still present, as requested I opened a new bug #1969516

Changed in gdm:
status: Unknown → Fix Released
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.