gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Same behavior for the last month, with shifting targets for the culprit this time. Whenever I turn on my monitor, the user session segfaults. I play music with the monitor off, and it continues playing up until the moment I turn back on the monitor.
dmesg output: gnome-shell[2039]: segfault at 18 ip 00007f868827b2d4 sp 00007ffcd12cbdf8 error 4 in libmutter-
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSign
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 16 09:10:59 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
b'org.gnome.shell' b'favorite-apps' b"['org.
b'org.
b'org.
b'org.
b'org.
InstallationDate: Installed on 2017-05-28 (202 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f868827b2d4 <meta_window_
PC (0x7f868827b2d4) 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: Upgraded to artful on 2017-10-21 (55 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
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.