Spotify and GnuPG logo in Linux terminal error

Solving Spotify Public Key Unknown Error

Running Spotify on Linux can be a challenge but it is possible and one such challenge is figuring out how to obtain the public key in order to install the Spotify client. Each package that is installed on a Linux system is verified using a public key to private key verification process. In this particular situation the public key is not found or unknown on the configured key server and therefore fails the verification process. To resolve this, the public key must be imported into the key database first before installing the Spotify client. Lets begin resolving this problem.

Environment

Tested using the following…

  • Arch Linux x86_64
  • Fish v3.3.1
  • GNU bash v5.1.12
  • Pikaur v1.8
  • Spotify v1.1.72.439

Assumptions

  • Steps prefixed with a “$” (dollar sign) represents the CLI (command-line interface) prompt
  • Steps prefixed with a “#” (number sign) represents the CLI prompt with elevated user permissions (e.g. root)
  • The text after the “$” or “#” is to be entered at the CLI
  • Understanding how to use an AUR helper (e.g. Pikaur)

Problem

Installation of the Spotify client fails with the following error message.

$ pikaur -Sy spotify
==> Verifying source file signatures with gpg...
    spotify-1.1.72.439-3-Release ... FAILED (unknown public key 5E3C45D7B312C643)
==> ERROR: One or more PGP signatures could not be verified!

Solution

Using curl the public key will be downloaded and then imported into the key database. Once this has completed successfully you will now be able to install the Spotify client.

$ curl -sS https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg | gpg --import -
# pikaur -Sy spotify

I’m publishing this as part of 100 Days To Offload. You can join in yourself by visiting 100DaysToOffload.com.

- modified
    • Fix link to https