GNOME Bugzilla – Bug 791378
System Freeze after dragging a window to a new workspace
Last modified: 2017-12-08 16:07:59 UTC
On a freshly booted Gnome 3.26.2 (linux 4.14.4-1-ARCH), I opened Nautilus and Geary, pressed the super key and dragged the Geary window to the second workspace (https://help.gnome.org/users/gnome-help/stable/shell-workspaces-movewindow.html.en). On mouse release the system hanged completely. Going to another terminal I could see this repeated in an infinite loop: JS ERROR: Error: Object St.Widget (0x55ae9ab9e040), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs _Draggable<._updateDragPosition@resource:///org/gnome/shell/ui/dnd.js:457:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _Draggable<._onEvent@resource:///org/gnome/shell/ui/dnd.js:227:24 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _getEventHandlerActor/<@resource:///org/gnome/shell/ui/dnd.js:54:46
Just tried again and I can reproduce it every time I try to move a window to a different workspace. Complete system freeze.
(In reply to CharlesG from comment #0) > On a freshly booted Gnome 3.26.2 (linux 4.14.4-1-ARCH) Uhm, no - the following error: > JS ERROR: Error: Object St.Widget (0x55ae9ab9e040), has been already > deallocated - impossible to access to it. This might be caused by the fact > that the object has been destroyed from C code using something such as > destroy(), dispose(), or remove() vfuncs has been added recently in gjs master, but not to stable 3.26.x. This and other fallout from that change is tracked in bug 791233. *** This bug has been marked as a duplicate of bug 791233 ***
Then this must be a different issue?. Have a look: ➜ ~ pacman -Qi gnome-shell Name : gnome-shell Version : 3.26.2+5+g3b4be770a-3 Description : The next generation GNOME Shell Architecture : x86_64 URL : https://wiki.gnome.org/Projects/GnomeShell Licenses : GPL2 Groups : gnome Provides : None Depends On : accountsservice caribou gcr gjs gnome-bluetooth gnome-menus upower gnome-session gnome-settings-daemon gnome-themes-standard gsettings-desktop-schemas libcanberra-pulse libcroco libgdm libsecret mutter nm-connection-editor unzip gstreamer Optional Deps : gnome-control-center: System settings [installed] evolution-data-server: Evolution calendar integration [installed] Required By : chrome-gnome-shell gdm gnome-shell-extension-dash-to-dock gnome-shell-extension-dash-to-panel gnome-shell-extensions Optional For : None Conflicts With : None Replaces : None Installed Size : 11.70 MiB Packager : Jan Alexander Steffens (heftig) <jan.steffens@gmail.com> Build Date : Wed 22 Nov 2017 04:37:03 PM CET Install Date : Mon 04 Dec 2017 07:14:05 AM CET Install Reason : Explicitly installed Install Script : No Validated By : Signature
(In reply to CharlesG from comment #3) > Then this must be a different issue?. Have a look: > > ➜ ~ pacman -Qi gnome-shell I said *gjs*, not gnome-shell. Arch updated gjs to a git snapshot that includes the new error, without giving us any time to fix the fallout.