Package Manager problems

[vinnywright]

ok now that the lock file's are no longer a problem ,,,,,,,,do this and report back what happens

sudo apt-get -f install

VINNY

[phil1349]

Here is the output of apt-get -f install :-

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-headers-3.5.0-17 linux-headers-3.5.0-17-generic
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
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-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-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.
linux-image-generic depends on linux-image-extra-3.5.0-23-generic; however:
Package linux-image-extra-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-geNo apport report written because the error message indicates it's a follow-up error from a previous failure.
No apport report written because the error message indicates it's a follow-up error from a previous failure.
No apport report written because MaxReports has already been reached
No apport report written because MaxReports has already been reached
neric:
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-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)

[blobfish]

type and read output of these 2 commands. They will just present options and information.

dpkg --help

dpkg --force-help

I will post what I would do next, but you might want to wait and see if there are any conflicting opinions before you follow it. You are getting into dangerous territory. I wouldn't be rebooting the machine until you get through this.

sudo dpkg --simulate --force-remove-reinstreg linux-image-3.5.0-23-generic

I have a funny feeling simulate won't work with force so you might not be able to test and will just have to go for it. If simulate works and you are comfortable with the output, you will have to run it again without the simulate option to make the change. I have used this years ago*, so it has worked for me in the past.




If that acts like it worked, I would run

sudo dpkg --audit

and see that it prints out nothing.


if audit looks good I would

sudo update-grub

Probably redundant, but just to be safe.




read the output of the commands and if you don't feel comfortable stop and post the terminal output to the this thread.


*My notes on this were on the page before my feisty fawn install notes!

[phil1349]

Running dpkg --audit produces the following output :-

The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
linux-image-generic Generic Linux kernel image
linux-generic-pae Transitional package.
linux-image-extra-3.5.0-23-generic Linux kernel image for version 3.5.0 on 32
linux-generic Complete Generic Linux kernel and headers

The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
linux-image-3.5.0-23-generic Linux kernel image for version 3.5.0 on 32 bit x8

No surprises there, I tried dpkg --configure as suggested only to produce the same error messages as previously posted.

I also tried synaptic as recommended by Frank 616 which initially looked promising as it showed linux-image-3.5.0-23 & all the other associated packages as being marked for re-installation but on trying this, it produced the following output :-

/usr/bin/deborphan: The status file is in an improper state.
One or more packages are marked as half-installed, half-configured,
unpacked, triggers-awaited or triggers-pending. Exiting.

Discarding: 1 over 9
Discarding: 8 over 9
Discarding: 14 over 15
Discarding: 14 over 15
/usr/bin/deborphan: The status file is in an improper state.
One or more packages are marked as half-installed, half-configured,
unpacked, triggers-awaited or triggers-pending. Exiting.

Discarding: 14 over 15
Discarding: 14 over 15


Again, it does not tell us anything we did not already know except for mention of the status file. Does anyone know the name of this file and where it can be found ?

[dequire]

There's some issue with linux-image-3.5.0-23-generic, as my APT configuration appears to be borked. Nohting I do seems to rectify it. Looking to re-install 12.10 with the point release to avoid that kernel altogether. This is the first time i've seen anyone else appear to have a problem with that package. Might be a coincidence, but my guess is that it's probably not. One weird affect in my case is that attemting to force in the intstallation to rectify the problem ends up making my /Home no longer writable until a cold reboot. I thought at first it was a bad sector problem (and I guess it still could be) but it only happens when I attempt a Dist-Upgrade. Very odd.