gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
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.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSign
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 9 18:08:20 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
ExecutableTimes
GsettingsChanges:
b'org.gnome.shell' b'enabled-
b'org.gnome.shell' b'favorite-apps' b"['google-
b'org.
b'org.
b'org.
InstallationDate: Installed on 2017-12-03 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/
ProcCwd: /home/tux
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f97ba3992d4 <meta_window_
PC (0x7f97ba3992d4) ok
source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_window_
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in meta_window_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
description: | updated |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724439, so 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. Please continue to report any other bugs you may find.