gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I can only describe the events leading up to the crash reporter popping up on my screen.
I have a Intel NUC i5-7260U connected via a HDMI cable to a Samsung UE46D6515 TV set. I turned off my TV using the remote control and when I turned it back on, the keyboard and mouse were unresponsive for a few seconds. Moments later, all was well but the crash reporter appeared.
I might add that I had difficulties with powering off the TV under 17.10, leading me to switch to X11 (which worked better but had similar problems).
All the best, Gísli
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu5
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 13 19:42:58 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.
InstallationDate: Installed on 2018-04-13 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f7f25cf0c24 <meta_window_
PC (0x7f7f25cf0c24) 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
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.