Similar stack for me:
Jan 5 20:31:26 DELL-E5510 gnome-shell[1801]: Object Meta.WindowActor
(0x55fec19a6400), has been already deallocated — impossible to access it. This
might be caused by the object having been destroyed from C code using something
such as destroy(), dispose(), or remo
ve()
I have found a work-around to get back to desktop.
If you have locked the screen and it has hung you can lock/unlock by
using the SUPER + L hotkey (Or whatever your shortcut key is).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Forgot to mention, you may need to use the hotkey twice to lock from
desktop.
--
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/1804008
Title:
Gnome Shell extensions crash
By disabling autohide, the error message in log does not go away, but
desktop will recover and does not end up with black screen after wake
up.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I would suggest to reconsider #7. For me this this error is happening when
closing the lid. See few entries before crash (reverse order):
pro 05 19:19:35 hermes org.gnome.Shell.desktop[1245]: #0 7ffead301600 b
resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f08f96cc040 @
pro
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.