Debugging GNOME Extensions

Hi guys,

I recently experience a crash whilst I was updating some of my gnome extensions. Somehow (don’t ask me how) this crashed my entire system and stopped my kernel from loading properly. Luckily I was able to fix the issue, but I have to keep all GNOME extensions disabled. Enabling them causes me DE (I think) to crash, and I have to do a full reboot, login via the terminal and disable all extensions and systemctl restart gdm. I already removed all the extensions that I installed manually but this also happens for the ‘build in’ extensions.

My question is, is there a way that I could debug this? Or at least enable all extensions in their disabled state so I can check which one is causing the issues? Or perhaps force a reinstall/update of all my extensions? I know I could always just delete them all but I’d like to avoid that if possible.

Thanks in advance!

First make sure that you don’t have any pending updates by :

sudo pacman-mirrors -f 5 && sudo pacman -Syyu

I don’t exactly understand what you mean by this. But, if you want to disable specific extensions, you could do the following.

To list all gnome extensions :

gnome-extensions list

To disable a particular extension (for example arcmenu@arcmenu.com):

gnome-extensions disable arcmenu@arcmenu.com

To re-enable:

gnome-extensions enable arcmenu@arcmenu.com

Thanks for your reply! Sorry if my description was a bit confusing what I meant was something similar to running

gsettings set org.gnome.shell disable-user-extensions false

but forcing all extensions to be toggled off. Right now I cannot even enable gnome extensions at all since it immediatly crashes.

Sorry if you have already tried this, but I would :

  1. Go into TTY

  2. Assuming the Extensions itself is enabled, I would list and disable all extensions one by one as given in my previous reply.

  3. Restart, login to your desktop and enable the extensions one by one to find the culprit.

(This is of course on the assumption that the Extensions app itself is not the culprit)

Also can you can check for errors using the command:

journalctl -b 0 -p err

Change 0 to 1 to get errors related to previous boot.

Yes it seems that maybe the extensions app itself might be the issue. As soon as I toggle this button:
Screenshot from 2021-09-30 09-56-16
GNOME immediatly crashes…

But perhaps with this command I will be able to figure out witch extension causes the crash. I will give it a try later today and report my findings. Thank you :slight_smile:

I kind of put this off for a while, but here is the output that I received:

Oct 07 09:36:00 benedikt-latitude3410 kernel: cgroup2: Unknown parameter 'memory_recursiveprot'
Oct 07 09:36:01 benedikt-latitude3410 kernel: proc: Bad value for 'hidepid'
Oct 07 09:36:01 benedikt-latitude3410 kernel: proc: Bad value for 'hidepid'
Oct 07 09:36:01 benedikt-latitude3410 kernel: proc: Bad value for 'hidepid'
Oct 07 09:36:02 benedikt-latitude3410 wpa_supplicant[973]: nl80211: kernel reports: Attribute failed policy validation
Oct 07 09:36:02 benedikt-latitude3410 wpa_supplicant[973]: Failed to create interface p2p-dev-wlp0s20f3: -22 (Invalid argument)
Oct 07 09:36:02 benedikt-latitude3410 wpa_supplicant[973]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp0s20f3
Oct 07 09:36:04 benedikt-latitude3410 bluetoothd[979]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Unknown Command (0x01)
Oct 07 09:36:04 benedikt-latitude3410 kernel: proc: Bad value for 'hidepid'
Oct 07 09:36:04 benedikt-latitude3410 wpa_supplicant[973]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Oct 07 09:36:04 benedikt-latitude3410 wpa_supplicant[973]: dbus: Failed to construct signal
Oct 07 09:36:07 benedikt-latitude3410 wpa_supplicant[973]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Oct 07 09:36:07 benedikt-latitude3410 wpa_supplicant[973]: dbus: Failed to construct signal
Oct 07 09:36:07 benedikt-latitude3410 wpa_supplicant[973]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Oct 07 09:36:07 benedikt-latitude3410 wpa_supplicant[973]: dbus: Failed to construct signal
Oct 07 09:36:07 benedikt-latitude3410 kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Oct 07 09:36:08 benedikt-latitude3410 kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Oct 07 09:36:08 benedikt-latitude3410 kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Oct 07 09:36:08 benedikt-latitude3410 kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Oct 07 09:36:08 benedikt-latitude3410 kernel: iwlwifi 0000:00:14.3: No beacon heard and the time event is over already...
Oct 07 09:36:10 benedikt-latitude3410 kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Oct 07 09:41:02 benedikt-latitude3410 gdm-launch-environment][716]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct 07 09:41:04 benedikt-latitude3410 kernel: proc: Bad value for 'hidepid'
Oct 07 09:41:05 benedikt-latitude3410 kernel: proc: Bad value for 'hidepid'
Oct 07 09:41:19 benedikt-latitude3410 gdm-password][2836]: gkr-pam: unable to locate daemon control file
Oct 07 09:41:29 benedikt-latitude3410 gdm-launch-environment][2553]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Oct 07 09:41:34 benedikt-latitude3410 kernel: proc: Bad value for 'hidepid'

And the previous boot:

Jun 15 13:11:29 benedikt-latitude3410 kernel: Bluetooth: hci0: advertising data len corrected 20 -> 19
Jun 15 13:11:30 benedikt-latitude3410 kernel: Bluetooth: hci0: advertising data len corrected 20 -> 19
Jun 15 13:11:30 benedikt-latitude3410 kernel: Bluetooth: hci0: advertising data len corrected 20 -> 19
Jun 15 13:11:30 benedikt-latitude3410 kernel: Bluetooth: hci0: advertising data len corrected 20 -> 19
Jun 15 13:11:31 benedikt-latitude3410 kernel: Bluetooth: hci0: advertising data len corrected 20 -> 19
Jun 15 13:11:34 benedikt-latitude3410 kernel: Bluetooth: hci0: advertising data len corrected 20 -> 19
Jun 15 13:11:57 benedikt-latitude3410 kernel: Bluetooth: hci0: advertising data len corrected 20 -> 19
Jun 16 08:30:32 benedikt-latitude3410 kernel: usb 1-2: 1:1: cannot get freq at ep 0x81
Jun 16 08:30:32 benedikt-latitude3410 kernel: usb 1-2: 4:1: cannot get freq at ep 0x2
Jun 16 08:30:32 benedikt-latitude3410 kernel: usb 1-2: 1:1: cannot get freq at ep 0x81
Jun 16 11:02:50 benedikt-latitude3410 kernel: Out of memory: Killed process 38258 (spotify) total-vm:14585444kB, anon-rss:311208kB, file-rss:0kB, shmem-rss:784kB, UID:1000 pgtables:2240kB oom_score_adj:300
Jun 16 11:14:40 benedikt-latitude3410 gdm[894]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
Jun 16 11:14:40 benedikt-latitude3410 systemd-coredump[196010]: Failed to connect to coredump service: Connection refused
Jun 16 11:14:45 benedikt-latitude3410 systemd-coredump[196451]: Failed to connect to coredump service: Connection refused
Jun 16 11:16:10 benedikt-latitude3410 systemd-cryptsetup[196459]: Device luks-e5c29191-0c87-43e9-bc95-0b67ef689310 is still in use.
Jun 16 11:16:10 benedikt-latitude3410 systemd-cryptsetup[196459]: Failed to deactivate: Device or resource busy
Jun 16 11:16:10 benedikt-latitude3410 kernel: watchdog: watchdog0: watchdog did not stop!

Any idea what this could mean?

It’s probably also worth mentioning that I have created a seperate admin user and the extensions work perfectly.