Daniel, not sure if they're related, but it seems that when I get back from the "slide" screen (even if not locked) I'm getting a lot of these errors repeated in journalctl:
May 24 14:52:47 kashyyyk gnome-shell[6901]: Object Meta.Background (0x562f8156e590), 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 May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: == Stack trace for context 0x562f7ecee330 == May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #0 0x7ffe191266b0 b resource:///org/gnome/shell/ui/background.js:718 (0x7f7fbc60f450 @ 22) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #1 0x7ffe19127610 b resource:///org/gnome/shell/ui/tweener.js:113 (0x7f7fc81c7e68 @ 37) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #2 0x7ffe19128580 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f7fc81d3b38 @ 54) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #3 0x7ffe191286d0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f7fc81d3bc0 @ 1626) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #4 0x7ffe19128780 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f7fc81d3c48 @ 100) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #5 0x7ffe19128810 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f7fc81d3cd0 @ 10) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #6 0x7ffe19128900 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f7fc81d3230 @ 386) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #7 0x7ffe191289b0 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7f7fc81cf808 @ 159) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #8 0x7ffe19128a10 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f7fc81b5de0 @ 71) May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #9 0x7ffe19128ab0 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7f7fc81cf780 @ 15) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769981 Title: Temporary screen freeze when coming back from screen standby Status in gnome-shell package in Ubuntu: Incomplete Bug description: When waking up the PC screen from standby, quite often the screen freezes for 10-20s. I can't move the mouse or type anything. After a while, it unfreezes. This is quite annoying because often the freeze is long enough to send the screen to standby again for absence of singal, so then I have to wake it up and wait again. This is not 100% reproducible but happens very frequently, both when the screen is locked and when it's not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 8 20:26:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-25 (72 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
