I’m a Linux noob. But I get suddenly when i try to download the updates the Fedora Software store is showing me, this fail,

package proton-vpn-gtk-app-4.7.4-1.fc41.noarch cannot be verified and repo protonvpn-fedora-stable is GPG enabled: /var/cache/PackageKit/41/metadata/protonvpn-fedora-stable-41-x86_64/packages/proton-vpn-gtk-app-4.7.4-1.fc41.noarch.rpm could not be verified. /var/cache/PackageKit/41/metadata/protonvpn-fedora-stable-41-x86_64/packages/proton-vpn-gtk-app-4.7.4-1.fc41.noarch.rpm: digest: SIGNATURE: NOT O.K.

  • UndulyUnruly@lemmy.world
    4·
    1 day ago

    https://protonvpn.com/support/official-linux-vpn-fedora/

    Following this guide, an error will occur re the pgp during the install, it did for me. Make sure you run *both after the cli commands

    sudo dnf check-update && sudo dnf upgrade

    and

    sudo dnf install --refresh proton-vpn-gnome-desktop

    You must accept the keys as outlined or it fails down the road. It never asked until running above code.

    That did it for me. Good luck.

  • §ɦṛɛɗɗịɛ ßịⱺ𝔩ⱺɠịᵴŧ@lemmy.mlEnglish
    5·
    2 days ago

    I’m pretty sure just using the “sudo dnf update --refresh” command in terminal will fix this problem. It will ask you verify those packages new repositories. After that, you should be good using the store again for updates. This is assuming you upgraded from Fedora 40 before these errors occurred.

  • stuner@lemmy.world
    4·
    2 days ago

    It sounds like Proton VPN (or its repo) is causing issues for you. Given that it’s a paid service, you can probably contact their support.

    Alternatively, you can also look for the repo file in /etc/yum.repos.d, something like /etc/yum.repos.d/file_name.repo, for Proton VPN. You can then disable it by renaming it to .repo.disabled and try again (sudo dnf upgrade in the terminal). Note: This is not really a permanent solution, as it will disable updates for Proton VPN.

    • somethingsomethingidk@lemmy.world
      2·
      2 days ago

      A lot of times you will see the format string for the fedora version in the .repo file. This means its probably looking for f41. Since fedora updates fast, third party repos are usually slow to move to the next version and this repo probably doesnt exist causing dnf to fail. You can try and change the format string to the last available version. It usually works without issue, and updates aren’t disabled as long as the vendor updates that version

  • lancalot@discuss.onlineEnglish
    2·
    2 days ago

    I had something similar going on in Fedora Silverblue. I didn’t really want to fiddle with it at the moment, so I just uninstalled whatever I got from ProtonVPN and the update went smooth afterwards. I hope someone else can point you towards a better answer.

  • eldavi@lemmy.ml
    1·
    2 days ago

    did you download & try to install it or is it coming from your package manager?

    • with chicken@lemmy.mlOP
      1·
      2 days ago

      I have downloaded it with terminal for some months ago. Its just now when I want to download the updates the software store in Fedora shows me,that the issue is coming.