workspaces-to-dock
workspaces-to-dock copied to clipboard
passingthru67
Problems in Debian Stretch
Linux Distribution version
Debian Stretch 9.1
Gnome Shell version
3.22.3
Extension version or branch
Current (I’m not at work anymore)
Description of the problem
In gnome-tweak-tool, I can’t de- or reactivate it, because I get „Error“ sign displayed instead of a switch – but somehow the shell extension works fine and I can use the settings config, too. Looking glass displays:
Error: No signal 'size-changed' on object 'ShellWM'
TypeError: intellihide is undefined
Steps to reproduce the problem
Install vanilla Debian 9.1 and WTD.
// journalctl tells me:
<WDT-ID> had error: Error: No signal 'size-changed' on object 'ShellWM'
st_widget_get_theme_node called on the widget [0x55ddad6573b0 StBin::insensitive] which is not in the stage.
st_widget_get_theme_node called on the widget [0x55ddad6573b0 StBin::insensitive] which is not in the stage.
But I’m not sure if the two following lines are due to WTD or something else, they’re not shown in LG.
That's strange to get an error and yet have the extension work just fine. Do you have any other extensions installed?
On my vanilla Debian Stretch 9.1 VM the extension (v40) seems to work fine. I can deactivate and reactivate the extension (v40) without any problem.
However, journalctl complains that the method get_theme_node is called on a St.Widget based widget:
Sep 22 20:33:44 stretch gnome-shell[1014]: st_widget_get_theme_node called on the widget [0x55ab0101ca60 StBin:insensitive] which is not in the stage.
Sep 22 20:33:44 stretch gnome-shell[1014]: st_widget_get_theme_node called on the widget [0x55ab0101ca60 StBin:insensitive] which is not in the stage.
Sep 22 20:36:51 stretch gnome-shell[1014]: /build/glib2.0-B1uXKV/glib2.0-2.50.3/./gobject/gsignal.c:2641: instance '0x55ab04e03d20' has no handler with id '30333'
Sep 22 20:36:54 stretch gnome-shell[1014]: st_widget_get_theme_node called on the widget [0x55ab0220bc60 StBin:insensitive] which is not in the stage.
Sep 22 20:36:54 stretch gnome-shell[1014]: st_widget_get_theme_node called on the widget [0x55ab0220bc60 StBin:insensitive] which is not in the stage.
Sep 22 20:36:56 stretch gnome-shell[1014]: /build/glib2.0-B1uXKV/glib2.0-2.50.3/./gobject/gsignal.c:2641: instance '0x55ab05544830' has no handler with id '50308'
Sep 22 20:36:57 stretch gnome-shell[1014]: st_widget_get_theme_node called on the widget [0x55ab04734d60 StBin:insensitive] which is not in the stage.
Sep 22 20:36:57 stretch gnome-shell[1014]: st_widget_get_theme_node called on the widget [0x55ab04734d60 StBin:insensitive] which is not in the stage.
Sep 22 20:41:47 stretch gnome-shell[1014]: /build/glib2.0-B1uXKV/glib2.0-2.50.3/./gobject/gsignal.c:2641: instance '0x55ab04fb0610' has no handler with id '53002'
But I don't think this log message is related to the mentioned problem here.
Do the journal messages go away when the extension is disabled and gnome-shell is restarted (assuming you're using Xorg).
I have the same Problem. Ubuntu 19.10 / GNOME 3.34 on Wayland. The extension version is the current master.
This is in my syslog:
Mar 10 13:00:14 hostname gnome-shell[12890]: st_widget_get_theme_node called on the widget [0x562c02892650 StBin:insensitive] which is not in the stage.
Mar 10 13:00:14 hostname gnome-shell[12890]: st_widget_get_theme_node called on the widget [0x562c02892650 StBin:insensitive] which is not in the stage.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: == Stack trace for context 0x562c019ce5a0 ==
Mar 10 13:00:16 hostname gnome-shell[12890]: message repeated 5 times: [ == Stack trace for context 0x562c019ce5a0 ==]
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c04320180.
Mar 10 13:00:16 hostname gnome-shell[12890]: == Stack trace for context 0x562c019ce5a0 ==
Mar 10 13:00:16 hostname gnome-shell[12890]: message repeated 4 times: [ == Stack trace for context 0x562c019ce5a0 ==]
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: == Stack trace for context 0x562c019ce5a0 ==
Mar 10 13:00:16 hostname gnome-shell[12890]: message repeated 2 times: [ == Stack trace for context 0x562c019ce5a0 ==]
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c04c00c80.
Mar 10 13:00:16 hostname gnome-shell[12890]: == Stack trace for context 0x562c019ce5a0 ==
Mar 10 13:00:16 hostname gnome-shell[12890]: == Stack trace for context 0x562c019ce5a0 ==
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c022f94d0.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c04b9d650.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c04b52e30.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c04870220.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c04c1beb0.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c0257b630.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c022d7d60.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c03d348f0.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c02a21d30.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c028eee30.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c04eff850.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c04fabb20.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c03a21bb0.
Mar 10 13:00:16 hostname gnome-shell[12890]: 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.
Mar 10 13:00:16 hostname gnome-shell[12890]: The offending signal was destroy on Gjs_BaseIcon 0x562c0453c390.
