@Jeremy I hope this warning in Ubuntu 19.10 is not a problem:-
pranav@exam:~$ gnome-shell-extension-prefs (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.409: 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. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.409: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61900. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.409: 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. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.409: The offending signal was destroy on Gjs_ExtensionRow 0x55eba4152690. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: 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. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61c00. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: 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. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61600. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: 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. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61f00. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.411: 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. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.411: The offending signal was destroy on Gjs_ExtensionRow 0x55eba4152390. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.411: 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. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.411: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61300. == Stack trace for context 0x55eba37d71a0 == pranav@exam:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718850 Title: Mode extensions appear off by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1718850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
