just for the record for future users who stumble on this from google as I did.
Here is the easiest way to get back to the dpkg configuration that failed.
Code:
ps -aux | grep dpkg
You should get a dpkg process somewhere with something like this:
Code:
root 4886 0.0 0.1 15760 5604 pts/2 Ss+ 09:28 0:00 /usr/bin/dpkg --status-fd 61 --configure tzdata-java:all libc6-i386:amd64 libc-dev-bin:amd64 linux-libc-dev:amd64 libc6-dev:amd64 libapt-inst1.4:amd64 resolvconf:all libxml2:amd64 ntfs-3g:amd64 gnome-media:amd64 libgstreamer-plugins-bad0.10-0:amd64 gstreamer0.10-plugins-bad:amd64 libxslt1.1:amd64 nvidia-common:amd64 apt-utils:amd64 isc-dhcp-common:amd64 isc-dhcp-client:amd64 apt-transport-https:amd64 libisc83:amd64 libdns81:amd64 libisccc80:amd64 libisccfg82:amd64 libbind9-80:amd64
Might be very long or shorter..
the pid should be the dpkg pid which was 4886 in my case.
Now you can resume from where you left of by doing:
Code:
sudo dpkg --configure -a
This usually happens because dpkg has a question for you to answer so it stalls, otherwise the upgrade might have finished without you.
Bookmarks