sudo dpkg --configure -a not resolving blocking of synaptic & updating

[Valtam]

What does : sudo apt-get install -f produce?

Sent from my Nexus 6 using Tapatalk

[m654321]

What does : sudo apt-get install -f produce?
Sent from my Nexus 6 using Tapatalk

Still stuck...

Code:

mike@mike-G750JS:~$ sudo apt-get install -f
[sudo] password for mike:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
mike@mike-G750JS:~$

[torreydale]

If you have a Systemback restore point, use it.  Otherwise reinstall the operating system.

[firenice03]

Might be worth a final try... Open Synaptic and click reload; once completed close then try in a terminal the

Code:

sudo dpkg --configure -a

Sounds like a package didn't completely install???

OR might be worth to look at
https://ubuntuforums.org/showthread.php?t=843690

If not then maybe as torreydale suggests.. (Systemback backups are life savers lol)

[Valtam]

Try:

Code:

sudo rm -rf /var/lib/dpkg/updates/*
sudo rm -rf /var/lib/apt/lists/*
sudo apt-get clean
sudo apt-get autoremove
sudo apt-get update

then:

Code:

sudo dpkg --remove --force-remove-reinstreq 4.4.0-42-generic

Code:

sudo apt-get dist-upgrade

Reboot.

If any of the above commands don't complete, continue to the next command regardless.

[m654321]

Try:

Code:

sudo rm -rf /var/lib/dpkg/updates/*
sudo rm -rf /var/lib/apt/lists/*
sudo apt-get clean
sudo apt-get autoremove
sudo apt-get update

then:

Code:

sudo dpkg --remove --force-remove-reinstreq 4.4.0-42-generic

Code:

sudo apt-get dist-upgrade

Reboot.

If any of the above commands don't complete, continue to the next command regardless.

Many thanks Jerry, and many thanks for your message re. Teamviewer but unfortunately I missed this as was away from PC.

I tried what you suggested above to the letter, but it failed, as the previous advice given by firenice, torreydale & jocklad. So rather than waste any more time on this I merely reinstalled LL3.0, using the existing '/home' partition as part of the refreshed setup - only took me an hour max - quicker than trying to find any other solution. Problem sorted. I think the problem may have originally arisen from me forgetting to use 'sudo update-grub' following a kernel update - maybe this explains why I had two older unused kernels still around within the system - just guessing here.

Worth noting (new observation for me), that though '/home' did preserve the browser bookmarks for firefox, slimjet & qupzilla browsers, I did need to reinstall the software that didn't come preinstalled with the fresh install of LL3.0, e.g. slimjet, qupzilla, clementine & others. Also the configuration files in '/home' did not appear to preserve the symlinks between the OS-drive and the data-storage-drive on my PC (setup1 in sig) - the symlinks for the folders Documents, Downloads, etc were shown as 'whited-out' folders with 'double arrows'. I deleted these in '/home' and simply reinstalled them - didn't take long.

Many thanks Jerry & all the team for your continued support & the great job you do generally.
Much appreciated

Regards
Mike

[m654321]

It's happened again!!! All the advice above in this thread didn't work as before.
It seems to be a weakness of LL on setup(1) in sig, though I'm now just running LL3.2 as a single OS on its own.
Locked out of synaptic, light tweaks (kernel removal & autoremove) & install updates... >

Ran sudo dpkg --configure -a, and this is what I got as before (except the kernel involved is a later version than before):

Code:

mike@mike-G750JS:~$ sudo dpkg --configure -a
[sudo] password for mike:
Setting up linux-headers-4.4.0-51-generic (4.4.0-51.72) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.4.0-51-generic /boot/vmlinuz-4.4.0-51-generic

Stuck on the last line - how long should I wait if it's going to do anything at all? How patient should I be?!

When I try to open Synaptic I get this error message as before & can't go further with this notification appearing:

Code:

E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
E: _cache->open() failed, please report.

I run sudo dpkg --configure -a numerous times, but to no avail, as before

uname -a gives the following:

Code:

mike@mike-G750JS:~$ uname -a
Linux mike-G750JS 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

...so I tried to use Lite Tweaks/Kernel Removal, to removal kernel 4.4.0-51 which is listed there but I get this message when I attempt a clean:

Code:

Kernel Cleaner has failed

I'm wasting a lot of time on this - I'd be really grateful if anyone could help, even if we have to go down the 'Teamviewer' route though that will take a bit of organisation given time zones & people's busy lives. I'm pretty much at my wits end with this problem as it's wasting so much time which I haven't got. I 'solved' the problem the first time by doing a clean-install of LL but I can't keep doing this...

The cause of the problem was likely to be my fault - I may have inadvertently interrupted 'Install Updates' (which in turn interrupted the kernel update) when I turned off my PC.  I think there needs to be some visible sign that updates are being installed rather than it disappearing off screen into the background only reappearing with a notification when it's completed...

Sorry to be a pain again, with this.
Mike

[firenice03]

I can maybe give a couple ideas to try in the meanwhile... ??  ??? ???

Rebooting and choosing LL Advanced options should give the option to choose which kernel to boot with; perhaps a previous would be listed then allowing you to remove the latest...

Or if you have a systemback back up revert to the most recent prior to the cancelled update...

Hope you get it straightened out..

[trinidad]

My guess is your old home partition is preserving kernel info for kernels that do not actually exist. Update grub will just keep adding them in. You'll need to use root to fix this which is risky, so this could be bad advice. Open a terminal and type sudo passwd root. Enter a new nix password twice and exit the terminal. Logout and reboot. Select other from lightdm login and type root, and enter the root password you set up. You will boot into root. You'll get an ioctl error which you can just ignore, x out the message, and root will load the xfce desktop. Clean out the kernel info from home there. To get rid of the root login afterwards open a terminal and type sudo passwd -dl root. Warning -- could be ugly. Don't go this route if you're not sure of what you're doing.

TC

[m654321]

My guess is your old home partition is preserving kernel info for kernels that do not actually exist. Update grub will just keep adding them in. You'll need to use root to fix this which is risky, so this could be bad advice. Open a terminal and type sudo passwd root. Enter a new nix password twice and exit the terminal. Logout and reboot. Select other from lightdm login and type root, and enter the root password you set up. You will boot into root. You'll get an ioctl error which you can just ignore, x out the message, and root will load the xfce desktop. Clean out the kernel info from home there. To get rid of the root login afterwards open a terminal and type sudo passwd -dl root. Warning -- could be ugly. Don't go this route if you're not sure of what you're doing.

TC

Thanks TC & firnice03 for the advice.

Time's a bit short, so I went for the 'easier option' to reinstall LL3.2 (though not a total clean-install like last time) rather than faff around any more 'in the dark' doing things that might not work or just get me in piled-high-and-deep! With this reinstall, I preserved the '/home' instead of overwriting it as I wanted to keep as many of my settings as possible & not have to reinstall these.  And it's worked: thankfully the configuration files in '/home' didn't carry over the 'mess' into the new installation !  I just had to revisit "Install Updates", "Lite Software" & one or two things from "Synaptic".  I did have to reset my symlinks, though that only took around 5-10 minutes.  I had to reinstall Virtualbox, though all my VMs were automatically reloaded and links preserved to my DATA partition.

Thanks guys for your continued interest & offers of help - much appreciated

Mike

PS. @firenice03: I'd already tried advanced options but "the computer said no"  - it just got stuck at the kernel I selected