Manjaro Difference between revisions of "Pacman troubleshooting"

Difference between revisions of "Pacman troubleshooting"

From Manjaro
m (added languages and translate tags)
(update package extension on manjaro keyring)
 
(24 intermediate revisions by 9 users not shown)
Line 2: Line 2:
__TOC__
__TOC__
<translate>
<translate>
= Software Installation =
= Software Installation = <!--T:1-->


<!--T:2-->
Various issues relating to the download and installation of software packages from the Manjaro repositories are dealt with here.
Various issues relating to the download and installation of software packages from the Manjaro repositories are dealt with here.


== "Unrecognized archive format" Error ==
== "Unrecognized archive format" Error == <!--T:3-->


<!--T:4-->
It has ocurred more than once, an update is issuing these messages in a seemingly never ending stream.
It has ocurred more than once, an update is issuing these messages in a seemingly never ending stream.
[https://forum.manjaro.org/t/pacman-could-not-open-file-sync-files/20046 Pacman could not open file: sync files]
[https://forum.manjaro.org/t/pacman-could-not-open-file-sync-files/20046 Pacman could not open file: sync files]


<!--T:5-->
  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
Line 16: Line 19:
  error: could not open file /var/lib/pacman/sync/multilib.db: Unrecognized archive format
  error: could not open file /var/lib/pacman/sync/multilib.db: Unrecognized archive format


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.
<!--T:6-->
The error relates to content of the db files. The error happens when pacman receives markup from the mirror instead of the database archives.


<!--T:97-->
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.
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.


=== One recipe for fixing this ===
<!--T:98-->
'''Run pacman-mirrors to refresh your mirrorlist'''
{{UserCmd|command=sudo pacman-mirrors -c Global}}


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.
<!--T:99-->
 
 
'''You will have to find the correct names by looking at'''
Browse [https://mirror.netzspielplatz.de/manjaro/packages/pool/overlay https://mirror.netzspielplatz.de/manjaro/packages/pool/overlay] for the current manjaro-keyring
and
Browse [https://mirror.netzspielplatz.de/manjaro/packages/pool/sync https://mirror.netzspielplatz.de/manjaro/packages/pool/sync] for the current archlinux-keyring
 
'''Replace yyyymmdd and x with the info found at the above links'''
 
sudo pacman -U https://mirror.netzspielplatz.de/manjaro/packages/pool/overlay/manjaro-keyring-yyyymmdd-x-any.pkg.tar.xz
sudo pacman -U https://mirror.netzspielplatz.de/manjaro/packages/pool/sync/archlinux-keyring-yyyymmdd-x-any.pkg.tar.xz
 
'''Remove your faulty databases'''
sudo rm -f /var/lib/pacman/sync/*
'''Download the databases and update the system'''
'''Download the databases and update the system'''
sudo pacman -Syyu
{{UserCmd|command=sudo pacman -Syu}}


== "Unable to lock database" Error ==
== "Unable to lock database" Error == <!--T:14-->


<!--T:15-->
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:
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:


<!--T:16-->
* Another installation is still taking place and has not yet finished, or
* 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)
* A previous installation attempt had not finished properly (e.g. due to being aborted early)


<!--T:17-->
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:
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:
{{UserCmd|command=sudo rm /var/lib/pacman/db.lck}}


sudo rm /var/lib/pacman/db.lck
<!--T:19-->
 
Once done, you should now be able to successfully re-attempt your intended installation.
Once done, you should now be able to successfully re-attempt your intended installation.


== Errors about Keys == <!--T:20-->


== Errors about Keys ==
<!--T:21-->
 
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.  
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.  


<!--T:22-->
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:
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:


<!--T:23-->
* one or more signature keys contained in your system's database being revoked, changed, corrupted, or out of date  
* 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
* one or more software packages not having been signed off properly when placed in a repository


<!--T:24-->
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:
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:


<!--T:25-->
{{Warning|The following commands only work, when your system time is set correctly! }}
{{Warning|The following commands only work, when your system time is set correctly! }}


'''1. Remove old (and possibly broken) keys''' by entering this command:
<!--T:100-->
{{BoxInfo|Info|Retrieving the latest keyring packages can be done by browsing a current mirrors pool folder. E.g. from '''https://mirror.easyname.at/manjaro/pool''' - using the '''overlay''' for Manjaro keyring and '''sync''' for Arch keyring and downloading them to your system. Do not download '''.sig''' files.}}
sudo rm -r /etc/pacman.d/gnupg


'''2. Reinstall keyrings including the latest keys''':
<!--T:101-->
{{BoxInfo|Info|Those running ARM can find the '''archlinuxarm-keyring''' and '''manjaro-arm-keyring''' in the '''sync-arm''' and '''overlay-arm''' folders respectively.}}


sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring
<!--T:102-->
'''Download the new keyring packages'''
Before you download ensure no keyring packages is in the current folder.
{{UserCmd|command=rm manjaro-keyring* archlinux-keyring*}}


'''3. Initialize the pacman keyring''':
<!--T:103-->
Use either your browser or curl to download. Using curl assumes you know the correct package name as located with the mirror. Replace '''YYYYMMDD-R''' as available from the mirror.


sudo pacman-key --init
<!--T:104-->
{{UserCmd|command=curl -O <nowiki>https://mirror.easyname.at/manjaro/pool/overlay/manjaro-keyring-YYYYMMDD-R-any.pkg.tar.zst</nowiki>}}
{{UserCmd|command=curl -O <nowiki>https://mirror.easyname.at/manjaro/pool/sync/archlinux-keyring-YYYYMMDD-R-any.pkg.tar.zst</nowiki>}}


'''4. Load the signature keys''':
<!--T:105-->
'''Remove the dysfunctional keyrings''' by entering this command:
{{UserCmd|command=sudo rm -r /etc/pacman.d/gnupg}}


sudo pacman-key --populate archlinux manjaro
<!--T:106-->
'''Initialize the pacman keyring''':
{{UserCmd|command=sudo pacman-key --init}}


'''5. Refresh and update the signature keys''':
<!--T:107-->
'''Install the downloaded packages'''
Assuming the files is the current folder and using wildcard so you don't have to deal with dates and versions - remove the packages after successful installation
{{UserCmd|command=sudo pacman -U manjaro-keyring*.pkg.tar.zst archlinux-keyring*.pkg.tar.zst}}


sudo pacman-key --refresh-keys
<!--T:108-->
 
'''Populate the keyrings''' - (optional as the install process will do that)
'''6. Clear out the software packages downloaded during the aborted installation''' (optional):
{{UserCmd|command=sudo pacman-key --populate manjaro archlinux}}
 
sudo pacman -Sc
 
{{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.}}


<!--T:109-->
'''Clear out the software packages downloaded during the aborted installation''' (optional):
{{warning|The 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.}}
{{UserCmd|command=sudo pacman -Sc}}


<!--T:110-->
After that try running '''sudo pacman -Syu''' to see if the errors were resolved.
After that try running '''sudo pacman -Syu''' to see if the errors were resolved.


== Conflicting files - ''FILENAME'' exists in filesystem == <!--T:39-->


== Conflicting files - ''FILENAME'' exists in filesystem ==
<!--T:40-->
 
'''If you cant can't install or update a package because of an error like this:'''
'''If you cant can't install or update a package because of an error like this:'''


<!--T:41-->
  error: could not prepare transaction
  error: could not prepare transaction
  error: failed to commit transaction (conflicting files)
  error: failed to commit transaction (conflicting files)
Line 106: Line 121:
  Errors occurred, no packages were upgraded.
  Errors occurred, no packages were upgraded.


<!--T:42-->
Then the package manager, pacman, has detected an unexpected file that already exists on the disk.
Then the package manager, pacman, has detected an unexpected file that already exists on the disk.


<!--T:43-->
'''Why is this happening?'''
'''Why is this happening?'''


<!--T:44-->
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.
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.


<!--T:45-->
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.
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.


<!--T:46-->
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.
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.


<!--T:47-->
'''How can I fix this?'''
'''How can I fix this?'''


<!--T:48-->
The first step is to identify which, if any, package owns the file. This can be easily done with:
The first step is to identify which, if any, package owns the file. This can be easily done with:


pacman -Qo /path/to/file
<!--T:49-->
{{UserCmd|command=pacman -Qo /path/to/file}}


<!--T:50-->
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).
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).


<!--T:51-->
'''Where can I read more?'''
'''Where can I read more?'''


<!--T:52-->
This post was inspired by (and adapted from):
This post was inspired by (and adapted from):


https://bbs.archlinux.org/viewtopic.php?id=56373143
<!--T:53-->
https://wiki.archlinux.org/title/Pacman#%22Failed_to_commit_transaction_(conflicting_files)%22_error


<!--T:54-->
The above post also has links to further reading.
The above post also has links to further reading.


== "Configuration file...not recognized" Error ==
== "Configuration file...not recognized" Error == <!--T:55-->


<!--T:56-->
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:
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:


<!--T:57-->
* Installing Manjaro and editing the mirrorlist file during installation, or
* Installing Manjaro and editing the mirrorlist file during installation, or
* Editing the mirrorlist file at a later time.
* Editing the mirrorlist file at a later time.


<!--T:58-->
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.
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.




== "GPGME error: No data" Error ==
== "GPGME error: No data" Error == <!--T:59-->


<!--T:111-->
{{Warning|This section duplicates information from [[Pacman_troubleshooting#Errors_about_Keys]] consider removing duplicated information}}
<!--T:60-->
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.
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.




=== Option 1: Basic Resolution ===
=== Option 1: Basic Resolution === <!--T:61-->


<!--T:62-->
To resolve this issue, first follow the basic procedure provided below. If this does not work, then there is a more comprehensive procedure available.
To resolve this issue, first follow the basic procedure provided below. If this does not work, then there is a more comprehensive procedure available.




<!--T:63-->
1. Download the package databases and update your system:
1. Download the package databases and update your system:


  sudo pacman -Syyu
  <!--T:64-->
{{UserCmd|command=sudo pacman -Syu}}


<!--T:65-->
2. Clear out the software packages downloaded during the aborted installation by entering the command:  
2. Clear out the software packages downloaded during the aborted installation by entering the command:  


  sudo pacman -Sc
  <!--T:66-->
{{UserCmd|command=sudo pacman -Sc}}


<!--T:67-->
3. Re-attempt the aborted download.
3. Re-attempt the aborted download.


=== Option 2: Comprehensive Resolution ===
=== Option 2: Comprehensive Resolution === <!--T:68-->


<!--T:69-->
If the basic proceedure still does not resolve the matter, further steps are available:
If the basic proceedure still does not resolve the matter, further steps are available:


 
<!--T:96-->
1. Resynchronise with the Manjaro servers to ensure that everything is up to date by entering the command:
1. Resynchronise with the Manjaro servers to ensure that everything is up to date by entering the command:
{{UserCmd|command=sudo pacman -Sy}}


sudo pacman -Syy
<!--T:72-->
 
2. Refresh and update the signature keys by entering the command:
2. Refresh and update the signature keys by entering the command:
{{UserCmd|command=sudo pacman-key --refresh-keys}}


sudo pacman-key --refresh-keys
<!--T:74-->
 
3. Reload the signature keys by entering the command:
3. Reload the signature keys by entering the command:
{{UserCmd|command=sudo pacman-key --populate archlinux manjaro}}


sudo pacman-key --populate archlinux manjaro
<!--T:76-->
 
4. Clear out the software packages downloaded during the aborted installation by entering the command:  
4. Clear out the software packages downloaded during the aborted installation by entering the command:  
{{UserCmd|command=sudo pacman -Sc}}


sudo pacman -Sc
<!--T:78-->
 
5. Re-attempt the aborted download.
5. Re-attempt the aborted download.


<!--T:79-->
If the error still persists, then it is recommended to '''[[Change to a Different Download Server|Change to a Different Download Server]]'''.


If the error still persists, then it is recommended to '''[[Change to a Different Download Server]]'''.
== "keyserver refresh failed: No dirmngr" Error == <!--T:80-->
 
 
== "keyserver refresh failed: No dirmngr" Error ==


<!--T:81-->
Try running the following command:
Try running the following command:
{{UserCmd|command=sudo dirmngr <nowiki></dev/null</nowiki>}}


sudo dirmngr </dev/null
= See Also = <!--T:83-->
 
 
= See Also =


* '''[[Change to a Different Download Server]]'''
<!--T:84-->
* '''[[Change to a Different Download Server|Change to a Different Download Server]]'''
* '''[[Pacman-mirrors|Reference Guide for pacman-mirrors]]'''
* '''[[Pacman-mirrors|Reference Guide for pacman-mirrors]]'''
* '''[https://wiki.archlinux.org/index.php/Pacman#Troubleshooting Arch wiki for more comprehensive troubleshooting]'''
* '''[https://wiki.archlinux.org/index.php/Pacman#Troubleshooting Arch wiki for more comprehensive troubleshooting]'''
</translate>
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Contents Page{{#translation:}}]]

Latest revision as of 04:27, 15 July 2024

Other languages:
English • ‎Türkçe • ‎español • ‎français • ‎русский • ‎中文（中国大陆）‎

Software Installation

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 

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/community.db: Unrecognized archive format
error: could not open file /var/lib/pacman/sync/multilib.db: Unrecognized archive format

The error relates to content of the db files. The error happens when pacman receives markup from the mirror instead of the database archives.

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.

Run pacman-mirrors to refresh your mirrorlist

user $ sudo pacman-mirrors -c Global COPY TO CLIPBOARD


Download the databases and update the system

user $ sudo pacman -Syu COPY TO CLIPBOARD


"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:

user $ sudo rm /var/lib/pacman/db.lck COPY TO CLIPBOARD


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

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:


Warning
The following commands only work, when your system time is set correctly!


Info
Retrieving the latest keyring packages can be done by browsing a current mirrors pool folder. E.g. from https://mirror.easyname.at/manjaro/pool - using the overlay for Manjaro keyring and sync for Arch keyring and downloading them to your system. Do not download .sig files.


Info
Those running ARM can find the archlinuxarm-keyring and manjaro-arm-keyring in the sync-arm and overlay-arm folders respectively.

Download the new keyring packages Before you download ensure no keyring packages is in the current folder.

user $ rm manjaro-keyring* archlinux-keyring* COPY TO CLIPBOARD


Use either your browser or curl to download. Using curl assumes you know the correct package name as located with the mirror. Replace YYYYMMDD-R as available from the mirror.

user $ curl -O https://mirror.easyname.at/manjaro/pool/overlay/manjaro-keyring-YYYYMMDD-R-any.pkg.tar.zst COPY TO CLIPBOARD


user $ curl -O https://mirror.easyname.at/manjaro/pool/sync/archlinux-keyring-YYYYMMDD-R-any.pkg.tar.zst COPY TO CLIPBOARD


Remove the dysfunctional keyrings by entering this command:

user $ sudo rm -r /etc/pacman.d/gnupg COPY TO CLIPBOARD


Initialize the pacman keyring:

user $ sudo pacman-key --init COPY TO CLIPBOARD


Install the downloaded packages Assuming the files is the current folder and using wildcard so you don't have to deal with dates and versions - remove the packages after successful installation

user $ sudo pacman -U manjaro-keyring*.pkg.tar.zst archlinux-keyring*.pkg.tar.zst COPY TO CLIPBOARD


Populate the keyrings - (optional as the install process will do that)

user $ sudo pacman-key --populate manjaro archlinux COPY TO CLIPBOARD


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

Warning
The 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.
user $ sudo pacman -Sc COPY TO CLIPBOARD


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

Conflicting files - FILENAME exists in filesystem

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

error: could not prepare transaction
error: failed to commit transaction (conflicting files)
libname: /insert/file/name/here exists in filesystem
Errors occurred, no packages were upgraded.

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:

user $ pacman -Qo /path/to/file COPY TO CLIPBOARD


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):

https://wiki.archlinux.org/title/Pacman#%22Failed_to_commit_transaction_(conflicting_files)%22_error

The above post also has links to further reading.

"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.


"GPGME error: No data" Error

Warning
This section duplicates information from Pacman_troubleshooting#Errors_about_Keys consider removing duplicated information

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.


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:

user $ sudo pacman -Syu COPY TO CLIPBOARD


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

user $ sudo pacman -Sc COPY TO CLIPBOARD


3. Re-attempt the aborted download.

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:

user $ sudo pacman -Sy COPY TO CLIPBOARD


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

user $ sudo pacman-key --refresh-keys COPY TO CLIPBOARD


3. Reload the signature keys by entering the command:

user $ sudo pacman-key --populate archlinux manjaro COPY TO CLIPBOARD


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

user $ sudo pacman -Sc COPY TO CLIPBOARD


5. Re-attempt the aborted download.

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

"keyserver refresh failed: No dirmngr" Error

Try running the following command:

user $ sudo dirmngr </dev/null COPY TO CLIPBOARD


See Also

Retrieved from "https://wiki.manjaro.org/index.php?title=Pacman_troubleshooting&oldid=52515"
Cookies help us deliver our services. By using our services, you agree to our use of cookies.