Announcement

**oshunluvr** · Feb 08, 2013, 08:57 AM

When you killed muon you left behind it's lock files. Look in /var/lib/dpkg for a file named "lock" and delete it.

**phil1349** · Feb 08, 2013, 07:12 PM

I tried oshunluvr's advice but it did not work, same problem. What is more worrying is that when Muon closes, the "lock" file remains, I would expect that if Muon closes properly that "lock" would be deleted.

**vinnywright** · Feb 08, 2013, 09:42 PM

Originally posted by phil1349 View Post

I tried oshunluvr's advice but it did not work, same problem. What is more worrying is that when Muon closes, the "lock" file remains, I would expect that if Muon closes properly that "lock" would be deleted.

there are one or 2 other lock files that can be in the way Humm look for this one next /var/cache/apt/archives/lock

VINNY

PS allso you could do a update check in the CLI and it will prob tell you whitch ones are the prob

Code:

sudo apt-get update && sudo apt-get dist-upgrade

**phil1349** · Feb 09, 2013, 03:48 PM

Tried apt-get update etc. which seemed to start OK but then bombed with the following error message:-
rrors were encountered while processing:
linux-image-3.5.0-23-generic
linux-image-extra-3.5.0-23-generic
linux-image-generic
linux-generic
linux-generic-pae
E: Sub-process /usr/bin/dpkg returned an error code (1)

My system is currently running 3.5.0-22 and was updating to -23 when the update hung but I cannot find any of the -23 files on my system.

Could it be the case that some settings were modified at the start of the update before the main files were downloaded which did not happen because the update failed ?

**vinnywright** · Feb 09, 2013, 05:08 PM

Originally posted by phil1349 View Post

Tried apt-get update etc. which seemed to start OK but then bombed with the following error message:-
rrors were encountered while processing:
linux-image-3.5.0-23-generic
linux-image-extra-3.5.0-23-generic
linux-image-generic
linux-generic
linux-generic-pae
E: Sub-process /usr/bin/dpkg returned an error code (1)

My system is currently running 3.5.0-22 and was updating to -23 when the update hung but I cannot find any of the -23 files on my system.

Could it be the case that some settings were modified at the start of the update before the main files were downloaded which did not happen because the update failed ?

post the output of

Code:

ls -la /var/cache/apt/archives/

and

Code:

ls -la /var/cache/apt/archives/partial

this will show what was dl'ed if you ave not run an apt-get clean yet + did the error not mention a sale lock file any where ?
it may just be a half/unconfigured package problem.

VINNY

**claydoh** · Feb 09, 2013, 05:08 PM

When the update was killed, there looks to be some packages that did not get processed. Try running:

Code:

sudo dpkg --configure -a

this will make the packaging backend process anything that didn't finish, and will give much better error info if there still is a problem. It might be a good idea to update again after this to be sure it is all up to date.

**vinnywright** · Feb 09, 2013, 05:13 PM

ya do what @claydoh has suggested first ,,,,,,cant hurt and was going to be my next suggestion ,,,,I just wanted to see if the files were their first.

VINNY

**Frank616** · Feb 09, 2013, 07:21 PM

Phil1439:

Once you delete the lock files, you can also try installing and then using Synaptic from now on. I have had grief with Muon in the past. Synaptic is a Gnome package, and when you install it, it will want a bunch of dependencies. I feel they are worth it. Synaptic is a mature piece of software, and will find and fix broken packages for you. They don't come much better.

Frank.

**claydoh** · Feb 09, 2013, 09:46 PM

To note, the same exact scenario can happen using Synaptic. If it were to hang, and was force-closed, the same lock file(s) can be left behind by the backend system (dpkg) that is doing the actual work.

**Frank616** · Feb 10, 2013, 11:24 AM

Claydoh:

I understand. However, I've not had it happen with Synaptic. Synaptic has fixed things for me that Muon would not touch. I really like it. It is a good and mature product -- even if it is Gnome.

Frank.

**phil1349** · Feb 10, 2013, 01:21 PM

The directories /var/apt/cache etc are empty probably because I did apt-get clean fairly early on in the hope that this would reset everything and allow a "clean" update - wrong ! I have also run dpkg --configure -a and that bombs with the same error messages as indicated in my last post as does apt-get update.

There has been some progress in that Muon will now install other packages, the message that another package manager is using the system has dissapeared but it still complains about unresolved dependencies regarding kernel 3.5.0-23 even though the software installs ok but the update icon is greyed out.

Maybe I will wait for 3.5.0-24 to come along in a few weeks time and hope that that installs ok. Is that feasible or do the present problems indicate that Muon is broken ? I might try re-installing Muon to see if that helps and I will install Synaptic as that seems a good idea.

**claydoh** · Feb 10, 2013, 01:37 PM

If there is an unresolved dependency, that will be a problem for any package manager, so we need to find what is missing.

Paste the actual output of "sudo dpkg --configure -a", that will lead us to the fix for the problem.

Since you are running the previous kernel ok, you could also try purging (complete removel) of any 3.5.0-23 packages, and trying to update again. The output from the dpkg command will help with this.

**claydoh** · Feb 10, 2013, 01:39 PM

Originally posted by Frank616 View Post

Claydoh:

I understand. However, I've not had it happen with Synaptic. Synaptic has fixed things for me that Muon would not touch. I really like it. It is a good and mature product -- even if it is Gnome.

Frank.

I have, and the pointer was just in reference to the specific problem.

**phil1349** · Feb 10, 2013, 06:20 PM

Here is the result of dpkg --configure -a, please note that I have already purged (or at least tried to) 3.5.0-23 and update still fails.

Setting up linux-image-3.5.0-23-generic (3.5.0-23.35) ...
Internal Error: Could not find image (/boot/vmlinuz-3.5.0-23-generic)
dpkg: error processing linux-image-3.5.0-23-generic (--configure):
subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of linux-image-generic:
linux-image-generic depends on linux-image-3.5.0-23-generic; however:
Package linux-image-3.5.0-23-generic is not configured yet.

dpkg: error processing linux-image-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-extra-3.5.0-23-generic:
linux-image-extra-3.5.0-23-generic depends on linux-image-3.5.0-23-generic; however:
Package linux-image-3.5.0-23-generic is not configured yet.

dpkg: error processing linux-image-extra-3.5.0-23-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
linux-generic depends on linux-image-generic; however:
Package linux-image-generic is not configured yet.

dpkg: error processing linux-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-pae:
linux-generic-pae depends on linux-generic; however:
Package linux-generic is not configured yet.

dpkg: error processing linux-generic-pae (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-3.5.0-23-generic
linux-image-generic
linux-image-extra-3.5.0-23-generic
linux-generic
linux-generic-pae

Announcement

Package Manager problems

Package Manager problems

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment