Terminal not working correctly on linux/flatpak

[chrisglass]

Reproduction steps

1. On linux (Pop_OS here), install the zed flatpak version.
2. Open the terminal pane

Current vs. Expected behavior

Current behavior:
The terminal starts with a bare "sh" shell, and running any comment (e.g."ls") results in:
ls: /app/lib/libselinux.so.1: no version information available (required by ls)

Furthermore, it seems like the shell doesn't source .bashrc, neither can it find e.g. git completion or starship (in other words, it seems unable to source any of the normal system config files).

The above started happening a few days ago - it was working as expected before that (starship and bashrc loaded fine).

Expected behavior:

System shell choice loads without issues, starship (or any other system customization) are loaded.

Zed version and system specs

Zed 0.230.1
bf3a143

0.230.1+stable.210.bf3a14350a4fa4b67747afe2e50128fb8fea4fa3

Pop_OS 24.04LTS

Zed installed via flatpak

Attach Zed log file

Zed.log

Relevant Zed settings

settings.json

Relevant Keymap

keymap.json

(for AI issues) Model provider details

No response

If you are using WSL on Windows, what flavor of Linux are you using?

None

[Zoldyako]

Same issue here, I'm on Fedora 43 Workstation, same Zed version

[spuxx-dev]

Can confirm. As a termporary workaround, using flatpak-spawn works for me. In your Zed's settings.json, include:

{
  "terminal": {
    "shell": {
      "with_arguments": {
        "program": "flatpak-spawn",
        "args": [
          "--env=TERM=xterm-256color",
          "--env=COLORTERM=truecolor",
          "--host",
          "bash",
          "--login",
          "-i"
        ]
      }
    }
  },
  // ...
}

The cause appears to be Flathub's sandboxing. Zed does not have access to what it needs to from the host. Even when forcing bash in settings.json, zed does not have access to .bashrc in the user folder.

[nikothee]

Cross-referencing this issue from the flathub zed repo: flathub/dev.zed.Zed#338
Specifically this commit changed the behaviour for zed to no longer escape its sandbox: flathub/dev.zed.Zed@786c1db

[chrisglass]

For reference: I've opened a reverting branch on the flatpak packaging to fix this issue

flathub/dev.zed.Zed#343

[chrisglass]

This seems to be intended behavior according to the flatpak contributors (?!). You can explicitly disable the sandbox of your flatpak yourself with:

$ flatpak override --user --unset-env=ZED_FLATPAK_NO_ESCAPE dev.zed.Zed

Or switch to a non-flatpak version.
I personally uninstalled the flatpak version and installed Zed for linux directly instead.

I'm unsure what to do with this issue now.

[codewing]

This is so much of a hassle... I would propose a non-sandboxed version of the flatpak.. maybe we can just fork it

[chrisglass]

I don't think it's going to be productive, honestly. From the flatpak community's perspective, all flatpaks should be sandboxed by default (that's the guarantee they offer), and users can punch holes in the sandbox explicitly.

Although I regret this position (for Zed specifically), I agree their point of view is reasonable: I trust Zed personally, but am quite happy that the myriad of other flatpaks are sandboxed by default.

Removing the sandbox from the flatpak means that there is very little value to use the flatpak in the first place, I have realized.

So, since I don't want Zed to be sandboxed on my development machine (I value the ease of access more than the sandbox for this particular app), I have come to the conclusion that I should just install Zed directly - the self-updaing executable.

[MarioNoll]

Similar to what @spuxx-dev mentioned, there is a section in the README, which explains how to to use the host shell in the integrated terminal, with the applied setting I can use my terminal again as I used to, while still using the flatpak version.