Project

General

Profile

error: key "6D42BDD116E0068F" could not be looked up remotely

mrycy - 9 months ago -

I attached the error message as a txt file.

recieved while trying to do 'pacman -Syu'

log.txt (499 Bytes) log.txt

Replies (12)

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - mrycy - 9 months ago -

I tried running:

< file attached >

but neither had fixed the issue.

log2.txt (194 Bytes) log2.txt
log2.txt (4.73 KB) log2.txt

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - telur - 9 months ago -

hello, there is many thread about this keyring error in parabola forum and bugtracker. you can go to parabola forum menu and do a search for this topics from there.

if you dont find any working solution, that means the keyring is not yet updated by the developer. until they fixed it, the fastest unrecommended way is to disable the package integrity check.

open your terminal

$ sudo nano /etc/pacman.conf

find siglevel line and change it into never

SigLevel = Never

as long you used official parabola repos you are probably fine.

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - nona - 9 months ago -

telur wrote:

$ sudo nano /etc/pacman.conf

find siglevel line and change it into never

SigLevel = Never

as long you used official parabola repos you are probably fine.

Please, avoid this. I'm not completely sure, but I think that a live USB, live DVD or similar approaches can be used to manage key-ring issues.

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - mrycy - 9 months ago -

Please, avoid this. I'm not completely sure, but I think that a live USB, live DVD or similar approaches can be used to manage key-ring issues.

I'd love to try and use a more secure method, however what would I do with a LiveUSB to fix the issue?

hello, there is many thread about this keyring error in parabola forum and bugtracker. you can go to parabola forum menu and do a search for this topics from there.

I did make an attempt at this, I have not seen any similar forum posts but if there is one please link it over and I'll switch to it.

As for issue trackers, I have tried 'pacman -Sy parabola-keyring' but recieve the same error after installation.

- Thanks

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - mrycy - 9 months ago -

Hey, the forum doesn't let me upload commands so I've put most of this message in the log file.

I attempted to populate and redownload the keys, still hasn't fixed the issue but got these:
< attached via log >

- Thanks

log3.txt (80.4 KB) log3.txt

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - nona - 9 months ago -

mrycy wrote:

Hey, the forum doesn't let me upload commands so I've put most of this message in the log file.

How did you try to upload commands? How did you get this log file? I am infamous for being able to unwillingly break many systems, and I am able to post code, as you will see :) .

I attempted to populate and redownload the keys, still hasn't fixed the issue but got these:
< attached via log >

- Thanks

Disregarding what you have tried, it seems that you don't have Parabola's keyring.

This is what I would try (I have not tried it myself, and I don't know if it will work; I'm just trying to help):
  1. Boot the LXDE live ISO without graphical install
  2. Open a terminal by (using your keyboard: [ALT] + [F2], then type lxterminal)
  3. Type
    ./install.sh
    
  4. Follow the instructions in the install.sh script, but don't do it all the way. This is NOT the graphical (Calamares) install.
  5. Follow the instructions up to the mounting point (if you like graphical environments, you will probably prefer to use the gparted option when it shows up).
    • If you have an encrypted drive or need to do LVM mounts, just do that first
    • By now, your drive should be mounted, and the live system should have a fresh keyring.
  6. Open a new terminal in the same way (or a new tab), and run
    1. arch-chroot /mnt rm -r /etc/pacman.d/gnupg. Remove old (and possibly broken) keys
    2. pacstrap -c /mnt gnupg parabola-keyring archlinux-keyring. This command will use the cache from the live system to install those packages.
    3. arch-chroot /mnt pacman-key --init. Initialize the key-ring
    4. arch-chroot /mnt pacman-key --populate archlinux parabola. Populate the key-ring

Did you try this: Pacman troubleshooting ?

Good luck. Remember: we are users who are trying to help. Be patient with us.

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - telur - 9 months ago -

hi, im forgot to tell if you doesnt come across the wiki yet, there is a tutorial for this issue

https://wiki.parabola.nu/Parabola_Keyring

it is a bit outdated but worth to try

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - doyle - 9 months ago -

I'm having the same issue. I've tried absolutely everything listed in the forums and the wiki, including checking accurate system time, refreshing keyrings, etc. This leads me to conclude that the problem is with the keyring.

file-1 (1.65 KB) file-1 showing an attempt to update keyrings

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - nona - 9 months ago -

Thanks for sending a log with the error and the command that you used.

It seems that you are trying to install the key-rings for the ARM, i386 and the x86-64 architectures. I doubt that you need all of them, and I would assume that the ARM package is faulty.

  1. Do you need all of them?
  2. Can you try installing one by one? (in fact, if you avoid those which you don't need, that would be better to solve your situation)

Good luck. Remember that I am just a user who is trying to help.

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - telur - 9 months ago -

Hi doyle i confirm that today i can refreshing the parabola-keyring and archlinux keyring sucessfully and can install/upgrade package normally.

im not pro but here is some of my though for everyone:
1.maybe the problem lies in wrong configuration or database ?
2.maybe something wrong with latest parabola installer ? i used the old parabola installer back then
3.maybe the keyring pkg is outdated ? im enabled testing repositories
4.maybe wait? sometimes im had this issue and sometimes dont between an upgrade (ussually temporary bypassing them when occured)

log attached.

edit
here is my method in order

$ sudo rm -r /etc/pacman.d/gnupg/*
$ sudo pacman-key --init
$ sudo pacman-key --populate parabola archlinux
$ sudo pacman-key --refresh-keys
$ sudo pacman -Sy parabola-keyring archlinux-keyring

log.txt (6.3 KB) log.txt
log2.txt (302 KB) log2.txt

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - doyle - 8 months ago -

Do you need all of them?

Can you try installing one by one?

You were right; I didn't need all of them. Although I tried installing one by one, and that didn't work for me either.

here is my method in order

I'm glad it worked for you. I tried the same sequence with no success. Sadly I've given up on Parabola for now, because I only have one machine and I need it to operate. I hope to return some day soon.

Thanks for the helpful responses.

RE: error: key "6D42BDD116E0068F" could not be looked up remotely - nona - 8 months ago -

doyle wrote:

You were right; I didn't need all of them. Although I tried installing one by one, and that didn't work for me either.

The idea was to check the error that you would get to help you further. By the way, the wiki has been updated https://wiki.parabola.nu/Parabola_Keyring https://wiki.parabola.nu/Pacman_troubleshooting .

--- 8< snip --- Sadly I've given up on Parabola for now, because I only have one machine and I need it to operate. I hope to return some day soon.

I have been there. I really hope that you are able to come back some day (I did).

Thanks for the helpful responses.

Thank you for your patience.

    (1-12/12)