SDKmanager error after installation on host PC

Hello, I am installing the SDKmanager (actual version sdkmanger_1.3.1-7110_amd64.deb) on my host PC (System: Ubuntu 20.04.01 LTS) for loading software from host PC to the nvidia jetson AGX. After installation according to instructions provided at Download and Run SDK Manager :: NVIDIA SDK Manager Documentation, an error prevents successful launch. After typing “sdkmanager” at command line, the system returns the message:

sdkmanager
/snapshot/main/node_modules/sql.js/js/sql.js:5
1<process.argv.length?process.argv[1].replace(/\/g,“/”):“unknown-program”);f.arguments=process.argv.slice(2);“undefined”!==typeof module&&(module.exports=f);process.on(“uncaughtException”,function(a){if(!(a instanceof ka))throw a;});f.inspect=function(){return"[Emscripten Module object]“}}else if(fa)f.print||(f.print=print),“undefined”!=typeof printErr&&(f.printErr=printErr),f.read=“undefined”!=typeof read?read:function(){throw"no read() available (jsc?)”;},f.readBinary=function(a){if(“function”===
^
Error: EPERM: operation not permitted, unlink ‘/tmp/sdkmanager.sock’
at Object.unlinkSync (fs.js:1129:3)
at Socket. (/snapshot/main/headless.bundle.js)
at Socket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: -1,
syscall: ‘unlink’,
code: ‘EPERM’,
path: ‘/tmp/sdkmanager.sock’
}

WHo can help?
Thanks a lot,
Ralph

I can’t really tell about this error, but it seems Ubuntu20 is not mentioned in SDK host requirements.
May you try from a Ubuntu18.04 (or Ubuntu16.04) host ?

I suspect it is what @Honey_Patouceul mentioned. Here are a couple of URLs on possibly getting 20.04 to look like 18.04 (no guarantee):

Hi, I loaded Ubuntu 18.04, installed SDKmanager there as mentioned. It doesn´t work right from the start either, but the error message looks easier to deal with. After typing “sdkmanager” at the command line, it says:

/opt/nvidia/sdkmanager/sdkmanager-gui: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

Still thinking what to do next…

sudo apt search libnss3
Sorting... Done
Full Text Search... Done
libnss3/bionic-updates,bionic-security,now 2:3.35-2ubuntu2.12 arm64 [installed,automatic]
  Network Security Service libraries

If it doesn’t show libnss3 installed as above (version/arch would be different), you would try to install it with:

sudo apt update
sudo apt install libnss3

and then retry SDKM.

also you may like to try headless sdkmanager

 sudo sdkmanager --cli  install --user youruseremail@youremail.com --logintype devzone --product Jetson --version 4.4 --targetos Linux --target P2888-0001 --flash all --targetimagefolder /home/username/Downloads/nvidia/installation_agx --downloadfolder /home/username/Downloads/nvidia

https://docs.nvidia.com/sdk-manager/sdkm-command-line-install/index.html

Hello, following your advice installing the libraries, things moved forward. After that I got the same message for libgtk-3, followed by libXss etc. I got rid of the error messages by simply installing all libraries the hard way:
$ sudo apt install lib*

After typing “sdkmanager”, I got the following message:

$ (sdkmanager-gui:22155):Gtk-WARNING **: 11:14:21:332: cannot open display

I have to add that I am running Ubuntu using WSL2 (Windows Subsystem for Linux Version 2). Before setting up a Linux-only host PC, maybe someone out there already knows the solution ?

what are the outcomes if executing the headless sdkmanger?
running from Windows is not suported, neither running from VM’s.
However, some folks used difficult way using virtualbox/ vmware. but it is also not supported

I have no experience with WSL, but it seems that the error comes from no X display being available. You may try to have a X server running in WSL and give access (not sure this is relevant, but seeing this it might be possible). Someone else more skilled with WSL and X may advise further.

Hello, you are right. The remaining issue is WSL. Someone else in the forum got exactly the same error in 2019 and installed XMing X Server for windows. I finally got the green sdkmanager gui onto my screen - but it didn´t connect with the interface for flashing the Jetson. I decided to revive an old PC with Ubuntu only.

Thanks to all for your prompt advice!

Seems indeed USB device support is not available yet from WSL2 (only some IP over USB) so flashing from WSL2 wouldn’t be supported so far. Sorry for wasted time.