This bug was fixed in the package mutter - 3.28.3-2
---------------
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstream branch to upstream/3.28.x, since we've
branched for experimental now.
[ Marco Trevisan (Treviño) ]
* d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch:
- Avoid crashing when warning about wrongly set crtc mode
(LP: #1754949)
* d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch:
- Don't crash if drmModeGetResources returns NULL (LP: #1767956)
* d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch:
- Always update monitor in wayland, avoiding crash (LP: #1784398)
* d/p/monitor-manager-Filter-out-low-screen-resolutions.patch:
- Don't return screen resolutions that can't be applied (LP: #1772831)
* d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch,
d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch:
- Don't crash if a modal dialog closes while being dragged
(LP: #1422253)
* d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch:
- Don't try to use an invalid monitor mode to figure out scaling
(LP: #1723615)
[ Simon McVittie ]
* Sort patch series in upstream order, with patches applied upstream
first
* d/copyright: Remove obsolete FSF postal addresses
* Standards-Version: 4.1.5 (no changes required)
* Set Rules-Requires-Root to no
* Update symbols file
-- Simon McVittie <[email protected]> Tue, 31 Jul 2018 15:35:03 +0100
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1723615
Title:
gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
Status in mutter package in Ubuntu:
Fix Released
Bug description:
https://gitlab.gnome.org/GNOME/mutter/issues/130
https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339
---
This happened while I was away from the computer. By the timing it
should have been well after the time it should have gone *into*
displaysleep, and was also about 45min before I returned, so certainly
wasn't the wake-up process either.
What I observed when I did return: My 4K monitor didn't wake up
(that's a known problem with this monitor, Dell P2715Q), the second
monitor (Dell U2711) did wake up, showing the login screen.
So although I've considered my Dell 4K problem a problem with waking
up, I wonder if it might be actually a problem with it apparently
going away completely after a longer displaysleep (it's usually fine
if I just do a short sleep of a minute or two).
Another possibility is the cat stepped on the keyboard and thus
triggered an attempted display-wake. But that would actually be out of
character (for the cat).
Either way is a bug because the session should survive monitor
shenanigans... :-)
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
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 14 15:39:50 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2017-07-30 (75 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7fae20ab44a0 <meta_monitor_mode_get_resolution>:
mov 0x8(%rdi),%eax
PC (0x7fae20ab44a0) ok
source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed
readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_monitor_mode_get_resolution () at
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_calculate_mode_scale () at
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_update_logical_state_derived () at
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_rebuild_derived () at
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
meta_monitor_manager_xrandr_handle_xevent () at
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1723615/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
