Muon update seems to be stuck

[steve7233]

I am attempting to update from Vivid but the update seems hung at 75% I can't tell what its doing as when I click on the program in the klipper it shows the window for the upgrade but the data in the window is the Firefox data for this web page. I hope my system didn't just get hosed. That is 75% of package installation.

[steve7233]

I thought I clicked on pre-installation. I must have clicked on software support by mistake and didn't notice.

[steve7233]

Upgrade failed!

How do I recover from a failed upgrade?

[claydoh]

In a terminal (konsole or via ctrl-alt-f2 ):

sudo dpkg --configure -a
then
sudo apt-get -f install

[steve7233]

In a terminal (konsole or via ctrl-alt-f2 ):

sudo dpkg --configure -a
then
sudo apt-get -f install

Trying that now.

[steve7233]

steve7233@steve7233-EP45-UD3P:~$ sudo dpkg --cofigure -a
[sudo] password for steve7233:
dpkg: error: unknown option --cofigure

Type dpkg --help for help about installing and deinstalling packages[*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked[*] produce a lot of output - pipe it through 'less' or 'more' !
steve7233@steve7233-EP45-UD3P:~$ sudo dpkg --configure -a
dpkg: error: dpkg status database is locked by another process
steve7233@steve7233-EP45-UD3P:~$

[claydoh]

configure, not cofigure

[steve7233]

I corrected that. Please read the entire message.

[claydoh]

It would be helpful to remove that extraneous and useless-for-the-problem output, to remove confusion (especially to those of us working at their day job while helping and are poor multitaskers ) And yes, I know it is evening for me, but it is still my 'day' job

If the upgrade tool window is still open, try cancelling it or closing it and try again. If it still does not work, try running 'apt-get update', which will give us a better error, by specifying where the 'lock' is so we can remove it and continue.


apt and dpkg use what is called a lock file, the presence of which keeps more than one instance of package management from running at the same time. If dpkg or apt hangs, or crashes or is forced to close, the lock file can be left behind, so we may have to look for it as it can be in a few different places depending on what is using this.

[steve7233]

I tried sudo apt-get update and it downloded a bunch of stuff from Wily repos.

Here are the last two lines of the output:

E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
steve7233@steve7233-EP45-UD3P:~$

Could it be that I could reboot and it fixes?

[claydoh]

I tried sudo apt-get update and it downloded a bunch of stuff from Wily repos.

Here are the last two lines of the output:

E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
steve7233@steve7233-EP45-UD3P:~$

Could it be that I could reboot and it fixes?

perfect. It tells us which file to delete: /var/lib/dpkg/lock

sudo rm /var/lib/dpkg/lock

rebooting is not a good idea, as you have an internet connection and at least a partially working desktop, and once you log off, you will have a broken system, as there are things left uninstalled or partially installed, and we don't know what you'll have if you do. Most likely you'd be OK, but you would have no gui, and you would have to run the 2 commands from there, but you'd very likely have to set up your wifi/lan connection manually, which is an extra bit of pain we don't want you to have to do.

[steve7233]

Ok something suggested to me that rebooting now might cause more pain. Good thing I waited and asked.

[steve7233]

I unlocked it and ran those two commands. It tells me to reboot now. So I will. I think the upgrade fixed but we will see.

[claydoh]

it should be. I am assuming that the first command ran a ton of package install and configuration, the second may have done nothing at all, but is used to make sure everything needed is installed, just in case something didn't .

[steve7233]

"Sorry Ubuntu 15.10 has experienced an internal error" I sent in the error report. I think the upgrade was fixed. Getting an error on the first boot is rather dismal. I hope it was just a fluke but hopefully it sent the error report like I told it to.