libselinux.so.1: no version information available (required by sed)

[Huluti]

Since latest update (Zed 0.230.0) I have this message in each terminal openned in Zed:

sed: /var/lib/flatpak/app/dev.zed.Zed/x86_64/stable/e88f8d8e3dcbbb9a23501fdeb645d10ccf2e9da23ae10d02c47b88bb912fa2a2/files/lib/libselinux.so.1: no version information available (required by sed)

[ai]

This error is completly breaking Dev Container feature

[ai]

It is an v0.230.0 regression. The issue can be fixed by:

flatpak update --commit=dd5411c7801bd2e08674f61e0d04e85890926ba56db3f7ba526153b8731c86b2 dev.zed.Zed

[Fringale]

See #330, this is caused by the LD_LIBRARY_PATH env variable being currently leaked by the Zed flatpak to the integrated terminal, and made more apparent in 0.230.0 by a probable change in the flatpak bundled libs in 0.230.0. Another workaround besides rolling back to a previous version is to unset LD_LIBRARY_PATH in terminal commands.

[colonthreeing]

@ai Hi, when trying to revert it, it says this:

◎ flatpak update --commit=dd5411c7801bd2e08674f61e0d04e85890926ba56db3f7ba526153b8731c86b2 dev.zed.Zed         ⌂ 17:07
Looking for updates…


        ID                  Branch         Op        Remote         Download
 1. [✗] dev.zed.Zed         stable         u         flathub        6.3 MB / 127.3 MB

Error: While pulling app/dev.zed.Zed/x86_64/stable from remote flathub: Server returned HTTP 404
Updates complete.
error: There were one or more errors

It gets to about 50% and then is unable to pull the rest of the changes :/

Do you know how to fix this? (or is it just a me problem perhaps?)

[ruben-bibsyst]

As @Fringale noted, the root of the problem is a leaked env variable. I fix it by adding the following to my settings.json:

  "terminal": {
    "shell": "system",
    "env": {
      "LD_LIBRARY_PATH": "",
      "LD_PRELOAD": ""
    }
  },

[acch]

Thanks much @ruben-bibsyst! This fixes the terminal, but the issue still prevents Dev Containers from starting successfully...

[ruben-bibsyst]

Thanks much @ruben-bibsyst! This fixes the terminal, but the issue still prevents Dev Containers from starting successfully...

I do not use Dev Containers myself, but I do see the same error message appear when an agent run commands in a shell, so I guess the "terminal" option in config.json only affects the interactive shell of the user?

[mati865]

You don't even need to run Zed to observe that problem:

❯ flatpak run --command=sh dev.zed.Zed
[📦 dev.zed.Zed ~]$ ls /
ls: /app/lib/libselinux.so.1: no version information available (required by ls)
app  bin  dev  etc  home  lib  lib64  proc  run  sbin  sys  tmp  usr  var

It doesn't happen with other flatpaks I have installed as they don't ship libselinux.so.1 in their /app/lib.

[GammaGames]

I have a similar error with the remote setup:

ssh: /home/me/.local/share/flatpak/app/dev.zed.Zed/x86_64/stable/16e7608f013aba8a7c192ebe246b0f18af90a1ebc96614b39dbba8f971e77c3f/files/lib/libselinux.so.1: no version information available (required by ssh)

The LD_LIBRARY_PATH settings do not fix it

[yump]

@GammaGames workarounds for non-terminal subprocesses are discussed in #330.