@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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1718850 Title: Mode extensions appear off by default Status in Release Notes for Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-tweaks package in Ubuntu: Triaged Bug description: Go to the Extensions panel in Tweaks. System extensions (dock and appindicators) appear off by default, where they are obviously not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-tweak-tool 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 08:02:59 2017 ExecutablePath: /usr/bin/gnome-tweak-tool InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2 SourcePackage: gnome-tweak-tool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1718850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp