You are not logged in.
Hi, I am new here but use MX Linux for a while. I struggled several hours today trying to install arch linux on virtualbox and failed.
I followed installation guide until I ran :
pacstrap /mnt base linux linux-firm
The errors I got are:
error: pam: signature from "Evanglelos Foutras <evangelos@foutrelis.com>" is invalid
:: File /mnt/var/cache/pacman/pkg/pam-1.3.1-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature))
Do you want to delete it? [Y/n]
...
(many similiar errors here)
...
errror: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded
==> ERROR: Failed to install packages to new root
Thank you for your help
Jjcpa
Last edited by Jjcpa (2020-03-24 21:16:31)
Offline
You either followed the installation guide, or that video. I gather the latter. That is not supported here.
Further if you want help here, describe your problem here. Don't link out to where you've cross posted expecting us to dig through some other website to find your problem. And when you post here, chose a thread title that says something ... anything. (edit: 1 out of 3 covered now).
Last edited by Trilby (2020-03-21 12:31:36)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I was just helping someone on IRC with this issue. All 3 of you are in VirtualBox. We tracked it back as far as we could, and gpgme is inexplicably returning a bad sig result, almost has to be a bad calculation related to the virtual machine.
Offline
It happened to me on real hardware during my last install.# pacman -S archlinux-keyring fixed it.
Last edited by 10PinkPanther (2020-03-21 04:35:16)
Offline
Thank you for your quick response. The errors are on screen which I cannot copy to here and I did not find a way to attach an image.
I just typed one of them as following. All the others are similar but different packages:
error: pam: signature from "Evanglelos Foutras <evangelos@foutrelis.com>" is invalid
:: File /mnt/var/cache/pacman/pkg/pam-1.3.1-2-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature))
Do you want to delete it? [Y/n]
...
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded
==> ERROR: Failed to install packages to new root
Offline
It happened to me on real hardware during my last install.# pacman -S archlinux-keyring fixed it.
Thanks, I tried this but no luck.
Offline
Fix your thread title: the current one is useless: https://wiki.archlinux.org/index.php/Co … ow_to_post
Offline
It happened to me on real hardware during my last install.# pacman -S archlinux-keyring fixed it.
If that fixed it, it's not the same issue. This is where some packages will verify and some won't with the same key.
Edit: for completion, log: http://ix.io/2eNt
and debug: http://ix.io/2eNZ
Notice how linux-api-headers verifies but glibc doesn't, both with the same key. We verified the checksum they had matches my local cache, so it's extremely unlikely that it's corruption.
Last edited by Scimmia (2020-03-21 05:53:44)
Offline
As others have requested, please edit your first post to set a descriptive thread title (e.g. PGP errors when installing on Virtualbox) and clarify the steps that you've followed while attempting to install. As noted, only the steps in the official guide on the wiki are supported. If you have followed some other guide then you will need to address the author of that guide for assistance.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
Warning: pacman-key depends on system time. If your system clock is wrong, you'll get:
error: PackageName: signature from "User <email@archlinux.org>" is invalid
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occured, no packages were upgraded.
Offline
Again, day4me, same key works for some packages but not others.
Offline
Warning: pacman-key depends on system time. If your system clock is wrong, you'll get:
error: PackageName: signature from "User <email@archlinux.org>" is invalid
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occured, no packages were upgraded.
I adjusted system time base on installation guide.
Thanks,
Offline
I don't think it *should* matter with signature verification, only for key initialization, but it's worth a shot: try to get 'haveged' running - if you can get it installed before you pacstrap, of course. VM guests have notoriously low entropy, maybe it's related?
Offline
haveged is running by default on the ISO
Offline
haveged is running by default on the ISO
thanks, tried this and it does not work
Offline
You didn't mention your OS. I assume you were on windows 10 and using virtualbox v6.1, also you had Hyper-V feature enabled.
If the assumption is correct, then the issue was related to Hyper-V. Virtualbox seems performing as "normal" when you have Hyper-V enabled. However, you would find some issues like above.
You may try to disable Hyper-V properly on windows (uninstall this feature).
Hope this helps and to get this issue resolved.
Last edited by oncee (2020-04-23 00:12:16)
Offline
You didn't mention your OS. I assume you were on windows 10 and using virtualbox v6.1, also you had Hyper-V feature enabled.
If the assumption is correct, then the issue was related to Hyper-V. Virtualbox seems performing as "normal" when you have Hyper-V enabled. However, you would find some issues like above.
You may try to disable Hyper-V properly on windows (uninstall this feature).
Hope this helps and to get this issue resolved.
The above are all true. I mostly gave up and turned to Debian 10. I may give a shot later on Windows 7.
Thanks a lot,
Offline
You didn't mention your OS. I assume you were on windows 10 and using virtualbox v6.1, also you had Hyper-V feature enabled.
If the assumption is correct, then the issue was related to Hyper-V. Virtualbox seems performing as "normal" when you have Hyper-V enabled. However, you would find some issues like above.
You may try to disable Hyper-V properly on windows (uninstall this feature).
Hope this helps and to get this issue resolved.
Hi oncee, yes it is working on windows 7/virtualbox. Thank you so much, I can start to build my system.
Offline
oncee wrote:You didn't mention your OS. I assume you were on windows 10 and using virtualbox v6.1, also you had Hyper-V feature enabled.
If the assumption is correct, then the issue was related to Hyper-V. Virtualbox seems performing as "normal" when you have Hyper-V enabled. However, you would find some issues like above.
You may try to disable Hyper-V properly on windows (uninstall this feature).
Hope this helps and to get this issue resolved.Hi oncee, yes it is working on windows 7/virtualbox. Thank you so much, I can start to build my system.
No worries! Glad to hear you've got things sorted out!
Offline
I am using Windows 10 + Virtual Box where I am facing the same issue with pgp sigs.
Is there a solution for this issue yet ?
Offline
Same issue
Offline
I encountered the same issue today on Win 10 Pro amd64 Build 19041, VirtualBox Version 6.1.12 r139181 (Qt5.6.2) with Arch 64-bit guest (no EFI), Arch ISO 2020.08.01 x86_64. Hyper-V is *not* enabled.
Confirmed the guest clock is accurate. In sync with the system clock and the real world at UTC.
Checking keys in keyring succeeds, checking package integrity fails as described by others here as
...invalid or corrupted package (PGP signature)
Confirmed haveged is running already by default.
I installed QEMU for Windows on the same system to troubleshoot and found everything worked. No issues there. I'm also able to enable and use Hyper-V to install Arch with their hypervisor.
I went back and explicitly disabled acceleration (on by default) for the VirtualBox VM, but that still failed on the PGP signing. Seems like there's something specific to VirtualBox preventing PGP validation from working properly. At least, that's my experience.
Offline
Hyper-V is *not* enabled.
And how exactly are you disabling it? We're not talking about guest paravirtualization.
Offline
I am sorry. I should be more explicit and I did not mean to cause any confusion. CPU Virtualization is enabled in BIOS settings. The Windows Hyper-V features (management tools, Hyper-V Hypervisor, Hyper-V Services) are all disabled in the Windows Features interface.
Offline
For some context, I found this post after following a couple reddit posts and some broad Googling.
On a random suggestion, I downgraded VirtualBox to 6.0.x, but no joy. Then I found a separate distinct error.
WHvSetupPartition failed - VERR_NEM_VM_CREATE_FAILED
That led me to a similar kubernetes issue and a VirtualBox forum post.
Running this command in Windows with a reboot got Arch install/pacstrap/PGP to work properly for me with the latest VirtualBox.
bcdedit /set hypervisorlaunchtype off
Everything working for my situation now.
Last edited by glombus (2020-08-10 20:17:51)
Offline