Broken apt upgrade (PEBKAC)

[jon danniken]

On Wed, Sep 2, 2020 at 7:52 AM Ken D'Ambrosio <ken at jots.org> wrote:

> Easy answer: reboot.  That *will* solve your file lock issue, though it
> might introduce other issues if there are packages mid-install.
>

> Less-easy answer:
> sudo fuser /var/lib/dpkg/lock-frontend
> That will return something like:
> /var/lib/dpkg/lock-frontend: 123
> (there might be additional numbers, too)
> Those are the process IDs -- PIDs -- of the processes that have that file
> open.  Kill 'em:
> kill 123; kill -9 123  # The "-9" is the "kill it with fire" option, in
> case the first one didn't succeed
> Then, probably an "apt-get -f install" to fix up anything left dangling
> from the interrupted apt-get, and then you should be good to go on with
> whatever you were trying to do in the first place.
>

Thanks Ken, I checked and the processes are indeed still running:

---------------------------------
$ sudo fuser /var/lib/dpkg/lock-frontend
/var/lib/dpkg/lock-frontend:  2869

$ ps aux | grep -i apt
root      2869  0.0  0.7 152484 94564 ?        S    Sep01   0:32 apt upgrade

$ ps aux | grep -i dpkg
root      3192  0.0  0.1  28100 12352 pts/2    Ss+  Sep01   0:00
/usr/bin/dpkg --status-fd 73 --configure --pending
root      8484  0.0  0.0   4628   824 pts/2    S+   Sep01   0:00 sh -c diff
-Nu \/etc\/grub\.d\/10\_linux \/etc\/grub\.d\/10\_linux\.dpkg\-new | pager
---------------------------------

I don't suppose there is any way to continue the running processes in a new
terminal window?

Thanks,

Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20200902/9536a5b1/attachment.html>