Manjaro Difference between revisions of "Translations:Pacman troubleshooting/17/en"

Difference between revisions of "Translations:Pacman troubleshooting/17/en"

From Manjaro
(Importing a new version from external source)
 
(Importing a new version from external source)
 
Line 1: Line 1:
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}}

Latest revision as of 09:25, 29 December 2022

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Pacman troubleshooting)
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}}

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


Cookies help us deliver our services. By using our services, you agree to our use of cookies.