gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm3 (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Honestly not sure why this bug appeared. I did not edit the gdm.conf file. Possibly due to hotplugging/
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSign
Uname: Linux 5.5.9-050509-
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
Date: Mon Mar 16 14:42:22 2020
ExecutablePath: /usr/sbin/gdm3
ProcCmdline: /usr/sbin/gdm3
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
Signal: 5
SourcePackage: gdm3
StacktraceTop:
?? () from /lib/x86_
g_main_context_new () from /lib/x86_
g_dbus_
?? () from /lib/x86_
g_dbus_
Title: gdm3 crashed with signal 5 in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
mtime.conffile.
separator:
This sounds like bug 1597150 but I can't be sure yet. If you haven't yet rebooted since the crash then please run:
journalctl -b0 > journal.txt
If you have rebooted once since the crash then please run:
journalctl -b-1 > prevboot.txt
And in either case attach the resulting text file here.