Errors while installing SDK Manager on host PC

I’am trying to install the SDK Manager on the host PC, and I get this error message!

micca@micca-PC:~$ sudo apt install ./sdkmanager_0.9.13-4763_amd64.deb
[sudo] password for micca:
Reading package lists… Done
Building dependency tree
Reading state information… Done
Note, selecting ‘sdkmanager’ instead of ‘./sdkmanager_0.9.13-4763_amd64.deb’
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
sdkmanager : Depends: libgconf-2-4 but it is not installable
Depends: libcanberra-gtk-module but it is not installable
E: Unable to correct problems, you have held broken packages.

How can I fix it?
Thanks in advance!

See if this allows install (I’m assuming a desktop PC install and not directly on the Jetson):

sudo apt update
sudo apt --fix-broken install
sudo apt-get install libgconf-2-4 libcanberra-gtk-module
sudo apt-get install python

After that can you install the sdkmanager deb file?

sudo dpkg -i ./sdkmanager_0.9.13-4763_amd64.deb

I am seeing the same complaint over and over again. Nvidia support folk keep providing the same advice such as one seen above by linuxdev. I wonder, if the real answer is to have the Development Kit connected to the host PC at the time of the SDK Manager installation.

Installing the “.deb” package onto an Ubuntu PC does not require a Jetson be connected at that time. However, if you actually run SDKM, then you do need the Jetson connected and in recovery mode for flash. If you are just adding packages and not flashing, then recovery mode is not required, but networking/ssh is required.

If you run just this without other commands, does this either work or indicate the package is already installed?
sudo apt-get install python

Same for:
sudo dpkg -i ./sdkmanager_0.9.13-4763_amd64.deb

Normally a wrong python version will provide an odd failure when running SDKM, but if the “.deb” is installed, and something fails at runtime, then it is a different failure. Either way details on any error messages would help.

linuxdev, to your point about python, python is apparently installed and the system for some reason not recognizing that pythong is out of date. Should I rip it out and let SDKM to install its own?

user01@X1-Carbon:~$ sudo apt-get install python
[sudo] password for anton:
Reading package lists… Done
Building dependency tree
Reading state information… Done
python is already the newest version (2.7.15~rc1-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


typically it is redundant just to install it with
sudo apt install libcanberra-gtk-module libgconf-2-4
no python installation is required, according to the errors listed in the original post

@Andrey1984, thanks! I am going to have to reinstall Ubuntu: I went a little agressive about managing packages and hosed the entire OS. Will report the results when I fix my Ubuntu host.

FYI, I think the problem is that Ubuntu upgraded to a Python 3 release, but the older Python 2 was still being used by SDKM. So it would have been the opposite of Python on the host PC being out of date. I think it was too new. There is no issue installing both Python 3.x and 2.x, but the package naming won’t always tell you which release it is unless you look closer. What you have for “python is already the newest version (2.7.15~rc1-1).” makes me wonder if instead the later SDKM switched to Python 3 and you need to add this (in addition to the 2.7 release). However, the other dependency issue would need to be fixed first before you make Python updates.

If you type part of a command and hit the tab key, then tab completion should show you possibilities. If you type “python” and hit the tab key a couple of times on your PC, does it show “python2” and “python3”?

What @Andrey1984 mentioned is related to this:

…and I am hoping the “sudo apt --fix-broken install” will allow you to continue.