I've been trying to find/fix a broken package(s). Syn. Pkg. Mgr. won't let me in and suggests 'dpkg --configure -a' to which I receive: dpkg: error: failed to open package info file '/var/lib/dpkg/dpkg/updates/0018' for reading: Input/output error. Wow!! Never had so much trouble w/ linux.

Rick

That's strange. Usually the updates folder is in /var/lib/dpkg, not /var/lib/dpkg/dpkg. I assume that you mistyped that?

Anyway, what you could try doing is:

then try dpkg --configure -a again.

RE: hydrurga

No sir, whenever possible I copy/paste. Unless the command was incorrect?(IDK) Alright, I'll use the commands you gave and get back here w/ results. Oh...correct me if I'm wrong, but wouldn't/shouldn't "updates" repair packages?

THANX:

RE: hydruga

No go, my friend: sudo rm -rf 0018 rm cannot remove '0018': I/O error

That sounds like filesystem corruption to me.

You should try running an offline fsck on the filesystem.

If that comes up clear, then try deleting the directory offline (i.e. having booted up from e.g. a removable media, not from the operating system itself).

Try starting Synaptic from the command line. Perhaps it will throw some useful error messages. If so, post them, being sure to surround them with "code" tags, which become available when you click the "Go Advanced" button beneath the "compose post" window.

RE: EVERYONE

Since I'd been having sssoooo much trouble, I wiped 17.3x and started over with 18.3x. When running updates, I came across a 'suggestion" from the updating program which said anyone running a "live" version should 'apt-cdrom'. I did so and, so far(?), the "live" seems to running like a desktop. Hope this was the answer to all the lags/freezes AND broken pkgs. I was experiencing. Should it 'break down", then rest assured, I'll be back here (you've been warned!!!) Ahmmm.... I'm going to mark this thread solved, although I'm not sure the way I solved the problem was really 'the answer"???

TNX ALL

Rick

Maybe not the answer, but certainly an answer. Nevertheless, some of the suggestions you got in this thread may help someone else.

(I can understand how frustration can lead to starting over. Sometimes troubleshooting gets to be more trouble than its worth!)

RE: frankbell

Ah....yes. We should coin a slogan such as " troubleshooting is too much trouble"! But, clearly, not in the Linux spirit. I wonder had I discovered apt-cdrom before I'd re-installed, if it would have been the remedy to all the maladies I was experiencing? So, your suggesting I leave the thread open?

Rick

TO; Everyone Who Has Replied

I'm not so sure I've "solved" the problem. Here's what I did: format pendrive (again) very carefully selected a legit D/l site and D/l'ed 18.3x. Ran updates immediately and when doing so, came across a "suggestion" in the terminal report suggesting I use apt-cdrom and designate the pendrive so it can run APT. It "seems" to be running much better, although, once in a while, it does still lag. Not nearly as much as previous. Once I discover what the entire command for apt-cdrom is, I'm guessing it'll run much smoother. Anyone know what the entire command would be for apt-cdrom to include the pendrive/'live" O.S? I'm pretty certain I don't want to assign it to a USB port.(?)

TNX