gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

Bug #1726352 reported by Grzegorz Daniluk on 2017-10-23
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
mutter (Ubuntu)

Bug Description


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
 b'' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>']"
 b'' 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
 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
 () at /usr/lib/x86_64-linux-gnu/
 meta_window_x11_configure_request () at /usr/lib/x86_64-linux-gnu/
 () at /usr/lib/x86_64-linux-gnu/
 () at /usr/lib/x86_64-linux-gnu/
 () at /usr/lib/x86_64-linux-gnu/
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

Grzegorz Daniluk (dgregd) wrote :

 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

Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
summary: - gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
David Girault (dfgweb) wrote :

Seems monitor_rect is invalid in my own 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>
 #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
         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/
 #6 0x00007f66e9ade3b9 in () at /usr/lib/x86_64-linux-gnu/
 #7 0x00007f66e9aa7ec0 in gdk_display_get_event () at /usr/lib/x86_64-linux-gnu/
 #8 0x00007f66e9ade162 in () at /usr/lib/x86_64-linux-gnu/
 #9 0x00007f66ec32ffb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/
 #10 0x00007f66ec3301f0 in () at /lib/x86_64-linux-gnu/
 #11 0x00007f66ec330502 in g_main_loop_run () at /lib/x86_64-linux-gnu/
 #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) wrote :
description: updated
tags: added: bionic
Rocko (rockorequin) wrote :

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.

Changed in mutter (Ubuntu):
status: New → Confirmed
Changed in mutter:
importance: Unknown → Critical
status: Unknown → Confirmed
wdoekes (walter+ubuntu) wrote :

By the way, upstream appears to have a fix for this too:

Daniel van Vugt (vanvugt) wrote :

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) wrote :

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

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Changed in mutter (Ubuntu):
status: Confirmed → Incomplete
Daniel van Vugt (vanvugt) wrote :

Yes, the crash stopped happening before 18.10.

Changed in gnome-shell (Ubuntu):
status: Incomplete → Fix Released
Changed in mutter (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.