After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 753690 - Fatal system crash when dragging gnome-terminal window between workspaces...
Fatal system crash when dragging gnome-terminal window between workspaces...
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: wayland
3.16.x
Other Linux
: Normal critical
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2015-08-16 16:42 UTC by AGS
Modified: 2016-01-04 12:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description AGS 2015-08-16 16:42:18 UTC
When running the GNOME Wayland session dragging gnome-terminal windows from one workspace to the next or between monitors in overview mode causes a fatal lockup that requires a hard-reboot, pressing the power-button.

Device: T430
Graphics: Intel HD 4000.
Kernel: 4.1.4-200.fc22.x86_64
Mutter: 3.16.3
Terminal: 3.16.2

Steps to reproduce:
1. Run a dual monitor setup with external monitor as the Primary.
2. Start working for a while with a terminal in any workspace/monitor.
3. Trigger Activities and drag gnome-terminal window from one workspace/monitor to the next.

Result:
GNOME Shell totally locks up and cannot access TTY's.  Clock still moves in the panel and the mouse can still be moved around but is stuck with the move-window icon, it just doesn't do anything.  System is totally unresponsive and requires a full power-cycle.

No log entries are produced when this happens but I do see this a few minutes leading up to the event:

---
/usr/libexec/gdm-wayland-session[1808]: Activating service name='org.gnome.Terminal'
/usr/libexec/gdm-wayland-session[1808]: Successfully activated service 'org.gnome.Terminal'
org.gnome.Terminal[1811]: (gnome-terminal-server:4150): Gdk-CRITICAL **: gdk_device_get_window_at_position_double: assertion 'GDK_IS_DEVICE (device)' failed
org.gnome.Terminal[1811]: (gnome-terminal-server:4150): Gdk-CRITICAL **: gdk_window_get_toplevel: assertion 'GDK_IS_WINDOW (window)' failed
org.gnome.Terminal[1811]: (gnome-terminal-server:4150): Gdk-CRITICAL **: gdk_window_get_device_position_double: assertion 'GDK_IS_WINDOW (window)' failed
(...)
gnome-session[1813]: Window manager warning: last_user_time (5618808) is greater than comparison timestamp (5618802).  This most likely represents a buggy client 
gnome-session[1813]: Window manager warning: 0x1200001 (bash - Res) appears to be one of the offending windows with a timestamp of 5618808.  Working around...
---
Comment 1 Rui Matos 2015-08-17 15:31:14 UTC
I don't think this is happening on master and since wayland sessions aren't default yet we don't generally backport fixes for it to stable branches.
Comment 2 AGS 2015-12-31 07:07:47 UTC
Reopening for reference purposes, here's additional information:

Dec 31 01:18:58 user.local gnome-shell-wayland.desktop[2216]: (gnome-shell:2216): GLib-GObject-WARNING **: gsignal.c:2634: instance '0x55a5293c1ee0' has no handler with id '56954'
Dec 31 01:18:58 user.local gnome-shell-wayland.desktop[2216]: (gnome-shell:2216): GLib-GObject-WARNING **: gsignal.c:2634: instance '0x55a5293c1ee0' has no handler with id '56955'
Dec 31 01:18:58 user.local gnome-shell-wayland.desktop[2216]: Gjs-Message: JS LOG: _onFocus [object instance proxy GType:MetaWindowX11 jsobj@0x7fdcc56669a0 native@0x55a5293b5660]
Comment 3 Michael Catanzaro 2015-12-31 14:55:11 UTC
If it's not happening on master, then no reason to keep the bug open! Closed bugs don't disappear. :)
Comment 4 Kamil Páral 2016-01-04 12:58:58 UTC
The window you have been moving was maximized, right? In that case it's https://bugzilla.gnome.org/show_bug.cgi?id=757676 and it's still happening on master (or at least on Rawhide's version - mutter 3.19.3.1).