Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

unclickable tab on windowlist applet #1147

leigh123linux opened this Issue Sep 18, 2012 · 3 comments


None yet
3 participants

leigh123linux commented Sep 18, 2012

I have a gnome-terminal tab on the windowlist that is unclickable, the 3 other gnome-terminal tabs are unaffected. here's the error

(cinnamon:1376): St-CRITICAL **: st_widget_get_theme_node called on the widget [0x56fd410 StBin.popup-menu-boxpointer popup-menu] which is not in the stage.
JS ERROR: !!! Exception was: TypeError: themeNode is null
JS ERROR: !!! lineNumber = '87'
JS ERROR: !!! fileName = '"/usr/share/cinnamon/js/ui/boxpointer.js"'
JS ERROR: !!! stack = '"(true)@/usr/share/cinnamon/js/ui/boxpointer.js:87
([object _private_St_Bin],[object _private_Clutter_Event])@/usr/share/cinnamon/applets/window-list@cinnamon.org/applet.js:429
JS ERROR: !!! message = '"themeNode is null"'


leigh123linux commented Sep 18, 2012

The "close this terminal" dialog caused the issue. once the window is covered it's lost, no left or right click on the windowlist , you have to minimize all other windows to get to it back.

If you dismiss the dialog a few times times it triggers the unclickable tab on windowlist applet

rjanja pushed a commit to rjanja/Cinnamon that referenced this issue Oct 4, 2012


rjanja commented Oct 4, 2012

To repro:

  • Open a terminal and run a command which does not return (e.g. yes).
  • Right-click applet button in window list, select "Close".

The dialog leigh123linux mentioned pops up confirming whether you'd like to close the terminal.
When you see the dialog, the right-click menu has already been deleted and can no longer be accessed no matter which action you take in the dialog.


autarkper commented Apr 26, 2013

Should be fixed by #1295, can be tested in current master and in the upcoming Cinnamon 1.8.

@autarkper autarkper closed this Apr 27, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment