Project

General

Profile

Keys Can't Be Looked Up Remotely

PublicLewdness - over 3 years ago -

I tried to install some packages or do updates but right now neither are possible. Any time I try I get an error saying "Key Can't Be Looked Up Remotely". The key it states changes from task to task but the rest is the same. I have attached a screenshot of the error as well as a text file of the copied text. I have tried doing the system update through Octopi as well as the terminal but the issue happens each time. I also got the error when trying

"pacman -Syy archlinux-keyring archlinuxarm-keyring parabola-keyring"

I am using the Systemd version of Parabola. Any help would be appreciated.

System Specs:

Intel G3220 | Intel HD Graphics | 16GB DDR3-1333 | Mushkin 120GB SSD | Kernel 5.1.6-gnu-1

octopi error.png (277 KB) octopi error.png Octopi Error
octopi error.txt (951 Bytes) octopi error.txt Octopi Text

Replies (10)

Keys Can't Be Looked Up Remotely - bill-auger - over 3 years ago -

it is most useful to show both the command and the error
message - i think the problem is known though

it is a problem with sks-keyservers.net - try this command:

  1. pacman-key --keyserver hkp://pool.sks-keyservers.net --refresh-keys

RE: Keys Can't Be Looked Up Remotely - PublicLewdness - over 3 years ago -

I tried that command. I attached a text file showing the response. Sadly it didn't solve the issue as when I tried to install Mate through Octopi I got the same message. I'm installing Mate through Octopi so I don't know if it shows the command that way. I think one of the possible issues is that the command you gave me tries to refresh 144 keys but the one that is giving the error (3B94A80E50A477C7) doesn't appear to be on the list of 144. At least when I do a Find for it in Abiword and Pluma they can't find any mention of it.

144 Keys.txt (26.2 KB) 144 Keys.txt Output of refresh keys

RE: Keys Can't Be Looked Up Remotely - bill-auger - over 3 years ago -

that text file does not indicate a failure or error message

have you tried to install mate, or any of the troublesome packages using pacman on the command line?

$ sudo pacman-key --populate fredRE: Keys Can't Be Looked Up Remotely - PublicLewdness - over 3 years ago -

So i tried a few other programs and used the command line to do so. Some, such as Plank; KeepassXC and Cool Retro term worked. Others such as Mate; system upgrade and Nextcloud did not. I've attached commands and results.

upgrade error.txt (164 KB) upgrade error.txt Upgrade Attempt
mate error.txt (1.54 KB) mate error.txt Mate Install
nextcloud error.txt (735 Bytes) nextcloud error.txt Nextcloud Error

RE: Keys Can't Be Looked Up Remotely - bill-auger - over 3 years ago -

the most curious bit is: "downloading required keys..." - you should have those keys already - try these commands:

# pacman-key --populate archlinux
# pacman -Sy archlinux-keyring

or in the opposite order:
# pacman -Sy archlinux-keyring
# pacman-key --populate archlinux

if that does not work, you could try the procedure in section 2 of this article:

https://wiki.parabola.nu/Parabola_Keyring

RE: Keys Can't Be Looked Up Remotely - PublicLewdness - over 3 years ago -

So I tried both and had a few issues. With the commands given on this page it didn't recognize the -S archlinux command. With the commands in section 2 a few of them had errors. I attached the outputs. I will try section 3 with the Live ISO later once i'm done work unless you think there's a better option to try.

populate archlinux.txt (2.69 KB) populate archlinux.txt populate archlinux issue
Section 2.txt (13.6 KB) Section 2.txt Section 2 issues

RE: Keys Can't Be Looked Up Remotely - bill-auger - over 3 years ago -

could you click "reply" at the bottom of the page instead of the "quote" button;
unless you intend to edit/minimize to specific bits from the quote
a complete quote from the previous is noise

perhaps some web-foo could add a more obvious "reply" beside "quote" - that could be a feature request on the bug tracker

RE: Keys Can't Be Looked Up Remotely - PublicLewdness - over 3 years ago -

So typing it correctly at least gave me a response this time but it tells me the keyring doesn't exist. So I tried to install it but it said it was already installed and just reinstalled it. I've atatched the log.

keyring doesn_t exist.txt (3.87 KB) keyring doesn_t exist.txt Doesn't exist but is already installed ?

RE: Keys Can't Be Looked Up Remotely - bill-auger - over 3 years ago -

my typo was the in pacman command package name - the pacman-key command keyname was correct - i had the same pacman-key command keyname as the pacman package name - they are different - i have corrected my previous post

RE: Keys Can't Be Looked Up Remotely - bill-auger - over 3 years ago -

if at any time, the `pacman` or `pacman-key` commands give an error message, that is usually a high-priority bug, with an associated bug report of high-quality, ASAP

regarding bug reports in general, for any project:

the first step of any bug report is to confirm reproducibility - then it would be escalated to a TODO work item on the bug tracker

the best description of a most problems, includes the exact commands typed, the exact error message lines, and/or the complete command outputs, in attachments if some commands are verbose (eg: longer than a few lines)

an excellent bug report looks something like:

steps to reproduce:
  1) # pacman --debug -Syyuu base your-initfreedom
  2) # pacman -S foo-openrc
  3) $ foo --print hello

expected result:
  i expected foo to print hello

actual result:
  it prints "ERROR: invalid argument" 

for parabola specifically, it is also helpful to specify the CPU architecture and init-system

the commands and outputs copy-paste texts alone, with no additional suggestion, example, or commentary (quoted or not), are usually sufficient information to confirm the bug - then other parabola users (regardlesss of their language) can try reproducing the same bug, and/or confirm the ticket, and/or offer a bug fix

if the bug is reproducible, it can be fixed; otherwise a fix is much less likely

    (1-10/10)