gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

[Grzegorz Daniluk]

https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052

---

Ordinary bug report in 17.10

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 13:08:15 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>']"
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2017-10-19 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f8d82fc8c5c: mov 0x18(%rax),%esi
 PC (0x7f8d82fc8c5c) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 meta_window_x11_configure_request () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 meta_window_move_resize_request (window=window@entry=0x55b29e7bef30, value_mask=<optimized out>, gravity=1, new_x=<optimized out>, new_y=76, new_width=<optimized out>, new_height=<optimized out>) at x11/window-x11.c:2095
 meta_window_x11_configure_request (window=window@entry=0x55b29e7bef30, event=event@entry=0x7ffc56ec6110) at x11/window-x11.c:2169
 handle_other_xevent (display=display@entry=0x55b29d182a00, event=event@entry=0x7ffc56ec6110) at x11/events.c:1456
 meta_display_handle_xevent (event=0x7ffc56ec6110, display=0x55b29d182a00) at x11/events.c:1784
 xevent_filter (xevent=0x7ffc56ec6110, event=<optimized out>, data=0x55b29d182a00) at x11/events.c:1823

[Launchpad Janitor (janitor)]

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

[David Girault (dfgweb)]

Seems monitor_rect is invalid in my own stacktrace.

Stacktrace:
 #0 0x00007f66ea88d1bc in meta_window_move_resize_request (window=window@entry=0x559031de5950, value_mask=<optimized out>, gravity=
1, new_x=<optimized out>, new_y=0, new_width=<optimized out>, new_height=<optimized out>) at x11/window-x11.c:2095
         rect = {x = 0, y = 0, width = 1606, height = 1368}
         monitor_rect = {x = 992734343, y = 0, width = 0, height = 0}
         x = 0
         y = 0
         width = 1606
         height = 1368
         allow_position_change = <optimized out>
         in_grab_op = <optimized out>
         flags = (META_MOVE_RESIZE_CONFIGURE_REQUEST | META_MOVE_RESIZE_MOVE_ACTION)
 #1 0x00007f66ea88e073 in meta_window_x11_configure_request (window=window@entry=0x559031de5950, event=event@entry=0x7ffc97e033b0)
at x11/window-x11.c:2169
         window_x11 = <optimized out>
 #2 0x00007f66ea882ead in handle_other_xevent (display=display@entry=0x55902cc7cbe0, event=event@entry=0x7ffc97e033b0) at x11/event
s.c:1456
         modified = <optimized out>
         window = 0x559031de5950
         property_for_window = <optimized out>
         frame_was_receiver = <optimized out>
         bypass_gtk = 0
 #3 0x00007f66ea883dcb in meta_display_handle_xevent (event=0x7ffc97e033b0, display=0x55902cc7cbe0) at x11/events.c:1784
         input_event = 0x0
         backend = <optimized out>
         modified = 46137345
         bypass_compositor = 0
         bypass_gtk = 0
         display = 0x55902cc7cbe0
 #4 0x00007f66ea883dcb in xevent_filter (xevent=0x7ffc97e033b0, event=<optimized out>, data=0x55902cc7cbe0) at x11/events.c:1823
         display = 0x55902cc7cbe0
 #5 0x00007f66e9ade0cf in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 #6 0x00007f66e9ade3b9 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 #7 0x00007f66e9aa7ec0 in gdk_display_get_event () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 #8 0x00007f66e9ade162 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 #9 0x00007f66ec32ffb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 #10 0x00007f66ec3301f0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 #11 0x00007f66ec330502 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 #12 0x00007f66ea863bcc in meta_run () at core/main.c:648
 #13 0x000055902b04c4ac in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:530
         ctx = <optimized out>
         error = 0x0
         ecode = <optimized out>

[Daniel van Vugt (vanvugt)]

This issue is also being tracked in:
https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052

[Rocko (rockorequin)]

Fwiw, this happens every time I turn off the only monitor attached to the computer, and it loses all unsaved data, so for me it's critical - I can't use gnome-shell on that computer.

[Rocko (rockorequin)]

This looks like https://bugzilla.gnome.org/show_bug.cgi?id=790207.

[Walter (wdoekes)]

Perhaps this helps?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/comments/29
->
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/

Cheers,
Walter Doekes
OSSO B.V.

[Walter (wdoekes)]

By the way, upstream appears to have a fix for this too: https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492

[Daniel van Vugt (vanvugt)]

Launchpad bug 1724439 already covers that.

It would be a bonus if this bug was resolved by the same fix so we'll wait and see.

[Daniel van Vugt (vanvugt)]

Looks like this was fixed in Gnome 3.28 ... let's see and this bug can auto-expire if so.

[Daniel van Vugt (vanvugt)]

Yes, the crash stopped happening before 18.10.