![unable to install vmware tools on kali linux read only unable to install vmware tools on kali linux read only](http://www.vmwarearena.com/wp-content/uploads/2017/09/Install-VMwareTools-on-Kali-Linux_2.jpg)
- #Unable to install vmware tools on kali linux read only update
- #Unable to install vmware tools on kali linux read only software
- #Unable to install vmware tools on kali linux read only windows
If you see an error like this: :~$ sudo apt install grub-customizerĮ: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)Į: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? Troubleshooting 1: “Unable to acquire the dpkg frontend lock”
#Unable to install vmware tools on kali linux read only update
Now if you run the sudo apt update command, everything should be fine.
![unable to install vmware tools on kali linux read only unable to install vmware tools on kali linux read only](https://www.kali.org/docs/virtualization/install-vmware-guest-vm/vm-21.png)
You can now safely remove the lock files using the commands below: sudo rm /var/lib/apt/lists/lockĪfter that, reconfigure the packages: sudo dpkg -configure -a If they do return at least one number, use the number(s) and kill the processes like this (replace the with the numbers you got from the above commands): sudo kill -9 It’s possible that the commands don’t return anything, or return just one number. Check the error and see what lock files it is complaining about and get the id of the processes holding these lock files. Use the lsof command to get the process ID of the process holding the lock files. But before you do that, it would be a good idea to stop any process that is using the lock files. To fix the problem, all you need to do is to remove the lock files. If the previous apt command was not terminated properly, the lock files are not deleted and hence they prevent any new instances of apt-get or apt commands. When apt or apt-get commands are run, they create lock files in a few places. As mentioned earlier, the lock files are used to prevent two or more processes from using the same data. In this case, the root cause is the lock file. For that reason, there were no processes running apt, but it still showed me the error. I was updating my system and accidentally closed the terminal. The above method would fix the problem for you in most cases. This will kill all the instances of a running program: sudo killall apt apt-get Method 2 If it is still running, force kill it with SIGKILL signal: sudo kill -9 Īnother, easier way would be to use the killall command. sudo kill Ĭheck if the process was killed by running the ‘ps aux | grep -i apt’ command. Replace the with the number you got in the output of previous command. You can use the process id to terminate it by sending the SIGTERM signal. You can ignore the last line containing ‘grep –color=auto’. In the example below, the process id is 7343. This will show you the id of the process running apt or apt-get. To do that, use the command below: ps aux | grep -i apt Use the Linux command line to find and kill the running process. If some other program is using apt, you need to handle it differently. Now, that was the simple scenario and it could be handled easily.
#Unable to install vmware tools on kali linux read only software
When the automatic update finishes, you should be able to install your software as usual.Īs a permanent solution, you may disable the check for automatic update and unattended upgrades altogether however I won’t advise that for security reasons. So if you see is using the apt process, all you have to do is to wait for a few minutes. If you are on Ubuntu server, you may check whether you have unattended upgrades enabled by checking the content of the file /etc/apt//20auto-upgrades. Ubuntu may install security updates in background Use this command: ps aux | grep -i aptįor me, it showed this output: :~$ ps aux | grep -i apt If none of the above is happening, check which other process is running the apt command (package manager for handling software).
#Unable to install vmware tools on kali linux read only windows
If there is no such application running, please check all the open terminal windows and see if you are running an update or installing a program. If that’s the case, please wait for the program to finish the running process. If you are using command line, check if an application like Software Center, Software Updater, Synaptic package manager, Gdebi is running any update/installation. The first thing you should do is to check if some other program could be running system update or installing a program. Let’s see what steps can you take to fix this issue of ‘unable to lock administration directory’. This locking is done so that two processes don’t change the content at the same time as it may lead to unwarranted situation and a possible broken system. When a command or application is updating the system or installing a new software, it locks the dpkg file (Debian package manager). You see this error because some other program is trying to update Ubuntu.
![unable to install vmware tools on kali linux read only unable to install vmware tools on kali linux read only](https://3.bp.blogspot.com/-_vme669jdPM/VRZyKmXBMMI/AAAAAAAALXA/Fj5EHoVE7l0/s1600/1.png)
Fixing “Unable to lock the administration directory (/var/lib/dpkg/)” error