The following signatures couldn't be verified because the public key is not available

The .deb packages signing gpg key got rotated?

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: beta InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AC2D62742012EA22
W: Failed to fetch  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AC2D62742012EA22

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided


  • Dayton_agDayton_ag

    Team Member

    Hey there @mrdoodiddle, I am really sorry you're running into this issue with 1Password! Let's get things working for you again.

    Is it possible you've been running 1Password for Linux since before it was released to stable? If so, you might need to update where to pull 1Password from - could you try running through the initial download steps, and let me know how it goes? I'll include links below with the relevant steps for both stable and beta channels:

    Download 1Password for Linux - Stable

    Download 1Password for Linux - Beta

    Thanks so much, I look forward to hearing if this gets you up and running again! :smile:

  • nprokopicnprokopic
    edited August 2021

    Hi @Dayton_ag, I have installed 1Password for Linux after it was released to stable, but I've hit the same issue like @mrdoodiddle wrote above.

    I'm running KDE Neon (based on Ubuntu 20.04):

    Distributor ID: Neon
    Description:    KDE neon User Edition 5.22
    Release:        20.04
    Codename:       focal

    Redoing steps from fixed the issue for me.

  • PeterG_1PPeterG_1P

    Team Member
    edited August 2021

    Hi @mrdoodiddle, thanks for letting us know about this.

    We've checked in with some of our server and development folks about this, and it turns out there was a change in how we host the public key. This has apparently caused an issue for a small number of customers. The good news is this issue shouldn't come up any more going forward.

    To fix the immediate problem, as @nprokopic helpfully mentioned, try redoing the installation steps at

    If that doesn't work for you, let us know and we'll help you sort it out. And thank you again for bringing this to our attention!

  • edited August 2021

    Yes I re-installed the public key, which allowed me to update and of course I failed to update my post here.

    Replacing the signing key surprised me, as blindly using a new key without any information is not good in my humble opinion.

    Is there a notification somewhere that the key got changed (maybe I missed it) ?

  • BenBen AWS Team

    Team Member

    Hi @mrdoodiddle

    My understanding is that the key itself did not change, only where it is hosted. Are you seeing indications otherwise?


  • Nah, it's been a while now I don't have the old repo config anymore, I am all set.

    Regardless im just saying that a repo change or sign key change is important for me, so having it in a release notes would have been a nice notice :).

  • BenBen AWS Team

    Team Member

    Got it. Thanks for sharing @mrdoodiddle. :)


  • I've hit this issue again, same workaround (redoing installation steps) helped.

  • PeterG_1PPeterG_1P

    Team Member

    Thanks for letting us know, @nprokopic. We'll keep an eye out for this issue!

  • The linux install steps to fix this did not work in zsh, I needed to use bash.

  • PeterG_1PPeterG_1P

    Team Member

    Thanks for this note, @doug_collier. We appreciate it!

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file