gnome-shell crashed with signal 5 in g_log_default_handler()

Bug #1741058 reported by Scott Lewin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I received this error message on logging into cinnamon. This error message popped up with out me doing anything other than logging in. I do not know if it is related, but before logging in with cinnamon I logged in with openbox which was having problems itself.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed Dec 27 00:54:45 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-11-15 (49 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171114)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Scott Lewin (sclewin) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _g_log_abort (breakpoint=1) at ../../../../glib/gmessages.c:554
 g_log_default_handler (log_domain=<optimized out>, log_level=<optimized out>, message=<optimized out>, unused_data=<optimized out>) at ../../../../glib/gmessages.c:3051
 default_log_handler (log_domain=log_domain@entry=0x7fb064c5db93 "mutter", log_level=log_level@entry=6, message=message@entry=0x56369dc1ac00 "Connection to xwayland lost", data=data@entry=0x0) at ../src/main.c:315
 g_logv (log_domain=0x7fb064c5db93 "mutter", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7fff691732f0) at ../../../../glib/gmessages.c:1341
 g_log (log_domain=log_domain@entry=0x7fb064c5db93 "mutter", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7fb064c6eaf0 "Connection to xwayland lost") at ../../../../glib/gmessages.c:1403

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 gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: artful
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (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 1505409, 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.