gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from gbm_get_next_fb_id()

[Mathieu St-Gelais]

https://gitlab.gnome.org/GNOME/mutter/issues/21
https://errors.ubuntu.com/problem/a3d143e94242ebfe1c753ef1e2809b7128702abc

--

The fix for this bug is included in mutter 3.28.2 upstream release, and as per that doesn't need specific SRU verification.

See bug 1778703

---

Randomly crashes in minutes following a reboot.

ProblemType: CrashDistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Mar 22 21:39:40 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2018-03-22 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7fce03ec7c90 <gbm_bo_get_plane_count>: mov (%rdi),%rax
 PC (0x7fce03ec7c90) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11SourcePackage: gnome-shell
StacktraceTop:
 gbm_bo_get_plane_count () from /usr/lib/x86_64-linux-gnu/libgbm.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
Title: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 gbm_bo_get_plane_count (bo=0x0) at ../../../src/gbm/main/gbm.c:342
 gbm_get_next_fb_id (gpu_kms=gpu_kms@entry=0x5632ba3f7cb0, gbm_surface=0x5632ba7335f0, out_next_bo=out_next_bo@entry=0x5632ba718298, out_next_fb_id=out_next_fb_id@entry=0x5632ba71828c) at backends/native/meta-renderer-native.c:1601
 meta_onscreen_native_swap_buffers_with_damage (onscreen=0x5632ba7307c0, rectangles=0x7ffd226793d0, n_rectangles=0) at backends/native/meta-renderer-native.c:1877
 cogl_onscreen_swap_buffers_with_damage (onscreen=onscreen@entry=0x5632ba7307c0, rectangles=rectangles@entry=0x7ffd226793d0, n_rectangles=n_rectangles@entry=0) at cogl-onscreen.c:319
 swap_framebuffer (stage_window=0x1, swap_with_damage=<optimized out>, swap_region=<synthetic pointer>, view=0x5632ba7341f0) at cogl/clutter-stage-cogl.c:400

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Also tracking in:
https://errors.ubuntu.com/problem/a3d143e94242ebfe1c753ef1e2809b7128702abc

[Daniel van Vugt (vanvugt)]

Fix committed upstream:
https://gitlab.gnome.org/GNOME/mutter/issues/21

Looks like the fix is in mutter versions 3.29.1 and 3.28.2.

[Daniel van Vugt (vanvugt)]

Fix released in 18.10 only so far. Not 18.04 yet.

mutter (3.28.2-2) unstable; urgency=medium

  * Team upload
  * d/p/frames-Handle-touch-events.patch,
    d/p/frames-Make-1st-button-motion-handlers-take-generic-event.patch:
    Drop cherry-picked patches that caused a regression (Closes: #899181)

 -- Simon McVittie <email address hidden> Sun, 20 May 2018 15:21:35 +0100

[Brian Murray (brian-murray)]

If you don't think the bug requires specific verification because it is a part of an upstream microrelease then don't put the bug number in the changelog or format it in such a way so that it becomes part of Launchpad-Bugs-Fixed.

Given that there is a link to an Error Tracker crash I can guess what the test case is but please still update the description since the changelog references this bug number.

[Brian Murray (brian-murray)]

Hello Mathieu, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.2-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Sebastien Bacher (seb128)]

3.28.2-2~ubuntu18.04.1 has no e.u.c report

[Launchpad Janitor (janitor)]

This bug was fixed in the package mutter - 3.28.2-2~ubuntu18.04.1

---------------
mutter (3.28.2-2~ubuntu18.04.1) bionic; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * Backport from cosmic (LP: #1778703)
    - Hybrid GPU: 'shallow' crash while interacting with the
      secondary screen (LP: #1758528)

mutter (3.28.2-2) unstable; urgency=medium

  * Team upload
  * d/p/frames-Handle-touch-events.patch,
    d/p/frames-Make-1st-button-motion-handlers-take-generic-event.patch:
    Drop cherry-picked patches that caused a regression (Closes: #899181)

mutter (3.28.2-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * d/p/theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch,
    d/p/xwayland-Don-t-abort-if-Xwayland-crashes.patch,
    d/p/xwayland-use-g_autoptr-for-GError-in-xserver_died.patch:
    Drop patches that were applied upstream
  * d/p/debian/synaptics-support.patch,
    d/p/debian/skip-failing-tests.patch,
    d/p/debian/skip-failing-tests-325.patch:
    Move patches not expected to be applied upstream to
    debian/patches/debian
  * Re-order patch series so most-upstreamable patches are first
  * d/p/clutter-evdev-Don-t-ignore-CAPS-lock-as-modifier.patch,
    d/p/clutter-evdev-ignore-injected-events-from-IM.patch,
    d/p/frames-Handle-touch-events.patch,
    d/p/frames-Make-1st-button-motion-handlers-take-generic-event.patch,
    d/p/wayland-Use-cursor-position-in-logical-monitor.patch:
    Add post-release fixes from upstream 3.28 branch

mutter (3.28.1-2) unstable; urgency=medium

  * Add xwayland-use-g_autoptr-for-GError-in-xserver_died.patch,
    xwayland-Don-t-abort-if-Xwayland-crashes.patch:
    - Cherry picked from upstream, to reduce noise of mutter on crashes
      which are actually caused by XWayland (LP: #1748450)

 -- Marco Trevisan (Treviño) <email address hidden> Tue, 26 Jun 2018 15:24:45 +0200

[Steve Langasek (vorlon)]

The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.