Right-Click Open Terminal in Gnome, SLED 15 SP2

ttrcfttrcf Established Member

We have a reasonably large number of workstations running SLED15 SP1 and SLED 15 SP2. We always use the SLE Classic option when the user logs in. When a machine is migrated form SLED15SP1 to SLED15SP2 we notice that the behavior of the right click menu on the Gnome desktop subtly changes. In SP1 there is the option on the right-click menu to 'Open Terminal' which opens a terminal in the user's home directory. In SP2 this has changed to 'Open in Terminal' which opens a terminal in the Desktop subdirectory of the user's home directory. Is there a way to restore the SP1 behavior in SP2?

Comments

  • malcolmlewismalcolmlewis Knowledge Partner

    @ttrcf Hi, Fire up GNOME tweaks and under extension Enable 'Desktop Icons' (hit the cog to configure which icons you want showing on the desktop, right click should be back.....

  • AndreasAndreas Senior Member

    This misbehavior was introduced in SLED12SP2 and is finally fixed (SLED15SP2). Have a read here:
    https://suse.com/releasenotes/x86_64/SUSE-SLED/12-SP2/#Packages.Packaging

  • ttrcfttrcf Established Member

    Still doesn't work I'm afraid. Enable desktop icons is selected but 'Open in Terminal' still goes back to the Desktop. When I run gnome-tweaks from a terminal it generates the following errors in the terminal window when I close desktop icons configuration window::

    (gnome-shell-extension-prefs:49831): Gjs-CRITICAL **: 09:49:22.517: 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:49831): Gjs-CRITICAL **: 09:49:22.517: The offending signal was destroy on Gjs_ExtensionRow 0x55b8b7d6f630.
    == Stack trace for context 0x55b8b764a1a0 ==
    
    (gnome-shell-extension-prefs:49831): Gjs-CRITICAL **: 09:49:22.517: 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:49831): Gjs-CRITICAL **: 09:49:22.517: The offending signal was destroy on Gjs_ExtensionRow 0x55b8b7f7b600.
    == Stack trace for context 0x55b8b764a1a0 ==
    
    (gnome-shell-extension-prefs:49831): Gjs-CRITICAL **: 09:49:22.517: 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:49831): Gjs-CRITICAL **: 09:49:22.517: The offending signal was destroy on Gjs_ExtensionRow 0x55b8b7f7b900.
    == Stack trace for context 0x55b8b764a1a0 ==
    
    (gnome-shell-extension-prefs:49831): Gjs-CRITICAL **: 09:49:22.517: 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:49831): Gjs-CRITICAL **: 09:49:22.517: The offending signal was destroy on Gjs_ExtensionRow 0x55b8b7d6f330.
    == Stack trace for context 0x55b8b764a1a0 ==
    
    (gnome-shell-extension-prefs:49831): Gjs-CRITICAL **: 09:49:22.517: 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:49831): Gjs-CRITICAL **: 09:49:22.517: The offending signal was destroy on Gjs_ExtensionRow 0x55b8b7d6f930.
    == Stack trace for context 0x55b8b764a1a0 ==
    
    (gnome-shell-extension-prefs:49831): Gjs-CRITICAL **: 09:49:22.518: 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:49831): Gjs-CRITICAL **: 09:49:22.518: The offending signal was destroy on Gjs_ExtensionRow 0x55b8b7d6fc30.
    == Stack trace for context 0x55b8b764a1a0 ==
    
    (gnome-shell-extension-prefs:49831): Gjs-CRITICAL **: 09:49:22.518: 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:49831): Gjs-CRITICAL **: 09:49:22.518: The offending signal was destroy on Gjs_ExtensionRow 0x55b8b7d6ff30.
    == Stack trace for context 0x55b8b764a1a0 ==
    
    (gnome-shell-extension-prefs:49831): Gjs-CRITICAL **: 09:49:22.518: 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:49831): Gjs-CRITICAL **: 09:49:22.518: The offending signal was destroy on Gjs_ExtensionRow 0x55b8b7f7b300.
    == Stack trace for context 0x55b8b764a1a0 ==
    

    ``

  • malcolmlewismalcolmlewis Knowledge Partner
    edited April 13

    @ttrcf Hi edit ~/.bashrc and add cd `pwd` or just cd then will always open in $HOME the pwd command will then allow the open terminal command to open in the browsed directory.

Sign In or Register to comment.