The log in comment #6 suggests the cause is in gnome-shell's window management:
JS ERROR: TypeError: this.actor is null _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:145:25 onStopped@resource:///org/gnome/shell/ui/windowManager.js:157:35 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:84:22 _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:250:60 _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1555:21 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1523:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:84:22 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:173:64 @resource:///org/gnome/shell/ui/init.js:21:20 But that might be a red herring because it wouldn't freeze the whole monitor. Please repeat comment #4 each time it happens so we can look for patterns. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
