Error in Pop!_Shop

[person123456789]

W: https://dl.winehq.org/wine-builds/ubuntu/dists/impish/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.protonvpn.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 71EB474019940E11
E: https://repo.protonvpn.com/debian stable InRelease is not (yet) available (The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 71EB474019940E11)

 

When I opened Pop!_Shop I got the above error message. Please help me.

[Bombastinator]

1 hour ago, person123456789 said:

W: https://dl.winehq.org/wine-builds/ubuntu/dists/impish/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.protonvpn.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 71EB474019940E11
E: https://repo.protonvpn.com/debian stable InRelease is not (yet) available (The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 71EB474019940E11)

 

When I opened Pop!_Shop I got the above error message. Please help me.

Well if this organization isn’t updating their sigs it could just actually be what happened.  Doesn’t help that it’s the 4th.  Major Holliday in the USA

[person123456789]

?

[Bombastinator]

1 hour ago, person123456789 said:

?

Your computer seems to be saying that the signatures of the apps are not properly updated.  This could mean either that they are and it is your computer is messed up, or it is not messed up and the signatures are in fact out of date.  In the latter case there is little to do because it is the 4th of July which is a major holiday in the USA.  There probably isn’t anyone there to fix it.   You could turn signature requirements off, but it creates a major security hole.  It is preferable to simply wait till the 5th.  It is also possible that your machine is messed up.  If it was though signatures from basically everything would be bad though, and your internet would be more or less non-functional.

[C2dan88]

Looks like protonvpn has updated the gpg key and popOS cannot verify the key as it is now invalid.

 

This post

https://askubuntu.com/questions/1350266/problem-in-sudo-apt-update-with-proton-vpn

Suggests uninstalling protonvpn and downloading the update manually (ubuntu instructions should be the same as popos)

 

If that does not work then contact protonvpn support.

[Bombastinator]

3 hours ago, C2dan88 said:

Looks like protonvpn has updated the gpg key and popOS cannot verify the key as it is now invalid.

 

This post

https://askubuntu.com/questions/1350266/problem-in-sudo-apt-update-with-proton-vpn

Suggests uninstalling protonvpn and downloading the update manually (ubuntu instructions should be the same as popos)

 

If that does not work then contact protonvpn support.

I should have thought of that.  I don’t deal with vpns much.