A crash must be fixed, anyway.
I've experienced it myself. It can be easily replicated using a remote shell to
launch gnome-session in an Xvfb display:
Xvfb -ac :100 2> Xvfb.log &
DISPLAY=:100
export DISPLAY
gnome-session --session=ubuntu
After that, gdm crashed. I had gdm debug enabled and found this in the
system journal:
ago 20 19:25:21 nxhost gdm3[172158]: Finding a graphical session for user 1000
ago 20 19:25:21 nxhost gdm3[172158]: Considering session 'c306'
ago 20 19:25:21 nxhost gdm3[172158]: Session 'c306' is not a graphical session
(type: 'tty')
ago 20 19:25:21 nxhost gdm3[172158]: Considering session '53'
ago 20 19:25:21 nxhost gdm3[172158]: Session '53' is not a graphical session
(type: 'tty')
ago 20 19:25:21 nxhost gdm3[172158]: GdmManager: Unable to find display session
for uid 1000: Could not find a graphical session for user 1000
ago 20 19:25:21 nxhost gdm3[172158]: GdmManager: trying to register new session
on display 0x1
ago 20 19:25:21 nxhost kernel: gdm3[172158]: segfault at 1 ip 00007fe66921277a
sp 00007ffee4f51140 error 4 in libgobject-2.0.so.0.6400.2[7fe6691e4000+36000]
ago 20 19:25:21 nxhost kernel: Code: c0 eb b3 66 66 2e 0f 1f 84 00 00 00 00 00
66 90 f3 0f 1e fa 41 55 41 54 49 89 fc 55 53 48 83 ec 28 48 85 ff 0f 84 a8 0>
ago 20 19:25:21 nxhost gnome-session[172571]: gnome-session-binary[172571]:
WARNING: Could not get session path for session. Check that logind is properly >
ago 20 19:25:21 nxhost gnome-session-binary[172571]: WARNING: Could not get
session path for session. Check that logind is properly installed and pam_syste>
ago 20 19:25:22 nxhost systemd[1]: gdm.service: Main process exited,
code=dumped, status=11/SEGV
ago 20 19:25:22 nxhost systemd[1]: gdm.service: Failed with result 'core-dump'.
Pointer display 0x1 is abnormal with any evidence. Crash report consistently
points to session registration in gdm:
Thread 1 (Thread 0x7fb04d5da8c0 (LWP 190922)):
#0 0x00007fb04ded877a in g_type_check_instance_cast () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#1 0x00005560143a2a6a in gdm_manager_handle_register_session
(manager=0x5560163e78f0, invocation=0x7fb04400a590, details=) at
gdm-manager.c:827
self = 0x5560163e78f0
display = 0x1
sender = 0x7fb04400b9b0 ":1.2718"
connection =
The crash occurs in gdm-manager.c when gnome-shell calls
LoginManager.registerSessionWithGDM():
https://github.com/GNOME/gdm/blob/gnome-3-36/daemon/gdm-manager.c
It looks triggered by gnome-shell trying to register its session to gdm:
https://github.com/GNOME/gnome-shell/commit/0e37cd2ec92c5fbbc0870272e5e00fc07a705eba
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861769
Title:
gdm3 crashed with SIGSEGV in g_type_check_instance_cast() from
gdm_manager_handle_register_session() from ffi_call_unix64() from
ffi_call() from g_cclosure_marshal_generic()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1861769/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
