![]() ![]() N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use. W: The repository ‘file:/var/cuda-repo-9-0-local Release’ is not signed. W: GPG error: file:/var/cuda-repo-9-0-local Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY F60F4B3D7FA2AF80 Hit:19 Index of /ubuntu-ports xenial-security InRelease This is the error that I get when I do “sudo apt-get update”: ![]() I’ll try to help you out.Īny other suggestions are also welcome in the comments.I’ve recently flashed the Jetson TX2 using the JetPack-L4T-3.2-linux-圆4_n my host is a Laptop with Ubuntu 16.04 (I just partitioned my computer to boot with this ubuntu version and be able to use the Jetpack).Īfter flashing the Jetson I didn’t see any error, however, now when I boot into the Jetson TX2 I cannot install anything, I get a ‘public key’ error and a ‘lock’ error. If you are still facing issue, let me know. I hope this small tip helped you fix the “Could not get lock /var/lib/dpkg/lock” error. Or, $ sudo rm /var/lib/dpkg/lock-frontendĪlso you may need to delete the lock file in the cache directory: $ sudo rm /var/cache/apt/archives/lockĪfter removing the lock, run: $ sudo dpkg -configure -a ![]() You can now safely remove the lock with commands: $ sudo rm /var/lib/dpkg/lock Just kill it to release the lock using command: $ sudo kill -9 9718 If the lock file is /var/lib/apt/lists/lock, run: $ sudo lsof /var/lib/apt/lists/lockĮxample output: find out which process that owns the lock fileĪs you can see in the above output, the PID of the process that holds the lock file is 9718. If the lock file is different, for example /var/lib/dpkg/lock-frontend, you can find PID of the process that owns this lock file with command: $ sudo lsof /var/lib/dpkg/lock-frontend In that case, follow the below procedure to fix it.įirst, let us find out which process that owns the lock file i.e /var/lib/dpkg/lock. Once that task is completed, the lock will be released automatically.īut if the process is stuck for some reason and it locked the apt database for several minutes, you have no choice but remove the lock. ![]() This process will take some time (5 to 10 minutes or more) to complete depending upon the size of the update. If you ever encountered with this problem, wait for a few minutes until the currently installing or updating or uninstalling task to complete. Fix “E: Could not get lock /var/lib/dpkg/lock” Error On Ubuntu Frontends like Aptitude (NCRS) and Synaptic (GTK +) are used for their friendly interface for APT. APT ( Advanced Package Tool), a high-level tool, is more commonly used than dpkg because it can bring packages to remote locations and deal with complex package relationships such as dependency fixes. It can install, remove, and build packages, but unlike other package management systems, it cannot automatically download and install packages or their dependencies. dpkg is a package manager for Debian-based systems. Whenever we are installing software, an error occurs with “ dpkg: error: dpkg frontend lock is locked by another process“. In this article we are going to learn How to fix “dpkg: error: dpkg frontend lock is locked by another process”. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |