This bug was fixed in the package mutter - 3.28.1-1
---------------
mutter (3.28.1-1) unstable; urgency=medium
[ Jeremy Bicha ]
* New upstream release
- Fix window button spacing when display is scaled (LP: #1725133)
* Bump Standards-Version to 4.1.4
[ Marco Trevisan (Treviño) ]
* Add patches proposed upstream:
* theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch:
- theme, frames: Use surface device scale instead of cairo_scale
(LP: #1764554)
* theme-use-gtk_render_icon_suface-to-paint-button-icon.patch:
- theme: use gtk_render_icon_suface to paint button icon
(LP: #1764558)
* theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch:
- theme: load icons as Gtk does with fallback and RTL support
* clutter-Smooth-out-master-clock-to-smooth-visuals.patch:
- clutter: Smooth out master clock to smooth visuals
* core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch:
- core: Return -1 if meta_window_get_monitor is called on an
unmanaged window (LP: #1724439)
* backends-Move-MetaOutput-crtc-field-into-private-struct.patch:
- backends: Move MetaOutput::crtc field into private struct
(LP: #1703668)
* backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch:
- backends: Add logical monitor -> monitor -> output -> crtc ref
chain (LP: #1703668)
-- Jeremy Bicha <jbi...@debian.org> Mon, 16 Apr 2018 22:35:14 -0400
** Changed in: mutter (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724439
Title:
gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
function_call()
Status in Mutter:
In Progress
Status in gnome-shell package in Ubuntu:
Fix Released
Status in mutter package in Ubuntu:
Fix Released
Status in gnome-shell source package in Bionic:
Fix Released
Status in mutter source package in Bionic:
Fix Released
Bug description:
https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854
---
left virtual box to update win10 came back and got error message
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 23:37:32 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-04-18 (182 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7feb2ed42d94 <meta_window_get_monitor+4>: mov
0x18(%rax),%eax
PC (0x7feb2ed42d94) 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_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
?? () from /usr/lib/libgjs.so.0
?? () from /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
