gdm3 crashed with signal 5 in g_main_context_new()

Bug #1706975 reported by Dan Acampora on 2017-07-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)

Bug Description

crash on boot

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gdm3 3.24.2-1ubuntu9
ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
Uname: Linux 4.11.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Wed Jul 26 22:17:40 2017
ExecutablePath: /usr/sbin/gdm3
InstallationDate: Installed on 2016-04-30 (452 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
ProcCmdline: /usr/sbin/gdm3
 PATH=(custom, no user)
Signal: 5
SourcePackage: gdm3
 ?? () from /lib/x86_64-linux-gnu/
 g_main_context_new () from /lib/x86_64-linux-gnu/
 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 g_dbus_connection_call_sync () from /usr/lib/x86_64-linux-gnu/
Title: gdm3 crashed with signal 5 in g_main_context_new()
UpgradeStatus: No upgrade log present (probably fresh install)

Dan Acampora (wmdwebs) wrote :
Dan Acampora (wmdwebs) wrote :


 g_wakeup_new () from /tmp/apport_sandbox_8HX17v/lib/x86_64-linux-gnu/
 g_main_context_new () from /tmp/apport_sandbox_8HX17v/lib/x86_64-linux-gnu/
 g_dbus_connection_send_message_with_reply_sync () from /tmp/apport_sandbox_8HX17v/usr/lib/x86_64-linux-gnu/
 g_dbus_connection_call_sync_internal () from /tmp/apport_sandbox_8HX17v/usr/lib/x86_64-linux-gnu/
 g_dbus_connection_call_sync () from /tmp/apport_sandbox_8HX17v/usr/lib/x86_64-linux-gnu/

Changed in gdm3 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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 1597150, 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.

information type: Private → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers