"bash: cannot set terminal process group (-1): Inappropriate ioctl for device" when open Visual Studio Code integrated terminal

[ghost]

Linux distribution and kernel version

Arch Linux x86_64
5.17.7-arch1-1

Flatpak version

Flatpak 1.12.7

Description of the problem

When I configure the integrated terminal according to the flatpak_warning.txt in the config file located in ~/.var/app/com.visualstudio.code/config/Code/User/settings.json

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

I get the following message every time I open the integrated terminal

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

[nikodunk]

I get this too but the terminal works just fine. Does your terminal work?

[tinywrkb]

You need a new pty to avoid the controlling terminal issue. This can be achieved with script.

"terminal.integrated.profiles.linux": {
  "Host: Bash (new pty)": {
    "path": "/usr/bin/flatpak-spawn",
    "args": ["--env=TERM=vscode", "--host", "script", "--quiet", "/dev/null"]
  },
  "Host: ZSH (new pty)": {
    "path": "/usr/bin/flatpak-spawn",
    "args": ["--env=TERM=vscode", "--env=SHELL=zsh", "--host", "script", "--quiet", "/dev/null"]
  }
}

[tinywrkb]

host-spawn is even better.

[ferrybig]

You need a new pty to avoid the controlling terminal issue. This can be achieved with script.

"terminal.integrated.profiles.linux": {
  "Host: Bash (new pty)": {
    "path": "/usr/bin/flatpak-spawn",
    "args": ["--env=TERM=vscode", "--host", "script", "--quiet", "/dev/null"]
  },
  "Host: ZSH (new pty)": {
    "path": "/usr/bin/flatpak-spawn",
    "args": ["--env=TERM=vscode", "--env=SHELL=zsh", "--host", "script", "--quiet", "/dev/null"]
  }
}

For some reason, your solution makes the /usr/bin directory different in the spawned shell, compared to the hosts /usr/bin directory, so not every command works

[fiantyogalihp]

You need a new pty to avoid the controlling terminal issue. This can be achieved with script.

"terminal.integrated.profiles.linux": {
  "Host: Bash (new pty)": {
    "path": "/usr/bin/flatpak-spawn",
    "args": ["--env=TERM=vscode", "--host", "script", "--quiet", "/dev/null"]
  },
  "Host: ZSH (new pty)": {
    "path": "/usr/bin/flatpak-spawn",
    "args": ["--env=TERM=vscode", "--env=SHELL=zsh", "--host", "script", "--quiet", "/dev/null"]
  }
}

the issue is fixed, but can't run some command properly

[kramfs]

host-spawn is even better.

I concur, host-spawn is a better solution. Here's a simple config:

    "terminal.integrated.defaultProfile.linux": "bash",
    "terminal.integrated.profiles.linux": {
        "bash": {
          "path": "/var/home/kramfs/.local/bin/host-spawn",
          "icon": "terminal"
        }
    }