This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---------------
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
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
mutter (3.28.3-1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1783311)
mutter (3.28.3-1) unstable; urgency=medium
* New upstream release
* d/p/backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch,
d/p/backends-Move-MetaOutput-crtc-field-into-private-struct.patch,
d/p/clutter-device-evdev-Get-devices-from-main-seat-if-no-rea.patch,
d/p/clutter-evdev-Don-t-ignore-CAPS-lock-as-modifier.patch,
d/p/clutter-evdev-ignore-injected-events-from-IM.patch,
d/p/clutter-seat-evdev-Add-function-to-get-device-by-id.patch,
d/p/device-manager-evdev-Add-main-seat-to-seats-by-default.patch,
d/p/device-manager-evdev-Free-the-main-seat-on-finalize.patch,
d/p/device-manager-evdev-Set-and-unset-the-stage-for-the-main.patch,
d/p/frames-Allow-for-unknown-mouse-buttons.patch,
d/p/frames-Handle-touch-events.patch,
d/p/frames-Make-1st-button-motion-handlers-take-generic-event.patch,
d/p/renderer-native-Don-t-crash-if-the-FB-surface-can-t-be-lo.patch,
d/p/wayland-Compare-geometries-after-chaining-up.patch,
d/p/wayland-Don-t-reset-input-focus-on-text-commit.patch,
d/p/wayland-Use-cursor-position-in-logical-monitor.patch,
d/p/wayland-update-enter-leave-output-after-effects.patch,
d/p/window-actor-add-new-signal-effects-completed.patch:
Remove patches already applied on 3.28 branch
-- Marco Trevisan (Treviño) <ma...@ubuntu.com> Fri, 03 Aug 2018
05:20:10 +0100
** Changed in: mutter (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
from meta_renderer_native_finish_frame()
Status in gnome-shell package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
New
Status in mutter source package in Bionic:
Fix Released
Bug description:
[ Description ]
GNome shell crashes after Xorg loggin
[ Test case ]
From GDM login in a GNOME Ubuntu session (so Xorg).
It should start with no issues
[ Regression potential ]
We were deferencing a NULL pointer while outputting an error.
This is pretty safe. Although the session might still not run properly as per
a driver issue to be addressed in linux package.
---
https://gitlab.gnome.org/GNOME/mutter/issues/70
https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665
https://salsa.debian.org/gnome-team/mutter/merge_requests/6
---
The crash was reported after booting and logging in to an X.Org
session.
$ lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
$ apt-cache policy gnome-shell
gnome-shell:
Instalovaná verze: 3.27.92-0ubuntu1
Kandidát: 3.27.92-0ubuntu1
Tabulka verzí:
*** 3.27.92-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: CrashDistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun Mar 11 11:08:00 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2017-12-19 (81 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=cs_CZ
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=cs_CZ.UTF-8
SHELL=/bin/false
SegvAnalysis:
Segfault happened at: 0x7f3fee5d2f17 <meta_gpu_kms_apply_crtc_mode+215>:
mov 0x20(%rax),%rcx
PC (0x7f3fee5d2f17) ok
source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed
readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell
StacktraceTop:
meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
meta_renderer_native_finish_frame () at
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
() at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
() at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
() at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
