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

[m654321]

It's happened again - seems to be a recurrent problem!!! 

Should I return to Windows OS as my main operating system?  Despite some of its  shortcomings, I have to say I never seemed to have any difficulties with Windows XP, 7 or 8.1 - it just worked, provided it was set up securely which I was always careful to do.  I know Windows OS has privacy/security issues but, to circumvent that, I have always kept my financial stuff on a pendrive rather than on an HDD and always view it offline. Windows OS attractiveness is its ease of operation & maintenance (e.g. I can install an Epson scanner in a straightforward fashion) for folk like me who are not computer specialists.  You need very little computing knowledge beyond the basics of how a computer works (if that) to run Windows OS - that's not the case with Linux.  Though LL is a superb operating system, and I always recommend it as the no.1 OS for anyone, beginners or expert, a lot of time and effort is still needed when things go wrong, even slightly wrong, especially if, like me, you feel you're not a Linux expert...

Returning to Windows is not an option I want to entertain as I've invested a lot of time in Linux generally (since April 2014), including donating to LL's very worthy cause. I've always said that LL has a great development team and folk are really helpful or certainly try to do their very best for everyone, but sometimes when I have difficulties to resolve (e.g the present one, installing an Epson Scanner, etc) they seem to take forever to fix, or no-one in the forum is quite sure how to fix it, which I think demonstrates the vastness & complexity of Linux generally, and particularly to eternal Linux newbies such as myself. Though I have bought books on Linux (I thoroughly recommend 'Ubuntu Linux Toolbox' by Christopher Negus, the most useful reference book I've seen) and have learnt a huge amount from this forum, I don't think I'll ever master Linux fully as it seems so vast...

Well, that's enough of me having a rant...  how do I fix this sudo dpkg --configure -a issue which has reared its ugly head again? 
I didn't try your idea TC in #18 - it sounded too speculative and by your own admission pretty risky... 

My apologies if I'm sounding a bit downbeat today...

Regards
Mike

[firenice03]

Perhaps the reoccurring problem has another underlying issues??
Have you created any systemback ups?
If so revert back...
If not, get in the habit I will try a minimum for monthly or every other... If I'm "trying" to fix, set up a new I will make a backup prior to entering the 1st line of code then once again after whatever is running. I'm not a Linux guru by no means but a good back will fix any mistake.

For the reoccurring problem... When does it seem to appear? It appears during updates, but is this the 1st update since the last reinstall? Or what system changes since the last successful update? Maybe an underlying hardware problem, which maybe the case if its the same 1 system out of 4.. Possibly in the way 3.x is designed as compared to the 2.x series.?.?.

I have gotten the same message once before (don't recall which series) but running the command resolved it - I know it was due to cancelling/stopping updates midstream - try to avoid this, until you have the "completed" window.

Has it "broke" when attempting the kernel update? Similar to the 1st post?
May help to post the following:
Output where the error lies:
Output of

Code:

uname -a

Keep your head up 

[m654321]

Many thanks firenice03 - just to acknowledge your reply - am busy with work at the moment but will post again here later when less busy...

Cheers
Mike