GNOME extensions disabled after second login

Since GNOME 45 (Wayland) now and then, all GNOME-Shell-Extensions are disabled. When I log in, the system falls back to a forced second log in. Seems that some problems with extensions have been detected. After the second log in, all extensions are disabled. When I enable the extensions again, everything works fine. Even when I disable all extensions except of Dash-to-Panel, this effect happens after every second, third or forth reboot.

Same here.

This sounds quite like an extension-specific issue, because of what you meantioned, it could be dash-to-panel. What you could try is to remove the extension, which you probably installed via the repos (or came preinstalled) and install the newest version from extensions.gnome.org. There was just a update yesterday, might fix your issue.

That means GNOME Shell crashed. Extensions are disabled by default when that happens.

What extensions do you have installed?

gnome-extensions-list

What do the logs show after this happens?

journalctl -b | grep gnome-shell

Also, after you login and re-enable extensions, this may also help to see what extensions are complaining:

journalctl -f -o cat /usr/bin/gnome-shell

Please post the output of the aforementioned commands using preformatted text

1 Like

These are the installed extensions:

gnome-extensions list                                                                                                      1 ✘ 
quick-settings-tweaks@qwreey
BringOutSubmenuOfPowerOffLogoutButton@pratap.fastmail.fm
tiling-assistant@leleat-on-github
color-picker@tuberry
appindicatorsupport@rgcjonas.gmail.com
apps-menu@gnome-shell-extensions.gcampax.github.com
arcmenu@arcmenu.com
auto-move-windows@gnome-shell-extensions.gcampax.github.com
custom-accent-colors@demiskp
dash-to-dock@micxgx.gmail.com
dash-to-panel@jderose9.github.com
drive-menu@gnome-shell-extensions.gcampax.github.com
forge@jmmaranan.com
gnome-ui-tune@itstime.tech
gsconnect@andyholmes.github.io
gtk4-ding@smedius.gitlab.com
launch-new-instance@gnome-shell-extensions.gcampax.github.com
legacyschemeautoswitcher@joshimukul29.gmail.com
native-window-placement@gnome-shell-extensions.gcampax.github.com
pamac-updates@manjaro.org
places-menu@gnome-shell-extensions.gcampax.github.com
screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com
space-bar@luchrioh
user-theme@gnome-shell-extensions.gcampax.github.com
window-list@gnome-shell-extensions.gcampax.github.com
windowsNavigator@gnome-shell-extensions.gcampax.github.com
workspace-indicator@gnome-shell-extensions.gcampax.github.com
x11gestures@joseexposito.github.io
light-style@gnome-shell-extensions.gcampax.github.com

Four of them are custom installations:

  • Bring out submenu of power off button
  • Color Picker
  • Quick Setting Tweaker
  • Tiling Assistant

All others are Manjaro system extensions.

Here are the first 2 minutes after boot from jctl: Nextcloud

And that is the output of journalctl -f -o cat /usr/bin/gnome-shell

Object .Gjs_ui_dateMenu_WorldClocksSection (0x563a55021110), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:384 (36b75b930d80 @ 55)
#1   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_EventsSection (0x563a550afbd0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c580 i   resource:///org/gnome/shell/ui/dateMenu.js:324 (36b75b930c40 @ 49)
#1   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:320 (36b75b930ba0 @ 238)
#2   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_EventsSection (0x563a550afbd0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c580 i   resource:///org/gnome/shell/ui/dateMenu.js:325 (36b75b930c40 @ 70)
#1   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:320 (36b75b930ba0 @ 238)
#2   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_WorldClocksSection (0x563a56a29040), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:384 (36b75b930d80 @ 55)
#1   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_EventsSection (0x563a55017bb0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c580 i   resource:///org/gnome/shell/ui/dateMenu.js:324 (36b75b930c40 @ 49)
#1   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:320 (36b75b930ba0 @ 238)
#2   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_EventsSection (0x563a55017bb0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c580 i   resource:///org/gnome/shell/ui/dateMenu.js:325 (36b75b930c40 @ 70)
#1   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:320 (36b75b930ba0 @ 238)
#2   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_WorldClocksSection (0x563a55021110), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:384 (36b75b930d80 @ 55)
#1   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_EventsSection (0x563a550afbd0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c580 i   resource:///org/gnome/shell/ui/dateMenu.js:324 (36b75b930c40 @ 49)
#1   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:320 (36b75b930ba0 @ 238)
#2   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_EventsSection (0x563a550afbd0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c580 i   resource:///org/gnome/shell/ui/dateMenu.js:325 (36b75b930c40 @ 70)
#1   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:320 (36b75b930ba0 @ 238)
#2   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)
Object .Gjs_ui_dateMenu_WorldClocksSection (0x563a56a29040), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x563a52aa25e0 ==
#0   563a52b8c4d8 i   resource:///org/gnome/shell/ui/dateMenu.js:384 (36b75b930d80 @ 55)
#1   563a52b8c448 i   resource:///org/gnome/shell/ui/init.js:21 (27f08b470ba0 @ 48)


Moderator edit: Formatting

Dash-to-Panel is a Manjaro-System-Extension which hasn’t been installed by me. The installed version is 59, which is just one version below the latest version 60. Since it is a system-extension, it should be handled by the package management (pacman, pamac), but not by me. Anyway, I forced a reinstall from pamac to version 60.1, and now it gets berserk. Let me do some checks, reboots, reinstalls. I will report later about my findings.

I don’t see anything in the logs that would suggest what caused the issue.

Which are enabled? I meant to ask that to begin with:

gnome-extensions list --enabled

Just an observation: Those two conflict as they’re both tiling extensions. I would not suggest having them both installed at the same time. One cannot toggle between them without restarting GNOME Shell / logging off, anyway.

gnome-extensions list --enabled

quick-settings-tweaks@qwreey
BringOutSubmenuOfPowerOffLogoutButton@pratap.fastmail.fm
tiling-assistant@leleat-on-github
color-picker@tuberry
appindicatorsupport@rgcjonas.gmail.com
dash-to-panel@jderose9.github.com
pamac-updates@manjaro.org

Since I’ve updated gnome-extensions info dash-to-panel@jderose9.github.com to version 60, I haven’t seen any problems. But it is still too early to give the all-clear. I will continue testing.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.