![]() ![]() Sudo dpkg -P snapd gives: dpkg: error: dpkg database lock is locked by another processĪm new to Ubuntu, so am a bit stuck. 1,583 2 2 gold badges 17 17 silver badges 30 30 bronze badges. Snap list gives: Name Version Rev Tracking Publisher Notes sudo killall apt to release the lock sudo dpkg -configure -a to fix the interrupted upgrade sudo apt upgrade to make sure no packages are left not upgraded Share. ![]() So I killed the original process, and then I get E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) Following the help on the above thread, I get the same until I try sudo apt upgrade again, where I get E: 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? is a disabled or a static unit, not starting it. Two minutes later, I can run all the code and see no issues. Even waiting for the lock using while fuser didnt work for us. I hate that I did this, but we added a pause statement before the APT code above. Our Docker instances dont have the same issue. Done E: The package packettracer needs to be installed, but I can't find an archive for it. bcampoli I found out, further to our issue, that its only happening when we build on AWS instances. The error is Setting up snapd (2.39.2+19.04). (base) email protected: sudo apt-get upgrade Reading packages lists.Done Building dependency tree Reading state information. Md5sum: /etc/apparmor.d/-confine: No such file or directoryĪppArmor parser error for /etc/apparmor.d/-confin… It freezes the terminal with the following sudo apt-get upgradeĮ: dpkg was interrupted, you must manually run 'sudo dpkg -configure -a' to correct the sudo dpkg -configure -a I have a brand new (1 day old) Ubuntu server 19.04 and after a day I tried to upgrade it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |