Failed to read package header from file "zoom_x86_64.rpm" | Community
Skip to main content
Newcomer
אברהם צבאן
Newcomer
June 23, 2026
Solved

Failed to read package header from file "zoom_x86_64.rpm"

  • June 23, 2026
  • 2 replies
  • 118 views

once I try to install zoom from rpm on my current fedora (44) workstation, I get an error:

Failed to read package header from file "zoom_x86_64.rpm"

It is possible to workaround using commands such as 

sudo rpm -Uvh --nosignature --nodigest /(...path...)/zoom_7.1.0.3715_x86_64.rpm

but it looks like there is some problem with the packages. it first appeared on zoom 7.0.5 rpm (previous linux version).

Claude claims the problem may be related to rpm 6.0 installed on fedora, meaning zoom packages the zoom app using an obselete rpm protocol (rpm v3), I doubt it since it looks like rpm 6 has been around for a while - but problems appeard only last month.

thank you

    Best answer by levili

    Hi ​@אברהם צבאן ,
     

    Zoom recently updated the published OpenPGP certificate used by the Linux RPM repository. The previous certificate did not explicitly mark the primary key as signing-capable, causing newer versions of rpm-sequoia to reject repository metadata signatures with the invalid: not signing capable error.

    The updated certificate explicitly includes the required signing capability. The key fingerprint and download URL remain unchanged. Most systems automatically retrieved the update, but some DNF5 installations may continue using the previously cached certificate and require the repository-specific keyring to be refreshed.

    Please run the script below to clear the DNF cache and re‑import the key
     

    # 1. Remove the old imported Zoom RPM key (full fingerprint)
    sudo rpmkeys --delete 84c365d6cc9a4886ca926bcc4f2197399706ac24

    # 2. Clear the dnf5 repo-cached Zoom key (rpmkeys --delete is not enough)
    sudo rm -rf /var/cache/libdnf5/zoom-release-*

    # 3. Import the latest Zoom public key
    sudo rpmkeys --import https://zoom.us/linux/download/pubkey

    # 4. Refresh repos and confirm the signature verifies
    sudo dnf makecache --refresh

     

    2 replies

    Newcomer
    jdbarnes
    Newcomer
    September 1, 2026

    this can be fixed by deleting all old signing keys and installing the new signing key

      Employee
      leviliAnswer
      Employee
      September 7, 2026

      Hi ​@אברהם צבאן ,
       

      Zoom recently updated the published OpenPGP certificate used by the Linux RPM repository. The previous certificate did not explicitly mark the primary key as signing-capable, causing newer versions of rpm-sequoia to reject repository metadata signatures with the invalid: not signing capable error.

      The updated certificate explicitly includes the required signing capability. The key fingerprint and download URL remain unchanged. Most systems automatically retrieved the update, but some DNF5 installations may continue using the previously cached certificate and require the repository-specific keyring to be refreshed.

      Please run the script below to clear the DNF cache and re‑import the key
       

      # 1. Remove the old imported Zoom RPM key (full fingerprint)
      sudo rpmkeys --delete 84c365d6cc9a4886ca926bcc4f2197399706ac24

      # 2. Clear the dnf5 repo-cached Zoom key (rpmkeys --delete is not enough)
      sudo rm -rf /var/cache/libdnf5/zoom-release-*

      # 3. Import the latest Zoom public key
      sudo rpmkeys --import https://zoom.us/linux/download/pubkey

      # 4. Refresh repos and confirm the signature verifies
      sudo dnf makecache --refresh

       

        Terms & ConditionsAccessibility statement
        Copyright © Zoom Communications, Inc. All rights reserved.