Update Error

[mandoman]

I couldn't figure where to post this, so if this isn't it, my apologies.
I got this error on the last update, 7-30-19, for 18.3 Sylvia.

Code: Select all

E: Malformed 1st word in the Status line
E: Error occurred while processing fonts-tlwg-umpush-ttf (UsePackage2)
E: Problem with MergeList /var/lib/dpkg/status
E: The package lists or status file could not be parsed or opened.
E: _cache->open() failed, please report.

It says to report it, so I'm reporting it. Please instruct me where to report this error if it's not here.

Thanks.

[deck_luck]

Where you having any computer problems before this event like crashes, disk failures, freezes,etc?

What command are you running when this error occurs and be specific.

Please provide additional informational and post the output from the following command:

Code: Select all

inxi -Fxrz

[sleeper12]

xenopeek gave this solution in another thread:

You can remove the package lists, and then fetch them anew. To do so open a terminal and run the following two commands (one at a time):

Code: Select all

 sudo rm -fv /var/lib/apt/lists/* 

Code: Select all

 sudo apt-get update 

That should solve the MergeList issue.

[karlchen]

Software Sources has got a Maintenance tab. And the Maintenance tab has got a fat button labelled Fix problems with MergeLists.
Clicking this button should do precisely what has been explained in the post above.

[mandoman]

I was having no prior problems with the computer. The information I gave in my original post was all I was given to pass along. I will run those commands, and get back to you, as I am on a different computer at this time. I went to Maintenance before making this post, and clicked on the

Fix problems with MergeLists

, and the error warning remained. I need to switch computers to run the requested commands.

[gm10]

Despite its name, the Fix MergeList problems button in Software Sources doesn't address this issue:

Code: Select all

E: Error occurred while processing fonts-tlwg-umpush-ttf (UsePackage2)
E: Problem with MergeList /var/lib/dpkg/status

for that one is with dpkg's database itself, not with the files the suggested terminal command or that button remove (that's one of the reasons I renamed that button in my version of Software Sources).

I'd need the output from this terminal command:

Code: Select all

grep "Package: fonts-tlwg-umpush-ttf" /var/lib/dpkg/status -A1

[mandoman]

Well, now the problem seems to have been addressed, though I ran your command anyway, with this result:

Code: Select all

Package: fonts-tlwg-umpush-ttf
Status: install ok installed

Someone seems to have picked up on the problem and corrected it since my first post. Thanks for the help.

[gm10]

Even better. (and yes, that looks correct)

[mandoman]

Well, I seem to be having all kinds of update problems. Here is the latest.

Code: Select all

W: http://archive.canonical.com/ubuntu/dists/precise/Release.gpg: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: http://us.archive.ubuntu.com/ubuntu/dists/precise-security/InRelease: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: http://us.archive.ubuntu.com/ubuntu/dists/precise-updates/InRelease: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: http://us.archive.ubuntu.com/ubuntu/dists/precise-backports/InRelease: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: http://us.archive.ubuntu.com/ubuntu/dists/precise/Release.gpg: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: GPG error: http://extras.ubuntu.com/ubuntu precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126D3A3E5C1192
W: The repository 'http://extras.ubuntu.com/ubuntu precise Release' is not signed.

It instructs me to use a different repository, but how do I know which ones are safe, and which are not. This is a new one for me.

[sleeper12]

In Software Sources, click 'Restore the default settings' button. See if that helps any.

[gm10]

Well, I seem to be having all kinds of update problems. Here is the latest.

Code: Select all

W: http://archive.canonical.com/ubuntu/dists/precise/Release.gpg: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: http://us.archive.ubuntu.com/ubuntu/dists/precise-security/InRelease: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: http://us.archive.ubuntu.com/ubuntu/dists/precise-updates/InRelease: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: http://us.archive.ubuntu.com/ubuntu/dists/precise-backports/InRelease: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: http://us.archive.ubuntu.com/ubuntu/dists/precise/Release.gpg: Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1)
W: GPG error: http://extras.ubuntu.com/ubuntu precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126D3A3E5C1192
W: The repository 'http://extras.ubuntu.com/ubuntu precise Release' is not signed.

It instructs me to use a different repository, but how do I know which ones are safe, and which are not. This is a new one for me.

None of those are safe, those are repositories from Ubuntu 12.04, which is end of life and most certainly not the operating system you are running. How did you manage to get those on your system? I think we'll need the output from

Code: Select all

inxi -Sr

to see what you have done.

[mandoman]

I have come to realize that what you say is the problem. At some point, and I can't remember when or why, I checked the "Other Repositories" in the update manager, and it totally screwed up the system. Since my last post I have unchecked those repositories, and tried to clean the system. I haven't been successful. As of last night, I could no longer boot up that computer. I think the codes were just too messed up, with some missing. I downloaded Linux Mint 19.2 Mate OS image on my laptop last night, and plan to create an installation mem. stick to install Linux Mint 19.2 Mate on the problem computer. I will try not to make the same mistake of checking those repositories, but with me anything is possible. Thanks.

[gm10]

I checked the "Other Repositories" in the update manager,

There is no such option in Mint's Update Manager actually. In case you mean "Additional Repositories" in Mint's Software Sources tool, anything listed there is something you added yourself, that list is empty on a clean install. If it's not that what you did then be careful with whatever software you used that had that option, it doesn't appear compatible with Linux Mint.

Either way, good luck with your new install, never wrong to start over with a clean slate.

[mandoman]

There was in Mint 18.3. All moot now.

gm10wrote: In case you mean "Additional Repositories" in Mint's Software Sources tool

Yeah, that's what I meant. Doesn't matter, as I think the desktop has gone belly up.

[Pepi]

I just can't imagine Windows running my freezer and ruining 100 lbs of Venison