flatpak installed vscode's integrated terminal not having desired behaviour #44

mundusnine · 2018-08-25T15:05:37Z

Linux distribution and version

Debian 9 strecth

Flatpak version

Flatpak 0.8.9

Description of the problem

microsoft/vscode-cpptools#1550
The fact that the app is virtualized makes it so that you can't run : flatpak run org.godotengine.Godot
or any flatpak command in the integrated terminal of vscode. You can't also use gnome-terminal as your integrated terminal in vscode because of this. This makes it also troublesome when trying to use external apps that are used by the extensions.(i.e. My haxe extensions in vscode can't find haxe in my path even though it is installed).

Haxe is available in /usr/bin/ so I guess vscode should detect it.

Steps to reproduce

Install vscode with flatpak
use the integrated terminal of vscode(try with sh/bash) and call flatpak list

Potential solution:

Adding --filesystem=/bin/ access to vscode ? Are there any reasons for not doing this ? What would be the work around.

mundusnine · 2018-08-25T18:27:06Z

Probably the real issue

Ok so I found out that the installation of Vscode considers only some apps in the /usr/bin/*.

So if you do in the integrated terminal of vscode:

which g++
which bash 
which python

It will work. But if you do:

which gnome-terminal
which haxe

It won't work saying no gnome-terminal in (/app/bin:/usr/bin:/home/jsnadeau/.var/app/com.visualstudio.code/data/node_modules/bin)

This behavior seems weird. I thought at first that it could be because haxe is a x-sharedlib but python is the same and it works.

Does the manifest determine what apps from usr/bin/ can be added ? Is there a way to tell it to use everything or just some apps.(looked in the docs and doesn't seem so)

barthalion · 2018-08-25T20:04:22Z

The main feature of Flatpak is sandboxing and there is no way to disable it. /usr and /bin you see in the integrated terminal come from Sdk, not your own system. If you pass --talk-name=org.freedesktop.Flatpak you can spawn commands on host with flatpak-spawn --host.

mundusnine · 2018-08-25T20:21:34Z

So how can vscode-extensions use outside components ? I talked about haxe but vscode can't use pylint either since it's limited to what is present in the Sdk.

Setting their path in the user settings doesn't work either.

allo- · 2018-09-14T17:11:58Z

The main feature of Flatpak is sandboxing and there is no way to disable it. /usr and /bin you see in the integrated terminal come from Sdk, not your own system.
How do I install stuff into the sandboxed /usr? Is there something like

flatpak add-to-sandbox com.visualstudio.code org.gnome.gnome-terminal # add gnome terminal package to the vscode sandbox

possible?

TingPing · 2018-09-14T19:36:36Z

@allo- No, they could have conflicting files.

allo- · 2018-09-14T20:04:17Z

Is there another way to get vscode to work? Internal terminal doesn't seem to be usable for debugging and whitelisting /usr isn't visible inside the jail. At least putting an xterm inside would be helpful.

TingPing · 2018-09-14T20:06:47Z

For the terminal to run on the host requires modifications to how the terminal works.

allo- · 2018-09-14T20:08:04Z

I guess running inside the jail would be the nicer solution, but for the moment I would like anything which allows me to test vscode with gdb debugging (Compiling a sample project and then pressing F5 should work ;-)).

TingPing · 2018-09-14T20:26:49Z

Well gdb is already in the SDK, but ofc that is only useful if you compile software against the SDK.

Really IDEs just need to be designed to be sandbox friendly which I know isn't helpful now.

danielfm123 · 2018-11-03T02:21:55Z

For developing is better to use snap IDEs like visual studio or pycharm.

thiblahute · 2019-07-24T03:06:28Z

For reference, I am using fedora silverblue with toolbox and I added the following to my settings:

    "terminal.integrated.shellArgs.linux": [
        "/var/home/thiblahute/bin/my-devtools/vscode-enter"
    ],

where the vscode-enter script contains:

#!/bin/sh

flatpak-spawn --host toolbox enter

This actually works pretty well for me :-)

Ablu · 2019-12-25T22:14:40Z

This actually works pretty well for me :-)

    "terminal.integrated.shell.linux": "flatpak-spawn",
    "terminal.integrated.shellArgs.linux": [
        "--host",
        "toolbox",
        "run",
        "bash"
    ],

^ that is a bit more robust for me. But the shell spawning time is really bad...

Iolaum · 2020-09-06T20:12:12Z

@thiblahute @Ablu Where/How did you add those settings? I am getting weird behaviour in flatpak VSCode terminal as well.

Iolaum · 2020-09-06T20:22:41Z

After looking at it a little more, I think the above settings are described here.

marquesmateus93 · 2021-11-20T14:24:40Z

Just to improve your tip, @Ablu :

File > Preferences > Configuration
In search bar, type "terminal"
Look up in results for "Terminal › Integrated › Automation Shell: Linux"
Click in "Edit settings.json"
Then replace the .json file content to:

{
    "terminal.integrated.shell.linux": "flatpak-spawn",
    "terminal.integrated.shellArgs.linux":[
        "--host",
        "toolbox",
        "run",
        "bash"
    ],
}

UniversalSuperBox · 2021-11-26T19:45:12Z

vscode is now deprecating the terminal.integrated.shell.linux setting in exchange for terminal profiles. Here is how you can configure a flatpak escape profile:

    "terminal.integrated.profiles.linux": {
        "Flatpak Escape": {
            "path": "flatpak-spawn",
            "args": [
                "--host",
                "toolbox",
                "run",
                "bash"
            ],
        }
      },
      "terminal.integrated.defaultProfile.linux": "Flatpak Escape"

YuvanNeko · 2021-12-09T01:10:32Z

vscode is now deprecating the terminal.integrated.shell.linux setting in exchange for terminal profiles. Here is how you can configure a flatpak escape profile:

    "terminal.integrated.profiles.linux": {
        "Flatpak Escape": {
            "path": "flatpak-spawn",
            "args": [
                "--host",
                "toolbox",
                "run",
                "bash"
            ],
        }
      },
      "terminal.integrated.defaultProfile.linux": "Flatpak Escape"

It says end of the file expected.

UniversalSuperBox · 2021-12-09T14:34:38Z

It says end of the file expected.

Check your JSON syntax. You might need a comma before or after the block you've pasted into your config file.

vwalek · 2022-02-20T05:21:28Z

I use this:

    "terminal.integrated.profiles.linux": {
        "BASH": {
          "path": "/usr/bin/flatpak-spawn",
          "args": ["--host", "--env=TERM=xterm-256color", "bash"]
        },
        "ZSHELL": {
          "path": "/usr/bin/flatpak-spawn",
          "args": ["--host", "--env=TERM=xterm-256color", "zsh"]
        },
        "Flatpak": {
          "path": "/bin/bash"
        }
    },

The zshell works out of the box with themes, just colors are little of (especially yellow). I also run flatpak bash to get into the isolated env. Hope it help ;)

//update
However, VSCode version 1.64 - on flatpak, has issues with default profiles. Works on 1.63.

cengiz7 · 2022-03-07T11:57:06Z

After 1 day, here is my working solution for ZSH shell on Elementary OS 6

"terminal.integrated.shell.linux": "/usr/bin/env",
"terminal.integrated.shellArgs.linux": ["flatpak-spawn", "--host", "--env=TERM=xterm-256color", "zsh"],
"terminal.integrated.fontFamily": "MesloLGS NF, Regular",

Nightfirecat · 2022-04-21T22:53:20Z

The recommendation of using terminal.integrated.defaultProfile.linux paired with a profile definition does not work for me. I've recently installed the flatpak on Debian 11, and adding the following to settings.json did nothing:

"terminal.integrated.defaultProfile.linux": "bash",
"terminal.integrated.profiles.linux": {
    "bash": {
      "path": "/usr/bin/flatpak-spawn",
      "args": ["--host", "--env=TERM=xterm-256color", "bash"]
    },
},

Launching a terminal still brought up a sh terminal, and there were no options available when running the "Terminal: Select Default Profile" command.

The only thing which did work was adding:

"terminal.integrated.shell.linux": "/bin/bash",

I'm not satisfied with that, though, since this is deprecated. I'd like to get the more future-proof profile method working if possible.

Iolaum · 2022-04-22T09:28:23Z

For what it's worth the "solution" I m using now is to spawn the terminal and manually run the appropriate flatpak-spawn command. Not a proper fix but better than nothing.

vwalek · 2022-04-22T17:28:54Z

The recommendation of using terminal.integrated.defaultProfile.linux paired with a profile definition does not work for me. I've recently installed the flatpak on Debian 11, and adding the following to settings.json did nothing:
"terminal.integrated.defaultProfile.linux": "bash",
"terminal.integrated.profiles.linux": {
    "bash": {
      "path": "/usr/bin/flatpak-spawn",
      "args": ["--host", "--env=TERM=xterm-256color", "bash"]
    },
},
Launching a terminal still brought up a sh terminal, and there were no options available when running the "Terminal: Select Default Profile" command.

The only thing which did work was adding:
"terminal.integrated.shell.linux": "/bin/bash",
I'm not satisfied with that, though, since this is deprecated. I'd like to get the more future-proof profile method working if possible.

What version are you running? There is issue with newer versions, 1.64+.

Nightfirecat · 2022-04-22T17:41:41Z

I'm on version 1.66.1, so I suppose that would be affected.

vwalek · 2022-04-22T17:53:07Z

I'm on version 1.66.1, so I suppose that would be affected.

Yeah, seems like the 1.66 doesn't even start the default profiles at all.

Running manually the spawn, it works.

Nightfirecat · 2022-05-06T18:53:57Z

I was experiencing #288, which was fixed in #309. I'm now able to remove the terinal.integrated.shell.linux line and use the profile definition without issue.

sigmaSd · 2023-10-14T07:39:58Z

This is what worked for me #315 (comment)

frknltrk · 2024-10-18T06:30:18Z

EDIT (21/01/2025)
Better solution: #44 (comment)

I've had the same issue of some commands not recognized by integrated terminal in VSCodium (Flatpak) on Linux Mint. Try adding the below key-value pairs to your settings.json (Manage > Settings > Open Settings (JSON))

    {
        "terminal.integrated.defaultProfile.linux": "bash",
        "terminal.integrated.env.linux": {
            "PATH": "/run/host/bin:/run/host/usr/bin"
        }
    }

Path Format:

'/run/host/' + '/some/path/to/somewhere'

Paths are separated by ':'

You may want to run echo $PATH in your external (built-in) terminal to explore the PATHs set.

Reference: https://www.reddit.com/r/flatpak/comments/lm2lln/comment/gntpr80/

andrew-ma · 2025-01-20T01:01:59Z

REFERENCE: https://github.com/flathub/com.vscodium.codium/blob/master/README.md#host-shell

barthalion closed this as completed Aug 25, 2018

NeroVanbiervliet mentioned this issue Nov 19, 2018

Wrong python binary is used microsoft/vscode-python#3229

Closed

DanMan mentioned this issue Aug 5, 2019

Can't find Haxe exec in PATH using VSC Flatpak vshaxe/vshaxe#367

Closed

Iolaum mentioned this issue Oct 18, 2020

Error when using extension in flatpak'd vscodium LaurentTreguier/vscode-rpm-spec#6

Open

godalming123 mentioned this issue Mar 19, 2022

[flatpak] Warning when using integrated terminal as some commands do not work microsoft/vscode#145443

Closed

be-rock mentioned this issue Aug 28, 2022

Pop!_OS (ubuntu debian) - default shell zsh not working microsoft/vscode#159200

Closed

frknltrk mentioned this issue Oct 18, 2024

dvilualatex: command not found when running with VSCodium in Flatpak sandbox matjp/latex-preview#3

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

flatpak installed vscode's integrated terminal not having desired behaviour #44

flatpak installed vscode's integrated terminal not having desired behaviour #44

mundusnine commented Aug 25, 2018 •

edited

Loading

mundusnine commented Aug 25, 2018

barthalion commented Aug 25, 2018

mundusnine commented Aug 25, 2018 •

edited

Loading

allo- commented Sep 14, 2018

TingPing commented Sep 14, 2018

allo- commented Sep 14, 2018

TingPing commented Sep 14, 2018

allo- commented Sep 14, 2018

TingPing commented Sep 14, 2018

danielfm123 commented Nov 3, 2018

thiblahute commented Jul 24, 2019

Ablu commented Dec 25, 2019 •

edited

Loading

Iolaum commented Sep 6, 2020

Iolaum commented Sep 6, 2020

marquesmateus93 commented Nov 20, 2021

UniversalSuperBox commented Nov 26, 2021

YuvanNeko commented Dec 9, 2021 •

edited

Loading

UniversalSuperBox commented Dec 9, 2021

vwalek commented Feb 20, 2022 •

edited

Loading

cengiz7 commented Mar 7, 2022

Nightfirecat commented Apr 21, 2022

Iolaum commented Apr 22, 2022 •

edited

Loading

vwalek commented Apr 22, 2022

Nightfirecat commented Apr 22, 2022

vwalek commented Apr 22, 2022

Nightfirecat commented May 6, 2022

sigmaSd commented Oct 14, 2023

frknltrk commented Oct 18, 2024 •

edited

Loading

andrew-ma commented Jan 20, 2025

flatpak installed vscode's integrated terminal not having desired behaviour #44

flatpak installed vscode's integrated terminal not having desired behaviour #44

Comments

mundusnine commented Aug 25, 2018 • edited Loading

Linux distribution and version

Flatpak version

Description of the problem

Steps to reproduce

Potential solution:

mundusnine commented Aug 25, 2018

Probably the real issue

barthalion commented Aug 25, 2018

mundusnine commented Aug 25, 2018 • edited Loading

allo- commented Sep 14, 2018

TingPing commented Sep 14, 2018

allo- commented Sep 14, 2018

TingPing commented Sep 14, 2018

allo- commented Sep 14, 2018

TingPing commented Sep 14, 2018

danielfm123 commented Nov 3, 2018

thiblahute commented Jul 24, 2019

Ablu commented Dec 25, 2019 • edited Loading

Iolaum commented Sep 6, 2020

Iolaum commented Sep 6, 2020

marquesmateus93 commented Nov 20, 2021

UniversalSuperBox commented Nov 26, 2021

YuvanNeko commented Dec 9, 2021 • edited Loading

UniversalSuperBox commented Dec 9, 2021

vwalek commented Feb 20, 2022 • edited Loading

cengiz7 commented Mar 7, 2022

Nightfirecat commented Apr 21, 2022

Iolaum commented Apr 22, 2022 • edited Loading

vwalek commented Apr 22, 2022

Nightfirecat commented Apr 22, 2022

vwalek commented Apr 22, 2022

Nightfirecat commented May 6, 2022

sigmaSd commented Oct 14, 2023

frknltrk commented Oct 18, 2024 • edited Loading

EDIT (21/01/2025) Better solution: #44 (comment)

andrew-ma commented Jan 20, 2025

mundusnine commented Aug 25, 2018 •

edited

Loading

mundusnine commented Aug 25, 2018 •

edited

Loading

Ablu commented Dec 25, 2019 •

edited

Loading

YuvanNeko commented Dec 9, 2021 •

edited

Loading

vwalek commented Feb 20, 2022 •

edited

Loading

Iolaum commented Apr 22, 2022 •

edited

Loading

frknltrk commented Oct 18, 2024 •

edited

Loading

EDIT (21/01/2025)
Better solution: #44 (comment)