You can see this pid by running ps u -pid 1131. If you look at the error carefully, you will see which process it is, packagekitd, and it's PID is 1131. If it's locked, there is something actively holding it and it shouldn't just be removed. I believe this particular lock is in the former category and so it shouldn't be able to go stale. Other kinds of locks are maintained manually and can get left behind (go stale) if the process crashes. Some locks are tied to running processes and will disappear when the process exits. Never just remove a lock unless you are sure it is stale. If this is not possible, you can still kill it safely. If you think it might be working as intended but just at an inconvenient time it is best to just wait until it is finished. If you are fairly certain the process is stuck somehow and will never end, you can kill it safely. Use psto check if process 1131 is still around. If you are 100% sure the process has crashed, you can remove the lock file without rebooting. During boot old lock files will be deleted since they can no longer be relevant. Rebooting is a very heavy-handed way of making sure that packagekitd is not running anymore. This might have left the system in a "halfway" state, but the package system is designed to detect and recover from that. If this process has in fact crashed without removing the lock file, the situation is different. Now, all this assumes that packagekitd is still running and doing things. This is simple and robust, but not very friendly to multi-taskers. The authors of this package system decided it was better to just make a global lock file. It is possible to write programs so that they can work at the same time without stepping on each others toes, but it is difficult and can give some really obscure bugs. The end result will be some random mixture of the two change sets, which might result in a broken system. The result can be that some of the changes made by one process can be overwritten by the other. Since there was no lock file, apt-get will also assume it is the only process making changes. If you remove the lock file, you make it possible for another process, such as apt-get, to make changes simultaneously with packagekitd. It was created so that that process could make changes to the package system without worrying about other programs doing other changes at the same time. Currently, anytime I restart my computer I have to run a pointless exe file located on the virtual CD that does not require a password in order for me to have access to my drive.The lock file was created by process 1131 (packagekitd). Setting > Apps and used that to uninstall the software it did not actually remove the unlocker. I believe that because I switched the Drive Letters when I went into I switched the Drive Letter of the Virtual CD (originally D:) with the Drive Letter of the external SSD(originally F:) so that the external SSD would appear higher in file explorer.Īfter realizing it would require me to enter a password in every time my computer restarts I decided to try and uninstall the SanDisk unlocker. It created a virtual CD Drive which has only read permissions used to unlock the drive before using it. It came with security software which I installed without really thinking. I recently purchased a SanDisk 2TB Extreme PRO Portable External SSD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |