gnome-shell crashed with signal 5 in g_log_default_handler()

Bug #1742542 reported by jrstravino
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Artful (17.10) Session logout after screen turned off

Whenever I turn off my screen and then turn it on the problem occurs. the computer (a desktop PC) logs me out of my session.
When I wake the screen, I get the GDM login screen and a new session opens.
The previous session is lost.

Here is a discussion thread with users of similar issue:
https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Jan 8 18:33:01 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1510175942
GsettingsChanges:

InstallationDate: Installed on 2017-12-03 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /var/lib/gdm3
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.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
jrstravino (jrstravino) 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=0x7fdc8ec61b93 "mutter", log_level=log_level@entry=6, message=message@entry=0x55f377a95f60 "Connection to xwayland lost", data=data@entry=0x0) at ../src/main.c:315
 g_logv (log_domain=0x7fdc8ec61b93 "mutter", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7ffc9606d690) at ../../../../glib/gmessages.c:1341
 g_log (log_domain=log_domain@entry=0x7fdc8ec61b93 "mutter", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7fdc8ec72af0 "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
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.

jrstravino (jrstravino)
description: updated
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
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.