nRF Connect SDK v2.6.1 and v2.7 fails Ubuntu 24.04 LTS

[vorrias]

There are multiple errors:

• Failed to clone the repositories: Error: Cloning into '~/ncs/v2.6.1/.west/manifest-tmp'... /~/ncs/toolchains/2be090971e/usr/local/libexec/git-core/git-remote-https: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory FATAL ERROR: command exited with status 128: git clone --branch v2.6.1 github.com/.../sdk-nrf /~/ncs/v2.6.1/.west/manifest-tmp Error: Launched process exited with non-zero status: 128 Error: Subprocess ~/.config/nrfconnect/nrfutil-sandboxes/toolchain-manager/0.15.0/bin/nrfutil-toolchain-manager failed with unexpected exit code Some(128)

• Error: Cloning into '~/ncs/v2.6.1/.west/manifest-tmp'... /~/ncs/toolchains/2be090971e/usr/local/libexec/git-core/git-remote-https: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory FATAL ERROR: command exited with status 128: git clone --branch v2.6.1 github.com/.../sdk-nrf /~/ncs/v2.6.1/.west/manifest-tmp Error: Launched process exited with non-zero status: 128 Error: Subprocess /~/.config/nrfconnect/nrfutil-sandboxes/toolchain-manager/0.15.0/bin/nrfutil-toolchain-manager failed with unexpected exit code Some(128)

I had no problems installing V2.6 some time ago on the same PC (UBUNTU  24.04 LTS)

[Elfving]

Hello,

That is odd. There are reasons why this might be problematic (ubuntu 24 is for instance not among the officially supported OSes), but I am surprised that it should fail when cloning something from github.

Are you using a VPN/Tor or anything like that?

Regards,

Elfving

[vorrias]

Hi Elfving,

Yes it is odd and to make things worse The problem exists when installing on Ubuntu 20.04.6 LTS

On both Ubuntu versions th SDK 2.6.0 installed without a problem (and versions before 2.6.0 too)

No I am not using a VPN. I did the same procedure as i did for previews versions.

If I am the only person having that problem the solution must be in frond of our eyes I think.
I think the problem starts when unpacking the tool-chain and starts initializing.

This may help. The tool chain manager is v1.5.1 . May be in the past some months ago when updated to 2.6 I did so with older tool-chain manager.

Regards

Vasilis

[Elfving]

I'll try it myself on an Ubuntu 22 later today. 

Could you try installing it using the VSC extension as well? You can do this by pressing the manage SDKs button while you have no SDK version currently selected in your file explorer. If you for instance have an NCS workspace selected this option might be grayed out.

Regards,

Elfving

[vorrias]

Strange. I can't see the second line "Manage SDKs ..." at all

My second line in VS code is "Manage west workspace"

VSC Version: 1.92.1

Until ver 2.6.0 everything went fine.

Am I doing something wrong?

2.6.0 opens fine