Ошибка не удалось открыть файл var lib pacman sync core db unrecognized archive format

Обновлено: 25.11.2022

Actually I don't know when it has happeened. My pacman seems to be broken. I'm still geting output:

pacman -S sth
Code: Select all error: could not open file /var/lib/pacman/sync/community.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/alarm.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/alarm.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/aur.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/aur.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/core.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/core.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/extra.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/extra.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/community.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/community.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/alarm.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/alarm.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/aur.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/aur.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/core.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/core.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/extra.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/extra.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/community.db: Unrecognized archive format
.

I have already tried:

Code: Select all pacman -Scc
Code: Select all pacman -Syy

Removing /var/lib/pacman/sync
and then Code: Select all pacman -Syyu

Changing my mirrors using rankmirrors, manually, and still nothing.

Have you got any ideas?

by maciar » Sat Jan 24, 2015 4:38 pm

by crashmaster » Sun Jan 25, 2015 1:34 am

by maciar » Sun Jan 25, 2015 4:41 pm

I have a new clue.

function sendRequest() var request = false;



















I'm using USB Modem as a internet gateway. It is available on 192.168.0.1 ip address or m.home domain. Mayby is it related in some way? If I remenber right, everything has beed ok before I connected USB modem on USB0 interface.

by crashmaster » Mon Jan 26, 2015 2:05 am

There has definitely going something totally wrong.
What happens with these .db files in /var/lib/pacman/sync after doing a 'pacman -Syy' ?

Compare the file sizes:

Code: Select all -rw-r--r-- 1 root root 28671 22. Jan 00:04 alarm.db
-rw-r--r-- 1 root root 68849 21. Jan 02:28 aur.db
-rw-r--r-- 1 root root 2675734 25. Jan 16:02 community.db
-rw-r--r-- 1 root root 169743 25. Jan 11:21 core.db
-rw-r--r-- 1 root root 2369379 25. Jan 14:33 extra.db

What does this 'file' command say?
file /var/lib/pacman/sync/core.db
It should be:
Code: Select all /var/lib/pacman/sync/core.db: gzip compressed data, last modified: Sun Jan 25 11:21:09 2015, from Unix

by maciar » Mon Jan 26, 2015 5:48 pm

Thanks for reply.

Before, and after pacman -Syy, files look the same:

ls -l /var/lib/pacman/sync/
Code: Select all total 60
-rw-r--r-- 1 root root 11193 Jun 7 2013 alarm.db
-rw-r--r-- 1 root root 11193 Jun 7 2013 aur.db
-rw-r--r-- 1 root root 11193 Jun 7 2013 community.db
-rw-r--r-- 1 root root 11193 Jun 7 2013 core.db
-rw-r--r-- 1 root root 11193 Jun 7 2013 extra.db

file /var/lib/pacman/sync/core.db
Code: Select all /var/lib/pacman/sync/core.db: HTML document, UTF-8 Unicode (with BOM) text, with CRLF line terminators

No idea what is wrong :/

by WarheadsSE » Mon Jan 26, 2015 7:51 pm

Something is obviously playing middle man. Perhaps your USB modem's interface.

Use wget/curl to look at the result of the url, see what crap is happening.

by WarheadsSE » Tue Jun 06, 2017 1:47 pm

The wifi connection was hitting landing page, because the user needed to authenticate.

Various issues relating to the download and installation of software packages from the Manjaro repositories are dealt with here.

"Configuration file. not recognized" Error

Manjaro's package manager - pacman - uses a file called mirrorlist to tell it the internet addresses of the Manjaro servers in order to download updates and software applications from them. This error will therefore occur if one or more server addresses contained in the mirrorlist file have not been listed properly, resulting in pacman being unable to connect to them. Another tell-tale sign is that this problem will also be encountered immediately after:

  • Installing Manjaro and editing the mirrorlist file during installation, or
  • Editing the mirrorlist file at a later time.

See the Change to a Different Download Server guide for more detailed information on how to correctly select and enable another Manjaro server for downloading.


">$ $ " />







I'm using USB Modem as a internet gateway. It is available on 192.168.0.1 ip address or m.home domain. Mayby is it related in some way? If I remenber right, everything has beed ok before I connected USB modem on USB0 interface.

by crashmaster » Mon Jan 26, 2015 2:05 am

There has definitely going something totally wrong.
What happens with these .db files in /var/lib/pacman/sync after doing a 'pacman -Syy' ?

Compare the file sizes:

Code: Select all -rw-r--r-- 1 root root 28671 22. Jan 00:04 alarm.db
-rw-r--r-- 1 root root 68849 21. Jan 02:28 aur.db
-rw-r--r-- 1 root root 2675734 25. Jan 16:02 community.db
-rw-r--r-- 1 root root 169743 25. Jan 11:21 core.db
-rw-r--r-- 1 root root 2369379 25. Jan 14:33 extra.db

What does this 'file' command say?
file /var/lib/pacman/sync/core.db
It should be:
Code: Select all /var/lib/pacman/sync/core.db: gzip compressed data, last modified: Sun Jan 25 11:21:09 2015, from Unix

by maciar » Mon Jan 26, 2015 5:48 pm

Thanks for reply.

Before, and after pacman -Syy, files look the same:

ls -l /var/lib/pacman/sync/
Code: Select all total 60
-rw-r--r-- 1 root root 11193 Jun 7 2013 alarm.db
-rw-r--r-- 1 root root 11193 Jun 7 2013 aur.db
-rw-r--r-- 1 root root 11193 Jun 7 2013 community.db
-rw-r--r-- 1 root root 11193 Jun 7 2013 core.db
-rw-r--r-- 1 root root 11193 Jun 7 2013 extra.db

file /var/lib/pacman/sync/core.db
Code: Select all /var/lib/pacman/sync/core.db: HTML document, UTF-8 Unicode (with BOM) text, with CRLF line terminators

No idea what is wrong :/

by WarheadsSE » Mon Jan 26, 2015 7:51 pm

Something is obviously playing middle man. Perhaps your USB modem's interface.

Use wget/curl to look at the result of the url, see what crap is happening.

by WarheadsSE » Tue Jun 06, 2017 1:47 pm

The wifi connection was hitting landing page, because the user needed to authenticate.

Various issues relating to the download and installation of software packages from the Manjaro repositories are dealt with here.

Conflicting files - FILENAME exists in filesystem

If you cant can't install or update a package because of an error like this:

Then the package manager, pacman, has detected an unexpected file that already exists on the disk.

Why is this happening?

By design pacman will not overwrite files that already exist. This is a design feature, not a flaw - package managers are designed to keep track of installed files.

This issue normally happens because you've manually added, copied, or created a file. It can also happen when you install software using a downloaded executable, run a make install, or use a third-party package system such as conda. It also occurs when you install an AUR package which installs files that conflict with a repo package.

When using a third-party installer you should always specify an alternative installation location, such as under your home directory, or under /opt or /usr/local/. Never install directly under / or /usr.

How can I fix this?

The first step is to identify which, if any, package owns the file. This can be easily done with:

If this identifies a conflicting package you can decide to remove it with pacman -R. If no package is identified you can delete the file (or move it to a backup location).

Where can I read more?

This post was inspired by (and adapted from):

The above post also has links to further reading.

One recipe for fixing this

It is mandatory to ensure that the keyrings is current. By ensuring the keyrings are in shape and then redownloading the databases we reestablish the chain of trust between the keyrings and the packages.


You will have to find the correct names by looking at

Replace yyyymmdd and x with the info found at the above links

Remove your faulty databases

Download the databases and update the system

Conflicting files - FILENAME exists in filesystem

If you cant can't install or update a package because of an error like this:

Then the package manager, pacman, has detected an unexpected file that already exists on the disk.

Why is this happening?

By design pacman will not overwrite files that already exist. This is a design feature, not a flaw - package managers are designed to keep track of installed files.

This issue normally happens because you've manually added, copied, or created a file. It can also happen when you install software using a downloaded executable, run a make install, or use a third-party package system such as conda. It also occurs when you install an AUR package which installs files that conflict with a repo package.

When using a third-party installer you should always specify an alternative installation location, such as under your home directory, or under /opt or /usr/local/. Never install directly under / or /usr.

How can I fix this?

The first step is to identify which, if any, package owns the file. This can be easily done with:

If this identifies a conflicting package you can decide to remove it with pacman -R. If no package is identified you can delete the file (or move it to a backup location).

Where can I read more?

This post was inspired by (and adapted from):

The above post also has links to further reading.

Errors about Keys

We all have our own unique signatures which are used to authenticate who we are and to prevent fraudulent or even malicious activities by others. This is also the case with software packages available from the software repositories. They all contain encrypted codes (signature keys) unique to their developers to ensure that they are authentic and not malicious in nature.

During the installation process, once any software packages have been downloaded, your system will first check their signature keys to ensure that they are authentic prior to actually installing them. If a signature key cannot be verified for any reason, then the installation process will be aborted. This problem will usually occur due to:

  • one or more signature keys contained in your system's database being revoked, changed, corrupted, or out of date
  • one or more software packages not having been signed off properly when placed in a repository

Where a package has not been signed off properly before being placed in a repository, it will be the responsibility of the developer(s) to correct this. However, as this problem will be more than likely due to a problem with your system's verification of a signiture key, this can be solved in three easy steps. Working net connection is required. Once you have opened your terminal:

1. Remove old (and possibly broken) keys by entering this command:

2. Reinstall keyrings including the latest keys:

2. Initialize the pacman keyring:

4. Load the signature keys:

5. Refresh and update the signature keys:

6. Clear out the software packages downloaded during the aborted installation (optional):

Info Improved version added, since it doesn't work that way above. The packages are signed and since /etc/pacman.d/gnupg has been removed, it cannot be installed due the check. Instead editing the /etc/pacman.conf and lowering the SigLevel, it would be better installing the keyrings without a check manually to overcome this problem.

1. Remove old (and possibly broken) keys by entering this command:

2. Initialize the pacman keyring:

3. Download the packages:

4. Remove the signatures:

5. Install the downloaded packages manually:

6. Clear out the software packages downloaded during the aborted installation (optional):

Warning The above command clears the pacman cache completely, and one will not be able to downgrade to a previous version of a package if required. Instead packages that are causing signing errors can be removed individually when upgrading.

7. Remove the custom package folder: (optional):


After that try running sudo pacman -Syu to see if the errors were resolved.

"Unable to lock database" Error

When downloading and installing software from the repositories, a special database lock file will be created in order to ensure that the current installation process is the only one running at that time. Otherwise, attempting to install multiple files from multiple sources simultaneously may corrupt the downloaded files, cause file conflicts - or worse still - damage your system. Once the installation has been completed, the lock file will then be automatically deleted. This error may therefore occur due to two possible reasons:

  • Another installation is still taking place and has not yet finished, or
  • A previous installation attempt had not finished properly (e.g. due to being aborted early)

It is therefore wise to first check to ensure that another installation is not (or had not been) in process at the time of the error. When satisfied that this is not the case, then the database lock file can be manually deleted. To do so, open up the terminal and enter the following command:

Once done, you should now be able to successfully re-attempt your intended installation.

"GPGME error: No data" Error

The most likely cause of this issue is that an error or corruption has been detected by pacman in one or more software packages being downloaded. Package signatures and checksums are used to verify the validity of downloaded software, and should they fail, the installation attempt will be aborted to protect your system until the matter is resolved.

One recipe for fixing this

It is mandatory to ensure that the keyrings is current. By ensuring the keyrings are in shape and then redownloading the databases we reestablish the chain of trust between the keyrings and the packages.


You will have to find the correct names by looking at

Replace yyyymmdd and x with the info found at the above links

Remove your faulty databases

Download the databases and update the system

Option 1: Basic Resolution

To resolve this issue, first follow the basic procedure provided below. If this does not work, then there is a more comprehensive procedure available.


1. Download the package databases and update your system:

2. Clear out the software packages downloaded during the aborted installation by entering the command:

3. Re-attempt the aborted download.

"Unable to lock database" Error

When downloading and installing software from the repositories, a special database lock file will be created in order to ensure that the current installation process is the only one running at that time. Otherwise, attempting to install multiple files from multiple sources simultaneously may corrupt the downloaded files, cause file conflicts - or worse still - damage your system. Once the installation has been completed, the lock file will then be automatically deleted. This error may therefore occur due to two possible reasons:

  • Another installation is still taking place and has not yet finished, or
  • A previous installation attempt had not finished properly (e.g. due to being aborted early)

It is therefore wise to first check to ensure that another installation is not (or had not been) in process at the time of the error. When satisfied that this is not the case, then the database lock file can be manually deleted. To do so, open up the terminal and enter the following command:

Once done, you should now be able to successfully re-attempt your intended installation.

Option 2: Comprehensive Resolution

If the basic proceedure still does not resolve the matter, further steps are available:


1. Resynchronise with the Manjaro servers to ensure that everything is up to date by entering the command:

2. Refresh and update the signature keys by entering the command:

3. Reload the signature keys by entering the command:

4. Clear out the software packages downloaded during the aborted installation by entering the command:

5. Re-attempt the aborted download.


If the error still persists, then it is recommended to Change to a Different Download Server.

Various issues relating to the download and installation of software packages from the Manjaro repositories are dealt with here.

"Unrecognized archive format" Error

It has ocurred more than once, an update is issuing these messages in a seemingly never ending stream. Pacman could not open file: sync files

The error relates to a mismatch in the information contained in the db files at the mentioned location and the db files at the first mirror in your mirrorlist. Pacman checks a package in the database and sees if the signature file matches the one in the database. If it does not, then pacman will say the package is corrupted.

While it sometimes is possible to fix the issue simply by deleting the files and the running a pacman update it far from every time.

Читайте также: