SIGSEGV when trying to open unstable VSCode/VSCodium in conda-shell environment

[64z3r]

Describe the bug

SIGSEGV when trying to open unstable VSCode/VSCodium in conda-shell environment.

Steps To Reproduce

Steps to reproduce the behavior:

1. Enter conda-shell environment.
2. Run "codium ." (but also with "code .")

Expected behavior

Open VSCode/VSCodium without SIGSEGV (as in stable version).

Additional context

Only happens with unstable versions. Works as expected with the stable version of VSCode/VSCodium.

Notify maintainers

@Synthetica9
@turion
@bobby285271
@eadwu
@maxeaubrey

Metadata

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
this path will be fetched (0.06 MiB download, 0.30 MiB unpacked):
  /nix/store/x8mymrkpsmpwyvqssjbwsq851kscf1kw-bash-interactive-5.1-p16-dev
copying path '/nix/store/x8mymrkpsmpwyvqssjbwsq851kscf1kw-bash-interactive-5.1-p16-dev' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.75, NixOS, 22.05 (Quokka), 22.05.3900.26eb67abc9a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.8.1`
 - channels(root): `"nixos-22.05, nixos-unstable"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

[turion]

What's a conda-shell environment? Can you give more context to reproduce?

[64z3r]

https://nixos.wiki/wiki/Python#conda

After installation you need to enter the shell with 'conda-shell' (alternatively with option '-c [your-default-shell]'; an fhs environment for conda), call 'conda-install' and conda might also ask you to run 'conda init [your-default-shell]' to update your shell config/init script. After that just call 'codium .' (or 'code .'; both will segfault).

[liketechnik]

Are you running stable on your system and only vscode from unstable? Then this may very well be another instance of #170897

[64z3r]

I am, and might really be an instance of that...

[64z3r]

https://discourse.nixos.org/t/glibc-error-in-fhs-nix-shell-with-stable-unstable-packages/14687

Can confirm that it's related to the issue.

With

env LD_LIBRARY_PATH= code .

VSCode starts from within the conda-shell environment (fhs), but this way it's pretty useless for me... VSCode is unaware of any Conda/Python envs.

Guess I will have to stay on stable until this problem gets resolved and luckily later stable versions of VSCode/VSCodium shouldn't be affected by this.

Thank you for looking into this!

[tdolega]

I think same thing started happening 2 weeks ago. I have conda from 23.05 and Code from unstable. Any tips besides rolling back or not using unstable?

conda-shell-chrootenv:tsd@desktop-nixos:~$ code .
*** stack smashing detected ***: terminated
Aborted (core dumped)