Upgrading to 3.34.1 broke my Gnome extensions
I just upgraded to 3.34.1 (Pop!_OS 19.10) and now my Gnome Extensions don't work. I can visit the extension web page and see the ones that I have installed but whenever I try to enable them nothing happens and when I reload the page they are all set back to disabled.
Here's the output of journalctl --user
when I try to configure the "Open Weather" extension:
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell[1879]: == Stack trace for context 0x5593152e91a0 ==
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d5db00.
Oct 25 03:48:28 pop-os gnome-shell[1879]: == Stack trace for context 0x5593152e91a0 ==
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell[1879]: == Stack trace for context 0x5593152e91a0 ==
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d5de00.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315a0b780.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315a0ba80.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d5d500.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d5d200.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d5d800.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315a0b480.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315a0b180.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d99160.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d99460.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315a0bd80.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d99760.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 25 03:48:28 pop-os gnome-shell-ext[9908]: The offending signal was destroy on Gjs_ExtensionRow 0x559315d99a60.
^C
rnhurt@pop-os:~/Downloads$ mutter --version
mutter 3.34.1
Copyright © 2001-2011 Havoc Pennington, Red Hat, Inc., and others
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
rnhurt@pop-os:~/Downloads$