Open lpereira opened 4 years ago
Do you have xprop installed? Get gnome-shell logs with journalctl /usr/bin/gnome-shell
to diagnose why it's crashing.
It looks like the same I encountered today, on Pop but not Arch, and on reboot. Removed the .local extension but I do not see this behavior after removing:
However, the top bar is black on white (rather than white on black), the hot corner on the top-left isn't active anymore (and toggling the checkbox in Gnome Tweak tool doesn't seem to have any effect), etc, even though the extension isn't active.
Everything seems to be back to normal.
The "black on white" changes were because I had selected the GNOME Classic session when the normal session was crashing and forgot about it.
Anyway, here's part of the logs as requested. I do have xprop, although this is a Wayland session. This is a new session that crashed and not the one that was active and crashed when building/enabling it:
Aug 27 08:17:50 sleeper gnome-shell[28901]: GNOME Shell started at Thu Aug 27 2020 08:17:48 GMT-0700 (Pacific Daylight Time)
Aug 27 08:17:50 sleeper gnome-shell[28901]: Registering session with GDM
Aug 27 08:17:56 sleeper gnome-shell[28901]: Window manager warning: Overwriting existing binding of keysym 76 with keysym 76 (keycode 37).
Aug 27 08:18:01 sleeper gnome-shell[28901]: ../mutter/clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implem>
Aug 27 08:18:06 sleeper gnome-shell[28901]: JS WARNING: [resource:///org/gnome/shell/ui/overview.js 170]: reference to undefined property "_visibleTarget"
Aug 27 08:18:08 sleeper gnome-shell[28901]: JS WARNING: [resource:///org/gnome/shell/ui/overview.js 162]: reference to undefined property "_animationInProgress"
Aug 27 08:18:34 sleeper gnome-shell[28901]: Window manager warning: Overwriting existing binding of keysym 76 with keysym 76 (keycode 37).
Aug 27 08:18:52 sleeper gnome-shell[28901]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00084
Aug 27 08:32:04 sleeper gnome-shell[28901]: Usage of object.actor is deprecated for EasyScreenCast.indicator
get@resource:///org/gnome/shell/ui/environment.js:287:29
_disable@/home/leandro/.local/share/gnome-shell/extensions/EasyScreenCast@iacopodeenosee.gmail.com/extension.js:640:9
wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27
disable@/home/leandro/.local/share/gnome-shell/extensions/EasyScreenCast@iacopodeenosee.gmail.com/extension.js:1044:19
_callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:107:32
_onEnabledExtensionsChanged/<@resource:///org/gnome/shell/ui/extensionSystem.js:500:18
_onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:499:21
Aug 27 08:32:30 sleeper gnome-shell[28901]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x160000d
Aug 27 08:32:47 sleeper gnome-shell[28901]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 14
Aug 27 08:32:47 sleeper gnome-shell[28901]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 14
Aug 27 08:32:49 sleeper gnome-shell[28901]: gnome-shell: Fatal IO error 0 (Success) on X server :0.
I've since disabled EasyScreenCast, as there are lots of warnings of it using deprecated properties and whatnot (and I wasn't really using it that much anyway).
I've since tried enabling this extension again, and while GNOME Shell crashed while being enabled for the first time, I was able to log in a second time. The extension seems to be working just fine.
Also getting this. Perhaps it has to do with the new Gnome 3.38? I'm running in my Gnome Classic right now because Gnome completely barfed.
Here are some log entries that stuck out at me:
JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1590:32
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1560:39
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:233:16
Sep 30 18:50:20 steelhead gnome-shell[24635]: JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1590:32
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1560:39
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:233:16
Distribution (run
cat /etc/os-release
): Arch Linux, GNOME Shell 3.36.5Related Application and/or Package Version (run
apt policy pop-shell
or provide the latest commit if building locally): HEAD was at 841632872d77abc3c45cd13540ffae755839655aIssue/Bug Description:
When running the
./rebuild.sh
script, things seemed to go smoothly, until the session crashed without any warning. Trying to log in was not possible, I would go back to GDM. I removed the extension directory from ~/.local, and I can log in again.However, the top bar is black on white (rather than white on black), the hot corner on the top-left isn't active anymore (and toggling the checkbox in Gnome Tweak tool doesn't seem to have any effect), etc, even though the extension isn't active.
Steps to reproduce (if you know): Run rebuild.sh.
Expected behavior: Extension be enabled and not crash the session. Being able to log in. Hot corners and non-shortcut-related settings to not be touched (or at least a warning in the rebuild script).
Other Notes: